Arbitrary

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.

I have only done limited testing, so it may be an issue with the location I selected and/or limited skill level... The physics didn't quite seem right; this may be intentional behavior but it also limits viability. Trying to takeoff from a player made road base on Syria just doesn't seem to be happening. When using the narrow road, it seems like the wheel that drifts off the tarmac into the grass surges forward and the wheel on the tarmac catches and twists the plane backwards on that side. Purely off road, the plane yaws a lot and sometimes suddenly noses over. I tried 5 or 6 times, crashed between 30 and 70 knots or so. Later, I caught my prop on a powerline while zig-zagging between the poles under the lines, tried to do a deadstick landing in a grassy field...the moment the wheels touched the terrain the plane tumbled over. If anyone else tries, please share your results and which map and what kind of terrain you tested along with the results.

I updated to the beta, and then it stopped outputting aircraft shakes. Settings appear to have reset themselves. I had to change it back to ForceFeel. Passes the massage test. I clicked DCS Repair Export. No luck. The log is spamming "10:01:07.3604 System.NullReferenceException: Object reference not set to an instance of an object." edit: ah, jeez. So it installs to a separate folder and screws up the linking between the non-beta and DCS, and I was launching the non-beta.

Might be related to this one as well.

null This really sucks when working in the mission editor. Why is there even this continuous login check when ED says 99.999999999999999999999999% of the player base is single player?

I was curious if this was fixed in the latest patch sans patch note. But it still seems to be present.

I just got this while working in the mission editor. Wasted a lot of time. Thank you.

Thank you. The crash remains a pain point until it is patched; if The Team could provide some insight into the root cause, we could implement some changes to the mission that may reduce/eliminate the mission crash. We would be very appreciative.

Thank you. The only annoyance for testing is that it I have no idea what is actually inducing it. It might happen more frequently with more players connected, or it might not. And like I said in the OP, it may require leaving the mission running for more than 6 hours. It is a pain point in my community because it can happen a few times in our flight nights. Other communities utilize the base mission lua and did mention crashes in discord chat.