Jump to content

Recommended Posts

Posted (edited)

Since the update a mission that was working fine now crashes when run on our dedicated server.

The same mission when run from my machine using the Mission / start multiplayer option works fine.

So assume issue with Dedicated Server now for some reason.

The mission uses the DML tool box by @cfrag which has previously caused no problems.

Does the dedicated Server now handle scripts differently?

 

EDIT I was typing this when the patch update was announced

dcs.log-20240411-170318.zip DDServerPersianGulf-1000hrs.miz

Edited by DD_Friar

Visit the Dangerdogz at www.dangerdogz.com. We are a group based on having fun (no command structure, no expectations of attendance, no formal skills required, that is not to say we can not get serious for special events, of which we have many). We play DCS and IL2 GBS. We have two groups one based in North America / Canada and one UK / Europe. Come check us out. 

  • ED Team
Posted

Hi, Ive moved the post to the crash area it will be more visible here for checking and wont get lost in the update thread 

 

@DD_Friar can you attach the dcs log from the server it does not seem to be in the zipped files 

 

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

I wondered where it had gone! 🙂

I will find the post and attached it there.

many thanks

 

Opps, I see this IS the Crash thread. I have attached one of the other zip files I got today that seems to have all the required files

dcs.log-20240411-155549.zip

Visit the Dangerdogz at www.dangerdogz.com. We are a group based on having fun (no command structure, no expectations of attendance, no formal skills required, that is not to say we can not get serious for special events, of which we have many). We play DCS and IL2 GBS. We have two groups one based in North America / Canada and one UK / Europe. Come check us out. 

Posted

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

 

---

Posted

@BIGNEWY - SOLVED! - The issue was a zone linked to the carrier. I took that out and the mission now loads on the dedicated server.

Visit the Dangerdogz at www.dangerdogz.com. We are a group based on having fun (no command structure, no expectations of attendance, no formal skills required, that is not to say we can not get serious for special events, of which we have many). We play DCS and IL2 GBS. We have two groups one based in North America / Canada and one UK / Europe. Come check us out. 

Posted (edited)

Yes, deleted that and the mission loaded

Edited by DD_Friar

Visit the Dangerdogz at www.dangerdogz.com. We are a group based on having fun (no command structure, no expectations of attendance, no formal skills required, that is not to say we can not get serious for special events, of which we have many). We play DCS and IL2 GBS. We have two groups one based in North America / Canada and one UK / Europe. Come check us out. 

  • 6 months later...
Posted

I have a mission on server that just gave me a CTD to my desktop with the same shipTrail.lua being called multiple times. I have 2 carrier groups and some armed speed boats in mission but no trigger zone for the carrier to go through. No trouble loading on server and fixed wing seemed fine the other day. Flying Apache and got the CTD after about 20 minutes in and about 2-3 minutes after destroying speedboats with hellfires. Anything else that could be causing it? Unfortunately I loaded DCS again so log is no longer available

Intel i9-13900k, Asus Z790-E Gaming Wi-fi 2 motherboard, 64gb Corsair Vengeance LPX DDR5-6400 RGB ram 2x32gb XMP2 profile, 4TB Crucial T700 PCIE 5.0 SSD internal, 2TB Crucial T700 PCIE 5.0 SSD internal, Asus ROG Strix OC GeForce RTX 4090, Corsair 7000X Case with 5 x 120mm side mounted intake fans and 3 x 140mm top mounted exhaust fans, 1 x 140mm rear mounted exhaust fans, front mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in 3 push, 3 pull intake configuration, 1 x 32" Samsung 3840x2160 display, 1x 32" Asus 2560x1440 display, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Posted
8 hours ago, 104th_Money said:

I have a mission on server that just gave me a CTD to my desktop with the same shipTrail.lua being called multiple times. I have 2 carrier groups and some armed speed boats in mission but no trigger zone for the carrier to go through. No trouble loading on server and fixed wing seemed fine the other day. Flying Apache and got the CTD after about 20 minutes in and about 2-3 minutes after destroying speedboats with hellfires. Anything else that could be causing it? Unfortunately I loaded DCS again so log is no longer available

That's likely a case of your anti-virus getting too horny and blocking or interfering with it.  Recently a transport.dll started causing some people issues and excluding DCS from AV solved it.

  • Like 1
Posted
6 hours ago, rob10 said:

That's likely a case of your anti-virus getting too horny and blocking or interfering with it.  Recently a transport.dll started causing some people issues and excluding DCS from AV solved it.

The dedicated server has all anti virus exclusions already, problem is when I put up mission on server to test and my pc crashed. But I also have all anti-virus exclusions for DCS, SRS, etc…was able to recover log of anyone could be so kind as to check it out for me.

dcs.log

Intel i9-13900k, Asus Z790-E Gaming Wi-fi 2 motherboard, 64gb Corsair Vengeance LPX DDR5-6400 RGB ram 2x32gb XMP2 profile, 4TB Crucial T700 PCIE 5.0 SSD internal, 2TB Crucial T700 PCIE 5.0 SSD internal, Asus ROG Strix OC GeForce RTX 4090, Corsair 7000X Case with 5 x 120mm side mounted intake fans and 3 x 140mm top mounted exhaust fans, 1 x 140mm rear mounted exhaust fans, front mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in 3 push, 3 pull intake configuration, 1 x 32" Samsung 3840x2160 display, 1x 32" Asus 2560x1440 display, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Posted

Ahh, I completely forgot I reinstalled the Bronco to try some stuff out. I’ll  give it a try when I get home. Thanks for catching that bud, much appreciated. 

  • Like 1

Intel i9-13900k, Asus Z790-E Gaming Wi-fi 2 motherboard, 64gb Corsair Vengeance LPX DDR5-6400 RGB ram 2x32gb XMP2 profile, 4TB Crucial T700 PCIE 5.0 SSD internal, 2TB Crucial T700 PCIE 5.0 SSD internal, Asus ROG Strix OC GeForce RTX 4090, Corsair 7000X Case with 5 x 120mm side mounted intake fans and 3 x 140mm top mounted exhaust fans, 1 x 140mm rear mounted exhaust fans, front mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in 3 push, 3 pull intake configuration, 1 x 32" Samsung 3840x2160 display, 1x 32" Asus 2560x1440 display, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Posted

I see a mention of UH-60L as well. This log also doesn’t contain a DCS game crash. If this was supposed to be a crash then it may be Windows killing the process… If this was definitely a crash, and even if not, then run the Windows dxdiag tool, save the entire report, and drop it here. This may aid in identifying the last few crashes of processes on your system. 
 

I realise this original post was for somebody else, so your problem may be unrelated and may need a different posting unless you can replicate and provide a log containing this. 

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...