@JollyFE

Hi,

Thanks for that and for the sound advice. I will give it a shot, though I’m not too bothered now that the problem has been identified as real. Easy work around is to never let the suicidal idiot act independantly in regards to RTB!

Kind regards
Dram.

Just flew again, same error. But at least I now know how to fix it. It’s just very annoying.

@airtex2019
I just did the test and the result is as expected:

[04:38:39.737] 19416 INPUT: SimThrottleIdleDetentForward (DOWN) [04:38:40.293] 19416 INPUT: SimXMitDec (DOWN) [04:38:41.556] 19416 INPUT: SimXMitDec (UP) [04:38:42.238] 19416 INPUT: SimThrottleIdleDetentBack (DOWN)

In the BMS - Auto.key these three key bindings look like this:

#======== WINWING Orion Throttle Base II TGRIP-F16 ======== SimThrottleIdleDetentBack 512 -1 -2 0 0x0 0 SimThrottleIdleDetentForward 512 -2 -2 0x42 0x0 0 SimXMitDec 532 -1 -2 0 0x0 310

So I basically move my throttle out of the cutoff position and that also triggers SimXMitDec.
But why?

@williang83 said in Crash to Desktop BMS 4.37.3:

@tiag haha fair! The point was just to report a something that could be improved to make the software more stable and avoid crashing due to bad usage

This is BMS, almost guaranteed that @tiag found and fixed another 4 issues when fixing this, so win win win win win 😁

Only lose, more U4 “delay” 😤

I just realized that my link contents had permission locked

@Icarus sorry forgot to unlock to everyone

I’ve also seen this happen in campaign, same scenario as above. Returning to base and the home base isn’t landable and ATC diverts me to alternate and the steerpoint automatically swaps over. I dismissed it as me doing something when I happened to me.

@gankailer so of course what you (and our pilots) are seeing shouldn’t be happening at all but this work-around is for any time you see the problem. From what i recall its NOT a “do it once and then you are good for the mission” kind of thing.

@MailMan This is also happening to me. Try to switch from A/G or A/A to NAV an back again. For me this sortes it out…

@cuisinart8 said in AGM-65D application hang:

@drtbkj
This is the first time it’s ever happened to me, too. I’m beginning to suspect it’s something to do either with the A-10’s systems in general or my install itself. I’ve flown 3 more missions and fired off around 12 mavericks and had no issues with those, but now ran into another CTD when attempting to switch from CCIP to CCRP on Mk 82s.

EDIT: Tried reinstalling just in case with a completely fresh download. Still getting the same issues. I’ve tried to replicate them in the F16C-50 and have been unsuccessful so far.

Hi, I am going to test this today in OFM, in both the A-10C and other jet(s).
Update:Tested in f-18C,fired multiple Mav-D’s in BORE. No ctd

@airtex2019 Thanks! This will be a nice addition.

@jgoodman
Hmm No registry tricks should be needed under Wine, can you tell me how do you launch AL/BMS?
I suspect you’re trying to run BMS from different (default?) wine prefix than it is installed.
Also which wine-mono version is installed in your system?

@Showboat_mass I use Google drive

@tiag I didn’t frag the flight by mistake, nor was it done in MC. I believe it’s the engine that generated it.