Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest WME version: WME 1.9.1 (January 1st, 2010) - download

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bfg100

Pages: [1]
1
Technical forum / Re: Dynamic Shadow. I need help.
« on: April 07, 2012, 08:36:16 AM »
@Django
Now it works perfectly! Thanks for help.

2
Technical forum / Dynamic Shadow. I need help.
« on: April 06, 2012, 09:23:19 AM »
I would like to get the actor shadow like in the Alpha Polaris for instance, where the shadow changes its position relative to the light source.
I have something like that:
Code: [Select]
var lightpos, lightposX, lightposY,lightposZ;

lightpos = Scene.GetLightPosition("Lamp");

 lightposX = lightpos.X - this.PosX;
 lightposY = lightpos.Y;
 lightposZ = lightpos.Z - this.PosZ;

actor.SetLightPosition(lightposX, lightposY, lightposZ);

What else should I do? Maybe some loop?
Maybe someone could help me with this, please.

3
Bug reports / SceneEdit problem (blue screen)
« on: March 28, 2012, 02:30:57 PM »
Hi Mnemonic,
Maybe you could help me:) I have a problem with the SceneEdit, because all the time, when I start it up I have a blue screen and system reboot.
I established that this issue is connected with nv4_disp.dll file. My graphic card is GeForce 7650 GS and I use Windows XP.
The problem does not occur on the older graphics drivers (169.21). However I would like to use newer drivers, because my graphic card has a much better performance then.
I don't have this problem with other programs and games. Moreover I prepared full Crash Dump file. It may be helpful.

Code: [Select]
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Mar 27 17:26:21.890 2012 (GMT+2)
System Uptime: 0 days 0:03:16.578
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..........
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bd1bbc62, b74acf14, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : nv4_disp.dll ( nv4_disp+1a9c62 )

4
Actually, I have not played yet. Of course, in this example, the lack of interaction yet, but it is already easy to do. I hope I can help someone.

5
Hello. Sorry for my English.:) I'm creating a FPP adventure game with the possibility of rotating through 360 degrees. Because the forum was a lot of inquiries as to obtain such an effect, I decided to attach an example.
I hope this helps someone. Obviously this is not fully completed, but it works:).
Scripts and the names of some of the names are in Polish, but I hope that there will be problems:) The package contains the source and compiled the project.
And here's the link to download: http://www50.zippyshare.com/v/64979137/file.html

Pages: [1]

Page created in 0.224 seconds with 23 queries.