• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**Nvidia G-Sync owners thread**

Bad power brick on mine and the dp cable possibly, sorted with a replacement brick from a mate and cable of auction. Working a treat now. For those few weeks it was like having a sports car on bricks.:D
 
Maybe this post might help you understand the type of lag I'm talking about Greg. Internally capping frames in my example has nothing to do with afterburner.

http://forums.blurbusters.com/viewtopic.php?f=10&t=895

Actually, it is kind of a law of physics limitation of sorts, rather than as a bug.

There is no easy workaround other than reinventing the 3D rendering paradigm to permit easy driver/hardware-side lagless framerate capping which is otherwise not easily possible.

  • External framerate limiters of any kind adds lag in current 3D architectures.
  • Internal framerate limiters can successfully avoid this lag.

Frames should be throttled right before input reads, and BEFORE rendering, not after already rendering, which is what external framerate limiters do (e.g. NVInspector, driver capping, VSYNC ON capping, GSYNC limit hitting). You have lost the lag battle if you already rendered the frame and then is forced to wait on presenting the frame. Game developers need to allow an internal method of frame rate capping, for full control over lag, without being forced to wait by external limiters after presenting the frame.

Only the appearance of the lag at, say, fps_max 143 (during 144Hz GSYNC) can legimately be called a potential issue. It can be improved so that there is no lag penalty when you use an in-game framerate limiter closer to Hz. But once an external limit is hit -- you yield game engine control of lag -- when something outside your game forces frames to wait.
Click to expand...

I do understand what you mean regarding the GSYNC limits but what I'm talking about is the lag between the game engine and the nvidia drivers. I had read that adopting a range between 135 and 143 reduced lag and this was something blurbusters successfully tested.

If nvidia have somehow fixed this then I would be interested but I can't see how it's possible.
 
You could be right Kiwi but I have never noticed it. I remember on my Dell IPS that would tear like a **** without V-Sync and with V-Sync, input lag was horrendous but maybe I am just old and slower now :D
 
Yeh I dunno, I think I was one of the first here to get a SWIFT so at the time was doing a lot of research on bluebusters trying to eliminate as much input lag as possible.

I wonder if nvidia will be releasing another iteration of GSYNC with less lag? Its still quite noticeable for me when compared to ULMB but my brain just can't handle the tearing.
 
Just joined the club with a Dell S2716DG, has totally transformed pc gaming for me, i love eye candy so annoying stutters used to do my head in falling off the v-sync, now its all gone :D

Cant say i notice any lag at all
 
Appreciate being added Greg picked up my Dell S2716DG during the Black Friday sales.

Havent had time to tweak it properly yet so its just out of th ebox set up wise, lookin forward to tweaking more over the xmas downtime :)
 
varkanoid said:
Just realised my horror is still on post 1 -
please remove this disgusting piece of junk from post 1. Thanks

Acer Predator XB280HK - Varkanoid
Click to expand...

lol

varkanoid said:
On another note I've got a PG279Q burning a hole in the floor next to me at work waiting to try.
Bit apprehensive whether I got a good one or not.
So hopefully this can replace it.
Click to expand...

Fingers crossed :)
 
You must log in or register to reply here.
Back
Top Bottom