@jagfour what window size are you looking to achieve?

If you select a resolution smaller than your native monitor, on the Setup/Graphics screen, it should apply to window size

No other way to hand select a custom window size … without hex editing the d3d11.dsp file

@jagfour you can delete your d3d11.dsp file, which stores window coords – BMS will recreate it

or run \Falcon BMS 4.37\Launcher\BmsDisplayConfig.exe to recreate it

@Dram said in BMS 4.37.8 Strange MFD behaviour in SP:

found that the FIX has been overwritten and that reapplying it solves the issue.

Just to be clear – you are not reapplying a fix, you are disabling a fix by changing that flag. I suppose it depends on one’s pov.

If I remember correctly, disabling the MFD updates while external view is active, was a crude but necessary fix, to prevent a severe crashing bug – please do not revert that bugfix.

@Browning do not spend money on anything with a single hat switch, like T.16000m

for the F-16, you want at least 3 four-way switches

Radar/MFD, TMS, DMS, CMS … plus trim … you can get by with using shift-layer for some of those, but not all

I think the VKB Gladiator NXT is still the best option for not too much money. I think pairing it with the TM throttle is a popular combo … maybe shop used market if budget can’t be stretched

@Karen I agree it’s a nice feature … on my list to make that separate from XInput, but not a top priority

in meantime, [shift+3] will show the “SA bar” which has a throttle indicator (I think it’s mislabeled “rpm”) at least it works for single-engine jets… I think still broken, for dual engine

there’s also external overlay apps like https://github.com/arithex/ThrottleOverlay/ (made by me, before I joined the dev team) … also only shows a single axis

Step 1 is to replace the contents of Config folder, as you’ve done

Next step … you’ll need to copy or rename the Setup*.xml files

The names of these files, include device-identifiers that are generated by Windows. These IDs will be new, on a new install … and this can sometimes happen even when unplugging/replugging … especially if different USB hubs are used, etc.

So in your old Config you’ll see maybe eg.

Setup.v100. VKBsim Gladiator NXT R SEM  {A9157640-B283-11EE-8001-444553540000}.xml

But in your new Config you’ll see same product name but different ID, maybe eg.

Setup.v100. VKBsim Gladiator NXT R SEM  {B0268751-B283-11EE-8001-444553540000}.xml

Copy the old files over the new files (rename the old file(s) to match the new ones).

Be very careful to preserve the spacing and punctuation, and capitalization, exactly.

hth

@the_tr00per

in Falcon BMS User.cfg

set g_nMinFrameTimeMs 16 // 16ms == 60 fps

@Machtoo probably requires OpenTrack to adapt it to TrackIR-compatible games like BMS

(? not sure)

@Machtoo looks like they have an open-issue on this
https://github.com/HeliosVirtualCockpit/Helios/issues/151

@xellophane oh you may be on to something there

The files are ID’d by DirectInput device id, which can sometimes change, on Windows, when moving USB plugs around… different hubs etc.

Haven’t heard of this being a problem on wine, but I haven’t tested it myself

@xellophane well you’ll have narrow it down

which files are getting reset? (keep a backup copy of the entire User/Config folder, and keep an eye on their timestamps)

are you using the Launcher to set the key, button and axis bindings?

Here are the most relevant files to keep watch on…

Setup*.xml – files saved by the Launcher

BMS-Auto.key – if you’re using the launcher … if not, monitor whatever key file you’re using
DeviceSorting.txt

{Callsign}.pop

@xellophane are you running SimAppPro in that wine container?

I hear folks have that same problem with it, on Windows

Fascinating, if it’s also true on Linux

@Alfred can you just tell us, what version you have?

(it’s in the lower-right corner of the screen … or you can right-click the Falcon BMS.exe file and click Properties/Details)

@Machtoo sorry I’m no expert on Helios, but I suppose I am on Windows dpi scaling – does Helios run as admin? If so you probably need to set the appcompat flags for both current-user and machine-wide / admin-user.

(Probably always a good practice to set appcompat flags for both machine-wide and current-user, to keep them consistent. I can’t ever remember which one overrides the other, if they differ.)

(Do this on the Helios exe … below I’m showing the setting for Falcon BMS exe)

The docs are not wrong but the math for the curve is very aggressive… I recommend a value of 2 or 3

Anything higher is a pretty sharp hockey stick.

@kungfoo will reply in DM

@lixus your stack-trace is from a thread owned by the TTS (TextToSpeech) component

not sure if or how that is related to the problem of RendererD3D11::createDeviceOnAdapter() failing

@lixus said in "Could not create device on adaptor":

[00:00:00.000] 13180 Please run without a graphics debugger attached.

This was a weird quirk/bug affecting HP Reverb G2 owners on Win11, iirc, over a year ago.

But if you don’t fit that profile… not sure. Try DxCpl.exe / D3DConfig.exe to ensure you don’t have debug layers enabled. Or if you have RenderDoc or some other similar graphics debug layer installed…

@fvelazdem

@Tomahawk ramp-start or taxi or in-flight?