@Cop23rd what if you shut down the jet and then disable the ejection seat?

@oakdesign thanks will try

I use link cable with the quest 3, things are normal. Recommend using default settings (nothing fancy) on resolution and see if that helps.

@Tumbler31 Quest 3 with openXR

@Fearripper96 I have this issue also. But the offset is minor so I’m just flying with it

@Rainmaker

@rubbra said in 4.37.5 VR Learnings / Tips:

VR has come a long way since its introduction with 4.37, and a lot of the recommendations/tips/tweaks have evolved.

I thought it worth collating what people know in one place.

Edit - my Docs folder didn’t have the latest docs in, so a lot of the below has probably been covered in much better detail in C:\Falcon BMS 4.37\Docs\01 Input Devices\04 VR Guide\BMS-VR-Guide.pdf

This particular post contains my settings for a Pico 4 + VirtualDesktop + 4070ti, thought most of it holds true for PicoConnect with SteamVR as the OXR runtime too.

Virtual Desktop settings - Ultra (3120x3120), SSW off. HEVC encoder at 150Mbps, VDXR as OpenXR runtime.

C:\Falcon BMS 4.37\User\Config\Falcon BMS User.cfg:

# General VR-y things
set g_fVRIPDMultiplier 0.88 # 112% World Scale
set g_b3DClickableCursorAnchored 0 #No cursor anchor in 2D

# I don't use Mixed Reality
set g_bMixedRealityCockpitCoverEnabled 0 

# Cursor follows head in VR
set g_b3DClickableCursorFixToCenterIfVR 1 

# Set BMS res to 1.6x base (1.6*(3120x3120))
set g_fVRResolution 1.6

# best performance. Some find setting to 0 helps with black bars
set g_bVRParallelRenderThread 1 

# disable render to monitor
set g_bVRNoPresent 1

# VR Performance vs Visual Settings
set g_bEnvironmentMapping 1 # 0 for more performance
set g_bWaterEnvironmentMapping 1 # 0 for more performance
set g_bShadowMapping 1 # 0 for more performance
set g_bShadowOnSmoke 1 # 0 for more performance
set g_bReducePSFires 0 # 1 for more performance
set g_nCloudRotatingMethod 1 # reduce the spinny clouds

# Fixed Foveated Rendering - Pico 4
set g_bVREnableFFR 1
set g_fVRInnermostRadiiFFR 0.55
set g_fVRMiddleRadiiFFR 0.60
set g_fVRPeripheralRadiiFFR 1.00

What else do I think I know?

0. Disable OpenXR Toolkit XR layer - BMS will crash
1. Disable XRNeckSafer XR layer - BMS seems to crash
2. Never ever ever ever change values in Falcon BMS.cfg - always set in Falcon BMS User.cfg or Falcon BMS VR.cfg
3. Don’t go over 2x anti-aliasing in the game as this has little visual impact but a lot of performance impact
4. Resolution is key to reading stuff. If you can’t see, increase resolution. If it’s a slideshow, decrease resolution until you find a balance
5. if at any point you had a config line like this - set g_sPriorityFixes "all-PFIX_4K_TEXT_AND_CURSOR_USER_DEFINE_AND_APPLY_DPI" - because the mouse cursor was disappearing in 4.75 initial release, get rid of it. Seems to cause crashes on joining a server, and was strongly discouraged by Max when I had it in my config.
6. Black bars at sides of view. This seems to still be a thing for some of us on non-PCVR headsets, e.g. Pico/Quest. It’s a thing. Don’t move your head so fast. Or try dropping down your bandwidth usage for VD/QuestLink.
7. Can’t see the HUD/radio menus? Drop your visor (Alt-V)
8. BMS in VR (and also not in VR) is awesome

With the above, I get 72fps ('cos that’s what I run my headset at; can’t notice any difference at 90fps) ALL the time. Cockpit visuals are lovely, I can read kneeboards (yes, even the teeny tiny WDP font, but I mostly use EZBoards).

The image below was posted on discord by oleuzop to explain FFR:

// Fixed Foveated Rendering
set g_bVREnableFFR 1
set g_fVRInnermostRadiiFFR 0.55
set g_fVRMiddleRadiiFFR 0.60
set g_fVRPeripheralRadiiFFR 1.00 

Right, discuss! Tell me where I’m wrong, and we can all try to keep an up-to-date VR guide going.

I’ll try the FFR method for my quest 3. But with its superior sweet spot enabled by its pancake lens won’t it be harder to read MFWs by glancing down?

@Atlas does hand pass through allow you to click the virtual cockpit? If so I’m very interested in that.

@Atlas oh okay I don’t use passthrough, and don’t have a 40XX series card to take advantage of the AV-1 encoding that VD(Meta) can use. Is there a compelling reason for me to get VD link wirelessly?

@Atlas are you referring to VD (Meta) or VD (steam)? I only have the steam version right now.

Hello, I recently sold my reverb g2 and got onboard with the Quest 3. It came with a link cable so that’s what I’m using. After tweaking the settings in the debug tool I found that it works very well. With the bit rate set to 560, rift app on the PC set to 1.2x, 72Hz and BMS config set to 1.3x I can’t see any degradation of image quality compared to the sweet spot of the G2. Async frame gen is far superior to WMR so I have no issues turning that on for butter smooth frame rates. Overall very happy with the headset. P.s. I don’t have a wifi6 router so not bothering with the VD wireless approach.

See if your Autopilot is set to alt hold or pitch hold on a physical switch. If you were on AP on a previous mission and forgot to reset the switch, the next time you jump in the cockpit while on the ground you’ll get a fault.

@cougar56th For some reason after the latest Win 11 update I have started getting this device error, as well. I seem to need to stop this holographic shell every time at computer start up. besides the bat file method, is there a way to permanently stop this?

Practice practice practice. It was hard to uncage my wife’s bra at first but luckily I had BMS in VR and it forced me to find key binds by feel. God bless this Sim.

@AcidRain said in A bit of F16:

In 2022 we had a military exhibition in my city, here are a few pictures.
It’s an older block, I’m sure someone will know which one.
I hope you enjoy.

Rate my Simpit!

Having sat in the pit, Just wondering how far was the ICP away from your face? I’ll try to use that to adjust my position in VR, thank you

My G2 is still going but I’m more and more inclined for an upgrade. So interested in the quest 3, as well. My only concern is the extra workload that encoding would bring to the computer. I also only have a wifi 4 router which is probably not fast enough for wireless

Okay everyone after flying a few sorties in 4.37.4.1 it feels like VR performance has improved. I didn’t do any empirical tests so this might purely be placebo effect. It seems to be most noticeable while on the ground where moving my head in the x/y/z axis feel smoother. Interested in what others have experienced.

@Dee-Jay yes you are correct, I am in a fully lit room and lateral head movement (left/right up/down) are all registering (the cockpit does not “move” with my head). It feels more like the headset thinks my eyes are positioned on the forward face of the G2 so when I look down, the screen pitches down as normal but it also seem to move my eyes closer to my stomach. I’m wondering if there is a way in OpenXR or WMR to adjust the relative motion of looking up and down to pivot more aft ( closer to my eyes) or have less up/down movement? (Does the necksaver app have any effect?)

Hey team, does anyone else have this issue? When looking up or down it feels like the head is translating up or down by more than it should. It almost feel like the rotation axis is not centered on the eyes and instead it’s on the headset which is slightly forward if the eyes. Is there a way to configure the axis of rotation to be further back of the headset?

@William thanks for giving us an idea of how the 3080 preformed with the crystal. I have a 3080 as well and still using the reverb g2. One of the things holding me back is the prospect of having to not just get the new HMD but also needing to upgrade the GPU