Got a G2 on Saturday, followed a number of videos I've watched and saved on setting up WMR and fixing the incorrect scale setting in Steam VR to get it back to around 2160x2160ish, tested out with another VR game everything worked great.  Fired up MSFS and nothing is working right, horrible FPS, and weird "preview window" issues.  I knew "4K" would be a hit from my 3440x1440 ultrawide but I was getting like 10-14fps when I loaded in according to the dev mode and Steam FPS meters as showing in the Preview window, which also was showing a split pane view of two images side by side not just one.  Not sure what's up with that as I've seen people stream in VR with this headset and that doesn't happen.  

 

Just as frustrating is nothing in the plane seemed to work.  I don't know if it's because I was trying to use the A32NX mod and it doesn't support VR or what.  I could see the mouse cursor moving around and, because I was using lock mode, the buttons and switches would highlight as usual but I couldn't actually operate any of them.  All I could do was sit in the seat and look around.   Some of the buttons were also weirdly lit up when they shouldn't be in an off aircraft.  I don't know if I launched into VR incorrectly or what.  I loaded the sim, went into settings and toggled VR from there which switched everything from desktop into the G2.  Hoping for some kind of pointers to get me going in the right direction since apparently all the hours of YouTube videos I watched on how to set things up were a waste of time.  

For starters the Mirror (Preview Window as you call it) has always been a split of both eyes, it has been requested to change this to just One Eye like most/all other VR games and Sims in existence but Asobo have been extremely lacking on VR this past year since they included it.

Also, unless you're specifically using something that requires SteamVR (like an overlay app), then do away with that and just use WMR alone. Get the Sim running smoothly with that, then if you require SteamVR fire that up. Warning that SteamVR can cause extra performance loss and can be very unpredictable, resulting in crashes and issues whereas using WMR alone is a better experience overall.

Finally, the mouse issues in the public build are a result of poor release management from Asobo with SU7, they didn't fix the game breaking bug before release. The good news is this is partially fixed in the beta, there's still issues (mouse over a window renders control input null & void...) but generally it's working better. Unfortunately no Hotfix was released in time and MS/Asobo appear to be extremely poor in communicating when this beta will be made public. So your best bet for now is to join the beta (information over at the official forums), or just sit it out and wait.

6 hours ago, MarcG said:

For starters the Mirror (Preview Window as you call it) has always been a split of both eyes, it has been requested to change this to just One Eye like most/all other VR games and Sims in existence but Asobo have been extremely lacking on VR this past year since they included it.

Also, unless you're specifically using something that requires SteamVR (like an overlay app), then do away with that and just use WMR alone. Get the Sim running smoothly with that, then if you require SteamVR fire that up. Warning that SteamVR can cause extra performance loss and can be very unpredictable, resulting in crashes and issues whereas using WMR alone is a better experience overall.

Finally, the mouse issues in the public build are a result of poor release management from Asobo with SU7, they didn't fix the game breaking bug before release. The good news is this is partially fixed in the beta, there's still issues (mouse over a window renders control input null & void...) but generally it's working better. Unfortunately no Hotfix was released in time and MS/Asobo appear to be extremely poor in communicating when this beta will be made public. So your best bet for now is to join the beta (information over at the official forums), or just sit it out and wait.

Ok thanks, sounds like I should just be waiting for the hotfix for the control issues specifically then.  I know there was a hotfix for something VR related right after SU7 but I guess it wasn't for the mouse.  On SteamVR yes I had read that I shoudn't use that, so I was only using the WMR and even then I followed a suggestion I saw here of not having any VR "portals" open but to just load the sim then toggle on VR and the sim would automatically load WMR and connect.  Maybe I should ask then, am I look at the wrong spot for the FPS (the Mirror window)?  Is there a way to see the FPS in the headset itself?  I'm thinking maybe the fps shown in the mirror is maybe just for the mirror window or something?  I turned on dev mode and the internal FPS counter thinking that would work but it didn't.

Ok, maybe I'm not understanding the load that VR puts on the system vs a 2D monitor, or the FPS meters don't work correctly in VR (like when you pop out a gauge and FPS tanks), but I just loaded up in standard 2D mode at 3440x1440 and set render scale to 135% to simulate about 9mil pixels which is close to the 9.3 of the G2 and I'm still at about 45fps vs the 17ish I was seeing last night.  My 2D mode also has a LOT higher settings than the VR graphics settings had.  I still feel like I've done something really wrong in setting this up and/or actually trying to use the headset with MSFS.  I went and watched/re-watched about half a dozen VR setup vids including 3-4 G2 specific ones that are from within the last month or two and I can't see anything obvious I'm doing wrong.

g2's optimal rendering resolution is 3164x3092 (which is 1.43x super sampling of physical LCD panels at 2160x2160).  now this is only for one eye.  you have 2 panels to drive with your gfx card.  

so openxr render 100% and in-game render at 100% will be taxing on any hw.  this is why the in-game render has to be set to ~80% (or lower, depending on your hw and gfx settings).  

if using g2 then don't use steamvr.  you can put mfs in dev mode and turn on the fps display (you can see the numbers on the 2d screen but not in g2).

5 minutes ago, kdfw__ said:

g2's optimal rendering resolution is 3164x3092 (which is 1.43x super sampling of physical LCD panels at 2160x2160).  now this is only for one eye.  you have 2 panels to drive with your gfx card.  

so openxr render 100% and in-game render at 100% will be taxing on any hw.  this is why the in-game render has to be set to ~80% (or lower, depending on your hw and gfx settings).  

if using g2 then don't use steamvr.  you can put mfs in dev mode and turn on the fps display (you can see the numbers on the 2d screen but not in g2).

Yeah I’m not using Steam VR right now. So on the rendering are you saying 100 and 100 in sim and open XR is 3xxx by 3xxx not 2160?  Ie like how in steam VR it shows up way higher at 100%?  If so that would definite explain the fps hit and why I see recommendations of 100 in sim 70 in openXR. 

100 oxr and 100 in-game will render each eye 3164x3092.  so set 100 oxr and in-game 70 or whatever in sim and start from there.  

in-game 70% means the scenery will be drawn 2215x2164 per eye, then it will get post processed to upscaled to 3164x3092 going to the g2.

 

 

9 minutes ago, kdfw__ said:

100 oxr and 100 in-game will render each eye 3164x3092.  so set 100 oxr and in-game 70 or whatever in sim and start from there.  

in-game 70% means the scenery will be drawn 2215x2164 per eye, then it will get post processed to upscaled to 3164x3092 going to the g2.

 

 

Ok thanks.  I've been playing with it a bit.  I was trying the 100 in sim/70 in OpenXR as recommended by one channel and it seemed ok, except I was at about 22FPS.  If I go the other way, 70-80 in sim and 100 to even 200 in OpenXR I get up to 30FPS, in the A32NX which means smaller aircraft might theoretically be better but trying to tune for "worst case".  One thing that's odd, and I can't tell from Google if it's me or an issue affecting G2 users in general but stuff seems to be wavy/shimmering.  like if you're loaded in, and hit Esc to pop up the settings menus you can see that wavering, and same with right click to focus say on the PFD you can see a wavering vertically in the gauge.  Not sure if it might even be a driver issue as I just installed the latest tonight I was on an older 471.22 before.

Uhh well, realized OpenXR changes don't take effect until you close out and restart VR.  I tried that after setting the OpenXR scale to 200, it didn't go well.  So far it seems like an 85% in sim, 100% in OpenXR which gives mostly 22.5 and occasionally 30 is what I'm going to have to live with until I get a new GPU.  Oddly, FPS counter says mainthread limited which I wouldn't expect of a 5950X and a 2080 Super.  It's also not the aircraft, tried the JF turbo arrow after the A32NX (both at a smaller more regional airport) and nothing seemed to matter.  Even most of the graphics sliders didn't matter except render scale and LOD sliders.  I might just give up on VR for now in MSFS.  This sim was one of 2-3 titles I initially picked it up for anyway, so it will be disappointing, but right now my 3440x1440 UW just seems to be giving a much better visual experience.  Yes the immersion is nice, but not if it makes me sick with a blurry/shimmery display.

You should have a look to this NIS scaler mod which is a real game changer for VR, for clarity and performance:

https://forums.flightsimulator.com/t/openxr-nis-upscaling-software-release-thread/482927

Once installed, set scales to 100%FS/100%OXR and adjust NIS scale only.

Avoid using both FS and NIS sharpen, only one of them.

5 minutes ago, roland_lfor said:

 

Once installed, set scales to 100%FS/100%OXR and adjust NIS scale only.

Avoid using both FS and NIS sharpen, only one of them.

Thanks. I assume you mean 100% render in sim and 100 in openXR?  Not sure I can get away with both of those right now. With OXR at 100 moving the sim from 85 to 90 solidly knocks me down to 22.5fps which I’ve now seen is supposed to be the cause of the waviness I was seeing earlier

 

@flyinion I use this for in headset FPS:
https://flightsim.to/file/16358/shift-z-stats
 

Also I observe that the switching OFF the Raymarched stuff gives really a better fps performance, for a low visual difference.

Thanks guys. Looks like I have my weekend project cut out for me with these extra tips. I found out the wavy stuff I was seeing is due to motion reprojection while at 22.5 so I definitely need to get to 30 for sure. At this point I’m willing to turn down some of the eye candy really far if it means keeping the render scale up for clarity.