How is your VR FPS?

[JPAX]

I am struggling with low FPS on my Quest 3, particularly in the AA3 mountains.

My system should be powerful enough as I have AMD RX 7900 XTX (Nvidia 4080 equivalent). CPU is AMD R5 7600.

I've set my Quest 3 to 72 fps & max resolution, Condor settings are at max, vsync off, 2x MSAA. But often the 72 fps cannot be sustained and it drops back to 36 fps. In this scenario CPU utilisation is 10-20% and GPU utilisation is only ~60%.

Running the same scenario with VR off at 4k resolution, GPU usage goes to 100% and I get 180 fps. VR at 5408*2912 should not be 5x harder to render than 4k?

So I am wondering how your VR setup performs, am I doing something wrong or is a solid 72 fps in AA3 mountains not achievable without lowering settings/resolution?

[k6chris]

Can you post a .FPL with an air start so we can all run the same scenario please.

Thanks

[pilatusb4]

I have similar experience.
Quest 3, lower spec pc than OP, CPU i5-9400f, RTX 3070, 32gb ram.
Q3 set to 72fps and max resolution.
The 72fps does drop to mid 30s fairly often, I've not tried to analyse when this happens but mountains and particularly clouds seem to be involved. I don't find the drop in fps to be too much of a problem provided that it does not go lower than mid 30s.
I've tried various C3 settings and am currently using distances at high, reflections and grass off, everything else at max.
How do you see the CPU and GPU utilisation when in VR?

[wickid]

What I think happens is, when the quest can't maintain 72 (or 90FPS) it halves the framerate to stop tearing. It then doesn't fully utilises the computer resources. When the GPU utilisation drops below 50% the FPS restores to 72 FPS and the GPU will again be back at almost 100%.

For me it happens rarely when there are big clouds and rain (lots of transparency causing a lot of overdraw). I'm running a RTX4080 laptop GPU and a i9-13980HX. The Quest 3 is set at 90 FPS and 1.1x resolution.

[Crakob]

Running on 72 fps settings too. Specs see below.
95% of the flights it’s ok.

Todays 13:30 flight thought reduced the fps to sometimes around 35 fps. (Lots of clouds and wide thermals.

So I guess, depending on the task, fps will drop, no matter what gpu / cpu you got.

[wickid]

Large clouds and high activity is the biggest FPS killer. The GPU becomes fill rate limited.

https://en.m.wikipedia.org/wiki/Fillrat ... n%20in,GPU)%20of%20a%20video%20card.

TLDR... lots of transparent textures so every frame has to be drawn many times from back to front to stack all the transparency on on top of eachother.

[Gutsy_Fungus]

Hi folks,

Thought I would post as I have a marginal hardware set-up (10 year old PC with GPU upgrade)...I'd welcome some feedback; I am totally new to Condor 3 and VR.

From Memory:

FPS:
- I was flying from Slovenia (iirc) the default free flight take off point. (With cloud streets, clouds, no rain, 27knot winds, I spent time dynamic soaring in the mountains there)
- circa 30 odd FPS: On or very close to the ground even when sat their doing nothing a fixed value didnt appear to change until a certian agl (perhaps 200ft or so?); both TO and landing.
- Thereafter fixed at 72Hz fps for > 99% all of the flight. There was 2 or 3 occasional micro stutters for reasons unknown that didn't seem to be related to anything I was doing in the glider at the time. It's early with VR but the 3s does appear a little glitchy across other non Condor apps too.
- In hindsight - Am wondering whether the Rift 3 would have been the better option. It is miles ahead in it's internal hardware versus the budget 3s. (He says on his 10 year old marginal PC with his RTX 3050 budget special GPU (which is for the rift 3 an unsuitable GPU)

- Graphics quality?
I have no idea what to expect here? absolutely no idea; I am new to VR.
a) Before I get critical what a mind blowing experience VR is!)
b) Hope the Nausea disspiates. the tow launching does NOT help!!!
c) graphics close up are pretty basic (blocky houses) - I dont need to see the BBQ in the back garden mind you.
d) graphics at distance work really well.
e) Looking at straight lines (for example a distant runway, power lines, tower blocks) glistened / flickered at a distance. Wasn;t keen on this. And fancy finding a setting that I can fiddle with on this.
f) More experimentation required. Though I dont know what to fiddle with. perhaps you guys might help?

Notes:

- tested for just two flights.
- Total novice to Condor 3 or its precursors.
- Total Novice to 'fixed' wing Gliding, I was a decent club Hang Glider Pilot back in the day. (A cockpit and instruments are a luxury)
- Total Novice to VR in any respect. (Taken 2 days to just understand my hardware and load the correct software to run Condor 3)
- had a few flights faffing and binding keys in the flight school around on Condor 3 on the monitor.
- Further testing required.
- Tow launches - they are pretty challenging in VR? On monitor impossible.
- VR does give me a bit of nausea. Especially on a tow.
- Graphics settings (havent played with them yet.)

PC Setup:

Intel i5-4670k @3.40 Ghz
16Gb Ram
RTX 3050 8Gb
Rift 3s 128Gb - Air Linked to PC
Win 10 Pro 64 bit

[wickid]

- circa 30 odd FPS: On or very close to the ground even when sat their doing nothing a fixed value didnt appear to change until a certian agl (perhaps 200ft or so?); both TO and landing.

I'm guessing you have grass enabled. Grass is a texture with lots of transparency. That is most likely the cause of the FPS drop. The Quest will half the refreshrate when it runs out of resources. So from 72 FPS to 36 in your case.

- Thereafter fixed at 72Hz fps for > 99% all of the flight. There was 2 or 3 occasional micro stutters for reasons unknown that didn't seem to be related to anything I was doing in the glider at the time. It's early with VR but the 3s does appear a little glitchy across other non Condor apps too.

Condor loads the next patches of terrain from time to time (about every 5.7 km you fly). That causes a small stutter, depending on your hardware. Usually it is just a tenth of a second or so.

e) Looking at straight lines (for example a distant runway, power lines, tower blocks) glistened / flickered at a distance. Wasn;t keen on this. And fancy finding a setting that I can fiddle with on this.

Do you have MSAA enabled? That greatly reduces that kind of flickering.

[Gutsy_Fungus]

I'm guessing you have grass enabled. Grass is a texture with lots of transparency. That is most likely the cause of the FPS drop. The Quest will half the refreshrate when it runs out of resources. So from 72 FPS to 36 in your case.

You guessed right. ALthough it was neiother here or there for me in terms of immersion turnign the grass off left me at 72fps.

Do you have MSAA enabled? That greatly reduces that kind of flickering.

I didn't. When I tested the game with all the Antil Aliassing options, x2, x4 ,x6 & x8. It reduced to proprtionally to more or less zero at x8.

At x2 there appeared to be minimal performace loss until in the mountians; as I came close to/inside the cloud I had reduced/fluctuating fps. I took screenshots to capture this effect. this was the only time I had fps issues at x2 MSAA. In respect to the OP this is when he noticed it too iirc.
Yesterday at no MSAA i had zero fps drop in the same flight.

At x8 the loss in fps was quite significant. Sometime 72fps. but a fair amount of time (circa 50%) after tow release the fps was fluctuating significantly downwards.

I need to do some more tests in the clouds at x4 and x6 to find my sweetspot I guess.

Screenshots! I took some. expecting fps in cloud pictures. I got the picture of the glider stationary on the runway. It seems the screenshot [ "shift"+ "s"] is of the monitor, which in my case doesnt replicate what I am seeing through my goggles. Rightly or wrongly.

Happy landings...

And many thanks for the steer Wickid...Any other tips and tricks on squeezing performace out of my setup?

[wickid]

For screenshots in VR you need to have mirror rendering enabled. This causes a rather large performance hit though as extra resolution has to be rendered. Alternatively you can take your headset off when you want to take a screenshot. The image then transfers to the monitor and you can screenshot.

For the MSAA. You may be able to let your GPU instead of Condor do the anti alliasing. That may improve performance. Largest performance hits in Condor are the grass and clouds/rain as they use a lot of transparency. Setting "draw distance" one notch less also helps a lot to increase FPS.