pitch error sum1 help me plz!
- Thread starter qwertyman
- Start date
The Solution
Ok guys..
while looking for a solution for the slowdown of the game in my other PC (P3 866, 384 MB RAM with GF 4 MMX videocard) I came across a topic in another forum that discussed some 3D Analyze settings. When I tried them, they not only speeded up the game, but also fixed this pitch problem I was also having. These are the settings:
In 3D Analyze (http://www.tommti-systems.com/main-Dateien/files.html), check the following options:
force z-buffer
disable 2-sided stencil
emulate HW TnL caps
quality on remove stuttering (performance makes it run faster, but screwed all the graphics sometimes for me)
force 16-bit z-buffer without stencil (guess you should set your display to 16 bit to use that, don't know)
Hope this help ya guys out.
Cheers
Ok guys..
while looking for a solution for the slowdown of the game in my other PC (P3 866, 384 MB RAM with GF 4 MMX videocard) I came across a topic in another forum that discussed some 3D Analyze settings. When I tried them, they not only speeded up the game, but also fixed this pitch problem I was also having. These are the settings:
In 3D Analyze (http://www.tommti-systems.com/main-Dateien/files.html), check the following options:
force z-buffer
disable 2-sided stencil
emulate HW TnL caps
quality on remove stuttering (performance makes it run faster, but screwed all the graphics sometimes for me)
force 16-bit z-buffer without stencil (guess you should set your display to 16 bit to use that, don't know)
Hope this help ya guys out.
Cheers
CtrlAltDel
Registered User
good stuff sabaum!
the z-buffer holds the z-coordinate of every pixel on the screen. It is usually 16 bit or 32 bit in size. all values are usually initialized to their full value and only saved if less then that (which is usually). its also computed for every polygon facing the screen. so polygons that are obscured are left out of the calculations. Obviously its gonna take more clock cycles from your GPU to calculate 32 bit Z buffer, than 16. especially on a card like the GF4 MX i'd definately scale back to 16. I'd only put this at 32 if you have a beefy system.
dunno why you'd need to do the 'emulate HW TnL caps' since your card has HW TnL Caps built into it...so you might get away with uncheckig that one.
the z-buffer holds the z-coordinate of every pixel on the screen. It is usually 16 bit or 32 bit in size. all values are usually initialized to their full value and only saved if less then that (which is usually). its also computed for every polygon facing the screen. so polygons that are obscured are left out of the calculations. Obviously its gonna take more clock cycles from your GPU to calculate 32 bit Z buffer, than 16. especially on a card like the GF4 MX i'd definately scale back to 16. I'd only put this at 32 if you have a beefy system.
dunno why you'd need to do the 'emulate HW TnL caps' since your card has HW TnL Caps built into it...so you might get away with uncheckig that one.
yeah, I got that.....
I also don't know why you need to check the emulate HW TnL caps option..... the guy in the other forum said so, and it worked fine, so I haven't changed it..... I'll try without to see if there's any difference...
What matters is that the textures are ok now!
I also don't know why you need to check the emulate HW TnL caps option..... the guy in the other forum said so, and it worked fine, so I haven't changed it..... I'll try without to see if there's any difference...
What matters is that the textures are ok now!
haha funny thing CtrlAltDel..... seems that the option that corrects the pitch problem is exactly emulate HW TnL caps... I tried to run the game without it and the error returned... go figure..... Gonna turn it back on
Now I'm running the game in my P3 in 1024x768 high details as well...
Now I'm running the game in my P3 in 1024x768 high details as well...