Since the update, I can't move past the loading screen

[Hikaruncat]

Since this update, the loading screen has become stuck.
I can't even remember what unofficial mods I installed
and which folder they were in.
I've removed all the mods I installed with GME
and performed a compatibility check on Steam
but there was no change.

thank you　

dcs.log

[MAXsenna]

@Hikaruncat Seems to hang on the MovingMap

 

[Hikaruncat]

7 minutes ago, MAXsenna said:

@ヒカルンキャット MovingMapにハングしているようです

 

I thought I removed that mod, but is it still there?
How do I delete it?
Thank you for your quick response.

[MAXsenna]

I thought I removed that mod, but is it still there?
How do I delete it?
Thank you for your quick response.

Look at the paths in the log, and you should be able to remove the files. I guess if you tried to remove them, you probably forgot the entry in the export.lua
Just delete the line, use Notepad++, and you should be fine.

Cheers!

Sent from my SM-A536B using Tapatalk

[sleighzy]

Your log is showing the below error message which has caused issues for a number of users. Can you rename your Saved Games\DCS\MissionEditor folder to MissionEditor.old and start DCS again. If this still fails then attach another log file.

2025-09-20 00:44:27.794 ALERT   LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string)
GUI debug.traceback: stack traceback:
	[C]: ?
	[C]: in function 'date'
	[string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews'
	[string "./MissionEditor/modules/me_news.lua"]:259: in function 'funCallBack'
	[string "./MissionEditor/modules/me_waitDsbweb.lua"]:90: in function 'updater'
	[string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

 

[H60MTI]

I have the same thing going on right now. I get the main screen with log in and the MIG-29 ad playing. I click launch. Get the NVIDIA screen, the small DCS screen then nothing. I've tried a slow repair, fast repair, and renamed the mission editor files. Still nothing...

[Raven (Elysian Angel)]

There seem to be 2 different problems that people have encountered with DCS since last patch.

The first can be fixed by renaming/deleting the Mission Editor folder in Saved Games, and the second by turning off Secondary Shadows in the System menu.

[H60MTI]

I've renamed the mission editor folder to MissionEditor.old and my secondary shadows were already off and still no getting into DCS.

Edit: I even removed the MissionEditor folder completely from my Saved Games folder. Still nothing...

Edited 17 hours ago by H60MTI

[gorma]

Yeah... 

[sleighzy]

8 hours ago, H60MTI said:

I've renamed the mission editor folder to MissionEditor.old and my secondary shadows were already off and still no getting into DCS.

Edit: I even removed the MissionEditor folder completely from my Saved Games folder. Still nothing...

Please attach your DCS log file. This issue may be unrelated, or have a different resolution, but need a log file.

[H60MTI]

I did on a topic I started but I'll still attach it. This log file is from this morning and the last time I tried to open her up. The game was working fine last weekend when I played before the update but this morning after the update, nada...

dcs.log

[sleighzy]

4 hours ago, H60MTI said:

I did on a topic I started but I'll still attach it. This log file is from this morning and the last time I tried to open her up. The game was working fine last weekend when I played before the update but this morning after the update, nada...

dcs.log 28.12 kB · 4 downloads

Yeah different issue from this one, initial eyeball this looks to be a network issue. I've dropped some responses on the post you raised.

Edited 54 minutes ago by sleighzy

[Sprite001]

For me DCS crashed on startup with new Geforce game ready driver Version: 581.29. Had to go back to 581.08 to fix it.

[sleighzy]

10 minutes ago, Sprite001 said:

For me DCS crashed on startup with new Geforce game ready driver Version: 581.29. Had to go back to 581.08 to fix it.

Thanks for the input, this is however not a GPU driver issue so is unrelated to your problem.