T3D 1.1 Beta 2 - Advanced Lighting Fails to initialize - CONFIRMED
by Tod · in Torque 3D Professional · 08/10/2010 (11:26 pm) · 6 replies
Windows 7 x64
nVidia 470GTX
Driver: 258.96
Run either demo included with TD3 1.1 beta 2. Works fine if advanced lighting is disabled. Enable advanced lighting, everything goes black and the following message in the console log:
nVidia 470GTX
Driver: 258.96
Run either demo included with TD3 1.1 beta 2. Works fine if advanced lighting is disabled. Enable advanced lighting, everything goes black and the following message in the console log:
Using Advanced Lighting GFXD3D9Shader::_compileShader - Error compiling shader: E_FAIL: An undetermined error occurred (80004005) I:/Torque/Torque 3D 2009 Pro 1.1 Beta 2/Demos/Physics/game/shaders/common/particlesP.hlsl(70,24): error X3004: undeclared identifier 'prepassUncondition' I:/Torque/Torque 3D 2009 Pro 1.1 Beta 2/Demos/Physics/game/shaders/common/postFx/edgeaa/edgeDetectP.hlsl(30,13): warning X3550: array reference cannot be used as an l-value; not natively addressable, forcing loop to unroll
#2
The biggest issue, however, is when distributing the game: it will obviously fail if installed in Program Files. In order for it to work, shaders must be generated only in memory (there's an option for this) and prefs, logs and other files created during run-time must go into %APPDATA%.
08/11/2010 (4:19 pm)
I had this issue. Turned out I installed T3D in a folder where normal users couldn't write, causing all sorts of failures. Changing the folder permissions or moving T3D to somewhere else gets around the problem.The biggest issue, however, is when distributing the game: it will obviously fail if installed in Program Files. In order for it to work, shaders must be generated only in memory (there's an option for this) and prefs, logs and other files created during run-time must go into %APPDATA%.
#3
08/11/2010 (4:44 pm)
Got a resource for that Manoel? [big_cheeky_grin]
#4
I don't know if those shader compile errors are related to the lighting issue. I kind of doubt it. If I run the Steampunk demo, I do not see those shader compile errors, however there will still be no lighting applied.
I then ran 1.1 beta 1 demo's and they ran just fine and they are located in same location as 1.1 beta 2.
08/11/2010 (5:18 pm)
Just to be sure I double checked permissions, and the permissions are ok, Change permissions granted to the account running the software. And just to be sure I ran it as administrator, same thing. The software also isn't installed in a windows protected folder or drive. I don't know if those shader compile errors are related to the lighting issue. I kind of doubt it. If I run the Steampunk demo, I do not see those shader compile errors, however there will still be no lighting applied.
I then ran 1.1 beta 1 demo's and they ran just fine and they are located in same location as 1.1 beta 2.
#5
1. Start up the steam punk demo. Defaults are 1024x768, No AA. Lighting Normal. Game starts and runs fine
2. Exit the mission and go into options. Change to 4X AA. Restart the mission. Everything is fine.
3. Exit the mission and go into options. Change resolution to 1152x864. You are now doomed from here. All lighting is gone.
4. Exit the mission and change to any other resolution. Lighting is still gone.
5. The only way I have found to get lighting back is to either exit completely "and" shutdown the toolbox, or set AA to none "and" change the resolution.
08/12/2010 (12:22 am)
After a lot of testing, I believe I have found the issue.1. Start up the steam punk demo. Defaults are 1024x768, No AA. Lighting Normal. Game starts and runs fine
2. Exit the mission and go into options. Change to 4X AA. Restart the mission. Everything is fine.
3. Exit the mission and go into options. Change resolution to 1152x864. You are now doomed from here. All lighting is gone.
4. Exit the mission and change to any other resolution. Lighting is still gone.
5. The only way I have found to get lighting back is to either exit completely "and" shutdown the toolbox, or set AA to none "and" change the resolution.
#6
Bug confirmed.
08/18/2010 (11:38 pm)
Thanks for those reproduction steps Tod, that really helped me reproduce this one. The key of the issue here seems to be having AA set to anything higher than 2 while AL is turned on and changing resolutions. It's also definitely specific to Nvidia cards in general.Bug confirmed.
Associate David Montgomery-Blake
David MontgomeryBlake