did nvidia take away the option to render zero frames ahead because of gsync?

[Anarchist420]

that's what i want to know.

i kind of think that gsync wouldnt be necessary under 5 conditions:

1. we had 120 hz and higher vsync rates (maximum of 8.33 ms lag).
2. no hdmi (not enough bandwidth but is more common because of royalties; hdmi could and should be destroyed by ihvs only using display port)
3. faster signal processing in monitors and advertising of it; (a maximum of 3 ms signal lag) at 60 hz input (would be less at higher than 60) or simply direct drive monitors.
4. more gamepads and keyboards that did 500 reports per second (2ms lag)
5. zero frames to render ahead was still an option.

i know that gsync would be totally free of signal and vsync lag, but it isnt that much difference from 2 ms lag vs 13.33 ms lag (which is the maximum estimate) with the proper options.

basically, gsync is a good idea, but the problem is that something very close to it that has been possible, is around today, and would cost less wouldve been better.

i do simply suspect, however, that nvidia removed the option to render zero frames ahead so they could make money off of gsync.

anyway, im sure that this op was filled with many inaccuracies but that's because my iq is in the 60 range.

 

[BrightCandle]

No they removed 0 frames render ahead because the driver model changed and it was no longer an option. Microsoft is the reason there is no 0 frames rendered ahead nowadays, it has nothing to do with gsync, they are completely different ends of the rendering for the GPU (render ahead is the input to the GPU and gsync is the output).

Even with 240ms monitors and zero signal processing latency and completely free and open standards gsync would still make things better.

 

[Anarchist420]

Even with 240ms monitors and zero signal processing latency and completely free and open standards gsync would still make things better.

but just barely because 240hz vsync would only be a maximum of 4 and 1/6 of a second lag.

No they removed 0 frames render ahead because the driver model changed and it was no longer an option. Microsoft is the reason there is no 0 frames rendered ahead nowadays, it has nothing to do with gsync, they are completely different ends of the rendering for the GPU (render ahead is the input to the GPU and gsync is the output).

i also suspected that for various reasons (but neglected to mention it in my op) although nvidia's official answer was that it is no difference. but i think they could make it work for opengl games and pre-DX10 games if they did it in a beta driver.

that said, bill gates is an a-hole one reason being because he achieved at least 90% of what he had envisioned (i.e., a microsoft computer on every desk) and it was achieved all because of the govt (Stephan Kinsella estimated that 70% or so of microsoft's profits have been due to IP). i also am mind boggled when trying to figure out why nvidia didnt completely ditch microsoft like 10 or 11 years ago because of all the lousy standards microsoft imposed... the R300's feature set was the bare minimum and the handwriting has been on the wall ever since that overrated pos came out in 2002.