Jump to content

2.7.0.4625 Open Beta crash at second mission load


XPACT

Recommended Posts

Guys, forget all the 'workarounds', this is something ED will just have to fix.  Hopefully very soon!


Edited by imacken
  • Like 2

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

Yep, totally agree.

 

If you can find a voodoo that works for a few days ... great, go with it. But everything seems to break after a while. And when it does, try something else because it might work for a few days more.

 

Eventually ED will get it fixed.

CPU:5600X | GPU:RTX2080 | RAM:32GB | Disk:860EVOm.2

Link to comment
Share on other sites

Khmm, I don't want to be devils advocate here, from BIGNEWYs comment this seems like we are few in numbers, they don't want to disclose numbers but I don't have any reason to doubt that we are minority, so I wouldn't be too optimistic about hotfixes considering this one

 

 

Link to comment
Share on other sites

2 hours ago, haze1 said:

Thank you, it works!

 

So far these permanent CTD did not appear anymore on my side, let´s see next time, if more CTD appear.

What I wonder about is, that the deleted *.fxo and *.meta2 in the terrain folders were not recreated after several restarts of DCS and even after restart of Windows. The folders keep empty.  

F-14b Tomcat   /   AV-8B Harrier   /   F-16C Viper  /   KA-50 Black Shark   /   Mi-24 Hind   /   MiG-21bis   

Link to comment
Share on other sites

31 minutes ago, XPACT said:

Khmm, I don't want to be devils advocate here, from BIGNEWYs comment this seems like we are few in numbers, they don't want to disclose numbers but I don't have any reason to doubt that we are minority, so I wouldn't be too optimistic about hotfixes considering this one

 

 

I don't think the actual crashes affect only a minority of us. But even then, suppose there are only 100 of us who have problems after the 2.7. update, then the question must be:

What is the root of the 2.7. beta update issues? What has changed fundamentally in comparison to 2.5.6. ? 

 

Isn't it precisely the function of a beta version that the developers carefully monitor any errors that occur? Even if only some but not all have these issues? 

Even if a majority have no problem, it should be important for the developers to see what effect a beta update has on different systems.

I mean OUR systems, not the dev's' reference systems.

 

Beta updates are for beta testers who have a wide range of differently configured PC systems.

If a beta update makes flying impossible, then no players can test the beta version. 


Edited by wernst
  • Like 1
Link to comment
Share on other sites

1 hour ago, imacken said:

Guys, forget all the 'workarounds', this is something ED will just have to fix.  Hopefully very soon!

 

 

In my case, reverting to previous version has worked great. At least I can practice offline..

Link to comment
Share on other sites

Maybe this is helpful:

 

I played the beta without the second-mission crash on Windows 10 V1909, but had a freeze on mission loading screen several times.

 

I updated to Windows 10 V20H2 (Inplace-Upgrade). No other updates / no driver updates.

Now with V20H2 i get the 2nd-mission-crash *every* time, i play the game.

Link to comment
Share on other sites

Considering, that this thread already has 22k+ views I dont think a tiny minority has this problem. 

 

But there has to be a problem and its in EDs intrest to find it. Maybe a new Windowsupdate or DCS-Update all oft a sudden makes it affect many more people?

 

Still would not expect any remedy in the immediate future....

 

The good thing about this situation is, that my intrest buying the Hind is gone for now. Already have my eyes on others games with the saved money....


Edited by Wali763
Link to comment
Share on other sites

In my case, going to the settings page in between every mission and clicking the "OK" button worked to avoid the second mission crash where nothing else did.  I just flew four missions in a row with no second mission loading crash, including a particular mission that has always crashed on second mission load in the past.  Ran that one twice in a row, no crashes.  Prior to this, the second mission crash happened 100% of the time for me (with one exception, discussed below).

 

I understand that no workaround has been 100% reliable so far, so I'll cross my fingers for now and will post an update in a few days.

 

I'm running the latest version of Windows 10, but I'm not running any special preview versions or anything like that.  I've got the latest Nvidia drivers for my graphics card.  I previously tried deleting my TEMP, fxo, and metashaders folders, but that alone did not help.  A quick check of those folders just now shows the TEMP and fxo folders have files in them, but the metashaders folder is still empty.

 

One more thing that seems relevant: there has always been one mission that reliably did not crash DCS, regardless of how many times I ran it: a custom mission I wrote a long time ago, a simple F-5E vs. MiG-21 dogfight over the Caucasus.  It's a favorite of mine, and when I upgraded to version 2.7 the very first thing I did was load that mission into the editor and play around with all the new weather permutations.  When the crash bug started happening, that was the one mission I could continue to run as many times in a row as I wanted without crashing DCS.  I have a hunch that it has something to do with the fact that this was the very first mission I ran after upgrading to 2.7, rather than anything particularly special about the mission parameters themselves.  Still, if anyone wants to examine the mission (or, hell, play it: the F-5E mod needs a good instant action dogfight against the MiG-21), I've attached it.

F5E v MiG21 Caucasus.miz

Link to comment
Share on other sites

As it seems you changed quite some things at the Engine (e.g. dx11background.dll is now only 1/3 to the stable Version), could it be that you did something that gets into issues with Windows MPO (multiplane overlay)? Because this is something that is supported by the nVidia drivers since 461.09 (I think it was that number).

 

I remember that there have been people that had issues with this even on Desktop and especially on chrome. And there was a registry setting to disable this. And nVidia told people to set VSync on at the global Settings. This is just a stab in the dark. But it is something that has changed not so long ago... But there might people who know better and could prove that this guess leads to nowhere...


Edited by FR4GGL3

14700K | MSI Z690 Carbon | Gigabyte 4090 Gaming OC | 64GB DDR5 6000 G.Skill Ripjaws S5 | Creative SoundBlaster X-FI Titanium HD on a Violectric V90 Headphone amp and Fostex TH600 Headphones | LG 42 C227LA & Samsung C32HG70 | TrackIR 5 | Virpil WarBRD with VFX Grip | Thrustmaster Warthog Throttle | VKB T-Rudder Pedals MK IV 

I only fool around the F-14 - and still having a hard time on it as there is so much to learn and so little time and talent. But I love it.

Link to comment
Share on other sites

Here I am, another one with this issue...CTD on second load of the same mission.

Night Flier

_________________________________________________________________________________________

i7 9700K, MSI RTX 2080, 32GB RAM (3200 MHz), SSD m.2 1TB, Monitor 32'' WQHD 2560x1440, Windows 10 Pro

Link to comment
Share on other sites

21 hours ago, Mike77 said:

Out of curiosity, is there any info around on interpreting the DCS log files?  I'm fascinated by it, but don't know where to start.

Here you go! Enjoy. 😉

 

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Here's a fairly consistent way to reproduce the crash on my machine. I noticed the difference first, when i played SP VS MP missions and it would seam that the crash occurs more often when respawning as client then when starting as player.

So, i took Bankler's CASE 1 Recovery Trainer, flew around a bit, landed. Took another slot. Landed that one as well. Went for the first lost again.....and crash. Restarted DCS, went into options, clicked Ok (to see if this fixes the crash), loaded the mission again. Took one slot, landed. Took another slot. Landed. Picked the first slot again. Landed. Took the second slot again....crash. All this in an F-14. Didn't try the F-18 slots. And never exited the mission, just changed slots.

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache

Link to comment
Share on other sites

Here is logfile when using Exit to Desktop option during mission. Same d3d11.dll crash at the end after DCS: application shutdown.

dcs.log

 

edit: comparing to normal exit

 

Crash

2021-05-09 08:40:16.863 INFO    TERRAIN: lSystem::exit()
2021-05-09 08:40:16.863 INFO    VISUALIZER: TerrainRenderer::release
2021-05-09 08:40:16.863 INFO    TERRAIN: lSystem::CleanScenes()
2021-05-09 08:40:17.692 INFO    EDCORE: try to write dump information
2021-05-09 08:40:17.694 INFO    EDCORE: # -------------- 20210509-084017 --------------
2021-05-09 08:40:17.696 INFO    EDCORE: DCS/2.7.0.5659 (x86_64; Windows NT 10.0.19042)
2021-05-09 08:40:17.697 INFO    EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll
2021-05-09 08:40:17.699 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at FDF86BAE 00:00000000
...

 

Normal

2021-05-09 08:10:23.764 INFO    TERRAIN: lSystem::exit()
2021-05-09 08:10:23.764 INFO    VISUALIZER: TerrainRenderer::release
2021-05-09 08:10:23.764 INFO    TERRAIN: lSystem::CleanScenes()
2021-05-09 08:10:40.140 INFO    VISUALIZER: SceneManager_Implement::~SceneManager_Implement()
2021-05-09 08:10:40.141 INFO    VISUALIZER: TerrainRenderer::release
2021-05-09 08:10:40.229 WARNING LOG: 1 duplicate message(s) skipped.
2021-05-09 08:10:40.229 INFO    TERRAIN: lSystem::exit()
2021-05-09 08:10:40.229 INFO    TERRAIN: lSystem::CleanScenes()
2021-05-09 08:10:40.275 INFO    DX11BACKEND: DX11Renderer::shutdown()
2021-05-09 08:10:48.158 INFO    DX11BACKEND: NVIDIA API exit OK
2021-05-09 08:10:48.158 INFO    DX11BACKEND: textures_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: textures_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: buffers_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: buffers_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: CB_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: CB_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: SB_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: SB_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: IB_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: IB_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: VB_count: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: VB_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: total_buffers_size: 0
2021-05-09 08:10:48.158 INFO    DX11BACKEND: total_size: 0

 


Edited by Norpa
Link to comment
Share on other sites

I have the same problem.

Restart a mission from the mission editor or a quick mission via SHF+R or even from the main menu ... CTD.

No mods, fresh driver install after uninstalled via guru in safe mode and slowly repair.

Still the same...

Link to comment
Share on other sites

for me Shift+R have 99 % chance to crash DCS. I sended dozens of crash reports.


Edited by Flia

PC: i7 9700K, 32 GB RAM, RTX 2080 SUPER, Tir 5, Hotas Warthog Throttle, VPC MongoosT-50CM2 Base with VPC MongoosT-50CM2 Grip, VKB-SIM T-RUDDER PEDALS MK.IV. Modules : NEVADA, F-5E, M-2000C, BF-109K4, A-10C, FC3, P-51D, MIG-21BIS, MI-8MTV2, F-86F, FW-190D9, UH-1H, L-39, MIG-15BIS, AJS37, SPITFIRE-MKIX, AV8BNA, PERSIAN GULF, F/A-18C HORNET, YAK-52, KA-50, F-14,SA342, C-101, F-16, JF-17, Supercarrier,I-16,MIG-19P, P-47D,A-10C_II

Link to comment
Share on other sites

I gave up of rummaging through the system, can only do worse... It seems like impossible mission....

At end only remains to hope that in the next pach the developers will solve this problem?!?

Link to comment
Share on other sites

Oh yes, on friday I could fly for 2 hours without any crash. Yesterday DCS crashed always, when loading a new mission, map or aircraft. Somehow I believe it´s always the same error. Hope ED will fix soon. 

  • Like 1

F-14b Tomcat   /   AV-8B Harrier   /   F-16C Viper  /   KA-50 Black Shark   /   Mi-24 Hind   /   MiG-21bis   

Link to comment
Share on other sites

Ok. I read here since the thread started. Just want ro mention I do suffer from this bug as well. My system sent automatic bug reports, too. There must be a lot of users with the very problem, I can't imagine that  the team isn't able to reproduce and fix that sh....

 

I remember I had that second mission load bug sometimes even the last year, but this time since 2.7 it happens EVERYTIME. Deleting fxo helps sometimes but not always.

 

Link to comment
Share on other sites

20 hours ago, Wali763 said:

Considering, that this thread already has 22k+ views I dont think a tiny minority has this problem.

 

Well...it sounds like a lot but...

 

Say this has been going on for 3 weeks --21 days--23,000/21=1095 (rounded to the nearest whole number).

 

Assuming most people, like me, are checking the thread multiple times a day. Say 5 times a day: 1095/5=219. If it were to average out to be 10 checks per day, that'd only be 110 people.


Edited by Ironhand
  • Like 1

YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg

 

_____

Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0.

Link to comment
Share on other sites

Having the issue too I though it was crashing due to problems with some maps and mig 21 (which I got last sale) but apparently its a dcs problem. I have downloaded latest nvidia drivers and have windows 10 20h2 which i installed the other day, with the previous windows 10 update the crashes weren´t as frequent.

Link to comment
Share on other sites

Never had this issue at all until the update on 6 May.

System:Motherboard Asus ROG Strix Z390-E,Asus ROG GeForce RTX 2080Ti OC, GPU, 32GB Corsair Vengeance DDR4 Ram, Intel i9 9900K @ 5 GHz , cooled by NZXT Kraken X52, Acer XB270HU G-Sinc monitor, Windows 10 Pro, Warthog joystick and throttle with wasy extension, VBK Gunfighter Pro and MCG Pro,MFG Rudder, running on a dedicated 1TB Samsung 970 Pro M2 Nvme , Super Wheel Stand Pro, with a HP Reverb G2

Link to comment
Share on other sites

59 minutes ago, Rocky49 said:

Never had this issue at all until the update on 6 May.

You are the lucky man 🙂


Edited by Flia

PC: i7 9700K, 32 GB RAM, RTX 2080 SUPER, Tir 5, Hotas Warthog Throttle, VPC MongoosT-50CM2 Base with VPC MongoosT-50CM2 Grip, VKB-SIM T-RUDDER PEDALS MK.IV. Modules : NEVADA, F-5E, M-2000C, BF-109K4, A-10C, FC3, P-51D, MIG-21BIS, MI-8MTV2, F-86F, FW-190D9, UH-1H, L-39, MIG-15BIS, AJS37, SPITFIRE-MKIX, AV8BNA, PERSIAN GULF, F/A-18C HORNET, YAK-52, KA-50, F-14,SA342, C-101, F-16, JF-17, Supercarrier,I-16,MIG-19P, P-47D,A-10C_II

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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