EVERYBODY - READ THIS *** VSYNC *** (UPDATED)

[OXO]

RECOMMENDATIONS

1 - On flat screens, use "Fullscreen emulation" rather than "Fullscreen"

2 - In order to avoid unwanted effects (tow rope breaks, possible parasitic sink), your GPU FPS should not be faster than your monitor refresh rate

To see what FPS (Frames Per Second) you get:
Set Vsync OFF; run Condor; enter Shift-D. There will be a FPS number in the top left corner of the screen. Make a note

- if you are using a flat screen with fixed refresh rate: you MUST set Vsync ON

- if you are using a flat screen with variable refresh rate: you may use Gsync but we haven't enough experience with it, so if you have such issues, please report here and maybe reduce the frame rate in the graphics board settings

- if you are using VR: the refresh rate is set by the headset, 90 (=2x45) or 72 (=2x36) are fine

VSYNC.png (16.89 KiB) Viewed 7719 times

[janjansen]

To people who, like me, think they understand exactly what v-sync does and does not do, and feel they dont need this info; when it comes to condor, you are wrong, and oxo is right. I just read in another thread not having vsync on causes the tow rope to break instantly. I certainly did not see that coming, and I doubt anyone else will.

This does lead me to a question; what about variable refresh rate monitors (g-sync, free-sync) ? Should people who have that, use it to keep monitor and GPU synced (even if it allows >200FPS/Hz on some monitors) or disable it?

[pilatusb4]

Does this have any relevance to use with a VR headset (Quest 3) rather than a monitor ?

[OXO]

Does this have any relevance to use with a VR headset (Quest 3) rather than a monitor ?

I don't know. VR makes me ill.

[Fabry]

Does this have any relevance to use with a VR headset (Quest 3) rather than a monitor ?

I'm running Quest3 and if i run V-Sinc on it's a constant stutter (i also had that in C2), I personally de-selected mirror rendering running full graphic options and MSAA x2 and the lowest i get over a big town with lots of thermals and heavy thunderstorm is 35 fps so still comfortable, if i let V-Sinc on I get instant nausea, my only minor issue and bottleneck is the occasional very short freezes when load landscapes bits (i also had that in C2 my HD is not SSD) , but overall i get same if not higher performances then C2.
Maybe OXO was referring to Monitor users.

My specs:
Windows 11 Pro
Intel Core i7-9700 @3.00GHz (8 CPUs)
16384MB RAM
NVIDIA GeForce RTX 2070 Super 16083 MB set to Use 3D app setting
Meta Quest3 on PCVR cable

[wickid]

Does this have any relevance to use with a VR headset (Quest 3) rather than a monitor ?

VR automatically uses Vsynch.

[p_a_harvey]

It's also worth mentioning that the refresh rate for Quest-based VR can be specified in the Quest Link app and is seemingly independent of your monitor.

I tested by configuring 72Hz and then 90Hz in Quest Link, and used Shift-D to check the resulting FPS in Condor 3. The FPS in Condor was very slightly lower than the specified refresh rate in Quest Link. (eg. 71.92fps instead of 72, though I don't remember the exact number).

Other than the slight difference in numbers, everything ran smoothly in VR. I could even have mirrored rendering.

[christimson]

Running without V-Sync selected on my machine gives 360 fps. The GPU is running 100% and the fans making lots of noise. I'm worried about it overheating. (Nvidia RTX3090) With V-sync selected performance is still good and smooth (60fps) but GPU runs at around 25% nice and cool.

Is running with v-sync ok in my case? I'm running a 2560x1440 @60hz monitor.

[wickid]

Running without V-Sync selected on my machine gives 360 fps. The GPU is running 100% and the fans making lots of noise. I'm worried about it overheating. (Nvidia RTX3090) With V-sync selected performance is still good and smooth (60fps) but GPU runs at around 25% nice and cool.

Is running with v-sync ok in my case? I'm running a 2560x1440 @60hz monitor.

Yes, it is recommended to have V-synch on. We found during testing that a large difference between framerate and monitor refresh rate can cause unwanted effects (like towropes breaking on launch).

[jcomm]

Just for curiosity sake, I haven't had any quirks running with Vsync unticked in Condor but then limiting FPS to half my monitor refresh rate (60 Hz, so 30 FPS) in RivaTunner.

No crashes, no GPU being pushed to limts... 30FPS smoothly going and confirmed if I use SHIFT-D.

But I will try without RivaTunner and by ticking it in the sim options !

[bluefang]

You MUST set up Vsync correctly.

Procedure:

1. See what fps you get. Vsync OFF, run Condor, Enter Shift-D. there will be a FPS number top left. make a note

2. If FPS is higher than your monitor refresh rate (or in doubt), set VSYNC ON in Condor.

Nvidia users: set Vsync OFF in Nvidia control panel. Let Condor control it.

This doesn't work for me.

If I set Vsync Off in Nvidia Control Panel, and check Vsync On in Condor, I get an FPS of around 130fps in Condor - but it is choppy / tearing a bit and is definitely not the sync-rate of my monitor (60fps).

If I set Vsync to "Use Application Setting" in Nvidia Control Panel, and check Vsync On in Condor, I get an FPS of around 20fps in Condor - and it is totally unusable.

The only settings that seem to work for me, are:
Vsync On in Nvidia Control Panel, Vsync Off in Condor. This gives me a consistent 59.96fps in Condor and Condor runs smooth (except for stuttering in AA3).

This is with a G-Sync enabled graphics card and monitor.

My Settings:

Core i7-8700 3.2 GHz (6 cores)
48 GB RAM
3060Ti w/ 8GB RAM with G-Sync enabled monitor
OS running off of SSD NVME drive

I am running Condor in Fullscreen mode @ 2560x1440

[janjansen]

This is with a G-Sync enabled graphics card and monitor.

You found the cause. When you enable g-sync, condor has no way of knowing what your monitor refresh rate is, because its variable. Enabling vsync in condor can not give good results. I dont think OXO is familiar with or has a g-sync monitor. I have not heard any of the beta testers saying if variable refresh rate does or does not solve the issue, so Im going to assume its untested/unknown.

Assuming you want to keep using G-sync for other apps, I would do one of two things; either what you did (forcing V sync through nvidia instead of condor), or, keep using G-sync, also enable it for condor. This may give you problems, but if no one tries we will never know. If my guess/gut feeling of what the root problem is, is correct, then g-sync should also solve it. But I would like to know, and love to hear if you can reproduce the tow line breaking issue. If you have the time and inclination, try flying without sync at all (not even G sync, turn it off completely for your monitor) and see if you can reproduce the problem of the tow rope breaking before taking off on some fields (not sure which, Im guessing non flat ones? Can someone fill us in?). If you can reproduce it, then turn on g sync and see if the rope still breaks. That might tell us if G-sync/feesync is also a solution to this problem or not. Id do it myself, but unfortunately no longer have a variable refresh rate monitor and so far, Ive not managed to reproduce the problem without sync.

[bluefang]

This is with a G-Sync enabled graphics card and monitor.

Assuming you want to keep using G-sync for other apps, I would do one of two things; either what you did (forcing V sync through nvidia instead of condor), or, keep using G-sync, also enable it for condor. This may give you problems, but if no one tries we will never know. If my guess/gut feeling of what the root problem is, is correct, then g-sync should also solve it. But I would like to know, and love to hear if you can reproduce the tow line breaking issue. If you have the time and inclination, try flying without sync at all (not even G sync, turn it off completely for your monitor) and see if you can reproduce the problem of the tow rope breaking before taking off on some fields (not sure which, Im guessing non flat ones? Can someone fill us in?). If you can reproduce it, then turn on g sync and see if the rope still breaks. That might tell us if G-sync/feesync is also a solution to this problem or not. Id do it myself, but unfortunately no longer have a variable refresh rate monitor and so far, Ive not managed to reproduce the problem without sync.

I went ahead an made a table of the 3 relevant settings and the results produced by each setting... This was tested on my own landscape as well as Slovenia - with Slovenia producing slightly lower fps when both v-sync settings are off.

condor-3-vsync-table.png (41.53 KiB) Viewed 7319 times

It looks like, regardless of the Nvidia setting for the G-Sync Enabled or Disabled, if I have V-sync enabled in Condor, then the FPS drops down to the really low point (~24fps). So disabling G-Sync is not an option.

But I would like to know, and love to hear if you can reproduce the tow line breaking issue. If you have the time and inclination, try flying without sync at all (not even G sync, turn it off completely for your monitor) and see if you can reproduce the problem of the tow rope breaking before taking off on some fields

I was never able to reproduce the rope-break issue. My home field is sloped, but not to the point where the glider moves on load in. And I never saw a rope break - but I use the "sane" rope length settings we use here in the US of 200ft

I can do some more rope-break test given a scenery and flight-plan file to test with.

[Lenticular]

I have VSync disabled, and not seen rope break problems.

Shift+D is not working for me. Is it assignable in options?

Based on how other sims run, I should be getting an easy 100+ FPS.

[janjansen]

It looks like, regardless of the Nvidia setting for the G-Sync Enabled or Disabled, if I have V-sync enabled in Condor, then the FPS drops down to the really low point (~24fps).

edit: I made a mistake. Need to look/think more closely. But your first entry cant be right.

But what I dont understand is that you never get more than 60 FPS with g-sync. I assume your monitor is capable of more than 60? Most (non sim) gamers buy g-sync monitors to get 144-200+ FPS/Hz without screen tearing. Are you sure G sync was enabled in nvidia control panel?

So disabling G-Sync is not an option.

I dont follow. Why not? I mean, it wouldnt be my first choice, but when the monitor runs at a fixed 60Hz instead of G Sync, according to your table, you can get basically get anything you want from 150+ FPS or 60FPS synced as OXO suggests, (or 24 fps if for some reason you prefer that ).

What you can NOT get without G sync, is smooth motion without some screen tearing at high FPS or micro stuttering at lower FPS. G-sync monitors can increase and reduce their refresh rate down to 1hz and still keep in step with GPU; 49 FPS at 49 Hz looks a lot smoother than displaying, 49FPS on a 60Hz monitor. That is one very good reason to want G-sync, but thats not going to show in the numbers.

I was never able to reproduce the rope-break issue. My home field is sloped, but not to the point where the glider moves on load in. And I never saw a rope break - but I use the "sane" rope length settings we use here in the US of 200ft

Hoping one of the beta testers jumps in here, but I think the issue may only reveal itself at much higher framerates (many 100's of FPS)?