resolved 2.7.0.4625 Open Beta crash at second mission load

[XPACT]

1 minute ago, RoxSy said:

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

 

I am not sure, but anything is possible at this point

[Cathnan]

39 minutes ago, RoxSy said:

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 ?

Not if my settings are anything to go by. I have it on max and haven't changed it and it still crashes on the second mission.

[Cathnan]

Just a quick report that I fixed my pagefile to 32786MB (same as RAM) and for the first time in days I could start a second mission without crash. I also could immediately end the mission, return to ME, change something and start the mission again several times without crash. Something like this reliably made DCS crash the last few days.

[Wali763]

Hi.

 

I just did a cleanup, emptyed the Temp, the fxo and metashaders2-folder, then set my pagefile to 32GB (even I have 64GB Ram). First mission-reload ended in a crash.

Then unchecked the Fullscreen in the settings. Again. First Mission-reload => crash. Both times with no crashreport-dialoge and I had to log out and back into my windows-account....

Yesterday, by making a a DCS-cleanup my system worked for some time, for sure more than 20 reloads- without a problem, but then it started again.  

[Flia]

Catch those crashes will be very hard im afraid.

[Flappie]

20 minutes ago, Wali763 said:

Hi.

 

I just did a cleanup, emptyed the Temp, the fxo and metashaders2-folder, then set my pagefile to 32GB (even I have 64GB Ram). First mission-reload ended in a crash.

Then unchecked the Fullscreen in the settings. Again. First Mission-reload => crash. Both times with no crashreport-dialoge and I had to log out and back into my windows-account....

Yesterday, by making a a DCS-cleanup my system worked for some time, for sure more than 20 reloads- without a problem, but then it started again.  

When you get no crash report, you can still attach your dcs.log file ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log ).

[Bungmiester]

I to have been been getting these crashes, but after the small update last week they stopped for me.

Last night I was doing some frame rate testing on different maps and was playing around with vsync in the Nvidia control panels and turned it from application controlled to adaptive. When I did this the crashes returned. In Dcs the vsync was set to on, turn the setting back to application controlled in the Nvidia control panels and the crashes have stopped for me so far. I'm running the latest version of Windows and Nvidia drivers on a 1060 Graphic card. By the way I haven't noticed that much improvement with the channel map fps and only have a mediocre computer.

[Wali763]

Lastest dcs.log

 

dcs.20210426-182147.dmp dcs.log

Edited April 26, 2021 by Wali763

[Ironhand]

  Given how difficult and frustrating this is for all of us, I think ED should send us duplicates of either Flappie’s or  Bignewy’s systems until this is resolved.

 

We promise to return them...eventually.

Edited April 26, 2021 by Ironhand

[CSL_Ondras]

On 4/25/2021 at 7:31 PM, CSL_Ondras said:

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.

 

Reminder of my previous post - I have crashed once this evening, during the 2nd mission load, than cleaned C:\Users\ondre\Saved Games\DCS.openbeta\fxo and now I am flying the whole evening without issues. Can anyone try to reproduce this to confirm, whether it is, or it is not, just me?

 

O.

[Flappie]

1 hour ago, Wali763 said:

Lastest dcs.log

 

dcs.20210426-182147.dmp 499.67 kB · 0 downloads dcs.log 439.02 kB · 0 downloads

 

Many thanks for your logs, @Wali763.

 

Hey, I see something here  that I hadn't seen in previous crashlogs, although I can see now both Kevtosmart and MattCri had it in theirs as well. A Lua errors is detailed after the crash dump. It deals with terrain initialization. Here:

 

2021-04-26 18:25:00.219 INFO    EDCORE: Minidump created.
2021-04-26 18:25:00.219 INFO    Lua::Config: stack traceback:
	[C]: in function 'Init'
	[string "./MissionEditor/modules/me_map_window.lua"]:811: in function 'initTerrain'
	[string "./MissionEditor/modules/me_mission.lua"]:1638: in function 'load'
	[string "./MissionEditor/modules/me_quickstart.lua"]:274: in function 'func'
	[string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater'
	[string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>
2021-04-26 18:25:00.219 INFO    Lua::Config: stack traceback:
2021-04-26 18:25:00.219 WARNING LOG: 1 duplicate message(s) skipped.

 

@BIGNEWYEither it's just a consequence of the crash, or we may have something here. For some reason, this Lua crash appears after the crashdump. This is probably why we don't see it often. But it seems to be of significant importance in these second missions loading crashes.

 

Same Lua error here, and  here.

Edited April 26, 2021 by Flappie

[zero]

Added just Syria map and F-16. to 2.7 for instant action test. - First flight is quick loading with no issues.

 

PC freeeze after loading  second  mission.

 

Memory use: 96%

 

2.7 looks great. No doubt DCS  will fix this..

 

 

[84-Simba]

I flew the whole evening the same custom AA combat training mission against Su-27s and Su-24s, over and over again.

 

The bad thing is : I suck ... but that's not the point.

 

Good thing though is that since I got killed numerous times I had to refly directly the mission (pressing ''Fly Again'') many times and did not crashed one single time.

 

I did the clear temp thing, but I don't know if it's related.

It didn't do any harm though.

 

One thing I noticed, and I really don't know if it is relevant, is that some details are different from one refly to another when I startup the Hornet, like default elevators pitch (sometimes nose down 2 degrees, sometimes 3, sometimes nose up a few degrees) and the radar contact memory (sometimes by default at 4 seconds, sometimes 8, sometimes 16)

 

I don't know if some parameters are just applied randomly or if they are supposed to be a certain value every single time you start-up cold and dark ...

Edited April 26, 2021 by RoxSy

[the_jovian]

On 4/26/2021 at 2:27 PM, BIGNEWY said:

Hi all, 

 

I am sharing your feedback with the team. 

 

so far I am unable to reproduce myself however.

 

thanks

 

I can consistently crash every time I try to refly the F-14B Training mission "Basics - Carrier Case-1 Trap". I don't think I've ever been able to refly this successfully.

 

Can anyone else try this one?

[Ironhand]

FWIW, two days ago, I deleted the folder in TEMP and Saved Games XFO, started DCS and select FULL SCREEN on the Options page. I have been through about 10 or 12 mission restarts closing the sim at the end of the day, starting the sim the next day (without deleting anything) and flown without a problem again.

[the_jovian]

On 4/26/2021 at 12:00 AM, jfnelson0127 said:

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

 

I'm running the standalone, but it might be somewhere in C:\Program Files (x86)\Steam\steamapps\common , there's probably a DCS folder somewhere there. Maybe under Eagle Dynamics?

 

This didn't help for me unfortunately, even though I thought it did at first.

[Flappie]

1 hour ago, the_jovian said:

 

I can consistently crash every time I try to refly the F-14B Training mission "Basics - Carrier Case-1 Trap". I don't think I've ever been able to refly this successfully.

 

Can anyone else try this one?

I've just tried this, and I'm stll unable to reproduce the crash.

Edited April 27, 2021 by Flappie

[theoklahomaaviator]

I’m gonna ask what might be a stupid question but would having adding Microsoft Flight Sim 2020 to my system introduced something that is why I get crashes and the Dev’s don’t?  Like perhaps an update to DirectX or one of the many .NET updates?  Do any of you that are experiencing crashes also have the latest Microsoft Flight Sim installed?  Reason I ask is my system really only has 3 things installed other than the Alienware stuff that came with the OS, the standard windows stuff, DCS, MSFS2020, and TrackIR 5.4.

 

I’m literally considering a fresh Windows install and then a fresh DCS install.  I’ve thought I had this beat as so many others have as well and about the time I feel confident it starts crashing again.

[the_jovian]

1 hour ago, theoklahomaaviator said:

I’m gonna ask what might be a stupid question but would having adding Microsoft Flight Sim 2020 to my system introduced something that is why I get crashes and the Dev’s don’t?  Like perhaps an update to DirectX or one of the many .NET updates?  Do any of you that are experiencing crashes also have the latest Microsoft Flight Sim installed?  Reason I ask is my system really only has 3 things installed other than the Alienware stuff that came with the OS, the standard windows stuff, DCS, MSFS2020, and TrackIR 5.4.

 

I’m literally considering a fresh Windows install and then a fresh DCS install.  I’ve thought I had this beat as so many others have as well and about the time I feel confident it starts crashing again.

 

I haven't got MSFS2020 installed and this is a pretty fresh system, only about 2 months old.

 

2 hours ago, Flappie said:

I've just tried this, and I'm stll unable to reproduce the crash.

 

 

That did give me an idea, though this is just a shot in the dark. @Flappie, what version of .NET are you running? I'm using 4.8.4084.0 .

[Art-J]

No MSFS on my system, and crashes are still here, although somewhat less frequent nowadays after using  in-game Full Screen off method.

Edited April 27, 2021 by Art-J

[theoklahomaaviator]

6 minutes ago, Art-J said:

No MSFS on my system, and crashes are still here, although somewhat less frequent nowadays after using  in-game Full Screen off method.

 

Even when I de-select full screen my DCS is always full screen.  At no point is it ever “windowed”.  Since discovering that I’ve wondered if it’s related to crashing.  I thought it was initially based on how I had no issues after de-selecting full screen but after restarting my computer the crashes are back regardless of this setting.  I will go through tonight and post any diagnostics I can gather along with what steps I can do to consistently get a crash.

[fagulha]

On 4/14/2021 at 6:25 PM, Flappie said:

OK. I can't find a previous crash report dealing with "D3D11CoreCreateDevice". This looks new from DCS perspective.

 

I copy-paste your crashlog here to ease discussion:

 

2021-04-14 15:59:33.688 INFO    WORLDGENERAL: loaded from mission Scripts/World/birds.lua
2021-04-14 15:59:33.703 INFO    TACVIEW.EXPORT: Loading C++ flight data recorder from [C:\Users\XPACT\Saved Games\DCS\Mods\tech\Tacview\bin\]
2021-04-14 15:59:33.703 INFO    TACVIEW.EXPORT: Tacview 1.8.2 C++ flight data recorder successfully loaded
2021-04-14 15:59:33.823 INFO    VISUALIZER: Preload() camera=-199523.829366, 500.757416, 518005.373777 radius=150000.000000
2021-04-14 15:59:33.823 INFO    EDTERRAINGRAPHICS41: ITerrainGraphicsImpl4::forceLoading(): pos=(-199524, 500.757, 518005), radius=150000
2021-04-14 15:59:34.031 INFO    EDTERRAINGRAPHICS41: surface5 clean up LOD 0: left 8  released 78
2021-04-14 15:59:34.032 INFO    EDTERRAINGRAPHICS41: surface5 clean up LOD 1: left 10  released 76
2021-04-14 15:59:34.032 INFO    EDTERRAINGRAPHICS41: surface5 clean up 3.203700 ms
2021-04-14 15:59:34.993 INFO    VISUALIZER: Preload() finished
2021-04-14 15:59:35.008 INFO    TACVIEW.DLL: Tacview Flight Data Recorder 1.8.2 Loaded
2021-04-14 15:59:35.008 INFO    TACVIEW.DLL: Config={bookmarkShortcut=0, compressionLevel=1, dataRecordingEnabled=0, debugModeEnabled=0, hostTelemetryPassword="", playbackDelay=600, profilingPeriod=600, realTimeTelemetryPort=42674, recordClientsSessionsEnabled=0, remoteControlPassword="", remoteControlPort=42675}
2021-04-14 15:59:35.008 INFO    DCS: Screen: mission_offline
2021-04-14 15:59:35.009 INFO    EDCORE: try to write dump information
2021-04-14 15:59:35.010 INFO    EDCORE: # -------------- 20210414-155935 --------------
2021-04-14 15:59:35.011 INFO    EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.19042)
2021-04-14 15:59:35.011 INFO    EDCORE: C:\Windows\SYSTEM32\d3d11.dll
2021-04-14 15:59:35.012 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 27946BAE 00:00000000
2021-04-14 15:59:35.013 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;F:\Games\SteamLibrary\steamapps\common\DCSWorld;F:\Games\SteamLibrary\steamapps\common\DCSWorld\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'XPACT'
2021-04-14 15:59:35.014 INFO    EDCORE: OS-Version: 10.0.19042 () 0x100-0x1
2021-04-14 15:59:35.547 INFO    EDCORE: 0x0000000000016BAE (d3d11): (function-name not available) + 0x0
2021-04-14 15:59:35.547 INFO    EDCORE: 0x00000000000169F9 (d3d11): (function-name not available) + 0x0
2021-04-14 15:59:35.547 INFO    EDCORE: 0x0000000000029EE3 (d3d11): D3D11CoreCreateDevice + 0x9823
2021-04-14 15:59:35.547 INFO    EDCORE: 0x0000000000028C25 (d3d11): D3D11CoreCreateDevice + 0x8565
2021-04-14 15:59:35.547 INFO    EDCORE: 0x00000000000295A6 (d3d11): D3D11CoreCreateDevice + 0x8EE6
2021-04-14 15:59:35.547 INFO    EDCORE: 0x000000000004B65B (d3d11): D3D11CoreCreateDevice + 0x2AF9B
2021-04-14 15:59:35.547 INFO    EDCORE: 0x0000000000043525 (d3d11): D3D11CoreCreateDevice + 0x22E65
2021-04-14 15:59:35.548 INFO    EDCORE: 0x0000000000042D16 (dx11backend): createRenderer + 0x2AFA6
2021-04-14 15:59:35.548 INFO    EDCORE: 0x0000000000042E82 (dx11backend): createRenderer + 0x2B112
2021-04-14 15:59:35.548 INFO    EDCORE: 0x000000000002DDC5 (NGModel): model::ModelMaterial::draw + 0x2595
2021-04-14 15:59:35.548 INFO    EDCORE: 0x00000000000315E0 (NGModel): model::ModelMaterial::draw + 0x5DB0
2021-04-14 15:59:35.548 INFO    EDCORE: 0x0000000000034F54 (NGModel): model::ModelMaterial::draw + 0x9724
2021-04-14 15:59:35.549 INFO    EDCORE: 0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
2021-04-14 15:59:35.549 INFO    EDCORE: 0x0000000000037E02 (NGModel): model::ModelMaterial::draw + 0xC5D2
2021-04-14 15:59:35.549 INFO    EDCORE: 0x0000000000041EF5 (NGModel): init_graphics_plugin + 0x2EE5
2021-04-14 15:59:35.549 INFO    EDCORE: 0x0000000000042038 (NGModel): model::NGModelLods::~NGModelLods + 0x48
2021-04-14 15:59:35.549 INFO    EDCORE: 0x000000000004286E (NGModel): model::NGModelLods::~NGModelLods + 0x87E
2021-04-14 15:59:35.550 INFO    EDCORE: 0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
2021-04-14 15:59:35.550 INFO    EDCORE: 0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20
2021-04-14 15:59:35.550 INFO    EDCORE: 0x0000000000801B04 (DCS):  ??  + 0x801B04
2021-04-14 15:59:35.550 INFO    EDCORE: 0x00000000007E91C9 (DCS):  ??  + 0x7E91C9
2021-04-14 15:59:35.550 INFO    EDCORE: 0x000000000011743A (edCore): Common::FSM::sendOutputSymbol_ + 0x4A
2021-04-14 15:59:35.550 INFO    EDCORE: 0x0000000000116AD2 (edCore): Common::FSM::enterToState_ + 0xC2
2021-04-14 15:59:35.551 INFO    EDCORE: 0x00000000001172B9 (edCore): Common::FSM::onSymbol_ + 0x1A9
2021-04-14 15:59:35.551 INFO    EDCORE: 0x00000000007FF141 (DCS):  ??  + 0x7FF141
2021-04-14 15:59:35.551 INFO    EDCORE: 0x00000000007D0174 (DCS):  ??  + 0x7D0174
2021-04-14 15:59:35.551 INFO    EDCORE: 0x00000000007D0544 (DCS):  ??  + 0x7D0544
2021-04-14 15:59:35.551 INFO    EDCORE: 0x0000000001C22FC2 (DCS): AmdPowerXpressRequestHighPerformance + 0xE29FBE
2021-04-14 15:59:35.551 INFO    EDCORE: 0x0000000000A060DE (DCS):  ??  + 0xA060DE
2021-04-14 15:59:35.552 INFO    EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2021-04-14 15:59:35.552 INFO    EDCORE: 0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21
2021-04-14 15:59:35.859 INFO    EDCORE: Minidump created.

 

 

I tried to reproduce from my end but I can't. What mission are you using for your test exactly?

Hi,

 

sorry to bother you but can you see my crash file please? do you know what possible can be?

Thank you.

 

Regards,

Bruno.

dcs.20210427-181331.crash

[XPACT]

I don't have MSFS2020 also, system except for GPU is 2 months old. For 2 days straight didn't have any crash but I am calmly expecting their return... 

[XPACT]

11 minutes ago, theoklahomaaviator said:

Even when I de-select full screen my DCS is always full screen.  At no point is it ever “windowed”.

 

 

Because DCS is running in so called borderless windowed regime, basically resolution will be the same and you won't know the difference but alt tab will function much better than exclusive fullscreen mode. If you have no black screen in between alt tabbing game is in borderless windowed. 

[hornblower793]

5 hours ago, the_jovian said:

 

I can consistently crash every time I try to refly the F-14B Training mission "Basics - Carrier Case-1 Trap". I don't think I've ever been able to refly this successfully.

 

Can anyone else try this one?

I tried this and got the crash at second mission load (log file and dxdiag attached). Having logged out and in again I then looked at my AV (Bitdefender) and realised I hadn't updated the exceptions list when I moved DCS, so it was still pointing at the old location. I changed this, have gone back into DCS and managed to start this training mission 4 times in a row without issue. I have also attached the log file from the run that worked happily in case there are any clues

DxDiag.txt dcs-F14 crash.log

dcs.log

Edited April 27, 2021 by hornblower793