Crashlog - Selective Jett
-
Il try to reproduce, i have the same mission i can try again.
So yeah, MiG21 DCA A2A load, 2 radar two heat, if it matters i can get exact types.
First i was trying to jettison my centre tank but couldn’t seem to do it.Here’s the top part of the log, i think it’s too big to post (said something about cannot post - too little text(and it was a tonne));
================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
0023:044BB88A Falcon BMS.exe, SmsDrawable::StepSelectiveJettisonMode()+42 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\smsdraw.cpp, line 1394+12 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0x9BBAE66C caused an access violation.
Bytes at CS:EIP: 8B 11 8B 42 6C FF D0 A8 04 75 5C C7 44 B7 28 0CRegisters:
EAX=0x09E555E8 EBX=0x00000001 ECX=0x9BBAE66C EDX=0x049AD75C ESI=0x00000007
EDI=0x0F1C0620 EBP=0x15E3FC24 ESP=0x15E3FBE0 EIP=0x044BB88A FLG=0x00010246
CS=0x0023 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002BCall Stack:
0023:044BB88A Falcon BMS.exe, SmsDrawable::StepSelectiveJettisonMode()+42 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\smsdraw.cpp, line 1394+12 byte(s), Parameters(0x00000007 0x00000000 0x0B068C00 0x00000000)
0023:044BB799 Falcon BMS.exe, SmsDrawable::SJPushButton()+153 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\smsdraw.cpp, line 1368+5 byte(s), Parameters(0x00000001 0x00000000 0x0B068C00 0x00000000)
0023:044BADB3 Falcon BMS.exe, SmsDrawable::PushButton()+83 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\smsdraw.cpp, line 688+14 byte(s), Parameters(0x00000007 0x00000000 0x00000001 0x00000000)
0023:044BFC5E Falcon BMS.exe, MFDClass::ButtonPushed()+174 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\mfd.cpp, line 671, Parameters(0x00000001 0x00000000 0x0452B07D 0x00000000)
0023:04610177 Falcon BMS.exe, SimCBEOSB_8R()+55 byte(s), e:\wip\bms\svn\source\newrelease\sim\siminput\commands.cpp, line 4896, Parameters(0x19AE9F24 0x00000000 0x6F054366 0x00000000)
0023:71300A83 d3d9.dll, Direct3DCreate9Ex()+81326 byte(s), Parameters(0x04D208C8 0x00000000 0x00000000 0x00000000)
0023:0453417C Falcon BMS.exe, OTWDriverClass::RenderFrame()+9452 byte(s), e:\wip\bms\svn\source\newrelease\sim\otwdrive\otwloop.cpp, line 3172, Parameters(0x04D208C8 0x00000000 0x020B4F5F 0x00000000)
0023:0452F36B Falcon BMS.exe, OTWDriverClass::Cycle()+1483 byte(s), e:\wip\bms\svn\source\newrelease\sim\otwdrive\otwloop.cpp, line 543, Parameters(0x00000000 0x00000000 0x00000000 0x00000000)Top of Stack:
0x15E3FBE0: 044BB799 00000007 0B068C00 00000001 044BADB3 00000001 0B068C00 044BFC5E …K……K…^.K.
0x15E3FC00: 00000007 00000001 0AF09418 04610140 04D208C8 40659D87 3F590B13 3F590A16 …@.a…e@…Y?..Y?
0x15E3FC20: 15E3FD04 15E3FD04 04610177 00000001 0452B07D 00000001 00000008 0A8394C8 …w.a…}.R…
0x15E3FC40: 497DAD01 00000000 04D208C8 3EB6EF5E BE8A548F 00000008 00000001 04D214BC …}I…^…>.T…
0x15E3FC60: 00FFFFFF 00000143 00000055 3F88BB2E 80000000 3F880443 BFCCF0A6 C00B97E1 …C…U…?..C…?..
0x15E3FC80: 3F9C74A8 43888000 00000000 00000000 00000000 49BF41E7 498F2D14 C6CE4A61 .t.?..C…A.I.-.IaJ…
0x15E3FCA0: 462D91CD 4651992E 19AE9F20 19AE9F24 00000000 00000000 19AE9F24 15E3FCF4 …-F…QF …$…$…
0x15E3FCC0: 71300A83 19AE9F24 6F054366 497DAD01 19AE9F20 04D208C8 19AE9F24 00000015 …0q$…fC.o…}I …$…
0x15E3FCE0: C123FD46 C186700C BEFD8D42 7147B254 00000001 15E3FE84 0495BB2E FFFFFFFF F.#…p…B…T.Gq…
0x15E3FD00: 00000006 15E3FE94 0453417C 04D208C8 00000000 19AE9F20 00000001 280B0AC0 …|AS… …(
0x15E3FD20: 04D208C8 00000000 442EF109 00000001 15E3FCFC 3F19999A 3F19999A 3F800000 …D…?..?..?
0x15E3FD40: 497DAD01 00000041 FE935278 0000000C 0515DAB8 77BE88CD 15E3FD98 0815A900 …}IA…xR…w…
0x15E3FD60: 280B0458 3D79DB24 280B0458 00000000 469773FF 6F58F800 FE935278 0000000C X…($.y=X…(…s.F…XoxR…
0x15E3FD80: 0515D9C8 3F800000 FE9102A6 0000000C 0498EFF8 00000008 4B18967F 00000000 …?..K…
0x15E3FDA0: 3F19999A 3F19999A 3F19999A 3F800000 3F19999A 3F19999A 3F19999A 3F800000 …?..?..?..?..?..?..?..?
0x15E3FDC0: BF2BD075 BF3A3C37 3E1200B1 00000000 00000000 00000000 00000000 3F800000 u.+.7<:…>…?
0x15E3FDE0: 00000000 00000000 00000000 3F800000 3F5DB3D7 3F441B7D 00000006 4E5731E0 …?..]?}.D?..1WN
0x15E3FE00: 15E3FE0C FE9102A6 0000000C 0515DB58 0498EFF8 00000008 4B18967F 00000000 …X…K…
0x15E3FE20: 3F19999A 3F19999A 3F19999A 3F800000 3F19999A 3F19999A 3F19999A 3F800000 …?..?..?..?..?..?..?..?
0x15E3FE40: BF2BD075 BF3A3C37 3E1200B1 00000000 00000000 00000000 00000000 3F800000 u.+.7<:…>…?
0x15E3FE60: 00000000 00000000 00000000 3F800000 3F5DB3D7 3F441B7D 00000006 00000041 …?..]?}.D?..A…
0x15E3FE80: 15E3FE64 15E3FEFC 0496146B 00000011 00000001 15E3FF08 0452F36B 04D208C8 d…k…k.R…
0x15E3FEA0: 020B4F5F 722026E0 00000041 0000000C 00000000 00000041 FE91028D 0000000C O…& rA…A…
0x15E3FEC0: FE91028D 0000000C 0515DBA8 049A5604 28E27320 00000000 0AC94788 049A5604 …V… s.(…G…V…
0x15E3FEE0: 00000000 00000000 00000400 00000300 00000000 3F800000 7220270C 15E3FF3C …?.’ r<…
0x15E3FF00: 0496149E 00000001 00000000 0479E80F 00000000 00000000 15E3FF48 00000000 …y…H…
0x15E3FF20: 0142EF0B 00000041 049A5604 28E27320 00000000 04A066E8 FB20ECA7 15E3FF6C …B.A…V… s.(…f… .l…
0x15E3FF40: 0495A2B8 FFFFFFFF 15E3FF7C 044B159A 00000000 00000000 00000000 00000000 …|…K…
0x15E3FF60: 00000000 15E3FF54 15E3F7B4 15E3FFC4 04955FAC 049DF968 00000000 15E3FF94 …T……h…
0x15E3FF80: 0479DEB7 0479E2B0 00000000 7715339A 00000000 15E3FFD4 77BE9ED2 00000000 …y…y…3.w…w…
0x15E3FFA0: 633C4272 00000000 00000000 00000000 00000000 00000000 00000000 15E3FFA0 rB<c…<br>0x15E3FFC0: 00000000 FFFFFFFF 77C21ECD 01627886 00000000 15E3FFEC 77BE9EA5 0479DEA0 …w.xb…w…y.Call Stack Reconstruction:
0023:044BB88A Falcon BMS.exe, SmsDrawable::StepSelectiveJettisonMode()+42 byte(s), e:\wip\bms\svn\source\newrelease\sim\displays\smsdraw.cpp, line 1394+12 byte(s)
0023:0453417C Falcon BMS.exe, OTWDriverClass::RenderFrame()+9452 byte(s), e:\wip\bms\svn\source\newrelease\sim\otwdrive\otwloop.cpp, line 3172
0023:0452F36B Falcon BMS.exe, OTWDriverClass::Cycle()+1483 byte(s), e:\wip\bms\svn\source\newrelease\sim\otwdrive\otwloop.cpp, line 543
0023:0479E80F Falcon BMS.exe, SimulationLoopControl::Loop()+1375 byte(s), e:\wip\bms\svn\source\newrelease\sim\simloop\simloop.cpp, line 534Call Stack Reconstruction failed!
Compiler Options:
_MSC_VER=1500 WINVER=0x600 _WIN32_WINNT=0x600 _WIN32_WINDOWS=0x501
NTDDI_VERSION=0x6000000 _WIN32_IE=0x700 ANSI SIMD=2 Release*System Information:
‘C:\Falcon BMS 4.32\bin\x86\Falcon BMS.exe’, run by Storm.
Error occurred at 21:49:24 on 2011-09-16.
Version: Falcon BMS 4.10029 (x86)
Game is Campaign type Local
Theater terrain path: ‘C:\Falcon BMS 4.32\Data\terrdata\korea’
Operating System: Windows XP (5.1.2600) Platform 2 Service Pack 3.
Computer Name: STORM-PC Domain: WORKGROUP.
2 logical processor(s), type 586.
CPU: Pentium Dual-Core CPU E5400 @ 2.70GHz. GenuineIntel. Stepping: A Model: 7 Family: 6.
GPU 0: NVIDIA GeForce 315. Vendor: 4318. Device: 2594. SubSys: 289478475. Revision: 162.
58% memory in use:
4096 MB physical memory
1698 MB physical memory free
10094 MB paging file
7119 MB paging file free
2048 MB user address space
698 MB user address space free</c…<br> -
Crashlog say’s: “PLEASE INSERT ANOTHER QUARTER TO CONTINUE GAME”……:-P
RAM22
-
@RAM22:
Crashlog say’s: “PLEASE INSERT ANOTHER QUARTER TO CONTINUE GAME”……:-P
RAM22
Rofl, like the good old days. Where do i put it?
This crash reminds me of crashes in the past to do with non-F16 aircraft, using the systems of the 16.
-
any usb port should do…
-
Yeah, this is going to be a familiar story…
“Hey doc, it hurts when I do THIS!”
“Well, sir, don’t do THAT!”
You tried to jettison weapons from a hardpoint that the MiG21 does not have. The equivalent works fine on the F-16 because all the hardpoints are present but marked empty when there’s nothing loaded so trying to jettison nothing doesn’t crash. Trying to jettison from a plane that simply doesn’t have such a hardpoint…well that’s going to crash each time. It could be fixed but it’s not going to be a priority. At least in the short term the recommendation has to be: stick to jettison for things that the SMS does show populated (corollary thought: expect the unexpected for flying non-F16’s in this dialect of Falcon4 anyway).
-
No prob. Is there a reason i can’t jett my centreline fuel tank tho?
-
That I don’t know. Probably a non-F16 thing too – the SMS is a very F-16 specific area of the code.
-
I’ve experienced this recently: CTD when pressing S-J OSB relating to hardpoint exceeding the number associated with an non-F-16 type. With MiG-21 and the only jettisonable store is a fuel tank (AA mission) this is no problem but otherwise is a pain. It’s also annoying not to be able to S-J stores which should be jettisonable. Is it just a simple database edit of which stores can be sel-jettisoned or not and it hasn’t been configured for MiG?
Expanding on this I also got a CTD when ordering wingmen to jettison “stores” via radio message but not every time (in fact I’ve had only one such CTD in Su-7 and several successful radio command jettisons MiG-21).
-
Is it just a simple database edit of which stores can be sel-jettisoned or not and it hasn’t been configured for MiG?
-
Interesting. I’m not familliar enough with this file to understand how one would make (or even find) the MiG-21’s centerline fuel tank able to be S-J’d through the SMS page if that’s even possible.
-
If you look at acdat you will see all mig21s use rack group37 under hardpoint data section. This is for rack.dat file in objects folder. If I were to fix this, I would not use 37 from rack.dat.
I think it would be better to make a new rack definition in bmsrack.dat file and use it. I could set it up to have selectable jettison there. This is a bit of a chore and a lot to write down step by step. I have done it before though and it is possible. This would change your bmsrack.dat file and mig21 acdat files. So online might be issues if you do this. I can make a vid of this being done if you still want to do it.
-
I’m curious. It would be a JSGME toy for giggles anyway.
So group37 has 3 30 31 45 but that’s as far as I get.