Jump to content

Syria map no longer working, crashes on start

Richrach

By Richrach
in Game Crash

 Share
Go to solution Solved by Richrach,

Recommended Posts

Richrach

Richrach

Posted
Posted

I have made numerous missions in Syria and Sinai and all have worked fine.  I spent a few months in Sinai building missions and flying, no problem.  Going back to Syria, the game crashes after loading.  It is semi-random, meaning the crash box shows up, but sometimes units continue to move or appear to be operating correctly for periods of time.  Other times, nothing moves and all is just frozen.  Running: DCS 2.9.3.51704

Not familiar enough with the logs to know what I am looking at, but I did find this error:

2024-03-23 14:29:08.707 ERROR   EDCORE (Main): No suitable driver found to mount mods/terrains/syria/assets/assetstextures.zip

There are a ton of other errors also appearing in the log, but not sure what to make of them as a whole.

I run VR with Pimax 8KX and it works quite well in Sinai, no problems.  In Syria, neither flatscreen or VR work correctly now.

The game runs fine with all the settings turned up higher than they are for Syria.  Log files attached.  Any help finding the problem is much appreciated.

 

Other things I have tried:

NVIDIA 4070 - Rolled back driver to one I know worked in the Syria map, no effect

No OC on CPU (everything worked with a mild overclock prior to this problem, all maps)

No XMP (has worked with XMP prior to this)

Removed VSN aircraft and mods (all worked in other maps)

 

The second log file attached is from the Sinai map.  I just loaded a mission with identical parameters for the computer and DCS and it works.  It seems to have just as many errors, if not more, but why does it work and Syria does not?

dcs.log dcs.log

Richrach

Richrach

Posted
  • Author
Posted

Just ran the cleanup and repair as you suggested.  Loaded a mission I had built and it crashed as it did before.

Is it possible the mission is somehow corrupted?  I can start a clean mission with just an A-4E in Syria and it will run.

Ugh... it would really stink to have to go back and recreate the mission I built... 

Richrach

dcs.log

Flappie

Flappie

Posted
Posted (edited)

If it always happens with the same mission, try this:

  1. Browse to "C:\Users\your-login\AppData\Local\Temp".
  2. There, you should find a folder called "DCS.openbeta". This is where DCS unzips mssion files. Delete the whole folder.
  3. Start DCS and try to load your mission again.

If it keeps crashing, please attach your mission file. I'll check.

Edited by Flappie

---

Flappie

Flappie

Posted
Posted

The good news is... the mission causes my DCS to crash too. 👍

We must find what causes this. Try removing stuff until DCS does not crash anymore.

The crash error does not ring a bell for now: 

2024-03-23 18:43:18.428 INFO    EDCORE (3240): # -------------- 20240323-184319 --------------
2024-03-23 18:43:18.428 INFO    EDCORE (3240): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631)
2024-03-23 18:43:18.429 INFO    EDCORE (3240): E:\DCS World\bin-mt\edterrain4.dll
2024-03-23 18:43:18.429 INFO    EDCORE (3240): # C0000005 ACCESS_VIOLATION at 00007fff4e6b20f7 00:00000000
2024-03-23 18:43:18.430 INFO    EDCORE (3240): SymInit: Symbol-SearchPath: 'E:\DCS World\bin-mt;', symOptions: 532, UserName: 'flapp'
2024-03-23 18:43:18.430 INFO    EDCORE (3240): OS-Version: 10.0.22631 () 0x300-0x1
2024-03-23 18:43:18.444 INFO    EDCORE (3240): 0x00000000000720f7 (edterrain4): buildMaxEdgeLengthUVSet + 0x16C7
2024-03-23 18:43:18.444 INFO    EDCORE (3240): 0x000000000023921c (edterrain4): landscape5::navGraph5File::findPath + 0x98C
2024-03-23 18:43:18.445 INFO    EDCORE (3240): 0x000000000026a1b3 (edterrain4): navGraphPath2::save + 0x43B3
2024-03-23 18:43:18.445 INFO    EDCORE (3240): 0x0000000000268723 (edterrain4): navGraphPath2::save + 0x2923
2024-03-23 18:43:18.445 INFO    EDCORE (3240): 0x0000000000268bc2 (edterrain4): navGraphPath2::save + 0x2DC2
2024-03-23 18:43:18.445 INFO    EDCORE (3240): 0x000000000001f4ac (edterrain4): ITerrainImpl4::createPathCB + 0x14C
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x0000000000207021 (Transport): wcRoute::createRouteWORoad + 0x91
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x00000000000be23a (Transport): RouteManager::clear + 0xBCA
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x0000000000034fb8 (edCore): ed::this_thread::yield + 0xB38
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x0000000000049ff6 (edCore): ed::this_thread::yield + 0x15B76
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x0000000000029363 (ucrtbase): _recalloc + 0xA3
2024-03-23 18:43:18.446 INFO    EDCORE (3240): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
2024-03-23 18:43:18.684 INFO    EDCORE (3240): Minidump created.

 

---

Richrach

Richrach

Posted
  • Author
Posted

Flappie, THANK YOU for working with me.  I was oging to start a new mission, but I will delete items until I/we find the reason for the problem.  Will let you know.

 

I feel like such a nerd...

Flappie

Flappie

Posted
Posted

You're welcome. I've just removed all drawings and all static units and the crash won't happen anymore. Maybe it has to do with the Massun 92 mod units.

  • Like 1

---

Richrach

Richrach

Posted
  • Author
Posted

I have done likewise. I also removed the Obstacle destruction zone.  Not sure which one did the trick, if it is actuall fixed or not.  More testing and experimenting.  Will know by the end of the weekend and post my findings.

  • Thanks 1
  • Solution
Richrach

Richrach

Posted
  • Author
  • Solution
Posted (edited)

99,

Doing further testing, my original results were not accurate.  I did all the normal things as described in the thread.  Drawings and the large amount of smoke I had in the scenario along with the updated Massuns92 pack seemed to be the problem.

Further testing revealed the problem is triggers / starting units after the beginning of the mission.  The Syria map does not like units starting after the beginning of the mission.  I had 150 units to start and another ~100 begin at later times.  Crashes ALL corresponded to the later start times.  I removed units starting later and began them all at the beginning.  Problem solved.  I even boosted the numbers up to 400+ units, all starting at the beginning of the mission without problem.

For some reason, triggers and later activations are a bug in Syria.

 

I hope this helps someone out there who builds larger missions.

Richrach

 

*** BELOW IS NOT VALID***  Additional testing completed.  See above

Actually, what I am finding is it is not the drawings and static objects, but the triggers at the beginning of the mission to get rid of the wall.  I set the triggers for a 1 ONCE / TIME MORE THAN 1.  When I set them to MISSION START / ALL COALITION OUT OF ZONE the mission worked withall the drawings.

The static objects were updated to Massuns92-Asset Pack 3.0

All worky-goody now.

Thank you for the help in knowing where to look and what to try!

Richrach

Edited by Richrach
Incorrect solution
 Share
Go to topic listing

  • Recently Browsing   0 members

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