resolved 2.7.0.4625 Open Beta crash at second mission load

[CSL_Ondras]

Hi Flappie

 

I thik might have the direction for finding the culprint of the second mission CTD. I have tried all the things sugested in this thread, with no positive result, just like every one elese. However I have found out, that if I erase C:\Users\ondre\Saved Games\DCS.openbeta\fxo every day before flying, or after the first CTD that day, I can then fly all day long.. until next day comes and new *.fxo files appear in the folder, with the new date. I hope this workaround helps everyone, until the bug is found.

 

O.

[Hammer1-1]

So heres my question: did anyone of you who are experiencing the crashes complete the first mission or did you just join one and then end it?

[Boogdud]

1 hour ago, Flappie said:

Thanks for the logs, Felix.

It seems all users having this issue are running the latest W10 version (Windows NT 10.0.19042). I'm running the previous version (10.0.19041). I'll update right now to see if I can reproduce.

 

 

I'm running the previous version of windows as well (OS build 19041.928) and I get the crashes. It seems random, sometimes I get crashes every load, other times I can run several missions in a row.  Early this morning I was running ww2 instant actions in the Spit, P47, P51, and BF109 and was getting crashes constantly.  Later this afternoon (with no changes) I did several missions with the huey and didn't have a single crash.  I don't think it has anything to do with the windows version.  

[84-Simba]

3 hours ago, Flappie said:

I've just tried this with the Hornet (start a first mission cold and dark, takeoff, leave the mission, edit mission so aircraft starts in mid-air, launch mission). I get no crash at all.

 

Did you get rid of these crashes for good, @RoxSy?

 

Thanks for the logs, Felix.

It seems all users having this issue are running the latest W10 version (Windows NT 10.0.19042). I'm running the previous version (10.0.19041). I'll update right now to see if I can reproduce.

 

EDIT: I'm now running the latest W10 version (Windows NT 10.0.19042) and I'm still unable to reproduce the second mission loading crash.

 

 

I think you did not understand what I meant with different aircraft state.

 

Fly the first mission with the aircraft cold and dark, startup, take-off, leave the mission ... and fly again directly.

The fact that the aircraft was in a different state between leaving the first mission (running) and entering the second (cold and dark) could have been a factor for some reason.

 

I came up with this idea because when it crashes DCS shows me a frozen image of the cockpit of my aircraft in its intended starting spot but running while it should have been cold and dark.

 

I tried your solution and I experienced no crash yesterday.

But last time I thought it was resolved it started to crash again a couple of days later.

 

I'll wait a few more days to report.

Edited April 25, 2021 by RoxSy
Precisisons

[the_jovian]

17 hours ago, Witz said:

Hello, I was having the same issue with crashing on second mission load after upgrading to 2.7.  I was using a few sounds mods located in C:\Users\(your name\Saved Games\DCS.openbeta.  This does not appear to be the issue (at least for me).  What I noticed after upgrading to 2.7 was this folder located in my install directory - C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_backup.000.  After deleting this folder (backup.000) I have been crash free and my sound mods work with no issues.  Not sure why the upgrade created this folder but hope this helps!

 

Witz

 

This seems to have fixed it for me. I was able to "fly again" multiple times in a row. Has anyone else tried this?

 

Spoke too soon, started crashing again.

Edited April 25, 2021 by the_jovian

[jfnelson0127]

11 minutes ago, the_jovian said:

 

This seems to have fixed it for me. I was able to "fly again" multiple times in a row. Has anyone else tried this?

I'm running the Steam version. Any idea where I would go to check for this file?

[Smashy]

@Flappie - I was having this problem off and on since 2.7 dropped and have submitted a bunch of crash logs via the dialog that pops up.  Hopefully someone got them.  A few days ago, I was able to temporarily remedy the crash by unchecking the fullscreen box.  The crashes returned after I toggled fullscreen back on (stupid, but I was trying to see if I lost any FPS with fullscreen disabled).

Since then I've been plagued by the "second mission or shift-R" crash.  I tried all the things listed here, cleaning up those temp AppData files, quit-to-desktop, removing options.lua, removing my saved games folder but nothing helped.  I also tried updating GPU drivers, multiple reboots, closing all other apps, avoiding alt-tab, changing from 2 monitors to 1, alt-enter. This is not the sort of thing tech support like to hear but I just shotgunned random things and yesterday my crashes disappeared.  I just now loaded up a simple Huey mission in Nevada and had no problem with a shift-R restart.  I wish I could tell you what fixed it but tbh, I don't remember everything I did yesterday to get it working.

 

I'm running Windows 10 Pro 10.0.19041

[Sonoda Umi]

On 4/23/2021 at 2:28 PM, Flappie said:

 

Many thanks for your thorough testing, @MileHiRyder.

 

@Sonoda Umi said earlier the problem was solved by deleting "Saved Games\DCS...\Config\options.lua". This file contains fullscreen setting among other things.

 

Can someone please try to rename this file? Call it whatever you want so DCS can't find it. You'll have to set your graphics settings anew. See if DCS keeps crashing on second mission loading after that.

 

I'm sorry to say that it cannot solve the problem completely. After deleted options.lua, my Current situation is that DCS will crash at the second mission loading when I run DCS at first time, and it won't crash at the second mission loading when I run DCS again.

[XPACT]

I might be onto something but I will need day or two to confirm it due to irregular crashing pattern.

 

Long story short seems like dx and the game don't know real amount of commit charge that is available when page file is set to system managed (could be OS bug but unlikely) so memory allocation errors occur.

 

By setting page file to fixed 32768 both initial and allocated, after multiple restarts and full day of testing I couldn't make the game crash. Why I even bothered to try it was because when DCS is open even tho physical memory is not even near being fully utilized so called hard faults occur regularly which means something is constantly using page file. 

 

Edited April 26, 2021 by XPACT

[unknown]

3 hours ago, XPACT said:

I might be onto something but I will need day or two to confirm it due to irregular crashing pattern.

 

Long story short seems like dx and the game don't know real amount of commit charge that is available when page file is set to system managed (seems like some OS bug) so memory allocation errors occur.

 

By setting page file to fixed 32768 both initial and allocated, after multiple restarts and full day of testing I couldn't make the game crash. Why I even bothered to try it was because when DCS is open even tho physical memory is not even near being fully utilized so called hard faults occur regularly which means something is constantly using page file. 

 

Interesting, my page file is set to 32768 for both initial/allocated and i don't have the problem. Maybe you're onto something, let us know how it works out for you, might help other users here.

[XPACT]

9 minutes ago, unknown said:

Interesting, my page file is set to 32768 for both initial/allocated and i don't have the problem. Maybe you're onto something, let us know how it works out for you, might help other users here.

 

This is the second day after I made the change, I tried changing missions, jets, maps loading thru or without mission editor, restarting game and PC many times and so far so good. Hopefully something comes out of this

[wowbagger]

4 hours ago, XPACT said:

...By setting page file to fixed 32768 both initial and allocated, after multiple restarts and full day of testing I couldn't make the game crash. Why I even bothered to try it was because when DCS is open even tho physical memory is not even near being fully utilized so called hard faults occur regularly which means something is constantly using page file. 

 

 

 

Agree! In some pretty limited testing, this seems to make a big difference. I haven't had a 2nd Loading crash after making this change.

 

I haven't tested any long missions yet. But Restarts, Watch Track, and loading successive missions which would usually cause a crash have not done so after the Page File change.

 

Cheers XPACT, I hope you have found it.

[Arikaj]

55 minutes ago, XPACT said:

 

This is the second day after I made the change, I tried changing missions, jets, maps loading thru or without mission editor, restarting game and PC many times and so far so good. Hopefully something comes out of this

May I ask if I should do the  custom page file on the main C drive or on another drive where I have my game installed?

Edited April 26, 2021 by Arikaj

[Flappie]

@ArikajJust leave the pagefile where it is. There's no known benefit to move it to the DCS drive.

[MattCri]

dcs.log-20210426-111055.zip

 

 

Changing the page file makes no difference for me, still crash every time on second load 

 

Edited April 26, 2021 by MattCri

[Flappie]

@MattCriHave you tried this already?

 

 

 

[BIGNEWY]

Hi all, 

 

I am sharing your feedback with the team. 

 

so far I am unable to reproduce myself however.

 

thanks

[XPACT]

20 minutes ago, MattCri said:

Changing the page file makes no difference for me, still crash every time on second load 

 

It could be that we have few bugs that intertwine with each other, first try deleting Temp/DCS or Temp/DCS.openbeta located in AppData/Local as Flappie suggested and after that untick fullscreen in game options (game should restart by itself if it doesn't do it manually)

 

EDIT: from logs both times mission was loaded from temp folder, hopefully it will make a difference when you delete it

Edited April 26, 2021 by XPACT

[MattCri]

45 minutes ago, Flappie said:

@MattCriHave you tried this already?

 

 

 

 

 

Yes, no difference. I see no pattern in my tests.

Sometime it crashes, sometimes i can load 3-4 missions changing maps and plane with no issue.

 

Already deleted that folder and running without fullscreen. Tried repair and started with a new save folder.

Edited April 26, 2021 by MattCri

[Flia]

1 hour ago, BIGNEWY said:

Hi all, 

 

I am sharing your feedback with the team. 

 

so far I am unable to reproduce myself however.

 

thanks

Each time when my DCS crashes im sending a crashlog. I hope this will help 

Edited April 26, 2021 by Flia

[BIGNEWY]

2 minutes ago, Flia said:

Each time when my DCS crashes im sending a crashlog. I hope this will help 

 

 

yes it all helps, also if you have auto reporting enabled this helps as it is sent to our crash database. 

 

thanks

[wowbagger]

The Page File change seems to work for both Full Screen enabled and Full Screen disabled on my system. The only crash I have had since changing the Page File was once right after I switched from Full Screen disabled to Full Screen enabled. But I emptied the metashader, fxo, and temp folders right after that crash and have not had another since that time. I have tested with multiple mission restarts, and DCS restarts, and a couple of pc restarts and it seems to be holding.

 

If it hasn't fixed the problem, it seems to have lessened it dramatically.

Edited April 26, 2021 by wowbagger

[MattCri]

So, im used to alt+enter at the main menu because i get i bit of flicker, only in the main menu,  without doing so (freesync issue i guess)

With fullscreen disabled and no alt+enter i have no crashes after loading and quitting 4-5 missions.

[XPACT]

Still didn't crash fingers crossed...

My preload radius is 100000

 

Now just to be clear even if this does fix or make the issue much less likely to happen it still seems like DCS is doing something wrong with memory allocation since it didn't happen before 2.7 and not to mention that there is no application on my PC that requires page file this big considering amount of physical RAM, it seems that here we are patching aquarium with duck tape and hope it won't leak.

 

I don't have a problem with lack of space but some here can't afford to lose that much for page file because one program is using it for who knows what reason.

[84-Simba]

24 minutes ago, XPACT said:

Still didn't crash fingers crossed...

My preload radius is 100000

 

Now just to be clear even if this does fix or make the issue much less likely to happen it still seems like DCS is doing something wrong with memory allocation since it didn't happen before 2.7 and not to mention that there is no application on my PC that requires page file this big considering amount of physical RAM, it seems that here we are patching aquarium with duck tape and hope it won't leak.

 

I don't have a problem with lack of space but some here can't afford to lose that much for page file because one program is using it for who knows what reason.

Now that you are talking about pre-load radius I realize that crashes started just after I turned it down from full.

Do you think having that pre-load maxed out could avoid the crashes ?