resolved 2.7.0.4625 Open Beta crash at second mission load

[RogSimu]

6 hours ago, Flappie said:

Good for you. But were you having the second mission loading crash?

 

If so, that's worth a shot for you guys: simply rename your "Saved Games\DCS...\Scripts" folder into "Scripts_backup" and see if you can reproduce the second mission loading crash.

 No crashes and crashes are only present in Windows 10 mode with the script folder, in Win8 mode with script folder guaranteed crash with 3 or 4 game loading, in Win 8 mode without script folder no crash, I just changed 20 times of flight, mission, plane, places, map syria, OMDB, caucasus I confirm no DCS game crash.
I reactivate by renaming the script crash folder when reloading the automatic flight.
In compatibility mode, check the options before testing the DCS Beta 2.7.

See image link opposite

https://servimg.com/view/20326109/257

Edited May 21, 2021 by RogSimu

[Flappie]

1 hour ago, Flia said:

RTX2080 here and im Shift+R positive too

 

Talking about Shift+R, have you ever tried this workaround?

 

0/ Disable Win 8 compatibility mode for the sake of the test.

1/ Fly the mission you want to fly.

2/ When mission is over, get back to main menu.

3/ Choose a different aircraft instant action mission: do you reach the cockpit or does it crash?

4/ Exit instant action mission, get back to main menu.

5/ Re-fly the mission you were flying at step 1: do you reach the cockpit or does it crash?

 

I ask you this because this is the current workaround for the second mission loading texture issue (those who don't crash get this bug as a reward). And I have a feeling these two bugs are connected.

Edited May 21, 2021 by Flappie

[Snakedoc]

1 hour ago, BioZ said:

I am new to this tread because I haven't had any issues. looked throught some posts and it seems as people that are getting the crash do have a mediocre GPUs like the AMD RX560. 

 

I have RTX3090 and I am completely crash free.

What GPU are you using?

 

 

I am experiencing this crash since the start of this 3d and I have a 3090 + 10700k (full specs in my signature)

 

I don't think it's hardware related 

[Fra298]

6 minutes ago, Snakedoc said:

 

I don't think it's hardware related 

 

    Agree with that. I had those crashes with 2.7.0, but they're gone with the last update.

[RogSimu]

13 minutes ago, Snakedoc said:

 

I am experiencing this crash since the start of this 3d and I have a 3090 + 10700k (full specs in my signature)

 

I don't think it's hardware related 

No, I think there is a coding conflict, due to the DX11 error, almost identical for everyone, if it was a material error it would be present on the stable version which is quite identical to the beta 2.7 except the more extensive coding present on the beta

[Flying Papa]

My good news is, after updating 2.7.1, my second mission crash for my F16 stopped. But still crash when loading F14 module. 

 

It seems to be module related? 

[RogSimu]

1 minute ago, Flying Papa said:

My good news is, after updating 2.7.1, my second mission crash for my F16 stopped. But still crash when loading F14 module. 

 

It seems to be module related? 

Maybe the reason that my DCS does not crash I do not have the F14 module, and my DCS does not crash absolutely no crash, but I run in Win8 mode without a script folder, if I put this folder back DCS crashes immediately

[Flappie]

@Flying Papa I believe the Tomcat module has its own loading bug. See here.

 

Just now, RogSimu said:

Maybe the reason that my DCS does not crash I do not have the F14 module, and my DCS does not crash absolutely no crash, but I run in Win8 mode without a script folder, if I put this folder back DCS crashes immediately

 

I believe you're having a different crash. Yours seems to be caused my some mod (the Scripts folder is created when installing mods).

Edited May 21, 2021 by Flappie

[zonie]

FYI, turning off 'full screen' in DCS fixed this for me.  I was having a 100% repeatable second mission crash which has now not happened again for 24 hours.  I'll update this post if it comes back.  Hope this helps.

 

Well 2 days later and I’ve had 1 crash on second mission load vs 100 % repeatable crash prior to disabling full screen.  FYI it definitely helped in my case 

Edited May 23, 2021 by zonie

[casserole]

Well I have the A-10C and A-10C II as well as the F/A-18C and all 3 crashed at second mission load all during SP "full screen" off. I didn't have anymore crashes during MP and "Instant Action" missions with the 2.7.1.6430 update.

BUT..... there is hope in SP:

Yesterday evening and today I tried the following during SP (Single Player): After playing the first mission I delayed a new load of the mission by hitting "Pause" in order for the CPU and the Graphic card to "cool off". After about 10 sec I quit the mission to return to the mission selection and then chose the same mission again. It loaded WITHOUT any CRASH.

I tried that again after I was shot down (Pause 10 sec, return to mission selection) and chose another mission. It worked as well. I tried it with "Instant Action", no crash, also with multiplayer, no crash after choosing another server. On this last instance, for delaying purposes, I went to spectators for 10 secs before exiting so that the action theater wasn't on screen.

After a few times, I tried to do it more quickly again, and NO crash. Exiting the game didn't create an error in the event viewer anymore.

What I haven't tried yet is what happens when a server reloads the mission while still being connected. That was fatal before.

At least this "delaying action to help the computer get straightened out again" helped me yesterday and today. We'll see what will happen this evening and this weekend.

May be it will help also somebody else, who knows.

Time to try it out, guys....

Edited May 21, 2021 by casserole

[Flia]

1 hour ago, Flappie said:

 

Talking about Shift+R, have you ever tried this workaround?

 

0/ Disable Win 8 compatibility mode for the sake of the test.

1/ Fly the mission you want to fly.

2/ When mission is over, get back to main menu.

3/ Choose a different aircraft instant action mission: do you reach the cockpit or does it crash?

4/ Exit instant action mission, get back to main menu.

5/ Re-fly the mission you were flying at step 1: do you reach the cockpit or does it crash?

 

I ask you this because this is the current workaround for the second mission loading texture issue (those who don't crash get this bug as a reward). And I have a feeling these two bugs are connected.

 

I followed every step exactly point by point and i didnt crash.

[Blinde]

Windows 8 compatibility mode works here too. My simple previously mentioned F-14B takeoff and second attempt works just fine. No more crashes on next tries.

Edited May 21, 2021 by Blinde

[XPACT]

In single player Windows 7/8 compatibility works for me also, no crashes so far, but when I want to fly with my small group of friends online my FPS will tank from usual 60-80 to unplayable slide show of 20 FPS. If I wanted crash free experience and good FPS I would constantly need to swap compatibility mode, which is a no go for me so I just keep it at Windows 10 and slowly but surely reaching proficiency in black magic so crashes are kept at minimum.

[Ironhand]

3 hours ago, Flappie said:

 

Talking about Shift+R, have you ever tried this workaround?

 

0/ Disable Win 8 compatibility mode for the sake of the test.

1/ Fly the mission you want to fly.

2/ When mission is over, get back to main menu.

3/ Choose a different aircraft instant action mission: do you reach the cockpit or does it crash?

4/ Exit instant action mission, get back to main menu.

5/ Re-fly the mission you were flying at step 1: do you reach the cockpit or does it crash?

 

I ask you this because this is the current workaround for the second mission loading texture issue (those who don't crash get this bug as a reward). And I have a feeling these two bugs are connected.

 

 

Hmmm. Maybe I didn’t understand the 2nd mission crash issue. For me, it’s never seemed to matter whether it was the same aircraft/mission or not. All that mattered was that it was the second attempt to fly a mission.

 

Also hasn’t mattered whether Shift-R or a menu is used.

Edited May 21, 2021 by Ironhand

[Flappie]

You mean you can't pass the test, then?

[Ironhand]

28 minutes ago, Flappie said:

You mean you can't pass the test, then?

 

Affirmative. If it’s going to crash, it hasn’t mattered whether it’s the same mission or aircraft. I won’t get beyond the first half of your test. It’s just that none of it is 100% repeatable. I might be fine one day and a crash-fest the next until I delete some folders.

Edited May 21, 2021 by Ironhand

[wowbagger]

Yes, Ironhand is correct. My experience is the same.

 

 

And deleting the temp and shaders folders is the only thing that seems to minimize the crashes, but not prevent them.

[Manhorne]

17 minutes ago, Ironhand said:

 

Affirmative. If it’s going to crash, it hasn’t mattered whether it’s the same mission or aircraft. I won’t get beyond the first half of your test. It’s just that none of it is 100% repeatable. I might be fine one day and a crash-fest the next until I delete some folders.

 

I have been experiencing the exact same thing. It was crashing every time I loaded a second mission and then last week it stopped mysteriously . I updated with the new DCS update today and it started crashing again loading the second mission. Will do it with any aircraft and any mission.

[MattCri]

59 minutes ago, Ironhand said:

 

Affirmative. If it’s going to crash, it hasn’t mattered whether it’s the same mission or aircraft. I won’t get beyond the first half of your test. It’s just that none of it is 100% repeatable. I might be fine one day and a crash-fest the next until I delete some folders.

 

can confirm this, i have the same beahviour

[Ironhand]

9 minutes ago, MattCri said:

can confirm this, i have the same beahviour

 

Not surprising, I suppose, since the sim breaks during or at the close of the first mission, whenever we encounter the crash. So what aircraft, mission, or map follows shouldn’t matter.

[casserole]

4 hours ago, casserole said:

Well I have the A-10C and A-10C II as well as the F/A-18C and all 3 crashed at second mission load all during SP "full screen" off. I didn't have anymore crashes during MP and "Instant Action" missions with the 2.7.1.6430 update.

BUT..... there is hope in SP:

Yesterday evening and today I tried the following during SP (Single Player): After playing the first mission I delayed a new load of the mission by hitting "Pause" in order for the CPU and the Graphic card to "cool off". After about 10 sec I quit the mission to return to the mission selection and then chose the same mission again. It loaded WITHOUT any CRASH.

I tried that again after I was shot down (Pause 10 sec, return to mission selection) and chose another mission. It worked as well. I tried it with "Instant Action", no crash, also with multiplayer, no crash after choosing another server. On this last instance, for delaying purposes, I went to spectators for 10 secs before exiting so that the action theater wasn't on screen.

After a few times, I tried to do it more quickly again, and NO crash. Exiting the game didn't create an error in the event viewer anymore.

What I haven't tried yet is what happens when a server reloads the mission while still being connected. That was fatal before.

At least this "delaying action to help the computer get straightened out again" helped me yesterday and today. We'll see what will happen this evening and this weekend.

May be it will help also somebody else, who knows.

Time to try it out, guys....

 

 

Well I talked too soon. Still got a crash or two this evening.

But the occurrence is far less than 2 days ago. Just got 1 visible crash after a server change in MP, and another unnoticeable one causing an error (ntdll.dll) in event viewer when closing the game. This during a period of about 5 hours and 4 sessions.

dcs.log-20210521-203912.zip

Edited May 21, 2021 by casserole

[Jakey-Poo]

I am also getting very regular crashes on second mission load in single player.  It is not every time, and it seems like some days it will not happen at all.  Today is one of the days where I cannot play more than a single mission without DCS crashing.  I am sending the crash report every time it happens, so hopefully this will get sorted in an update soon. 

[Wali763]

Yesterday aternoon I deleted the Scrips folder and then DCS was updated to 2.7.1. This update was done only when I switched back to non-Win8-mode, I was using all week.

 

Since then I had one 1st mission crash, when DCS crashed during loading of the first mission after DCS-startup. But no 2nd mision-crash so far. Did not really have extensive time to test this, but I did al least as many reloads (30?) and restarts (4?) of DCS, that with 2.7.0 DCS for sure would have crashed. 

 

Other than that, with Win8-mode I had "only" two crashes, that were not during loading. First crash could be due to undervolting my GPU too much (as Flappie sugested OC as the reason) and the second crash was in MP and the other players had problems with AI-aircraft and ships not moving for a while too. Upon restarting DCS, after some time all the unit-icons on the F10-map disappered and upon leaving the sever I had no aircraft-icons in the DCS-menu. Most probably not related to this here I guess.

Edited May 22, 2021 by Wali763

[Flappie]

Interesting. Fra298 told me he has no more crashes since 2.7.1.6430. Here's what he did:

1. Updated to DCS 2.7.1.6430
2. Renamed his "Saved Games\DCS..." folder (mind that if you do it, you need to manually copy your custom controls, your logbook...)

So far, his second mission loading crashes are gone.

[Flia]

Im testing it 

 

Update : No change here. Still crashing when Shift+R.

Edited May 22, 2021 by Flia