@Atlas My tips …

1. approach at an offset … eg. 500 ft off the left wing. so you can get a sense of the tanker moving “backward” in your fov as you approach

2. set g_fSmartScalingThreshold 3.0 //nautical miles

the idea here is to have things scale smoothly, within gun range (~3.0 nm) and also for flying formations, overhead-break and carrier landing patterns etc

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…

@TxMtb are you using RTT or MFDE or Helios or some other MFD-extraction software?

Looks to me like maybe something changed (inadvertently or purposefully) re the line-drawing commands, written to the shared-memory buffer.

@MaxWaldorf @Raven8tr I just hopped into TR#15 to test … I confirm, on my acmi it looks like each JSOW just impacted a single unit in the middle of the column(s) I targeted.

Is the EGEA parameter intended to be barometric MSL or AGL elevation?

The training doc implies AGL but I’m not sure. I think I left egea at the default 700ft … and iirc the target columns are at around 1200 ft elevation, so maybe that’s my problem.

@drtbkj true it’s a bit more nuanced and dimensional, than my simplified 5 levels

fyi I do see some diffs in the AFM flight model for F-18C … just diff’ing 4.35 and 4.36 folders. the changes look mostly related to gear and flaps. not sure if it addresses the flat-spin issue you mention.

@Sgt_Fresh-0 the F-18C with Viper avionics is super fun and addictive …

@Caster what version of AL?

I’m not sure if even the latest supports the throttle-axis-reverse setting of 4.36.

@Sgt_Fresh-0 there’s sortof a ladder to how jets are modelled in BMS…

L1) flyable, basic flight model and with F-16 cockpit
L2) advanced flight model
L3) custom cockpit
L4) ramp-startable cockpit
L5) special non-F16 features and avionics (eg. autothrottle) but still mostly F-16 avionics

I think F-18C and Harrier AV-8B are the only “L5” jets? Not sure.

I see Su-35 and Yak-38 have new AFM dat files, in 4.36… interesting.

Mirage 2k and the A-10 also got a lot of love and attention, in the past, but I haven’t tested them recently…

For monitors 1440p or 4k or higher, I recommend using Magnifier accessibility tool (hit [Win+NumpadPlus]) to navigate the 2D menu / setup / map screens. (hit [Win+Escape] to revert to normal).

In ‘borderless’ mode, the 3D world will snap to fill the Windows desktop / current monitor resolution and refresh rate.

@Bowser I suspect this is going to need better repro-steps… is this something you can reproduce consistently, in one of the TR missions? with ACMI recording?

hung A-A missiles should be pretty rare, I would think.

@Atlas My tips …

1. approach at an offset … eg. 500 ft off the left wing. so you can get a sense of the tanker moving “backward” in your fov as you approach

2. set g_fSmartScalingThreshold 3.0 //nautical miles

the idea here is to have things scale smoothly, within gun range (~3.0 nm) and also for flying formations, overhead-break and carrier landing patterns etc

@Caster someone else was having similar sounding problem, with Virpil CM3 throttle

https://forum.falcon-bms.com/topic/22567/throttle-wont-back-off

the “reverse” axis checkbox is new for 4.36 … it’s possible there’s a bug or quirk with Virpil throttles

@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