New Water Shaders on Laptop
by Robert Rice · in Torque Game Engine Advanced · 06/16/2005 (6:21 am) · 6 replies
I just bought a new laptop that has an nVidia GeForce Go 6800 which has up to date shader support. However, when I try to run the water_and_terrian_demo mod on the M2 version of TSE, I get a pop up that tells me it cannot build one of the pixel shaders. I followed the 'fix' posted on anothet thread (about changing the version of the offending shader from 1.4 to 2.0), and that did not help. I deleted the shader from the file altogether, and then I got the same type of message, but this time it was concerning a vertex shader.
Is anyone encountering the same type of situations on a laptop with this type of video card?
Is anyone encountering the same type of situations on a laptop with this type of video card?
#2
06/16/2005 (12:05 pm)
Did you move both the shaderData AND the CustomMaterial up to 2.0 rendering?
#3
In defaults.cs, I set $pref::Video::forcedPixVersion = 2.0;
For EVERY ShaderData datablock, I set pixVersion = 2.0;
For EVERY CustomMaterial, I set version = 2.0;
I updated the error message that someone had posted in another thread so that the error message gave the shader and target names. I did this for both pixel and vertex shaders.
In attempting to run both the demo and the terrain_water_demo, I get the message "Unable to compile vertex shader shaders\shaderV000.hlsl for target vs_3_0".
06/18/2005 (6:10 am)
Here are more details.In defaults.cs, I set $pref::Video::forcedPixVersion = 2.0;
For EVERY ShaderData datablock, I set pixVersion = 2.0;
For EVERY CustomMaterial, I set version = 2.0;
I updated the error message that someone had posted in another thread so that the error message gave the shader and target names. I did this for both pixel and vertex shaders.
In attempting to run both the demo and the terrain_water_demo, I get the message "Unable to compile vertex shader shaders\shaderV000.hlsl for target vs_3_0".
#4
"Mapping string: MissionStartPhase2Ack to index: 1
error X3506: unrecognized compiler target 'vs_3_0'"
06/18/2005 (6:36 am)
While I'm at it, this is in the console..."Mapping string: MissionStartPhase2Ack to index: 1
error X3506: unrecognized compiler target 'vs_3_0'"
#5
A) to force pixel shaders down to 2.0, you need BOTH these lines:
$pref::Video::forcePixVersion = 1; // this tells it you want to force to some version
$pref::Video::forcedPixVersion = 2.0; // this is the version you want to force it to
B) Pixel shader 3.0 support was added in a later version of DirectX than what you are linking with. Update your DirectX SDK to a later version. Make sure you uninstall your current DXSDK before installing a new one. If you are using VC6, get the October 2004 release and the Extras pack.
06/21/2005 (12:17 pm)
Ah, OK, here's the problem.A) to force pixel shaders down to 2.0, you need BOTH these lines:
$pref::Video::forcePixVersion = 1; // this tells it you want to force to some version
$pref::Video::forcedPixVersion = 2.0; // this is the version you want to force it to
B) Pixel shader 3.0 support was added in a later version of DirectX than what you are linking with. Update your DirectX SDK to a later version. Make sure you uninstall your current DXSDK before installing a new one. If you are using VC6, get the October 2004 release and the Extras pack.
#6
WOW, that water looks even more phenominal than in a still or video. Amazing!
06/22/2005 (5:20 am)
Ahhh. Part A of your post did the trick, Brian. Thanks!WOW, that water looks even more phenominal than in a still or video. Amazing!
Torque 3D Owner Jameson Bennett