CTD to desktop on ITO 80's 1.06.2
-
@Seifer ok got it
I deleted all flag lines from user config as you commentedI ran the sim from launcher.exe and not from alternative launcher as before
I had some CTDs but this time was different I did not see the sim crashing like after take off like previous attempts. In fact the sim did not crash at all and the mission went on as normal !!
Had two CTD when loading a mission and only one landing the jet but definitely not like before
Here in case you want to see save mission files link text
I am feeling this is getting hopeless
-
@zamcesarc I need a fresh DMP to investigate this. Please, send me a DMP file generated by these last crashes without alternate launcher.
-
@petrouvis thanks, taking a look.
-
@zamcesarc said in CTD to desktop on ITO 80's 1.06.2:
I had some CTDs but this time was different I did not see the sim crashing like after take off like previous attempts. In fact the sim did not crash at all and the mission went on as normal !!
Had two CTD when loading a mission and only one landing the jet but definitely not like before
Here in case you want to see save mission files link text
Can you reproduce the CTD? And can you describe the steps that lead to a CTD? Sofar your savegame runs fine here
-
Hey there.
I did install Isreal theatre to a clean U3 bms… downloaded the full installer and followed instructions. However when I start the campaign, I can be in the cockpit for like a minute and then crash to desktop without any kind of error message. The game just disappears.
I checked, its not my antivirus. I am launching the game via the alternate launcher.================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_BREAKPOINT in:
0000000004705BD6 Falcon BMS.exe, AirframeClass::CalcBodyRates()+1958 byte(s), D:\WIP\bms-code\SIM\Airframe\Eom.cpp, line 553+7 byte(s)
Exception handler called in UnhandledExceptionHandler.
BreakpointBytes at CS:RIP: CC 8B 8B D8 09 00 00 83 F9 04 0F 8C 89 01 00 00Registers:
RAX=0x000000024308f501 RBX=0x000000024308f160 RCX=0x3fe0000000000000 RDX=0x000000003dc28f5d
RSI=0x000000003e3cee00 RDI=0x0000000001000083 RBP=0x000000002e73f970 RSP=0x000000002e73f870
RIP=0x0000000004705bd6 FLG=0x0000000000000246
R8=0x0000000000000000 R9=0x0000000000000000 R10=0x0000000004ece300 R11=0x000000002e73fa60
R12=0x0000000000000000 R13=0x000000000e2b58f0 R14=0x000000024307da50 R15=0x000000024308fa18
CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002BCall Stack:
0033:0000000004705BD6 Falcon BMS.exe, AirframeClass::CalcBodyRates()+1958 byte(s), D:\WIP\bms-code\SIM\Airframe\Eom.cpp, line 553+7 byte(s), Parameters(0x000000004463DB9E 0x0000000000000000 0x000000004308F160 0x00000000C0000000)
0033:000000000470A75E Falcon BMS.exe, AirframeClass::EquationsOfMotion()+158 byte(s), D:\WIP\bms-code\SIM\Airframe\Eom.cpp, line 90, Parameters(0x0000000000000001 0x000000004308F160 0x0000000040E00000 0x000000003F333333)
0033:00000000046FCD4D Falcon BMS.exe, AirframeClass::Exec()+2973 byte(s), D:\WIP\bms-code\SIM\Airframe\Airframe.cpp, line 1242+89 byte(s), Parameters(0x0000000047435000 0x0000000043043BCA 0x000000004307DA50 0x0000000000000000)
0033:00000000046B1E9A Falcon BMS.exe, AircraftClass::Exec()+1786 byte(s), D:\WIP\bms-code\SIM\Aircraft\Aircraft.cpp, line 1794, Parameters(0x000000003F4A9250 0x000000003F1C86F9 0x00000000022EF87D 0x000000004307DA50)
0033:00000000049DF0E9 Falcon BMS.exe, SimVuDriver::ExecModel()+41 byte(s), D:\WIP\bms-code\SIM\SIMLIB\simvudrv.cpp, line 31, Parameters(0x000000004307DA50 0x000000002E73FD80 0x00000000022EF87D 0x0000000000000000)
0033:0000000004AEE2A3 Falcon BMS.exe, VuMaster::Exec()+35 byte(s), D:\WIP\bms-code\vu2\src\vudriver.cpp, line 590, Parameters(0x000000004307DA50 0x0000000005205820 0x000000000E2B5AF8 0x0000000005205820)
0033:0000000004997F5B Falcon BMS.exe, SimulationDriver::Cycle()+971 byte(s), D:\WIP\bms-code\SIM\SIMDRIVE\Simdrive.cpp, line 727, Parameters(0x000000002E73FE01 0x0000000000000000 0x00000000022EF87D 0x0000000000000000)
0033:00000000049E01D7 Falcon BMS.exe, SimulationLoopControl::Loop()+1143 byte(s), D:\WIP\bms-code\SIM\SimLoop\Simloop.cpp, line 558, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x00000000049DFD60)
0033:0000000004530CFD Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), D:\WIP\bms-code\FALCLIB\ehandler.cpp, line 1588+5 byte(s), Parameters(0x0000000000000000 0x000000002D813940 0x0000000000000000 0x0000000000000000)
0033:0000000004C8F2D5 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)
0033:0000000083CE7034 KERNEL32.DLL, BaseThreadInitThunk()+20 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:00000000852026A1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) -
@BreakerHUN please describe the exact steps: which airbase, which campaign, which flight?
-
-
-
@zamcesarc thanks for the full DMP. Takiong a quick look, seems to be coming from an F4E or F4G.
Something in its airframe computation is causing a division by zero. Trying to figure this out with Tumbler.
-
By looking at the DMP, the CTD is happening when making an interpolation on the mach and alpha tables of this aircraft.
I am comparing the values I have here in my ITO install, and they are not matching what I see in the DMP.
For example, in the DMP there are only 4 mach breakpoints for the table: 5, 6, 7 and 8. In my install, there are 23 mach breakpoints.
I’m gonna try to pinpoint which aircraft it is exactly so we can determine if this is a bad install issue for some reason or a bad database for a given aircraft.
And for the record, I still cannot repro the CTD even after following BreakerHUN instructions.
-
The exact vehicle is an F-4E IAF.
Now, @zamcesarc , I need you to do some checking for me.
- Open your falcon folder.
- Inside it, navigate to
Data\Add-On Israel\Add-On Israel 80s\Sim\Acdata
- Look for a file called
F-4E IAF.dat
. - Open it with notepad.
- Inside it, look for MACH BREAKPOINTS.
Please, paste what you see in both MACH BREAKPOINTS and ALPHA BREAKPOINTS. For example, mine looks like this:
#----------------------------------------------------- # MACH BREAKPOINTS #----------------------------------------------------- +23.000000 # Num MACH # +0.000000 +0.200000 +0.300000 +0.400000 +0.500000 +0.600000 +0.700000 +0.800000 +0.850000 +0.900000 +1.000000 +1.050000 +1.100000 +1.200000 +1.300000 +1.400000 +1.500000 +1.600000 +1.700000 +1.800000 +1.900000 +2.000000 +2.500000 #----------------------------------------------------- # ALPHA BREAKPOINTS #----------------------------------------------------- +44.000000 # Num Alpha # -8.000000 -7.000000 -6.000000 -5.000000 -4.000000 -3.000000 -2.000000 -1.000000 +0.000000 +1.000000 +2.000000 +3.000000 +4.000000 +5.000000 +6.000000 +7.000000 +8.000000 +9.000000 +10.000000 +11.000000 +12.000000 +13.000000 +14.000000 +15.000000 +16.000000 +17.000000 +18.000000 +19.000000 +20.000000 +21.000000 +22.000000 +23.000000 +24.000000 +25.000000 +26.000000 +27.000000 +28.000000 +29.000000 +30.000000 +32.000000 +34.000000 +36.000000 +38.000000 +40.000000 ```
-
@zamcesarc actually please share the whole file
F-4E IAF.dat
. Strongly suspecting of a missing line. -
-
@zamcesarc link doesnt seem to work
-
@zamcesarc same here, link does not work.
-
@Seifer @Tumbler31 please try again link text
-
@zamcesarc bingo, we got it. Your file is different than mine, yours is missing the AOA Max AI line:
Now, comes the question: why this is happening?
I don’t know, but your install seems foobared. Maybe you installed an old version of ITO 1980 campaign?
The right procedure is to ONLY install the IAF mod and NOTHING else, since it already comes with the 1980 in it. Tumbler took a look at your DMP and identified that you had a different version of 1980 installed:
Maybe you installed a 1980 campaign after installing ITO? That would explain it.
The only other ways I can see for this happening is:
- you installed an outdated version of ITO;
- you installed some mod that overwrites the acdata
Or last:
- you changed the file manually?
Does any of those sounds reasonable?
-
@Seifer @Tumbler31 well thanks a lot I’m glad that that may resolve the problem
As for the installation goes frankly I am quite surprise I have two different version of ITO installed. I have no clue how that could have happened. I recently re installed Windows10 then installed BMS 4.36 from scratch and then downloaded ITO v2 via full installer. What I recalled vAiCon asked me to re write Acdata but I cant remember if I did that after I downloaded ITOv2
Do you suggest I should uninstall ITO v2 and then download again via full install steps?
https://forum.falcon-bms.com/topic/22493/israel-theater-of-operations-for-bms-4-36maybe I did not follow the installation steps correctly. Do you mind explaining what Exe means on point 3 in the below step procedure ?
-
@zamcesarc that is correct.
1- Remove your current ITO install completely.
2- Download that full installer of 1.06.2
3- Install it.At this step you are done. But given all that happened, check that your
F-4E IAF.dat
looks exactly like mine (ie you can see AOA Max Player and AOA Max AI). -