Jump to content

Game crashes when loading at "Visualizer Start Simulation", fresh install.


Go to solution Solved by Flappie,

Recommended Posts

Posted (edited)

As the title says, on a fresh install and with official modules only, the game crashes to desktop or freezes on loading, specifically when the loading bar says "Visualizer Start Simulation".

Specs:
AMD Ryzen 5 5500 @ 4.5Ghz
32gb Ram @ 3200Mhz
Nvidia 2060 6Gb
64gb swap file
Game installed on an M.2 drive (Corsair MP600 pro)
Running on MT client.
 

 

dcs.log-20231224-185434.zip dcs.log-20231224-185417.zip dcs.log-20231224-185438.zip dcs.20231224-185438.dmp dcs.log-20231224-185436.zip dcs.20231224-185438.crash dcs.log dcs.log.old

Edited by enjOy
Extra logs attached
Posted
15 minutes ago, enjOy said:

the game crashes to desktop or freezes on loading


I dont see anything strange on the log, did you perform a dcs_updater repair (or file integrity check in the case of Steam) ?  … to make sure that your install is not corrupt.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

@enjOy It's a Windows dll that crashes:

2023-12-24 18:54:14.955 INFO    EDCORE (Main): try to write dump information
2023-12-24 18:54:17.727 INFO    EDCORE (Main): # -------------- 20231224-185417 --------------
2023-12-24 18:54:17.727 INFO    EDCORE (Main): DCS/2.9.2.49629 (x86_64; MT; Windows NT 10.0.19043)
2023-12-24 18:54:17.727 INFO    EDCORE (Main): C:\windows\system32\ntdll.dll
2023-12-24 18:54:17.727 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 000000017002a53a 00:00000000
2023-12-24 18:54:17.727 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'enjoy'

And these messages makes me think you might have a RAM issue:

# -------------- 20231224-185438 --------------
DCS/2.9.2.49629 (x86_64; MT; Windows NT 10.0.19043)
C:\windows\system32\ntdll.dll
# C0000005 ACCESS_VIOLATION at 000000017002a53a 00:00000000
SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'enjoy'
OS-Version: 10.0.19043 () 0x0-0x1
0x000000000002a53a (ntdll): (function-name not available) + 0x0
0x000000000002d148 (ntdll): (function-name not available) + 0x0
0x00000000000338d4 (ucrtbase): (function-name not available) + 0x0
0x000000000000e032 (input): (function-name not available) + 0x0
0x000000000005aed9 (input): (function-name not available) + 0x0
0x000000000005b9f1 (input): (function-name not available) + 0x0
0x000000000005bbdf (input): (function-name not available) + 0x0
0x000000000049b40c (dcs): (function-name not available) + 0x0
0x00000000000045a5 (dxgui_win_adapter): (function-name not available) + 0x0
0x00000000000034c7 (dxgui_win_adapter): (function-name not available) + 0x0
0x000000000005ae1a (user32): (function-name not available) + 0x0
0x000000000005cf9f (user32): (function-name not available)

 

If a DCS repair does not help, you should test your RAM using MemTest86:

 

Edited by Flappie
  • Like 1

---

Posted (edited)

Interesting, probably the ram issue could be from me overclocking it? No other games show any kind of fault. Repair install didnt help, but I'll follow along the RAM issue track. I'll update this post once i have test results.

edit: Memtest86 says my RAM is all good, no errors. Slow repair to installation still no good. Researching for further clues on the DLL crashing.

Edited by enjOy
test updates
Posted
8 hours ago, Flappie said:

Empty these folders:

  • Saved Games/DCS.../fxo
  • Saved Games/DCS.../metashaders2

then see if DCS keeps crashing.

Yup. That does it. I'll figure out a way to automate clearing the fxo and metashaders folder before launching the game

Posted
2 minutes ago, enjOy said:

I'll figure out a way to automate clearing the fxo and metashaders folder before launching the game

 

I do it manually, but just when DCS has been updated, about once per month.

  • Like 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)
On 12/25/2023 at 4:46 PM, Rudel_chw said:

 

I do it manually, but just when DCS has been updated, about once per month.

Nah, if I dont clean fxo and metashaders before launching the game crashes.


One more info regarding the solution. It fixes the single thread client. MT still has the same isssue. And multiplayer performance is down the tubes

Edited by enjOy
Posted
1 minute ago, enjOy said:

Nah, if I dont clean fxo and metashaders before launching the game crashes

 

You just discovered yesterday that the shaders folders existed ... and now you are that sure about the need to clear them at every game run? 🙄

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
1 minute ago, Rudel_chw said:

 

You just discovered yesterday that the shaders folders existed ... and now you are that sure about the need to clear them at every game run? 🙄

Yup, I was doing some config work to figure out if there was any combination of settings that would make multiplayer playable for me, so I launched the game several times. And like clockwork, if the shaders folder has anything on it, the game freezes and/or crashes at the same spot.

  • Like 1
Posted

Did your problems start with 2.9? I had to upgrade my video card to a second hand 2080Ti. While I did have other errors compared to you, I've had no issues post upgrade. Could you borrow a newer one for testing purposes?
Cheers!

Sent from my SM-A536B using Tapatalk

Posted (edited)
15 hours ago, MAXsenna said:

Did your problems start with 2.9? I had to upgrade my video card to a second hand 2080Ti. While I did have other errors compared to you, I've had no issues post upgrade. Could you borrow a newer one for testing purposes?
Cheers!

Sent from my SM-A536B using Tapatalk
 

Yes, the issues started with 2.9. I was looking to upgrade to a 6650XT, I'll see if I can borrow a different card. If the issue is lack of video memory, maybe I'll have to reach for something bigger

Edited by enjOy
clarity
  • Like 1
Posted
Yes, the issues started with 2.9. I was looking to upgrade to a 6650XT, I'll see if I can borrow a different card. If the issue is lack of video memory, maybe I'll have to reach for something bigger
Hmmm... My card crashed whenever it started compiling the shaders. It was the original Titan with 6GB. Cross my fingers that you are able to borrow a card for the troubleshooting!

Sent from my SM-A536B using Tapatalk

  • Recently Browsing   0 members

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