farebro Posted February 29, 2024 Posted February 29, 2024 any advice getting Game crashes, fly apache for an hour or 2 jump in Hornet hit A/G and then get crash. fly Hornet first then apache it crashes shortly after. reinstalled completely and get the same 1
Flappie Posted February 29, 2024 Posted February 29, 2024 Hi. Please attach the latest zip file from "Saved Games/DCS.../Logs". ---
farebro Posted March 1, 2024 Author Posted March 1, 2024 Hey Flappie dcs.log-20240301-185650.zip dcs.log-20240229-195723.zip 1
Flappie Posted March 1, 2024 Posted March 1, 2024 (edited) Thanks. It's the first time ever I see this kind of crash: 2024-03-01 18:56:18.060 WARNING BACKENDCOMMON (1788): Need to reprocess [DDS] image '/textures/Deck_Normal.dds' 2024-03-01 18:56:18.255 ERROR_ONCE DX11BACKEND (9800): texture 'wet_map_map' not found. Asked from '' 2024-03-01 18:56:19.344 INFO ASYNCNET (Main): Current ping: 1.4ms 2024-03-01 18:56:20.491 ERROR_ONCE DX11BACKEND (1788): texture 'nimitz_details_72_dm_map' not found. Asked from '' 2024-03-01 18:56:21.971 WARNING BACKENDCOMMON (1788): Need to reprocess [DDS] image '/textures/F18C_1_DIFF_STAY_nm.dds' 2024-03-01 18:56:22.377 WARNING BACKENDCOMMON (9800): Need to reprocess [DDS] image '/textures/Deck_Normal.dds' 2024-03-01 18:56:49.348 INFO ASYNCNET (Main): Current ping: 1.6ms 2024-03-01 18:56:49.942 ERROR GRAPHICSCORE (2080): Failed assert `depthBuffer.getDims() == dims && depthBuffer.getMSAA() == msaa` at D:\Projects\Buildworker\nevada_testing\build\Projects\render\renderer\Include\rwrappers\inl/FrameBuffer.inl:339 2024-03-01 18:56:49.942 ERROR DX11BACKEND (2080): depth buffer mfdDepthBuffer (1280x1280) must be the same size as color targets (1024x1024) 2024-03-01 18:56:49.942 ERROR DX11BACKEND (2080): Failed assert `false && "depth buffer must be the same size as color targets"` at Projects\render\dx11backend_win8\Source\DX11FrameBufferManager.cpp:101 2024-03-01 18:56:49.944 INFO EDCORE (2080): try to write dump information 2024-03-01 18:56:49.947 INFO EDCORE (2080): # -------------- 20240301-185650 -------------- 2024-03-01 18:56:49.947 INFO EDCORE (2080): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.19045) 2024-03-01 18:56:49.948 INFO EDCORE (2080): E:\DCS World\bin-mt\dx11backend.dll 2024-03-01 18:56:49.948 INFO EDCORE (2080): # C0000005 ACCESS_VIOLATION at 00007ffc68628c77 00:00000000 2024-03-01 18:56:49.949 INFO EDCORE (2080): SymInit: Symbol-SearchPath: 'E:\DCS World\bin-mt;', symOptions: 532, UserName: 'davef' 2024-03-01 18:56:49.950 INFO EDCORE (2080): OS-Version: 10.0.19045 () 0x300-0x1 2024-03-01 18:56:49.950 INFO EDCORE (2080): 0x0000000000018c77 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 2024-03-01 18:56:49.955 INFO EDCORE (2080): 0x0000000000017788 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 2024-03-01 18:56:49.956 INFO EDCORE (2080): 0x000000000000be2e (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x40E 2024-03-01 18:56:49.956 INFO EDCORE (2080): 0x00000000000a3a41 (GraphicsCore): render::ShadowMapModule::queryCasters + 0x921 2024-03-01 18:56:49.956 INFO EDCORE (2080): 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 2024-03-01 18:56:49.956 INFO EDCORE (2080): 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4 2024-03-01 18:56:49.956 INFO EDCORE (2080): 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 2024-03-01 18:56:49.957 INFO EDCORE (2080): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 2024-03-01 18:56:49.958 INFO EDCORE (2080): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92 2024-03-01 18:56:49.958 INFO EDCORE (2080): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14 2024-03-01 18:56:52.232 INFO EDCORE (2080): Minidump created. It seems to deal with MSAA and wet carrier deck texture. Try this: Rename options.lua to options.lua.bak (in Saved Games/DCS.../Config). Purge your "fxo" and "metashaders2" folders (in Saved Games/DCS...). Purge this folder: "C:\Users\your-login\AppData\LocalLow\NVIDIA\PerDriverVersion". Edited March 1, 2024 by Flappie ---
HeliHell Posted March 2, 2024 Posted March 2, 2024 Apache to Hornet seems to be the issue. # -------------- 20240301-194052 -------------- DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631) C:\Program Files\Eagle Dynamics\DCS World\bin-mt\dx11backend.dll # C0000005 ACCESS_VIOLATION at 00007ffbbea18c77 00:00000000 SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'adamc' OS-Version: 10.0.22631 () 0x100-0x1 0x0000000000018c77 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 0x0000000000017788 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 0x000000000000be2e (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x40E 0x00000000000a3a41 (GraphicsCore): render::ShadowMapModule::queryCasters + 0x921 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
farebro Posted March 2, 2024 Author Posted March 2, 2024 Flappie done as briefed still the same dry weather runway all crashes but not giving a log, ED said reinstall Nvidia drivers. mate its not just me with this issue 1
farebro Posted March 2, 2024 Author Posted March 2, 2024 dcs.log-20240302-170226.zip dcs.log-20240302-171257.zip 1
silverdevil Posted March 2, 2024 Posted March 2, 2024 (edited) @Flappiedcs.log and @farebro i can confirm i crashed viewing the posted track immediately after spawning into Hornet from Apache. Edited March 2, 2024 by silverdevil 1 2 AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
RAFFT Posted March 2, 2024 Posted March 2, 2024 dcs.log-20240302-175003.zip It's happening to me too.
silverdevil Posted March 2, 2024 Posted March 2, 2024 (edited) 2 hours ago, Flappie said: Thanks @silverdevil, I'll check tomorrow. you are welcome. more info i gathered after crash in case it helps Quote corresponding windows event in application log Log Name: Application Source: Application Error Date: 3/2/2024 12:37:31 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-FG6S6BJ Description: Faulting application name: DCS.exe, version: 2.9.3.51704, time stamp: 0x65d64608 Faulting module name: dx11backend.dll, version: 2.9.3.51704, time stamp: 0x65d3ca7d Exception code: 0xc0000005 Fault offset: 0x0000000000018c77 Faulting process id: 0x5fe8 Faulting application start time: 0x01da6cc7ab982397 Faulting application path: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe Faulting module path: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\dx11backend.dll Report Id: 9c51eaf4-cb6e-4f9f-a25f-545ba84d604d Faulting package full name: Faulting package-relative application ID: noticed that screen saver after the crash did not engage; needed to restart windows when restarting windows a .NET 4.0.0 hidden notification window prevented windows from restarting; windows after a slight delay did restart. i searched and found some precedence, albeit old. Edited March 2, 2024 by silverdevil AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Flappie Posted March 3, 2024 Posted March 3, 2024 If anyone has the crash happening over Caucasus too, I'd be interested in getting the zip file. Thanks. ---
farebro Posted March 3, 2024 Author Posted March 3, 2024 Flappie here u go mate Caucasus too dcs.log-20240303-121842.zip 2
Dangerzone Posted March 4, 2024 Posted March 4, 2024 On 3/1/2024 at 7:13 AM, farebro said: any advice getting Game crashes, fly apache for an hour or 2 jump in Hornet hit A/G and then get crash. fly Hornet first then apache it crashes shortly after. reinstalled completely and get the same Re DCS crashing to desktop when you hit the A/G mode in your Hornet. Did that happen for you only after flying the Apache, or have you had that issue when only flying the one airframe? I've had the A/G mode crash on me twice too. I don't recall if I was flying the Apache prior, but am trying to figure out a workaround or what I can do as a precaution before the patch is released, as we've got a big DCS event coming up this coming weekend and any info on what to avoid crashing out on with A/G mode in the Hornet would be very much appreciated.
farebro Posted March 4, 2024 Author Posted March 4, 2024 Morning Dangerzone happens to most pilots and as far as i can see its the Apache and Hornet that are having issue. we tried going back to to spectators before swapping but still same issue and on other maps. ED did come back to me almost straight away and suggested Nvidia may be the cause (standard response) but i have sent so many bug reports hope they can sort it out 1
Flappie Posted March 4, 2024 Posted March 4, 2024 6 minutes ago, farebro said: ED did come back to me almost straight away and suggested Nvidia may be the cause (standard response) but i have sent so many bug reports hope they can sort it out The issue is now reported internally, whether it is NVIDIA-related or not. 1 ---
Dangerzone Posted March 5, 2024 Posted March 5, 2024 On 3/4/2024 at 6:22 PM, farebro said: Morning Dangerzone happens to most pilots and as far as i can see its the Apache and Hornet that are having issue. we tried going back to to spectators before swapping but still same issue and on other maps. ED did come back to me almost straight away and suggested Nvidia may be the cause (standard response) but i have sent so many bug reports hope they can sort it out Thanks. So basically it's only an issue if swapping between these 2 airframes. If I stick to one, then log out, and log back in to change to another I should be safe (at least from what you've observed so far)? I'm submitting bug reports as they crash for me as well. The only thing is I couldn't remember the time it's crashed in the FA18 when selecting Ground if I had been in the Apache prior to.
Flappie Posted March 5, 2024 Posted March 5, 2024 1 hour ago, Dangerzone said: Thanks. So basically it's only an issue if swapping between these 2 airframes. If I stick to one, then log out, and log back in to change to another I should be safe (at least from what you've observed so far)? Yes, that should work. Please bear in mind there is another bug in town (not 100% reproducible, unlike the other) which cause a crash when you respawn in the same aircraft (happens so far with Mi-24P, Spitifre and A-10C). Both bugs are under investigation by devs. 1 ---
Batrag Posted March 5, 2024 Posted March 5, 2024 (edited) Before 2 Days after i heard from this i Tryed to force this Crash. Setting up a Mission and Fly first Apache and then Fa 18 and switch`d to A/G Mode and expierienced no Crash. Today i Changed my Setup from intel 13600K to 14900K And tested the Sim. As Soon as i switched in the Same Mission from Ah64 to Fa 18 and activated A/G mode DCS Crashed. I dont think it has something to do with the Processor Change but i better mentioned here. dcs.log-20240305-170240.zip Edited March 5, 2024 by Batrag 1
QbanRambo Posted March 15, 2024 Posted March 15, 2024 (edited) Happens to me too... make me crazy... Now I realize is always when change from Ah-64 to F-18 AND A10C II too... # -------------- 20240315-005654 -------------- DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631) D:\DCS World\bin-mt\dx11backend.dll # C0000005 ACCESS_VIOLATION at 00007ff91cc18c77 00:00000000 SymInit: Symbol-SearchPath: 'D:\DCS World\bin-mt;', symOptions: 532, UserName: 'yurim' OS-Version: 10.0.22631 () 0x300-0x1 0x0000000000018c77 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 0x0000000000017788 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 0x000000000000be2e (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x40E 0x00000000000a3a41 (GraphicsCore): render::ShadowMapModule::queryCasters + 0x921 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D Edited March 15, 2024 by QbanRambo
Flappie Posted March 15, 2024 Posted March 15, 2024 That's the one, indeed ("AtmosphereWrapper"). It's fixed internally. The fix should be part of the next DCS update. 2 ---
Chesster Posted March 20, 2024 Posted March 20, 2024 (edited) The same issue is also valid when spawning into the A-10C II after having spawned into the Apache first (logs attached). dcs.log-20240320-090158.zip edit: Noticed QbanRambo's post explaining the same thing. Edited March 20, 2024 by Chesster 1
GunnyCook Posted April 4, 2024 Posted April 4, 2024 I get the same, started a thread in AH bugs, Removed all mods and did a slow repair deleting any files found after. created a map on cauc, 1 base with 1 AH and 1 KA/3. started a multiplayer server, selected the AH, spawned, hovered and landed, jumped into the KA/3 and the game crashed. i have done the same with most of the maps i have with the same result. Win10 64, GeForce GTX1080 Ti, Rift touch, i5- 2.90GHz(o/c), 16gb Corsair Vengance RAM, X-56 KA-50-3, AH-64D, A10c II, AV-8B, MI-8, Spitfire, Viggen, FC3, F-14, F-15c,FA-18, S/Carrier, CA, Nevada, Normandy 44, Channel, Persian gulf, Marianas, Syria, Sth Atlantic,
Recommended Posts