Hi,<br> I already sent you an email, but I found a bug regarding the Direct3D (and I assume OpenGL) prerenderlimit setting (rendering X # of frames ahead).<br> <br> "00" should be a valid number for this, as rendering 0 frames ahead actually helps completely eliminate the "mouse lag" problem, when the FPS drops below 60. ESPECIALLY with vsync enabled. Increasing the prerender limit tends to cause mouse and keyboard lag, much more so if vsync is on.<br> <br> I tested this out in the Geforce Tweak utility and in NVMAX.<br> In GTU, if the check-box "RENDER no more frames ahead than "X" " is checked, then the slider starts at '1' (the lowest value). <br> UNCHECKING the check box, changes the PRERENDER LIMIT to "0" (and disables the slider, as it seems that the prerender limit is actually off). I would expect OpenGL to allow the same thing (in NVmax it does, although GTU doesn't allow this setting tweaked in openGL yet). <br> <br> NVmax simply allows you to enter the value directly "00", for instance.<br> <br> I did some "input" tests, to test responsiveness, and although "0" and "1" both are good, it seems that "0" is perfect (assuming 60 fps here), and "1" is almost perfect, having a TINY TINY bit of mouse lag, which is REALLY hard to detect. <br> <br> Anyway, can you update Rivatuner to allow "PRERENDERLIMIT" of "0", for Direct3D (and the corresponding setting for OpneGL?).<br> <br> Thanks
You can use the power user page to choose any value.<br> <br> And i think other ppl reported setting of 3 works best.
I've already answered by email, but I think that others would like to read my answer too. Here it is:<br> <br> Direct3D driver checks prerender limit value and sets it to 1 if it's less than 1. OpenGL driver sets prerender limit to 2 if it's less than 2. RivaTuner uses the same validation code. Both NVMax and GTU uses incorrect validation codes for prerender limit registry entries.<br><br><i>This message was edited by Unwinder on 01 Sep 2001 12:54 AM</i>
<BLOCKQUOTE>quote:<HR>Originally posted by LoyC:<br> <b>Just to double-check:<br> prerender limit value 3 for <i>Both</i> Direct3D & OpenGL?</b><HR></BLOCKQUOTE><br> <br> I use 3 in d3d and 2 in ogl. Default values. But i have VSync on in d3d and off in ogl.
Hey Kakaru2, thx for the default values, if only I knew why OpenGL uses 2 instead (through countless research by our programmers prehaps? <IMG SRC="smileys/rolleyes.gif"> )<br> <br> Anyway, may I ask why you choose to have vsync off in ogl? Is it because it was sucking too much fps, yet showing little help in it? Sometimes I also want to master in getting the optimal settings...like many others.<br> <IMG SRC="smileys/bounce.gif"> I'm using 12.90s and they're running great, though I haven't tried the 14.xx series, which should have better quality (stereo too) in trade with raw performance... What's your drivers? <IMG SRC="smileys/knock.gif">
Personal impressions:<br> If D3d is "build" by MS around VSync ON i feel OGL runs better with VSync Off, quality included. I always set the refresh rates at 85 Hz in Q2, Q3A, etc and that seems to be all that I need. <br> VSync off is a pain in D3D but is very likeable in Ogl.