OK, here’s the timeline:

2004: I was contracted by Fighter Ops (remember them??) to develop a realistic model for g-forces on the human body. I worked with an aviation medic who had done studies in that area, and together we wrote a really good simulation of G-LOC and vision/muscle impairment. Probably the most detailed such simulation that’s ever been written for a desktop sim. We all know what happened to Fighter Ops, though.

2010: I figured I shouldn’t let my hard work go to waste, so I offered up the research (but not the code) to the Falcon BMS team. The forum post went mostly unnoticed…

2012: @Dee-Jay contacted me asking for the link to the research, which had expired by that point. I never noticed this chat message.

2021: Falcon BMS gets new forums, and the chat messages are migrated over. I finally notice his post!

So, Dee-Jay, and anyone else on the team who’s interested, here is the correspondence between myself and the aviation medic, including some charts and tables. It’s not all there, some of it is gone forever now, but hopefully what is there helps you guys out.

https://www.dropbox.com/sh/b2uocw0lfkir526/AADzQTJMHx-57ez9CGc6Wqzva?dl=0

@Kavelenko Because we want UHF on the left, not the right.

Mouse in one eye is a known issue with all VR headsets so far. JHMCS in one eye is realistic.

Mouse in one eye is a known issue with all VR headsets so far. JHMCS in one eye is realistic.

@Tumbler31 Unfortunately, that didn’t do the trick. I launched BMS Launcher, reset the throttle axes to be unassigned, quit and relaunched BMS Launcher, bound the two throttle axes, inverted them, and set the detents.

The idle detent still works backwards. Moving the throttle backwards through the detent causes the in-game throttle to move to the idle position, and moving the throttle forwards through the detent causes the in-game throttle to move to the cutoff position.

Giving this topic some visibility outside of the Virpil forums, since I suspect it is a bug in BMS generally: https://forum.falcon-bms.com/topic/25023/inverted-throttle-idle-detent-not-working?_=1681530515058

Re: Virpil CM3 Throttle inverted axis

Just as a heads-up, 4.36 now allows for inversion of throttle axis

This is indeed true, however, when using the CM3 Throttle with the axis inverted in BMS (not in VPC Configurator), the idle detent doesn’t work.

Moving the physical throttle forward past the idle detent threshold causes the virtual throttle to go back into the cutoff position. Moving the physical throttle aft past the idle threshold causes the virtual throttle to move forward into the idle position.

I think the function of the idle detent threshold needs to also be reversed if the axis is reversed.

Some current bugs in VR, in case they haven’t already been reported:

• External views (e.g., missile view) sometimes make you go cross-eyed. I think the fix for this is to remove all zoom in external views. Should be 1:1 zoom just like in internal views.
• External views rotate too much to follow the aircraft. Stabilize the camera and let the aircraft rotate independently.
• Join/leave/screenshot messages are outside of the render area (Varjo Aero).
• Loading images (pies) are rendered much larger than the viewport prior to entering 3D mode. They should be scaled to fit the viewport.
• Likewise, with g_bVRNoPresent off, the rendered image on the monitor is much larger than the screen size.

And some QoL fixes I recommend:

• Route cockpit intercom sounds to a different audio device than exterior ambient sounds.
• Add an option to position audio sources according to head position (for people who use their headset for all audio output), and an option to position audio sources according to rotational origin (for people who use their headset for cockpit intercom audio only).

Thanks!!

Dogfight mode, 1v1 vs Ace J-20. 6x F3, 2x all-aspect F2, ECM on, unlimited guns. Random strategy, 25000 ft, 60 NM distance. Crash occurred after committing while loading 3D world.

https://mega.nz/file/HtoCRLYJ#p-P4S1OEzhGl6dbPgTj8249HoQ830NOWTj6aP_lSqJM

With U1 out, do we still want to disable water/environment mapping to avoid crashes/graphical glitches due to excessive draw calls? Or has that been fixed?

Hey, I have occasionally had issues launching my second HARM. I pickle but it doesn’t come off the rail, and I get a “HUNG STORE” message on the SMS page. Max G indication was 4.0 and no PFL messages present. Ideas? Happens in HAS mode.

@Wolfman I’m referring to AI comms.

@Kavelenko Because we want UHF on the left, not the right.