I use this fog ‘feature’ to spot ground targets when they are otherwise completely invisible.

Origins of the names are interesting, and can seen as history that two cultures have in common with each other. Most South Koreans over the age of 40 can write Chinese characters. It’s part of the Korean heritage and I do not know any Korean person think less of their culture because of it. Does that give the peoples republic of China rights to claim Korea? No because other countries also speak and write Chinese. Singapore, for example. Singapore should by definition also have claim to Korea then shouldn’t them? Let’s give the OP the benefit of the doubt that they have no political agenda, and just trying to find the original meaning of the landmarks.

<p>@Foxtrot701 No politics, I’m trying to find a theater of operations that is relevant to current events for personal reasons. Last I checked Korea is still at war, people in Israel/Palestine are still dying, yet we have definitely those theaters for BMS?<br /><br />Edit: yeah I see how asking this question now can be seen as insensitive… I retract my question</p>

@robmypro oh eww no not at all, you are supposed to set AF to 16x. Your graphics card can handle it. World of difference. You’re welcome!

Just received them. They are in great condition! Thank you again I’ll take good care of them!

@Stevie I find that snowplow mode works great on tgts of opportunity.

Thank you. After testing for another few hours, here are my optimal settings (low end machine, 4790k, 16 GB DDR3 with a 3060 Ti, Reverb G2):

Steam VR resolution set to 84%
Steam VR smooth motion on
WMR for Steam VR reprojection on
WMR for Steam VR graphics card resource optimization on
WMR for Steam VR force DirectX 11 on

Config file:
set g_bVRParallelRenderThread 1
set g_fVRResolution 1.3
set g_bEnvironmentMapping 0
set g_bWaterEnvironmentMapping 0
set g_bShadowMapping 1
set g_bVRNoPresent 1

This set-up gets me pretty decent performance (airfield and in the air). jitter is kept to a minimum and the sim is enjoyable. My 2 Cents.

@Snake122 I have the reverb G2. With 110 percent scaling applied. My main concern is the apparent distance to the MFDs. Doesn’t seem like my arms would reach it even fully stretched. The pedals shouldn’t be that close to the pilot, it needs to be positioned further forward of the aircraft (deeper into the pit). The pilots model makes the MFDs look like they are just above the ankles. This is incorrect. If the pedals are deeper then the knees would go in more and below the MFDs.

Reading through this thread is both fascinating and amusing. From an outsider looking in, it’s like Einstein arguing with Hawking, over the the 9th decimal of the cosmological constant, with the majority of us not aware of any difference between the two. I commend the efforts that both sides are striving to make BMS into the most realistic flight model.

Put a small cut eraser and adhere it onto a key like Q using double sided tape and you’ll be able to reach for it with ease in VR.

@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.