Another tool from AirTex that literally nobody asked for!

https://github.com/arithex/ThrottleOverlay/#readme

Simple WPF app to easily visualize your joystick/throttle position
Use this tool to keep an eye on your throttle axis – this is especially useful, if you have a joystick with a dodgy/crappy throttle slider like mine (or a nicer throttle that slides around your desk and isn’t fixed relative to your seat).

Changes from green to yellow as you pass through the afterburner detent…!

Get it here…
https://github.com/arithex/ThrottleOverlay/releases/tag/v1.0.2021.1005

@obi1 I don’t really know why (or if) anything about DX11 would be fundamentally slower than DX9. I think for most people, with modern hardware and higher/default graphics settings, BMS did get faster.

I think what you’re seeing is the additional complexity of the theater-world in 4.35 (more buildings, bigger airbases, things like wind turbines, etc) and also higher level of detail, and changes in the way the engine computes lighting and shadows… eg. we lost the 4.34-era “per-vertex lighting” setting which was probably a benefit on your rig.

At the end of the day, the pace of development will surely continue to put increasing load on system reqs… not less. So it seems unavoidable that every major release will drop support for someone. But I actually think the BMS team is doing an admirable job of targeting a trailing ~10 year window of hardware compatibility… not going overboard with super-high detail cockpit textures etc, which are obviously available in the community.

Especially at a time when it’s so hard/expensive to acquire high-end CPU and GPU parts.

@b0bl00i Try sheref’s set g_nCloudRotationMethod 1

I fly with this cfg, too… highly recommend it.

It eliminates the (literally) head-spinningly-fast rotation you see as you turn your head around quickly, eg. in AA or AG engagements.

Instead, the clouds rotate slowly, as you pass by / through them.

If you turn your head 90° and hold that direction, you can see them rotate, but it’s much less artificial looking… imho. (It’s not fast enough to distract from whatever SAM site or bogey you’re trying to keep an eye on.)

@jayb Seems like this is ~80% of the way to a fun, 2D top-down-scroller casual game.

Fly around, tap to steer in response to bullseye callouts… tap on a bad guy to launch an amraam.

I’d pay $1 for that in the app store … just sayin.

@airtex2019 said in U3 performance issues:

With 4.35.0 I’m getting about 27fps with 100% usage on the NVidia GPU … ~25% usage on the Intel IGP

4.35.1 => about 30fps

4.35.2 => about 38fps

4.35.3 => high 50s fps, touching 60fps (v-sync limit)

(Astonishing, really… amazing work, BMS devs.)

Not sure what’s going on with your laptop, but I didn’t confirm any regression from U2 to U3.

@chuckles BMS looks great on my 4k monitor.

With TVs, there are a couple wonky details to pay attention to… but none of this is really BMS specific (vs DCS or any other PC game)

HDR => normal HDMI 2.0 can’t carry an uncompressed 10-bit HDR signal, 4k @ 60hz, so there may (?) be some compression artifacts if your connection is 4:2:2 or 4:2:0 instead of full-fledged RGB.

Dynamic range => for whatever historical reasons, TVs often expect a “compressed” dynamic range… if your PC sends the full range of RGB values, blacks can get crushed and things (especially at night) will look very very dark

Iirc this isn’t something negotiated in the EDID handshake, so you have to set it manually on your TV (if possible) and also on your PC.

@suhkoi69 I recommend Magnifier. Built in accessibility tool.

Hit [win+NumpadPlus] to make everything 200%

Then hit [win+Esc] to close it as you launch into 3D

@kyros I agree. Seems like should be a simple code fix to not rng trees within N km of center of airbase… but either it’s not so simple, or just didn’t meet the bar for 4.36.

It’s much worse when a Patriot battery decides to park on the middle of the runway … at night … and they do collision-detect. I wonder if that has been fixed or improved… time will tell…

@jstnj Often I take advantage of the fact the TGP and FCR are pre-boresighted to one another… then find something on the FCR to boresight the mavs on.

It’s not 100% but it seems most things that generate a radar-return in GM mode are lockable by mavs, in BMS.

(In the real jet, I wonder, do you have to “lock” the mav before you can click BSGT button? Seems like it would be sufficient to just slew it to point at the right thing… any ground-stabilized target. Like a lone tree on a hillside or something. )

Somewhere on youtube I once saw a RL preflight check involving calibrating the HUD and gun-camera etc. Made me glad there are limits to the realism of BMS…

I think the Monday release announcement, combined with forum move, is the reason for the quietness. (I think U3 wasn’t mentioned on Reddit until ~Tuesday.)

Also, we are all probably busy regression-testing our personal list of bug reports… lol

@Sgt_Fresh-0
https://www.google.com/search?q=falcon bms alternative launcher
=>
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases

although it does sound like maybe you do have faulty hardware … still it’s a $500 throttle, so I too would persevere a bit

@Sgt_Fresh-0 is Virple throttle one of the ones that needs reverse direction?

this is newly supported in 4.36 … do you have that checked?

or are you running Virple software to reverse the axis direction…

@airtex2019 said in Yeachon ILS 28:

Seosan has 2 runways, still 02/20 L/R but appear updated in 4.36 world … kneeboard is correct but ATC tells me to land runway 03R

Oops no the new runways at Seosan really are 03/21 aligned. It’s the kneeboard that’s out of date, again.

@Micro_440th no WDP just stock KTO

@Micro_440th not sure if these are all already reported but I’ve noticed a few KTO airbases have been updated, and diverged from the info on the kneeboards or what ATC thinks…

Kwangju has 2 parallel runways, 04/22 L/R but kneeboard shows single runway 02/20

Taegu has 2 parallel runways, 13/31 L/R but kneeboard shows single runway 14/32

Seosan has 2 runways, still 02/20 L/R but appear updated in 4.36 world … kneeboard is correct but ATC tells me to land runway 03R

@JeffC you will need to launch BMS with the -mono command-line switch added to the shortcut

you will see lots of debugging logs spew on a black and white console window … this content is also written to a xlog file, in your User\Logs directory, eg. C:\Falcon BMS 4.36\User\Logs\2022-05-13_213112_xlog.txt

@zap737 and my standard pro-tip for 4k users… especially if running 150% or 200% dpi scaling: use [Win+NumpadPlus] to activate Magnifier, for the 2D screens

then [Win+Escape] to deactivate it, as you launch into 3D

(Sadly the 2D and 3D windows don’t play nice together, when it comes to Windows high-DPI scaling.)

@jagfour it doesn’t mean what you think … it’s a common point of confusion.

Output => which monitor will be used (if you have a multi-monitor system)

depending on your graphics mode, this often shows “1024x768” which is just the resolution of the old 2D setup/menu screens from 1990s… doesn’t affect 3D world

Resolution => how the 3D world will be rendered … except if you run ‘borderless’ in which case it will end up running as the native Windows desktop resolution and frame-rate, for the monitor you selected above.

(and I do strongly advise ‘borderless’ mode, for best stability and reliability, and with little or no performance penalty on Win10-11)

@ericfa2a @zap737 on nvidia panel I have mine set to “Application-controlled” and in BMS cfg set to 0 (default/max). Seems fine.

I don’t know what else could be interfering with that… especially exhibiting a difference between 4.35 and 4.36.

@zap737 @ericfa2a there’s a cfg variable for it … it is ‘0’ by default which means “max available” per gpu hardware.

set g_nAnisotropicValue 0                            // The max anisotropic filter value to use if anisotropic filtering is ON in the setup UI. Valid values: 0 = max available (default), 2, 4, 8, 16