Arbitrary

After a lot of testing: 1/ it might be limited to some RED ground units, as it didn't happen in the tests that I conducted with all ground replaced with M-113, or all ground replaced with BLUE ground units. 2/ current suspects might include: Kub 1S91 str Kub 2P25 ln RPC_5N62V S-200_Launcher SA-11 Buk CC 9S470M1 SA-11 Buk SR 9S18M1 3/ Disabling EVASION_OF_ARM on SAM units allowed one test mission to run nearly 12 hours; test terminated without triggering the edcore.dll access violation. So it might be more rare or simply not happen with blue ground units; might be limited to one or more red ground unit (not limited to the list above).

-Tested with no HMMWV and no T72B/T72BU/T80/T90 (replaced with M113 BTR_D and T-55), UH-60A replaced with UH-1H, removed all infantry class units to see if resolved...no luck. -Tested without Stennis and without Tarawa (all naval assets removed). No luck. It ran longer, but that may just be random chance. -Tested without naval assets and with Mi-28, Ka-50, Mi-24V, Mi-24P replaced with AH-1W; Mi-26 and Ka-27 replaced with UH-1H. Also removed CRAM. No luck. -Tested with the above helicopter changes and naval asset removal, but also replaced RED JF-17, MiG-23MLD, MiG-25PD, MiG-25RBT, MiG-27K, MiG-29A, MiG-29S, MiG-31, Su-24M, Su-25/T/TM, Su-27, Su-30 with F-16; Tu-160, Tu-95 replaced with F-18 SLAM-ERs; Tu-22M replaced with F-4; IL-78M replaced with KC-135 MPRS. No luck.

I started down that path, but have not yet taken it to its conclusion (I will get to it eventually). Over the past week I have run many many tests, still reproducing the same ED Core DLL bug. -Tested with no SA-11 (replaced with SA-6) to see if resolved...no luck. -Tested with no SA-10 (replaced with SA-2) to see if resolved...no luck. -Tested with no NASAMS (replaced with SA-6) to see if resolved...no luck. -Tested with no SA-19 to see if resolved...no luck. -Tested with no SA-15 to see if resolved...no luck. -Tested AI Hellfire Ks to see if resolved...no luck. -Tested with no Su34 Su25TM (replaced with player variant F-16) to see if resolved...no luck. -Tested with no Su34 Su25TM Su30 MiG31 (replaced with player variant F-16) to see if resolved...no luck. -Tested with no Su34 Su25TM Su30 MiG31 Su25T Tu95 Tu160 (replaced with player variant F-16 and F-18) to see if resolved...no luck. -Tested with no HMMWV and no T72B/T72BU/T80/T90 (replaced with M113 BTR_D and T-55) to see if resolved...no luck. -Tested with no HMMWV and no T72B/T72BU/T80/T90 (replaced with M113 BTR_D and T-55) and then with UH-60A replaced with UH-1H to see if resolved...no luck.

Does The Team have any suggestions for areas to test based on the crash dump? I ran ~10 test over the past 2 days and still have not narrowed it down. I understand The Team haven't infinite resources, but any help can be reciprocated by the community so that we can hopefully get to the bottom of this. -Tested with NO SA-11 to see if resolved...no luck. -Tested with NO SA-10 to see if resolved...no luck. -Tested with NO NASAMS to see if resolved...no luck. -Tested with NO SA-19 to see if resolved...no luck. -Tested with NO SA-15 to see if resolved...no luck. -Tested with NO AI Hellfire Ks to see if resolved...no luck.

I tested removing SA-11 only, no luck. I tested removing SA-10 only, no luck. I tested removing NASAMS only, no luck. Will run some more tests later.

Yeah, that is an odd thought. It would be effectively spread across all modules, much like the modern assets, not linked to a single aircraft.

Roll the asset pack cost into the price of the aircraft please. You are needlessly fracturing multiplayer with (micro? macro?) transactions. The announcement at the end of May seemed like you had corrected course, but now you are completely walking it back.

2025-07-27 02:13:33.337 INFO EDCORE (Main): try to write dump information 2025-07-27 02:13:33.377 INFO EDCORE (Main): # -------------- 20250727-021333 -------------- 2025-07-27 02:13:33.379 INFO EDCORE (Main): DCS/2.9.18.12722 (x86_64; MT; Windows NT 10.0.22631) 2025-07-27 02:13:33.381 INFO EDCORE (Main): D:\DCS World Server\bin\edCore.dll 2025-07-27 02:13:33.383 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffbe47bb30a 00:00000000 2025-07-27 02:13:33.384 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\DCS World Server\bin;', symOptions: 532, UserName: 'user' 2025-07-27 02:13:33.386 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 2025-07-27 02:13:33.388 INFO EDCORE (Main): 0x000000000001b30a (edCore): LinkBase::Set + 0x1A 2025-07-27 02:13:33.390 INFO EDCORE (Main): 0x00000000000dc604 (Transport): woCar::checkMissileThreat + 0x84 2025-07-27 02:13:33.392 INFO EDCORE (Main): 0x00000000000bedd8 (Transport): wcColumn::GetLastWaypointId + 0x1C8 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000004508 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3D8 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000a644ed (DCS_server): SW + 0x44D3ED 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000a641c4 (DCS_server): SW + 0x44D0C4 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000a87b39 (DCS_server): SW + 0x470A39 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000a3c844 (DCS_server): SW + 0x425744 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000000a3de83 (DCS_server): SW + 0x426D83 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x0000000002584cf0 (DCS_server): AmdPowerXpressRequestHighPerformance + 0x107ECEC 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x00000000010c5632 (DCS_server): SW + 0xAAE532 2025-07-27 02:13:33.393 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-07-27 02:13:33.654 INFO EDCORE (Main): Minidump created. Looks like the same bug as in the OP is still happening. Same mission file I shared with BIGNEWY in a PM before.

Edit: disregard; after another test and closer inspection, what I originally had in this post was determined to be an entirely different bug. removing to avoid mixing up of issues.

During earlier testing I ran the Cold War unit set on Syria without any crashes after 36 hours of continuous runtime. So it might point to something on Caucasus and/or the modern unit set, or might be completely unrelated.

2025-07-11 05:15:43.437 INFO EDCORE (Main): try to write dump information 2025-07-11 05:15:43.467 INFO EDCORE (Main): # -------------- 20250711-051543 -------------- 2025-07-11 05:15:43.469 INFO EDCORE (Main): DCS/2.9.17.12034 (x86_64; MT; Windows NT 10.0.22631) 2025-07-11 05:15:43.471 INFO EDCORE (Main): D:\DCS World Server\bin\edCore.dll 2025-07-11 05:15:43.473 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffbdfa6b55a 00:00000000 2025-07-11 05:15:43.475 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\DCS World Server\bin;', symOptions: 532, UserName: 'arbitrary' 2025-07-11 05:15:43.477 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 2025-07-11 05:15:43.479 INFO EDCORE (Main): 0x000000000001b55a (edCore): LinkBase::Set + 0x1A 2025-07-11 05:15:43.480 INFO EDCORE (Main): 0x00000000000dc0b5 (Transport): woCar::checkMissileThreat + 0x85 2025-07-11 05:15:43.482 INFO EDCORE (Main): 0x00000000000be4d5 (Transport): wcColumn::GetLastWaypointId + 0x1B5 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x000000000000461b (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000004c42 (World): wSimCalendar::DoActionsUntil + 0x262 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000a5d51a (DCS_server): SW + 0x4453FA 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000a5d1f1 (DCS_server): SW + 0x4450D1 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000a826c2 (DCS_server): SW + 0x46A5A2 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000a36964 (DCS_server): SW + 0x41E844 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000000a38023 (DCS_server): SW + 0x41FF03 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x0000000002576d08 (DCS_server): AmdPowerXpressRequestHighPerformance + 0x107BD04 2025-07-11 05:15:43.483 INFO EDCORE (Main): 0x00000000010bd38e (DCS_server): SW + 0xAA526E 2025-07-11 05:15:43.484 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-07-11 05:15:43.701 INFO EDCORE (Main): Minidump created. Looks like this is the same bug as initially reported. Didn't know dedicated server produced tracks. Please see attached. e: looks like it took ~4 hours to trigger it. 2025-07-11 01:23:52.954 is miz load 2025-07-11 05:15:43.437 is crash pop-up dcs.log-20250711-051543.zipserver-20250711-102353.trk

I haven't been running it, but I will fire it up again to test.

Just sitting in the dirt next to the taxiway at Al Dumayr, the tail wheel (unlocked) was jumping and jittering and jerking all over despite being otherwise stationary. I could throttle up to 100% without the plane rolling or nosing into the dirt (no brakes applied). Something is fishy. In other situations, like if the brakes were applied at that throttle setting, it would tip forward and wreck the prop. e: I have attached a screenshot of the situation; throttle and prop pitch reduced while trying to take the screenshot

2.9.2 update seems to have broken my Export.lua again

Yes, I have a fair bit of experience with road landings and off road landing in several aircraft. This is dissimilar behavior.