OK, it’s working again after a PC reboot. I checked by looking at the wing struts on the Stearman to see if they get pixelated when I turn FFR on or off, which they did and the FPS rose by about 7-8fps using performance plus narrow.
I haven’t touched Scale Factor, and I’m definitely GPU bound; depending on settings I get values like these I jotted down yesterday:
FFR OFF: CPU 1200
GPU 2400
FFR ON: CPU 1190
GPU 1670
I’ve just shut down the sim for some lunch, but will check after if you still want the VRS and VRSw values.
One other thing that I haven’t yet had time to look into properly. I tried out the frame limiter in the Toolkit and set it at 30, just to see how it worked and to limit the temps on my GPU, so it’s not at 100% all the time (also to check for any effect on 1% and 0.1% lows). It seemed noticeably jerkier when I moved my head from side to side, particularly on the windscreen frames of the Stearman. I use Radeon Chill at times to do the same thing when I’m just sightseeing and don’t recall that amount of jerkiness using the Radeon driver software. I’ll look into comparisons more closely later today.
Just tested frame rate limiting using either Radeon Chill or the Toolkit, both set at 30fps. There is definitely a difference at least on the cockpit coaming, instrument panel and windscreen frame on the Stearman…the scenery seemed to show little if any difference. 30fps using the Toolkit causes noticeably larger steps as you move your head from side to side than Radeon Chill, making it more distracting and noticeable. FPS frame counter showed 30fps with both. I have absolutely no idea why that should be the case.
Thanks. Looking back at the code I think I can see why that is.
I truly hate this feature, I only added it because people would not stop asking. Limiting frame rate is a terrible thing to do in VR (and nobody will convince me otherwise). And it’s already causing problems…
I’ll change things around for 1.2.1.
Edit: your temperature control is probably the only sensible explanation I’ve gotten so far w.r.t using frame limiter, I will give you that
LOL
I know you hate it, so I was a bit shy to mention it. But if it’s a Toolkit feature, I thought you needed to know about any problems. It certainly wasn’t a complaint or a moan, especially given all the hard work you have put into this great software.
Thanks. For me it makes sense when I’m just tootling around looking at the scenery, as I said. My GPU gets pretty hot, despite a great case with heaps of fans; the junction temperature sometimes gets close to throttling and, well, why thrash it if you just want to sightsee slowly in an old biplane.
Really must add this, I was blown away how much better the scenery looks when I got back on the Toolkit after not using it in the SU19 beta. The ability to adjust the brightness, colours, contrast etc made the countryside so much more beautiful, even without Bijan’s excellent tree mod. So thanks again.
I wonder what settings are you usong for that? MSFS colors are too saturated, so I decreased saturaion a bit, but I don;t want to suck too much color from the sky… I wonder what would be a good setting for the most realistic visuals.
Well, I started off by copying someone else’s settings, so it would be really funny if they were yours, which they could well be.
Anyway my clear skies look well saturated (if I get rid of the new high altitude cirrus that is now the stock clear sky preset). I can take a screenshot of my Toolkit settings if you like.
Thinking of presets, it would be nice if we could have an option to select some in the Toolkit, as today I was flying over the countryside near my place and it all looked really good, but then I flew into a different area near town, with a very noticeable more washed out set of scenery tiles and it didn’t look so nice. A quick keyboard shortcut to select a different set of values would be nice.
Edit: I don’t think I’ve changed these settings since I copied them from somebody else, maybe the brightness and contrast at times I would change a bit. It’s likely a very personal perception thing and depends on the headset too. I use a G2.
Hello I just got into VR and have been using this excellent OpenXR Toolkit with MSFS.
I have noticed that when I use ASW at 30hz to lock my frame rate to 27 FPS in the headset, the performance headroom DECREASES instead of increasing. However my GPU does run cooler.
Why is limiting frames in VR a bad idea? New to this so apologies if this has been answered before.
What’s the conventional wisdom for optimizing sharpness for fully glass cockpits in VR? We have had the sharpness setting in OXR and now this new AMD slider is the sim. Use one over the other or both?
Do you find any other settings improve the ability to read those tiny numbers - perhaps disabling FFR? I use a Reverb G2 with prescription inserts.
