Rocky49 Posted May 7, 2021 Share Posted May 7, 2021 (edited) Can't proceed past load mission I have run a complete repair and can get it to run but now framerates are so low that it can't be played dcs.20210507-163639.crash Edited May 7, 2021 by Rocky49 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 More sharing options...
Pocket Kings Posted May 7, 2021 Share Posted May 7, 2021 (edited) Hey Michael, I'm quoting myself from another thread: On 5/4/2021 at 4:59 PM, Pocket Kings said: Are you aware of the Windows Update package KB4589212. Some people noted that uninstalling, rebooting and reinstalling the package helped a great deal. Also, use newest NVidia drivers. I'm afraid I can't be of more help since I don't encounter these crashes. This is the thread BTW: Edited May 7, 2021 by Pocket Kings formatting Link to comment Share on other sites More sharing options...
Rocky49 Posted May 8, 2021 Author Share Posted May 8, 2021 Thanks for the response. I have the latest Nvidia Driver 466.27, which, up to Yesterday worked great on DCS. I do not have the KB4589212 installed. My version of Windows 10 is 20H2 KB4023057 which was installed 29 April, prior to this latest DCS update and worked great. 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 More sharing options...
Flappie Posted May 8, 2021 Share Posted May 8, 2021 (edited) Please attach the most recent zip file you can find in "C:\Users\username\Saved Games\DCS...\Logs\". Edited May 8, 2021 by Flappie typo Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Rocky49 Posted May 8, 2021 Author Share Posted May 8, 2021 Flappie, Zip file as requested dcs.log-20210507-171937.zip 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 More sharing options...
Flappie Posted May 8, 2021 Share Posted May 8, 2021 (edited) Thank you. You're having the second mission loading crash. This issue came with DCS 2.7 initial release, and has not been fixed yet. I made a summary of existing solutions that may work, at least for some time. You're free to try the different solutions. 2021-05-07 17:19:36.108 INFO DCS: Screen: mission_offline 2021-05-07 17:19:36.109 INFO EDCORE: try to write dump information 2021-05-07 17:19:36.114 INFO EDCORE: # -------------- 20210507-171937 -------------- 2021-05-07 17:19:36.116 INFO EDCORE: DCS/2.7.0.5659 (x86_64; Windows NT 10.0.19042) 2021-05-07 17:19:36.117 INFO EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll 2021-05-07 17:19:36.118 INFO EDCORE: # C0000005 ACCESS_VIOLATION at D82977A4 00:00000000 2021-05-07 17:19:36.123 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\DCS World OpenBeta;D:\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Michael' 2021-05-07 17:19:36.125 INFO EDCORE: OS-Version: 10.0.19042 () 0x100-0x1 2021-05-07 17:19:36.517 INFO EDCORE: 0x00000000000A77A4 (d3d11): D3DKMTWaitForVerticalBlankEvent + 0x53174 2021-05-07 17:19:36.518 INFO EDCORE: 0x000000000000AAA4 (d3d11): (function-name not available) + 0x0 2021-05-07 17:19:36.518 INFO EDCORE: 0x000000000004F2AD (d3d11): D3D11CoreCreateDevice + 0x2EBED 2021-05-07 17:19:36.519 INFO EDCORE: 0x0000000000029580 (d3d11): D3D11CoreCreateDevice + 0x8EC0 2021-05-07 17:19:36.519 INFO EDCORE: 0x000000000004B65B (d3d11): D3D11CoreCreateDevice + 0x2AF9B 2021-05-07 17:19:36.519 INFO EDCORE: 0x0000000000043525 (d3d11): D3D11CoreCreateDevice + 0x22E65 2021-05-07 17:19:36.519 INFO EDCORE: 0x0000000000042D16 (dx11backend): createRenderer + 0x2AFA6 2021-05-07 17:19:36.519 INFO EDCORE: 0x0000000000042E82 (dx11backend): createRenderer + 0x2B112 2021-05-07 17:19:36.520 INFO EDCORE: 0x000000000002DDC5 (NGModel): model::ModelMaterial::draw + 0x2595 2021-05-07 17:19:36.520 INFO EDCORE: 0x00000000000315E0 (NGModel): model::ModelMaterial::draw + 0x5DB0 2021-05-07 17:19:36.520 INFO EDCORE: 0x0000000000034FB4 (NGModel): model::ModelMaterial::draw + 0x9784 2021-05-07 17:19:36.520 INFO EDCORE: 0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473 2021-05-07 17:19:36.521 INFO EDCORE: 0x0000000000037DC2 (NGModel): model::ModelMaterial::draw + 0xC592 2021-05-07 17:19:36.521 INFO EDCORE: 0x0000000000041F3D (NGModel): init_graphics_plugin + 0x2F6D 2021-05-07 17:19:36.521 INFO EDCORE: 0x0000000000042088 (NGModel): model::NGModelLods::~NGModelLods + 0x48 2021-05-07 17:19:36.521 INFO EDCORE: 0x000000000004291E (NGModel): model::NGModelLods::~NGModelLods + 0x8DE 2021-05-07 17:19:36.521 INFO EDCORE: 0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3 2021-05-07 17:19:36.522 INFO EDCORE: 0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20 2021-05-07 17:19:36.522 INFO EDCORE: 0x0000000000801E54 (DCS): SW + 0x5114A4 2021-05-07 17:19:36.522 INFO EDCORE: 0x00000000007E9349 (DCS): SW + 0x4F8999 2021-05-07 17:19:36.522 INFO EDCORE: 0x000000000011786A (edCore): Common::FSM::sendOutputSymbol_ + 0x4A 2021-05-07 17:19:36.522 INFO EDCORE: 0x0000000000116F02 (edCore): Common::FSM::enterToState_ + 0xC2 2021-05-07 17:19:36.522 INFO EDCORE: 0x00000000001176E9 (edCore): Common::FSM::onSymbol_ + 0x1A9 2021-05-07 17:19:36.523 INFO EDCORE: 0x00000000007FF491 (DCS): SW + 0x50EAE1 2021-05-07 17:19:36.523 INFO EDCORE: 0x00000000007D0234 (DCS): SW + 0x4DF884 2021-05-07 17:19:36.523 INFO EDCORE: 0x00000000007D060D (DCS): SW + 0x4DFC5D 2021-05-07 17:19:36.523 INFO EDCORE: 0x0000000001C38FBD (DCS): AmdPowerXpressRequestHighPerformance + 0xE49FB9 2021-05-07 17:19:36.523 INFO EDCORE: 0x0000000000A071BE (DCS): SW + 0x71680E 2021-05-07 17:19:36.524 INFO EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 2021-05-07 17:19:36.524 INFO EDCORE: 0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21 2021-05-07 17:19:36.753 INFO EDCORE: Minidump created. Edited May 8, 2021 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Rocky49 Posted May 9, 2021 Author Share Posted May 9, 2021 Thank-you for the update. I did not have this issue with the initial roll out of DCS 2.7 but it appeared after the update on the 6th of May. I have done most of the things you list so I guess I just have to wait to see if the can fix this issue. 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 More sharing options...
Pocket Kings Posted May 9, 2021 Share Posted May 9, 2021 Another user in another thread rolled back to the initial 2.7 version and flew one 2h mission and one 3h mission without any crash or hickup. If you can live without MP for the time being, maybe that's a viable workaround for you. Link to comment Share on other sites More sharing options...
SliderCDN Posted May 10, 2021 Share Posted May 10, 2021 13 hours ago, Pocket Kings said: Another user in another thread rolled back to the initial 2.7 version and flew one 2h mission and one 3h mission without any crash or hickup. If you can live without MP for the time being, maybe that's a viable workaround for you. That's me and it's not a solution. Merely a proving point there is something wrong with the latest update. Link to comment Share on other sites More sharing options...
Pocket Kings Posted May 10, 2021 Share Posted May 10, 2021 I didn't say it's a solution, it certainly isn't. I used the word workaround. IMO it's better to fly without the canopy, but still fly, than crash down right away. If you can't live with DCS currently, these are your options: 1. quit 2. fly stable 2.5.6 3. rant on None of the three get you or me closer to a solution. Don't forget, we're talking beta here and beta means "something wrong", I've never encountered a bug free beta in my life as a professional. Link to comment Share on other sites More sharing options...
Recommended Posts