BMS 4.34 crash on joining online campaign
-
We are using a dedicated BMS 4.34 server in our group and it has been pretty stable for us. After the 4.34 release, we went through a few Korea campaigns, Balkans campaign and Kuril Islands campaign before now trying Lorik’s new Korea campaigns. We fired up the Enclave campaign and flew our first mission, which all went fine. (Well, we got wiped out but BMS worked just fine ).
Upon joining the second mission, I got a CTD at “Receiving Units”. And I keep getting CTDs when joining the campaign at this same point. All the other guys can join just fine, for some reason I am now having this problem?
I tried rebooting , etc. No difference.The error log header:
================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
00000000403203FB Falcon BMS.exe, GroundClass::Init()+619 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\ground\grndmain.cpp, line 287+11 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0000000021a30088 caused an access violation. -
I had a similar issue today after changing theatre from Balkans back to KTO to match Falcon Lounge server. After joining online it would get to “Receiving Units” and go no further. Didn’t CTD so i could exit but standard KTO single player campaign’s were greyed out and i could not start a new campaign. Switching theatres again had no effect on KTO.
Only way for me to fix was to uninstall and reinstall 4.34. I figured something was broken in the KTO theatre and only way i could reinstall KTO was to redo whole program.
Sent from my SM-G930F using Tapatalk
-
We have been experiencing the exact same issue with the exact same crashlog (gndmain.cpp) over at Falcon Online to no avail while running battle for sinai campaign.
At first we believed it to be network or campaign data related but with this other report I’m not sure any more.
The odd part is if you take down the server and reload the current autosave there’s no issue until it reappears after several client reconnection attempts.
Sometimes it works fine for hours but sometimes it will occur after a much shorter period of time since the server has been brought back online.
When it happened on my end I managed to get back in after possibly 10-20 attempts over half an hour. I did manage to get back into the campaign 2d, but as soon as I left the session I would again receive the crash on receiving units. Hope it helps.
-
Please provide full crashlog and’dmp
This is likely a corrupted ground entity on server side we need to investigate
-
DMP : http://www.mediafire.com/file/ichgfet7juqbvos/2019-10-05_133847_crash.zip
2019-10-05_133847_crash :================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 00000000403203FB Falcon BMS.exe, GroundClass::Init()+619 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\ground\grndmain.cpp, line 287+11 byte(s) Exception handler called in UnhandledExceptionHandler. Read from location 00000000189fc418 caused an access violation. Bytes at CS:RIP: F3 0F 10 4C 88 08 F3 0F 11 8B D4 04 00 00 F3 0F Registers: RAX=0x000000000f896010 RBX=0x0000000047d9bfc0 RCX=0x0000000042459900 RDX=0x0000000000000001 RSI=0x000000001d81efe0 RDI=0x000000001d81efe0 RBP=0x0000000000000001 RSP=0x000000001d81ee20 RIP=0x00000001403203fb FLG=0x0000000000010206 R8=0x00000000000ffc01 R9=0x0000000000000400 R10=0x00000000000003ff R11=0x000000001d81eda0 R12=0x0000000000000001 R13=0x000000000dd03910 R14=0x0000000000000000 R15=0x0000000000000000 CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B Call Stack: 0033:00000000403203FB Falcon BMS.exe, GroundClass::Init()+619 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\ground\grndmain.cpp, line 287+11 byte(s), Parameters(0x0000000000000001 0x000000001D81EFE0 0x000000001D81EFE0 0x00000000406D212F) 0033:00000000404527D0 Falcon BMS.exe, AddVehicleToSim()+400 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simlib\simobj.cpp, line 394, Parameters(0x0000000047D9BFC0 0x000000001D81EFE0 0x000000001D81F060 0x000000004677AE9D) 0033:000000004045246B Falcon BMS.exe, AddObjectToSim()+427 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simlib\simobj.cpp, line 302+5 byte(s), Parameters(0x0000000047CBA030 0x0000000000000215 0x000000004677AE9D 0x000000004677AE84) 0033:00000000405F32D7 Falcon BMS.exe, UnitClass::DeaggregateFromData()+1847 byte(s), e:\wip\bms\svn\source\rel-4.34\campaign\camplib\unit.cpp, line 2014, Parameters(0x0000000000000000 0x000000000B08E5A0 0x000000004677AE9D 0x0000000000000000) 0033:00000000400A8A8D Falcon BMS.exe, FalconSimCampMessage::Process()+557 byte(s), e:\wip\bms\svn\source\rel-4.34\falclib\messages\simcampmsg.cpp, line 175, Parameters(0x0000000046679B30 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000040579012 Falcon BMS.exe, VuMessage::Dispatch()+98 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vuevent.cpp, line 1074, Parameters(0x0000000046679B30 0x000000000000007A 0x0000000046679B30 0x000000000000007A) 0033:000000004057801B Falcon BMS.exe, VuMessageQueue::DispatchAllMessages()+219 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vuevent.cpp, line 410+171 byte(s), Parameters(0x0000000000000000 0x000000001D81F3C0 0x000000001D8827E1 0x0000000000000000) 0033:000000004056E3D8 Falcon BMS.exe, VuMainThread::Update()+8712 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vu.cpp, line 1498, Parameters(0x0000000009C26470 0x0000000000000000 0x0000000000000000 0x00000000407F62B0) 0033:00000000404636D2 Falcon BMS.exe, SimulationLoopControl::Loop()+1794 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simloop\simloop.cpp, line 501+128 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000040462FD0) 0033:00000000400787CD Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), e:\wip\bms\svn\source\rel-4.34\falclib\ehandler.cpp, line 1583+5 byte(s), Parameters(0x0000000000000000 0x000000001A967FA0 0x0000000000000000 0x0000000000000000) 0033:000000004070305D 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:00000000A1AE7BD4 KERNEL32.DLL, BaseThreadInitThunk()+20 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:00000000A312CEE1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) Top of Stack: 0x000000001D81EE20: 0000000047D9BFC0 000000001D81EFE0 0000000047D9BFC0 000000014045A459 ...G...............G....Y.E@.... 0x000000001D81EE40: 0000000000000007 0000000140712DB8 FFFFFFFFFFFFFFFE 0000000000000002 .........-q@.................... 0x000000001D81EE60: 0000000047D9C340 000000014045A629 0000000000000000 0000000000000000 @..G....).E@.................... 0x000000001D81EE80: 0000000043C999F2 0000000000000000 0000000044D00000 0000000000000000 ...C...............D............ 0x000000001D81EEA0: 0000000000000000 0000000000000002 000000000DD03910 0000000000000001 .................9.............. 0x000000001D81EEC0: 0000000047D9BFC0 000000001D81EFE0 0000000000040000 00000001404527D0 ...G.....................'E@.... 0x000000001D81EEE0: 0000000000000001 000000001D81EFE0 000000001D81EFE0 00000001406D212F ......................../!m@.... 0x000000001D81EF00: FFFFFFFFFFFFFFFE 00000000000000FF 0000000046782740 000000014045246B ................@'xF....k$E@.... 0x000000001D81EF20: 0000000047D9BFC0 000000001D81EFE0 000000001D81F060 000000004677AE9D ...G............`.........wF.... 0x000000001D81EF40: FFFFFFFFFFFFFFFE 0000000046782740 0000000046782740 00000001405F32D7 ........@'xF....@'xF.....2_@.... 0x000000001D81EF60: 0000000047CBA030 0000000000000215 000000004677AE9D 000000004677AE84 0..G..............wF......wF.... 0x000000001D81EF80: 0000000000000000 0000000045FAE840 0000000000000000 0000000045FAE840 [email protected][email protected].... 0x000000001D81EFA0: 0000000000040000 000000FF00000003 0000000000000050 000000010000000C ................P............... 0x000000001D81EFC0: 0000000045FAE840 00000001407EAFE0 0000000046782740 0000000000000080 @..E......~@....@'xF............ 0x000000001D81EFE0: 0000000700000007 0000000045FAE840 0000000046782740 0000000000000000 [email protected]....@'xF............ 0x000000001D81F000: 000000FF10000200 0000027900000080 0000000100000000 00000004000C00FF ............y................... 0x000000001D81F020: 0000000200000000 00060D0021000527 020201F402000204 00005C0000000080 ........'..!.................\.. 0x000000001D81F040: 075D11001D81F070 000001701D81F060 0000000000000000 0000000000000000 p.....].`...p................... 0x000000001D81F060: 0000000000000000 000000FE00000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F080: 000000000000FFFF 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F0A0: FFFFFFFFFFFFFFFE 000000FF00000003 0000000000000000 0000000045FAE840 [email protected].... 0x000000001D81F0C0: 0000000009C26470 0000000000000000 0000000046782740 0000000046679B30 pd..............@'xF....0.gF.... 0x000000001D81F0E0: 000000001D81F1F0 00000001400A8A8D 0000000100000000 000000000B08E5A0 ...........@.................... 0x000000001D81F100: 000000004677AE9D 0000000100000000 0000000000000000 FFFFFFFFFFFFFFFF ..wF............................ 0x000000001D81F120: 0000000000000001 0000000000000000 0000000003FB90C0 00007FFAA310083D ........................=....... 0x000000001D81F140: FFFFFFFFFFFFFFFE 000000000A6B8F30 6941206874303031 736E656665442072 ........0.k.....100th Air Defens 0x000000001D81F160: 6C61747461422065 00746E00006E6F69 0000000003DA0EA0 0000001200640000 e Battalion..nt...........d..... 0x000000001D81F180: 0000000000000000 0000000046678010 0000000000000000 0000000000000000 ..........gF.................... 0x000000001D81F1A0: 0000000000000000 000000001CA70B00 0000000000000000 0000000000000000 ................................ 0x000000001D81F1C0: 0000000000000000 0000000000000000 0000000009C26470 0000000000000000 ................pd.............. 0x000000001D81F1E0: 0000000046678860 00007FFAA30FFC11 0000000200000019 0000000000640000 `.gF......................d..... 0x000000001D81F200: 0000000000000000 0000000000000000 0000000000000000 000000000B08E360 ........................`....... 0x000000001D81F220: 0000000000000001 0000000140710774 0000000046678860 0000000000000079 ........t.q@....`.gF....y....... 0x000000001D81F240: 000000004658D930 0000000000000079 0000000000000000 0000000140579012 0.XF....y.................W@.... 0x000000001D81F260: 0000000046679B30 0000000000000000 0000000000000000 0000000000000000 0.gF............................ 0x000000001D81F280: 000000000A6B1850 000000014057801B 0000000046679B30 000000000000007A [email protected]....... 0x000000001D81F2A0: 0000000046679B30 000000000000007A 0000000000000000 000000014056E3D8 0.gF....z.................V@.... 0x000000001D81F2C0: 0000000000000000 000000001D81F3C0 000000001D8827E1 0000000000000000 .................'.............. 0x000000001D81F2E0: 407930001D8827E1 000000001D882799 0000000000000028 0000000000000001 .'...0y@.'......(............... 0x000000001D81F300: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F320: 0000000000000000 0000000000000048 0000000000000000 0000000000000000 ........H....................... 0x000000001D81F340: 0000000000000000 0000000000000000 00000001407F62B0 00000000391AAED0 [email protected].... 0x000000001D81F360: 0000000009B22A50 00000001408E7900 000000001D8827E1 0000000000000000 P*.......y.@.....'.............. 0x000000001D81F380: 0000000000000000 0000000000000000 00000001407F7340 000000000B08EAE0 ................@s.@............ 0x000000001D81F3A0: 0000000000000000 00000001408E7900 0000000000000000 0000000000000000 .........y.@.................... 0x000000001D81F3C0: 00000001407F64F0 000000000B08EF60 000000001D81F3E0 00000001408E7900 .d.@....`................y.@.... 0x000000001D81F3E0: 00000001407F64F0 000000000B08E560 000000001D81F350 00000001408E7900 .d.@....`.......P........y.@.... 0x000000001D81F400: 0000000000000000 0000000002000002 0000000000000000 00000000E90006EF ................................ 0x000000001D81F420: 0000000007680BF0 0000000000000410 000000000000002D 0000000000000000 ..h.............-............... 0x000000001D81F440: 0000000000000410 00000000E90006EF 0000000000582410 00007FFAA3106653 .................$X.....Sf...... 0x000000001D81F460: 32303A31303A3730 000000003739302E 0000000000000001 00000000000003FF 07:01:02.097.................... 0x000000001D81F480: 0000000007680BF0 0000000007680ED0 0000000000000000 0000000000000000 ..h.......h..................... 0x000000001D81F4A0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F4C0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F4E0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F500: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F520: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F540: 0000000000000000 0000000000000000 0000000000000000 00007FFAA30FC55E ........................^....... 0x000000001D81F560: FFFFFFFFFFFFFFFE 00000000000003D0 0000000000000000 0000000000000000 ................................ 0x000000001D81F580: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F5A0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F5C0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F5E0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D81F600: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ ================================================================================ Object at RCX(0000000042459900) Data inaccessible ================================================================================</unsigned>
DMP: http://www.mediafire.com/file/335wn4zwllw8hqk/2019-10-05_134706_crash.zip/file
2019-10-05_134706_crash:================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 00000000403203FB Falcon BMS.exe, GroundClass::Init()+619 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\ground\grndmain.cpp, line 287+11 byte(s) Exception handler called in UnhandledExceptionHandler. Read from location 0000000018420418 caused an access violation. Bytes at CS:RIP: F3 0F 10 4C 88 08 F3 0F 11 8B D4 04 00 00 F3 0F Registers: RAX=0x000000000f2ba010 RBX=0x0000000046beeff0 RCX=0x0000000042459900 RDX=0x0000000000000001 RSI=0x000000001d0defe0 RDI=0x000000001d0defe0 RBP=0x0000000000000001 RSP=0x000000001d0dee20 RIP=0x00000001403203fb FLG=0x0000000000010206 R8=0x00000000000ffc01 R9=0x0000000000000400 R10=0x00000000000003ff R11=0x000000001d0deda0 R12=0x0000000000000001 R13=0x000000000dba9920 R14=0x0000000000000000 R15=0x0000000000000000 CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B Call Stack: 0033:00000000403203FB Falcon BMS.exe, GroundClass::Init()+619 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\ground\grndmain.cpp, line 287+11 byte(s), Parameters(0x0000000000000001 0x000000001D0DEFE0 0x000000001D0DEFE0 0x00000000406D212F) 0033:00000000404527D0 Falcon BMS.exe, AddVehicleToSim()+400 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simlib\simobj.cpp, line 394, Parameters(0x0000000046BEEFF0 0x000000001D0DEFE0 0x000000001D0DF060 0x000000004515353D) 0033:000000004045246B Falcon BMS.exe, AddObjectToSim()+427 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simlib\simobj.cpp, line 302+5 byte(s), Parameters(0x00000000469FB800 0x0000000000000215 0x000000004515353D 0x0000000045153524) 0033:00000000405F32D7 Falcon BMS.exe, UnitClass::DeaggregateFromData()+1847 byte(s), e:\wip\bms\svn\source\rel-4.34\campaign\camplib\unit.cpp, line 2014, Parameters(0x0000000000000000 0x000000000A3E9C60 0x000000004515353D 0x0000000000000000) 0033:00000000400A8A8D Falcon BMS.exe, FalconSimCampMessage::Process()+557 byte(s), e:\wip\bms\svn\source\rel-4.34\falclib\messages\simcampmsg.cpp, line 175, Parameters(0x000000003EE7D5F0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000040579012 Falcon BMS.exe, VuMessage::Dispatch()+98 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vuevent.cpp, line 1074, Parameters(0x000000003EE7D5F0 0x0000000000000087 0x000000003EE7D5F0 0x0000000000000087) 0033:000000004057801B Falcon BMS.exe, VuMessageQueue::DispatchAllMessages()+219 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vuevent.cpp, line 410+171 byte(s), Parameters(0x0000000044A81D30 0x000000001D0DF3C0 0x00000000000585C3 0x0000000000000001) 0033:000000004056E3D8 Falcon BMS.exe, VuMainThread::Update()+8712 byte(s), e:\wip\bms\svn\source\rel-4.34\vu2\src\vu.cpp, line 1498, Parameters(0x0000000008D187E0 0x0000000000000000 0x0000000001891851 0x00000000407F62B0) 0033:00000000404636D2 Falcon BMS.exe, SimulationLoopControl::Loop()+1794 byte(s), e:\wip\bms\svn\source\rel-4.34\sim\simloop\simloop.cpp, line 501+128 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000040462FD0) 0033:00000000400787CD Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), e:\wip\bms\svn\source\rel-4.34\falclib\ehandler.cpp, line 1583+5 byte(s), Parameters(0x0000000000000000 0x000000001C112260 0x0000000000000000 0x0000000000000000) 0033:000000004070305D 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:000000001E7B7BD4 KERNEL32.DLL, BaseThreadInitThunk()+20 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:000000001EAACED1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) Top of Stack: 0x000000001D0DEE20: 0000000046BEEFF0 000000001D0DEFE0 0000000046BEEFF0 000000014045A459 ...F...............F....Y.E@.... 0x000000001D0DEE40: 0000000000000007 0000000140712DB8 FFFFFFFFFFFFFFFE 0000000000000002 .........-q@.................... 0x000000001D0DEE60: 0000000046BEF370 000000014045A629 0000000000000000 0000000000000000 p..F....).E@.................... 0x000000001D0DEE80: 408F400000000000 0000000000000000 3FE6666660000000 0000000000000000 .....@.@...........`ff.?........ 0x000000001D0DEEA0: 0000000000000000 0000000000000002 000000000DBA9920 0000000000000001 ................ ............... 0x000000001D0DEEC0: 0000000046BEEFF0 000000001D0DEFE0 0000000000040000 00000001404527D0 ...F.....................'E@.... 0x000000001D0DEEE0: 0000000000000001 000000001D0DEFE0 000000001D0DEFE0 00000001406D212F ......................../!m@.... 0x000000001D0DEF00: FFFFFFFFFFFFFFFE 00000000000000FF 0000000044A60940 000000014045246B [email protected]$E@.... 0x000000001D0DEF20: 0000000046BEEFF0 000000001D0DEFE0 000000001D0DF060 000000004515353D ...F............`.......=5.E.... 0x000000001D0DEF40: FFFFFFFFFFFFFFFE 0000000044A60940 0000000044A60940 00000001405F32D7 [email protected][email protected]_@.... 0x000000001D0DEF60: 00000000469FB800 0000000000000215 000000004515353D 0000000045153524 ...F............=5.E....$5.E.... 0x000000001D0DEF80: 0000000000000000 000000003F3562A0 00000001408E7900 000000003F3562A0 [email protected]?.... 0x000000001D0DEFA0: 0000000000040000 000000FF00000003 0000000000000050 000000010000000C ................P............... 0x000000001D0DEFC0: 000000003F3562A0 00000001407EAFE0 0000000044A60940 0000000000000080 .b5?......~@[email protected]............ 0x000000001D0DEFE0: 0000000700000007 000000003F3562A0 0000000044A60940 0000000000000000 [email protected]............ 0x000000001D0DF000: 000000FF10000200 0000027900000080 0000000100000000 00000004000C00FF ............y................... 0x000000001D0DF020: 0000000200000000 00060D0021000527 020201F402000204 00005C0000000080 ........'..!.................\.. 0x000000001D0DF040: 075D11001D0DF070 000001701D0DF060 0000000000000000 0000000000000000 p.....].`...p................... 0x000000001D0DF060: 0000000000000000 000000FE00000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF080: 000000000000FFFF 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF0A0: FFFFFFFFFFFFFFFE 000000FF00000003 00000001408E7900 000000003F3562A0 [email protected]?.... 0x000000001D0DF0C0: 0000000008D187E0 0000000000000000 0000000044A60940 000000003EE7D5F0 [email protected].......>.... 0x000000001D0DF0E0: 000000001D0DF1F0 00000001400A8A8D 0000000100000000 000000000A3E9C60 ...........@............`.>..... 0x000000001D0DF100: 000000004515353D 0000000100000000 0000000000000000 000000001D0DF200 =5.E............................ 0x000000001D0DF120: 00000000450ECB00 000000001D0DF220 000000001CC74670 00007FF81EA8083D ...E.... .......pF......=....... 0x000000001D0DF140: FFFFFFFFFFFFFFFE 0000000000000000 6941206874303031 736E656665442072 ................100th Air Defens 0x000000001D0DF160: 6C61747461422065 00746E00006E6F69 000000001CC74670 000001C2006F0000 e Battalion..nt.pF........o..... 0x000000001D0DF180: 0000000000000000 000000003EE71010 0000000000000000 0000000000000000 ...........>.................... 0x000000001D0DF1A0: 0000000000000000 0000000003DCEF00 0000000000000000 0000000000000000 ................................ 0x000000001D0DF1C0: 00000001408E7900 0000000000000000 0000000008D187E0 0000000000000000 .y.@............................ 0x000000001D0DF1E0: 000000003EE7D580 00007FF81EA7FC11 0000000000000000 00000000006F0000 ...>......................o..... 0x000000001D0DF200: 0000000000000000 0000000000000000 0000000000000000 000000000A3E9CE0 ..........................>..... 0x000000001D0DF220: 0000000000000001 0000000140710774 000000003EE7D580 0000000000000086 ........t.q@.......>............ 0x000000001D0DF240: 00000000446C8CF0 0000000000000086 0000000000000000 0000000140579012 ..lD......................W@.... 0x000000001D0DF260: 000000003EE7D5F0 0000000000000000 0000000000000000 0000000000000000 ...>............................ 0x000000001D0DF280: 00000000096D1800 000000014057801B 000000003EE7D5F0 0000000000000087 ..m.......W@.......>............ 0x000000001D0DF2A0: 000000003EE7D5F0 0000000000000087 0000000000000000 000000014056E3D8 ...>......................V@.... 0x000000001D0DF2C0: 0000000044A81D30 000000001D0DF3C0 00000000000585C3 0000000000000001 0..D............................ 0x000000001D0DF2E0: 4078D000000585C3 00000000000585A0 0000000000000028 0000000000000000 ......x@........(............... 0x000000001D0DF300: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF320: 0000000000000000 0000000000000048 0000000000000000 0000000000000000 ........H....................... 0x000000001D0DF340: 0000000000000000 0000000000000000 00000001407F62B0 000000004464E690 [email protected].... 0x000000001D0DF360: 0000000008F08F60 00000001408E7900 00000000000585C3 0000000000000000 `........y.@.................... 0x000000001D0DF380: 0000000000000000 0000000000000000 00000001407F7340 000000000A3E9760 ................@s.@....`.>..... 0x000000001D0DF3A0: 0000000000000000 00000001408E7900 0000000000000000 0000000000000000 .........y.@.................... 0x000000001D0DF3C0: 00000001407F64F0 000000000A3E9720 000000001D0DF3E0 00000001408E7900 .d.@.... .>..............y.@.... 0x000000001D0DF3E0: 00000001407F64F0 000000000A3E9660 000000001D0DF350 00000001408E7900 .d.@....`.>.....P........y.@.... 0x000000001D0DF400: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF420: 0000000000000000 0000000000000000 0000000000000000 00000000E4087B97 .........................{...... 0x000000001D0DF440: 0000000000000000 0000000002000002 0000000000000000 0000000000000000 ................................ 0x000000001D0DF460: 31323A39303A3730 000000003337382E 000000000000002E 0000000000000000 07:09:21.873.................... 0x000000001D0DF480: 00000000000001C8 0000000002310000 0000000000000000 0000000000000000 ..........1..................... 0x000000001D0DF4A0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF4C0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF4E0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF500: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF520: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF540: 0000000000000000 0000000000000000 0000000000000000 00007FF81EA7C55E ........................^....... 0x000000001D0DF560: FFFFFFFFFFFFFFFE 00000000000003D0 0000000000000000 0000000000000000 ................................ 0x000000001D0DF580: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF5A0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF5C0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF5E0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000001D0DF600: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ ================================================================================ Object at RCX(0000000042459900) Data inaccessible ================================================================================</unsigned>
-
Khronik, could you please tell us what is the ground type of the “100th Air Defense Battalion” in your campaign (which SAM type is it)?
Is it a default KTO campaign ? If no please provide me the whole theater.
-
It’s not stock kto but rather Battle for Sinai which we currently have an event running.
Campaign Installer link sent via pm.
Thanks for looking at this.
Edit: I found another report of this issue, albeit on Battle for Balkans with the same crash log.
http://falcon-online.org/forum/index.php?topic=2903.msg32095#msg32095
User claims changing his bw settings allowed him to get all the way through to the campaign 2D without crash on receiving units. This could be a false positive repro, and more to do with chance but it is of interest.
Ironically I did get all the way through to the campaign 2D after crashing out several times on receiving units by also lowering my bw settings, but wasn’t able to on the next repro attempt (same ctd on recv units).
Could this be remotely related to some clients having bandwidth settings set to as high as 300000 for up/down? Latest instructions state to set to 80% of available BW but some clients are on fiber and have very high values set. Only the bms devs could confirm but due to the randomness of the issue but the fact that 14 players can be on the server having completely normal flights while others are crashing on receiving units would suggest it’s not specifically unit corruption, at least not from the actual data in the campaign but the server’s session itself? Maybe when specific players with very high settings (or very low) are connected to the server this occurs? This is all speculation of course as I don’t have any insight to how the network code handles these variables.
-
@Bad:
Khronik, could you please tell us what is the ground type of the “100th Air Defense Battalion” in your campaign (which SAM type is it)?
Is it a default KTO campaign ? If no please provide me the whole theater.
Yes BB all the battalions are not modified from stock KTO, no changes in the composition and in the armament used.
D. -
Yes BB all the battalions are not modified from stock KTO, no changes in the composition and in the armament used.
D.Yes right, i saw that. The only remaining issue (DB side) is related with the MB339 (i can fix if you want). I’ll also check your campaign file because last time we was in contact i was not really availalbe
-
@Bad:
Yes right, i saw that. The only remaining issue (DB side) is related with the MB339 (i can fix if you want). I’ll also check your campaign file because last time we was in contact i was not really availalbe
I just fixed after the suggestion you sent me on discord. Really appreciated Bad Boy
D. -
I just fixed after the suggestion you sent me on discord. Really appreciated Bad Boy
D.I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
-
@Bad:
I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
Hi Bad Boy
In our discord chat you told me: “I think i have a good solution for your MB939 squadron that you want the players to join first when committing into the online session. There will be at least one aircraft in this squadron (one because it is mandatory regarding the database sake) but if a stupid player forgot to join his dedicated squadron then :
first : only one MB939 will be available
second : when he will try to add a MB939 flight (add package) the MB939 will not be available in the list of available aircraft
how to do that :
remove the MB939 entry in the teplanes.lst (while the MB939 is still there in the VALIDAC.act file)”. In other words no mention for this problem.
D. -
Hi Bad Boy
In our discord chat you told me: “I think i have a good solution for your MB939 squadron that you want the players to join first when committing into the online session. There will be at least one aircraft in this squadron (one because it is mandatory regarding the database sake) but if a stupid player forgot to join his dedicated squadron then :
first : only one MB939 will be available
second : when he will try to add a MB939 flight (add package) the MB939 will not be available in the list of available aircraft
how to do that :
remove the MB939 entry in the teplanes.lst (while the MB939 is still there in the VALIDAC.act file)”. In other words no mention for this problem.
D.Hi Danguard
This sentence was a solution for your server dedicated Airbase. Not a fix for the database errors.
I’ll respond to your pm in the day
-
We have only had 1 or 2 users over the last few days that has experienced the crash on receiving units using the exact same build/version that was exhibiting the crash on receiving units earlier in the event progression. For the 1 or 2 users who reported the issue since this weekend, attempting another time corrected the issue for them.
The server has also been running for over 24hrs without a crash (1-2 reboots within 48-60hrs), with more than 30+ users flying on the server going in and out.
If this is in-fact a database problem, it sure seems very selective. I’m not sure if BMS sends all units on a client connection, but if this was in-fact db error or corruption then I would have assumed for it to be more widespread.
One factor that has changed is the number of players that were initially connected or trying to connect just after the start of the event (more than 30+ users connecting at once). Now it’s maybe 6-8 at once I assume.
I’m still at a loss of how a corrupted unit can allow some to connect without issue (at least on the first attempt) and then manifest itself persistently for others.
Possibly it has been destroyed or isn’t being sent due to the campaign progression?
@Bad:
I’ve checked your last 2.3.3 installer (the one that Khronik was pointing to me) and the MB339 database issue are still there. Do you have a most recent version ?
UCD 402 ("MB339") - Error -> Squadron and corresponding flight are using different specific types UCD 402 ("MB339") FLT - Info -> Flight is not linked to a squadron
The BFS 2.3.3 link is the same build that the crash logs were sourced from. Your suggestion concerning the MB339 came after your request for the theater link, and 2.3.3 is what is currently active on the server since the beginning of the event.
-
Could you investigate if the clients who are crashing are also maybe the ones who moved one (or more) ground units on the map.
Anyway Mav-JP will add a guard (only in MP) to not allow the client to change the battalion’s path to an objective (i mean to not “move to” anymore the battalions in MP)
-
@Bad:
Could you investigate if the clients who are crashing are also maybe the ones who moved one (or more) ground units on the map.
Anyway Mav-JP will add a guard (only in MP) to not allow the client to change the battalion’s path to an objective (i mean to not “move to” anymore the battalions in MP)
I crashed dozens of times and never in my life I had moved a ground unit on FO.
They already disabled the option to move ground units and it kept happening.
-
….
They already disabled the option to move ground units and it kept happening.
This is not working with the current 4.34 but is already fixed in our dev version
-
Please provide full crashlog and’dmp
This is likely a corrupted ground entity on server side we need to investigate
Sorry, I completely overlooked your message in the flurry of responses
Here’s a link to the full dump, log and screenshot:
https://www.dropbox.com/s/a64zhg2el221ozs/2019-10-06_213804_crash.zip?dl=0
-
Coming to the news on that topic. I was running a test today on a campaign created on the basis of the TvT setup. Most people (a handful) were stuck on receiving units. I could connect from my other computer (same router) without any trouble. It was not permanent, some could at first connect fine. Starting a TE goes well too.