odourboy

Well that's really the bottom line... and the reason I still fire up 2020 for any serious VR sessions.

Top shelf dude!

Pico 4 user. I am not a happy MSFS2024 VR user. 😠 I'm pretty sure the main issue is VRAM exhaustion. I'm back onto MSFS2020 for VR. Smooth and steady. I'll revisit 2024 when the beta is released. It sounds promising.

Just ordered one of these!

Dude! That really stinks. 🙁

This is both good news and bad. Appears to confirm that some of the performance issues are indeed caused by 2024's memory footprint, which can be addressed. But the prospect of blowing another couple of hundred $ on RAM I don't otherwise need is a bit annoying. 😆

It's no CL but it's been a solid performer for me. I'm happy with it until the 'perfect' headset come out. 😏

Just as a data point, I'm running 4412X4412 per eye DLSS Quality with my Pico 4.

Thanks for the report!

You need to up the rendering resolution in DLSS to match TAA instrument image quality. You give up some FPS to run the higher resolution but not as much as TAA costs.

Nope. I ran my test scenario and exceeded my 32Gb RAM (by roughly the same amount as prior to the latest patch).

I'll recheck this. I've only done one flight since the update and it wasn't fantastic, but as you suggested, it could have been server related.

I really want VR to succeed in 2024 and I keep going back to it, but I feel it's like pushing a chain up a hill. My conclusion is Asobo has to get a handle on the memory footprint for 2024 otherwise I'm just wasting my time.

Continuously for a couple of weeks.

Many, including me, are having the opposite experience. With similar settings I used in 2020, my RAM usage in 2024 in VR exceeds my physical installed RAM (32G). Clearly this is an issue but why should I have to compromise appearance to run 2024 satisfactorily?