rctcool0 wrote:I'm not an expert on what it ACTUALLY does, but I believe how the game works is that the CPU/GPU sync attempts at syncing the Frame processing in the GPU to the core clock of the CPU. So, in theory, the GPU is told to do so many frames in a certain amount of CPU clock cycles.
Almost exact, with 1 frame cpu/gpu, we have
time_0: cpu begins frame 0 drivers begin to receive frame 0 datas and send them to gpu
time_1: cpu ends frame 0 gpu has begun working on frame 0 yet not finished yet (started after cpu)
time_2: cpu begins frame 1 drivers begin to receive frame 1 datas, gpu may still work on frame 0
time_3: cpu ends frame 1 AND WAIT GPU TO END FRAME 0 <<== the synchro is here
Then with 1 frame synchro cpu & gpu can work in parallel within 1 frame.
Immediate synchro reduce input lag to minimum (cpu waits end of gpu render for the same frame), yet average fps is usually quite low.
3 frames synchro has the maximum input lag but the better
average fps.
Now I'm really not sure about the Display Sync, though I would guess that it is there to reduce visual tearing. This means that the GPU would be forced to run frames according to the refresh rate of the monitor. However, this seems too much like VSync, and I know that is a separate option.
Display sync on means gpu (and cpu) can not render more than display mode frequency (usually 60 or 120Hz).
Yes it removes visual tearing (when player can see 2 frames vertically split)
Another advantaged of VSync is that fast movement looks more "continuous" or "fluent" than without.
This can be seen more easily in TM than SM.
(Without VSync, none of the 2 frames teared have the right time, one is before, the other is after, this creates a kind of visual noise on fast moving objects)
If you have display sync enabled, previous cpu/gpu sync makes usually no difference (except immediate case which should not be used with VSync).
A difference with cpu/gpu synchro is that display sync is based upon a FIXED FREQUENCY (the display one).
This is important, and linked with the last sync parameter: the triple buffer:
triple buffer off:
VSyncOnAt60+GameFps=80 => actual fps = 60fps (no problem)
VSyncOnAt60+GameFps=55 => actual fps = 30fps !! this can be quite anoying !!
triple buffer on:
VSyncOnAt60+GameFps=80 => actual fps = 60fps (no problem)
VSyncOnAt60+GameFps=55 => actual fps = 55fps (or close to)
Yet, tripple buffer has a default : it increase the input lag (one frame more is buffered)
Basically, the ideal situation is for the game to run at EXACTLY 60 fps. This means that the frames match your monitor's refresh rate, and your system won't be overworking itself. I have actually not done any multiplayer on SM, so I can't give you an example of the fps drop from having the game process the actions of multiple players. Also, I've never really played a First Person Shooter before, so I don't have much experience there.
Try running different benchmarks on Maniaplanet and find the one that gets the closest (preferably slightly higher) to 60 fps. If you have any other questions about the graphics settings, I've done a lot of tweaking, so I may be able to help if you need it.
To sum up, you have to
a) choose if you want to enable VSync or not and with what display frequency
b.0) Without VSync: select the cpu/gpu synchro to choose between high global fps or low input lag
(tripple buffer is ignored)
b.1) With VSync: select at least 1 frame, or 2 frames of gpu/cpu synchro (or even no gpu/cpu sync)
and enable/disable triple buffer to choose between low input lag or fps stability
(I'll put a warning message in the launcher if you set immediate + VSync)
