Any love for Pico4?
1 Like
Don’t have one.
But,
Only supports SteamVR.
Only supports ■■■■■■ compression.
Keep advertising features they don’t actually support on PC (hand tracking, eye tracking).
Edit: Jokes aside, if there’s something I can do with this, I will, it might just not be DLSS related.
5 Likes
I see.
It was more of a broad question as I have a 6800xt.
Thanks for your work.
I (we, the VR users) are all so grateful for your work and the time you spend on trying to get the best VR experience for everyone. Thank you so much. Sad to hear the FG won’t double frames in VR, at least not until your epiphany arrives 
- Good luck and thank you. I’m not surprised Nvidia won’t reply and find it incredibly disappointing that indie devs are left on their own to figure things out. Kind of how consumers are left to fix (some) developer’s mistakes too. Thank you
1 Like
Can you please help with setting up correctly a Varjo Aero ? Is open composite switcher needed ? I do get an error call when I set to OpenXR. I do not want to use Steam VR in MSFS. What else is needed for best performance ?
OpenComposite translates from OpenVR to OpenXR. MSFS is native OpenXR app, doesn’t require OpenComposite. Whatever you set in OpenComposite has no impact on MSFS:
After investing some time in reading this excellent manual you will feel much more in control of your VR setup.
OpenXR Toolkit setup is described here:
“Whatever you set in OpenComposite has no impact on MSFS”…apart from crashing the sim
I need to set in on Steam VR to function…but thank you for your thought and guide. 
It’s not the sim that’s crashing, it’s SteamVR itself. If you use OpenComposite system-wide install, it will break SteamVR regardless of the app. On Varjo, SteamVR is always used for the lighthouse tracking.
Just toggle the OpenXR switch in Varjo Base under the System tab. That’s all you need.
@mbucchia Hello Matthieu. As far as i know you are the only person on the planet that have so far even acknowledged the over-sensitive tracking, or so called “heartbeat shaking” of WMR headsets in Win11. If i remember correctly you’ve even sent some internal communications at some point regarding the issue. Do you have any kind of information if this issue will ever be resolved for WMR? I’m still stuck on win10 because of it and we all know that won’t be a solution for much longer. Best regards
I haven’t worked on WMR for 6+ month since my team was re-organized. I don’t know anybody who does.
Let’s be real, even 6 months ago, I was pretty much one of 2 people doing meaningful work on it. The other guy is also working on other stuff now. So I think you can guess the answer.
I assume you ask because “Over-prediction reduction” isn’t helping you enough? There is something odd about MSFS though, because this issue does not happen in other apps (or at least not all of them). I think there is something about how MSFS does frame pipelining that just increases the latency unnecessarily and confuses the reprojection (and this is what “Over-prediction reduction” helps reduce).
For Win10 vs Win11, I’m not sure what you mean. I’m on Win10 22H2 now, and I’m pretty sure the issue happens here too.
4 Likes
Thank you for your reply and also for your continuous support of the community here so far.
2 Likes
Thank you for clarification. As for the issue, no, i’m definitelly not having this issue in win10. And in win11 it was so bad (even with over-prediction) that i don’t even dare try again, that’s how immersion-breaking the issue was for me. Other users are now reporting that covering 2 of the external cameras seems to help the issue a lot, and i never have tried that when i was on win 11. Well… in any case, based on your answer, i guess us WMR users are out of options once Win10 support ends. I do agree however that this issue is by far most obvious in MSFS.
I find tracking with my new Aero less smother than with my old Reverb G1, cannot figure why, regardless how and where I position the lighthouses. Frames are also fluctuating frustratingly from 45 to 30 or even below and it does not matter how I set the so called vertical refresh rate in Varjo base (45 or 30fps seems to make no difference). If you guys have any tips on improving the experience or justifying the so much cash spent :-)… please let me know. I am running a 4090 on a 13900K oc @ 6.1, HT disabled, HAGS on. There seems to be less artefacts with Over-prediction however for some strange reason whit the Aero.
Another thought or question that I have is …does foveated rendering with eye tracking have to be “ON” in the Tool Kit if Quad View foveated is also installed ? There are so many settings and parameters to fiddle with it makes me dizzy
AFAIK Quad Views is not supported in MSFS (it is in DCS).
I noticed it immediately after switching to 11, having never experienced anything similar on 10. Personally think it’s also evident in DCS, just nowhere near the same extent to which MSFS suffers.
Over-prediction reduction makes it tolerable at least (actually not noticeable most of the time) and is very much appreciated.
1 Like
In testing my new Aero headset I noticed I do get a strange stereoscopic effect in the headset particularly noticed with bright colours and in particularly RED… but other instances as well. Object appear to stick out, similarly like going to say a 3D cinema and wearing 3D glasses.
If I close one eye the picture appears normal. With both eyes open however I see this strange effect with objects popping out of the picture. Wonder if any of you guys have experienced this problem.
AFAIK Aero has specific H/W design which results in this red colour issue. Google “Vario Aero red shift” or similar.
When using Dynamic Foveated Rendering for the Pimax Crystal, with PimaxXR Runtime and Openxr, do I need to set it to ”Minimum/Balanced/Maximum” in Pimax Play for it to work?
Or is it correct to leave it ”Off” and just set ”Allow use of the eye tracker” in PimaxXR and make the adjustments in OpenXr?
Pimax Play foveated rendering settings have 0 effect on OpenXR applications such as MSFS. So you shouldn’t worry about these settings.
3 Likes
Quest 2 user here.
Someone here had successfully use hand tracking with PMDG 737? Did you change the FS2020.cfg file? At the moment it’s almost impossible to use hand tracking with this airplane.