Flappie

@DD_Friar This one?

Brilliant bug report. Thanks. Issue reported.

The crash seems to be related to aircraft carriers (woShip). 2024-04-11 15:55:49.364 WARNING EFFECTS2 (Main): OParticleSystem: preset '' not found in 'shipTrail.lua', using default 2024-04-11 15:55:49.744 WARNING LOG (5392): 11 duplicate message(s) skipped. 2024-04-11 15:55:49.744 INFO EDCORE (Main): try to write dump information 2024-04-11 15:55:49.752 INFO EDCORE (Main): # -------------- 20240411-155549 -------------- 2024-04-11 15:55:49.754 INFO EDCORE (Main): DCS/2.9.4.53549 (x86_64; MT; Windows NT 10.0.19045) 2024-04-11 15:55:49.756 INFO EDCORE (Main): F:\DCS World\bin-mt\WorldGeneral.dll 2024-04-11 15:55:49.758 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff8d1fe3c3c 00:00000000 2024-04-11 15:55:49.761 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'F:\DCS World\bin-mt;', symOptions: 532, UserName: 'Colin' 2024-04-11 15:55:49.763 INFO EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1 2024-04-11 15:55:49.769 INFO EDCORE (Main): 0x00000000000b3c3c (WorldGeneral): wsZonesStorage::operator= + 0xDDC 2024-04-11 15:55:49.771 INFO EDCORE (Main): 0x00000000000b789e (WorldGeneral): wsZone::load_from_state + 0x107E 2024-04-11 15:55:49.773 INFO EDCORE (Main): 0x000000000003bb1a (WorldGeneral): slot_decompose_ex + 0x8EA 2024-04-11 15:55:49.775 INFO EDCORE (Main): 0x000000000003edd7 (WorldGeneral): WorldManager::notifyBirth + 0x37 2024-04-11 15:55:49.778 INFO EDCORE (Main): 0x000000000011226b (Transport): woShip::createControlActivity + 0x12B 2024-04-11 15:55:49.778 INFO EDCORE (Main): 0x000000000011d529 (Transport): woShip::netActivate + 0x49 2024-04-11 15:55:49.778 INFO EDCORE (Main): 0x000000000011da5c (Transport): woShip::netCreate + 0x4DC 2024-04-11 15:55:49.778 INFO EDCORE (Main): 0x000000000012bbd7 (Transport): woShip::waiting + 0x3E87 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x00000000000866a2 (edCore): Mail::Reader::stream + 0x1462 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x0000000000b43f13 (DCS): SW + 0x683033 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x0000000000b6c11c (DCS): SW + 0x6AB23C 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x0000000000b4d9a1 (DCS): SW + 0x68CAC1 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x00000000008e52d1 (DCS): SW + 0x4243F1 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x00000000008a2144 (DCS): SW + 0x3E1264 2024-04-11 15:55:49.779 INFO EDCORE (Main): 0x00000000008a3873 (DCS): SW + 0x3E2993 2024-04-11 15:55:49.780 INFO EDCORE (Main): 0x00000000004a1c00 (DCS): (function-name not available) + 0x0 2024-04-11 15:55:49.780 INFO EDCORE (Main): 0x000000000284350c (DCS): AmdPowerXpressRequestHighPerformance + 0x13E1508 2024-04-11 15:55:49.780 INFO EDCORE (Main): 0x0000000000cf05ee (DCS): SW + 0x82F70E 2024-04-11 15:55:49.780 INFO EDCORE (Main): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14

It's completely broken, I won't be able to repair it. Here is its content: options = { ["miscellaneous"] = { ["autologin"] = true, }, } Sorry, but you'll have to reset all your options. At least, DCS is back on track. And you still have you custom controls, which is the most important part, I think. No idea why your options.lua got corrupted but you're not the first one.

Ensure in DCS.exe properties that you have not checked "Run as administrator".

2024-04-11 14:50:29.756 INFO EDCORE (Main): (dDispatcher)enterToState_:1 2024-04-11 14:50:29.912 ALERT Dispatcher (Main): Error starting Game GUI: [string "./MissionEditor/modules/TableUtils.lua"]:3: assertion failed! The sim explains with his own words that your options.lua file is corrupted. Try this: Browse to "Saved Games/DCS.../Config". Rename your "options.lua" file to "options.lua.bak". Start DCS. You will have default options. I'll help you with that: please attach your options.lua.bak file, I'll make my best to repair it.

Thank you for reporting this in the first place.

No news so far, I'll bump the report right away.

I don't see a CTD. Maybe DCS freezes? You were refueling, right?

Please record this in a short DCS track and attach it here.

Please attach your dcs.log (from Saved Games/DCS.../Logs).

Mate, I'm not responsible for the changelog and I'm not an ED employee. You're barking at the wrong tree. Especially since I make the effort to warn you here.

@randomTOTENtThese are two separate issues. I'll bump my old report.

This was fixed with yesterday's update.

You just need to insure that it's not limited to 10 Amps. That's what happened to another user. Gaming PCs need 16 Amps. 10 Amps is not enough and can lead to freezes/crashes.

Then you should contact ED support. Log into the DCS website, click Support, then click Create a new ticket.

I've just bumped the internal report.

You mean the "How to transfer keyless DCS modules purchased on STEAM?" procedure does not work? https://www.digitalcombatsimulator.com/en/support/faq/steam/#3303126

Hi @sjebens. What about now with today's update? I cannot reproduce the issue.

I've just bumped the internal report.

You mean polygons with more than four points? I don't think it's planned. These quad-point trigger zones had a few issues when they arrived. The one below is still present AFAIK. I expect ED devs to fix it before allowing for more complex polygon trigger zones.

As asked by SpecialK on Discord, please attach your dcs.log (from Saved Games/DCS.../Logs).

@nachinus Is your problem solved for good?

@Homelander It should be fixed with today's update.

@Jeepnaked95 Is your issue solved with today's update?