Solved [4.36] [Crash] Crash when trying to jettison
-
Hey,
I tried to jettison (just pressed the jettison button on the left console) a GBU31A that was dropped but still remained on the aircraft somehow, I know it was still there because I still had to trim it out (and I saw it attached from external view) but as you can see it’s not in the INV.0033:00000000048601FA Falcon BMS.exe, FireControlComputer::Exec()+1386 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\FCC\Fccmain.cpp, line 589+15 byte(s), Parameters(0x0000000030E4F2F0 0x00000000FFFFFFFF 0x000000000920F650 0x0000000000000002) 0033:00000000046B1524 Falcon BMS.exe, AircraftClass::DoLogic()+13892 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\Aircraft\Aircraft.cpp, line 3650+12 byte(s), Parameters(0x0000000000000001 0x0000000004F51840 0x0000000000000003 0x0000000004F51840) 0033:00000000049CBD2D Falcon BMS.exe, SimulationDriver::Cycle()+3869 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\SIMDRIVE\Simdrive.cpp, line 825+12 byte(s), Parameters(0x0000000000000001 0x0000000000000003 0x000000001850B9E0 0x0000000004F527A8) 0033:0000000004A1A84B Falcon BMS.exe, SimulationLoopControl::Loop()+2459 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\SimLoop\Simloop.cpp, line 558, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x000000001C8105DB) 0033:00000000045113DD Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), E:\WIP\BMS\SVN\Code-4.36\FALCLIB\ehandler.cpp, line 1588+5 byte(s), Parameters(0x0000000000000000 0x0000000030265720 0x0000000000000000 0x0000000000000000) 0033:0000000004E2BA19 Falcon BMS.exe, thread_start<unsigned int (__cdecl*)(void * __ptr64)>()+93 byte(s), d:\th\minkernel\crts\ucrt\src\appcrt\startup\thread.cpp, line 115+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
-
I don’t know what would cause a crash here.
But for hung weapons I would like to refer to this video:
-
@Amadeus75 Thanks for the info. But I’m not sure that this is the case here, because in the video you can clearly see the “Hung store 4”, whereas you can’t see it in my screen shot.
And that’s also probably the reason why it crashed. -
@JaZzBrE said in [4.36] [Crash] Crash when trying to jettison:
Hey,
I tried to jettison (just pressed the jettison button on the left console) a GBU31A that was dropped but still remained on the aircraft somehow, I know it was still there because I still had to trim it out (and I saw it attached from external view) but as you can see it’s not in the INV.Do you have a repo case? And please enable full dumps(https://forum.falcon-bms.com/topic/20866/enabling-dump-files-at-all-times-and-creating-frozen-game-dump-files) and share the dump file
-
@Tumbler31 sadly no repo case.
I haven’t enabled large dump filles yet, mine are only 160mb, do I attach them directly or do you have some other method? -
@JaZzBrE zip it and put it on onedrive/gdrive/etc
-
-
-
@Tumbler31 I did enable the huge crash dumps now. And I re-checked the post - I had everything but in the user config (as initially stated) so I’ll move them to falconbms.cfg instead and we’ll see what happens.
The last two crashes I reported happened one after the other, both when going on DEAD missions with GPS/INS guided weapons, so we’ll see.
But of course from my experience bugs never want to appear when you’re searching for them, you have to forget about them and they maybe appear again hah.
Thanks! -
@JaZzBrE thanks for enabling the full dumps. When you mention INS/GPS weapons, it hints to the store damage change that be should disabled. But let’s see how it goes now, thanks again for your updates.
-
@Tumbler31 Thanks, I just played two sorties without a problem, doing the same thing as I did when it crashed, so it seems the flags in the cfg fixed it.
-