resolved 2.7.0.4625 Open Beta crash at second mission load

[comcat]

for me so far the Nvidia Update did the trick.... no crash since.....

[Smashy]

8 hours ago, Smashy said:

I was having consistent second-mission-load crashes today.  I saw maybe 6-8 of them.  I saw the latest posts here and installed Windows 10 20H2 KB5001391 and did about 4-5 mission reloads with no crashes.  I'm cautiously optimistic that this update has done something to help.  If the crashes return, I'll update here.

 

Welp, crashses while loading 2nd missions are back. 

[zampe]

 

1 hour ago, Smashy said:

 

Welp, crashses while loading 2nd missions are back. 

 

Yes, it came back to me too, but it’s much rarer. Maybe of 10 (2nd mission starts) 2or3 will be with crash

Edited May 5, 2021 by zampe

[Gronank]

Does anyone get the sensation that this is caused by the mission editor?

 

It feels like after you bash the computer around (delete folders, install drivers, et.c) reloading missions works fine as long as you stay out of the editor. Then you go into the editor and do *something* and then some corrupt state get cached and will crash on reload until you delete folders et.c. again.

 

Does anyone else get the same feeling? Does anyone get the crashes without ever touching the editor?

 

(I do get the uneasy feeling of being a confused villager trying to appease a capricious crash god)

[Ironhand]

1 hour ago, Gronank said:

...Does anyone get the crashes without ever touching the editor?...

 

Yes. The only pattern I've been able to discern is that it will happen either the 2nd or 3rd day after deleting the FXO folder and the DCS folder in TEMP. By that time, I have closed out the sim and restarted it. During the first day, however, I can close and restart without an issue. OTOH, I haven't tested to see if the issue occurs if I leave the sim running for days.

Edited May 5, 2021 by Ironhand

[trashcan]

54 minutes ago, Gronank said:

Does anyone get the crashes without ever touching the editor?

 

Without touching the editor, because I'm currently not doing anything in the mission editor.

Edited May 5, 2021 by trashcan

[Conroy]

Definitely there's something broken we need to sort ourt.

W10 update and Nvidia update give you some time without CTD, but they come back. This is really strange.....with or without touching the ME.

 

For my opinion is time to move on, the problem is elsewhere than W10 update or driver update.

 

 

dcs.log-20210505-034802.zip dcs.log-20210505-114813.zip

[Flia]

I agree. When i try fly mission straight from the  mission editor the probility of crash is 99 %

[Flappie]

49 minutes ago, Conroy said:

For my opinion is time to move on, the problem is elsewhere than W10 update or driver update.

 

The problem certainly lies inside DCS 2.7, since there was no such issues with 2.5.6. The problem is:

• The log file doesn't tell much,
• The bug happens on some PCs and never on some others, and we still don't know why.

By the way, do you guys use FPS capping?

[wowbagger]

No FPS capping, no vsync. 

 

I do use g-sync. 

[Ironhand]

36 minutes ago, Flappie said:

By the way, do you guys use FPS capping?

Yes. @ 60

[Flappie]

A user told me he had identified FPS capping as the major source of 2.7 instability on his rig. I had asked him to reset NVIDIA panel to default, which he did. He had no more crashes. Then he tried re-setting the NVIDIA panel like he used to, then DCS crashed a lot again as soon as he enabled FPS capping.

 

Since we don't have a fix yet, you can try disabling FPS capping and see how it goes.

[XPACT]

Just now, Flappie said:

Since we don't have a fix yet, you can try disabling FPS capping and see how it goes.

 

On AMD side it doesn't make a difference Vsync on/off, FreeSync on/off, Radeon control panel settings default or not

 

I am currently running windowed with vsync enabled @144Hz

and I am again in a phase where game won't crash whatever I do but it will return at some point, that is obvious now.

[zampe]

No FPS capping here, and I don't use any type of sync.

 

[Flia]

1 hour ago, Flappie said:

 

The problem certainly lies inside DCS 2.7, since there was no such issues with 2.5.6. The problem is:

• The log file doesn't tell much,
• The bug happens on some PCs and never on some others, and we still don't know why.

By the way, do you guys use FPS capping?

Yes 60 FPS. Im trying to improve life of my RTX 2080. Beacouse i cannot afford new one for triple price

[wernst]

1 hour ago, Flappie said:

 

The problem certainly lies inside DCS 2.7, since there was no such issues with 2.5.6. The problem is:

• The log file doesn't tell much,
• The bug happens on some PCs and never on some others, and we still don't know why.

By the way, do you guys use FPS capping?

 

Who uses fps limit? I never got more than about 40 fps, with 2.7. is it the same or rather less. I wish I could release any fps brake.

Edited May 5, 2021 by wernst

[wowbagger]

33 minutes ago, XPACT said:

...and I am again in a phase where game won't crash whatever I do but it will return at some point, that is obvious now.

 

Yep, I'm in the same boat. After I updated nVidia drivers and Windows, the crashes came back with a vengeance. So I ended up changing the Page File again - I set it to System Managed Size on the C: Windows drive and set an additional fixed page file (32768) on a separate drive. Both are SSDs.

 

This has gotten rid of the crashes for now, despite all my many efforts to induce them over a couple of days and several system restarts. The problem seems to be memory related for me, since changing the page file is the only thing that has affected it noticeably on my system.

[bandit648]

I've been plagued by this issue as well and have tried everything in this thread. Like others I'd change something and think it fixed it as the crashes would disappear for a couple days but then would come back. Today I discovered something that I can consistently reproduce the mission reload crashed with.

 

Preload Radius @ 150000 = Crash

Preload Radius @ 100000 = No Crash

 

I can switch between these settings, restart the game and at 150000 I get a crash every time on the second reload. I'll keep testing but this seems to be the trigger on my system.

 

EDIT: More testing and it appears not to be related to the preload setting it self, but changing the setting and restarting the game. The crashes are so random its driving me insane. I hope ED can find a solution.

 

Edited May 5, 2021 by bandit648

[Tepnox]

20 hours ago, Tepnox said:

Worked for me as well! No crashing so far after intense testing.

 

 

My crashes after 2nd load are back for me - despite the prior installation of KB5001391 . Fiddling around with capping FPS and vsync on/off: still consistent crash after 2nd mission load. Back to zero I think - disappointed.

[Flia]

Yea this bug always come back to you and hit you again...

Edited May 5, 2021 by Flia

[rforce]

New Open beta 

looks good!!!

no crash at the moment 

[Wali763]

Just installed in the new update with no change. First LShift+R ended in a crash, the second at least produced a crash-report, that I could send.

 

Using RadeonChill to cap FPS to max of 60 because of TrackIR. Also am using a slight undervolt on my CPU (PBO Curve optimizer) and on my GPU.

 

Yesterday, when I both CPU and GPU set to default and clearing all the mentioned folders it did not take long to witness the first crash, or freeze, as somebody here called it, that does not get crashes...... 

Edited May 5, 2021 by Wali763

[rforce]

What is LShift +R ? Replay mission ?

for me ist works 

[Ironhand]

41 minutes ago, rforce said:

New Open beta 

looks good!!!

no crash at the moment 

Give it time...

[Buhli]

Yep reload the mission