Jump to content

Terrain Preload 100: ,Stage 38 crash.


AtlasR1se

Recommended Posts

So after the lengthy update to 2.9, thought I would try out a few training missions to check it all out.

Imagine my (not very much) surprise when all missions at all settings lock up on loading screen,

loading stops and locks up at Terrain Preload 100 : Stage 38.
Any guidance into what is happening would be a massive help.
Thanks.

Link to comment
Share on other sites

Yes, that's even better that what I asked, since some of these zips include the dcs.log file alog with other useful files such as dxdiag.log (DirectX log).

Here we go:

2023-10-21 22:04:23.535 INFO    APP (Main): CPU cores: 6, threads: 12, System RAM: 49068 MB, Pagefile: 7168 MB

DCS has just enough memory (RAM + pagefile) to run in MP and over a big map such as Syria. Your issue doesn't seem to come from a memory shortage, so I won't ask you to edit your pagefile settings for now.

Here comes the crash:

2023-10-21 22:05:24.992 INFO    EDTERRAINGRAPHICS41 (12476): 	 distanceFactor = 1.200000
2023-10-21 22:05:24.992 INFO    EDTERRAINGRAPHICS41 (12476): 	 instancerDetailsFactor = 0.341667
2023-10-21 22:05:24.992 INFO    EDTERRAINGRAPHICS41 (12476): 	 forestDistanceFactor = 0.730000
2023-10-21 22:05:24.992 INFO    EDTERRAINGRAPHICS41 (12476): 	 forestDetailsFactor = 0.508333
2023-10-21 22:05:25.221 INFO    EDCORE (12476): try to write dump information
2023-10-21 22:05:25.458 INFO    EDCORE (12476): # -------------- 20231021-220525 --------------
2023-10-21 22:05:25.458 INFO    EDCORE (12476): DCS/2.9.0.46801 (x86_64; MT; Windows NT 10.0.19045)
2023-10-21 22:05:25.459 INFO    EDCORE (12476): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\Visualizer.dll
2023-10-21 22:05:25.459 INFO    EDCORE (12476): # C0000005 ACCESS_VIOLATION at 00007ff9d3f55111 00:00000000
2023-10-21 22:05:25.460 INFO    EDCORE (12476): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'paulm'
2023-10-21 22:05:25.461 INFO    EDCORE (12476): OS-Version: 10.0.19045 () 0x300-0x1
2023-10-21 22:05:25.461 INFO    EDCORE (12476): 0x0000000000075111 (Visualizer): DemoScene::waitForModelsL + 0xA51
2023-10-21 22:05:25.462 INFO    EDCORE (12476): 0x00000000000a0d3c (GraphicsCore): render::ShadowMapModule::queryCasters + 0xA0C
2023-10-21 22:05:25.462 INFO    EDCORE (12476): 0x0000000000053bdf (GraphicsCore): render::BaseRenderingPass::execute + 0x1F
2023-10-21 22:05:25.462 INFO    EDCORE (12476): 0x00000000000542ec (GraphicsCore): render::BaseRenderingPass::execute + 0x72C
2023-10-21 22:05:25.462 INFO    EDCORE (12476): 0x0000000000058b2d (GraphicsCore): render::RenderGraph::render + 0x11D
2023-10-21 22:05:25.462 INFO    EDCORE (12476): 0x000000000001b7f2 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x0000000000150ca1 (Visualizer): smSceneManager::regLua + 0x1281
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x0000000000141834 (Visualizer): smSceneManager::DestroySceneManager + 0x3094
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x000000000003452f (edCore): ed::this_thread::yield + 0x54F
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x000000000002460a (edCore): ed::make_render_thread_tasks + 0x1A
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x000000000013c6d6 (Visualizer): smCamera_Implement::getClipRegion + 0x19346
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x0000000000128746 (Visualizer): smCamera_Implement::getClipRegion + 0x53B6
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x000000000013fb72 (Visualizer): smSceneManager::DestroySceneManager + 0x13D2
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x00000000000335b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-10-21 22:05:25.463 INFO    EDCORE (12476): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14
2023-10-21 22:05:25.514 WARNING BACKENDCOMMON (15500): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'
2023-10-21 22:05:25.748 INFO    EDCORE (12476): Minidump created.

I'm not quite sure what happens, so let's first try these solutions:

  1. Browse to "C:\Users\your-name\AppData\Local\Temp\", and delete any "DCS..." folder you can find there.
  2. Run a DCS cleanup and repair.

 

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

Link to comment
Share on other sites

3 minutes ago, AtlasR1se said:

This is going to be the bane of your life

I've seen worse in DCS. 😉 I'd like to ensure your pagefile is not stored on your HDD. Please run this command into a "cmd" window, then copy-paste its result:

wmic pagefile

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

Link to comment
Share on other sites

Similar problems here, Buddy Spike blue Flag Caucasus 80s.
"Mission load done", then crash boom bang.
Tried ST, MT, with and without VR.




 

dcs.20231025-192430.log dcs.20231025-192008.log dxdiag.txt dcs.20231025-193321.log

dcs.20231025-195427.log


Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

Not until now, will try now and report back in a few mins...

edit: folder emptied, tried again -> crash boom bang again

 

dcs.20231025-213750.log


Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

Anytime I go to do a sortie in the F-14B or any kind of DCS world module DCS crashes at Terrain Preload 100; Stage 38 every time starting with the day I updated from 2.8 to 2.9 and I never had this issue before, and I've repaired DCS done a complete re-install 4 times and still the same result and my pc meets the minimum requirements so whats the issue? 


Edited by Khadrion-Acer

Maj. C. "Hot Take" McIntosh

Virtual 17th WPS CO

Link to comment
Share on other sites

  • Khadrion-Acer changed the title to DCS Crashes at Terrain Preload 100; Stage 38 every time I load.

Microsoft Windows [Version 10.0.19045.3570]
(c) Microsoft Corporation. All rights reserved.

C:\Users\---->wmic pagefile
AllocatedBaseSize  Caption          CurrentUsage  Description      InstallDate                Name             PeakUsage  Status  TempPageFile
7168               C:\pagefile.sys  0             C:\pagefile.sys  20230424221912.857656+060  C:\pagefile.sys  0                  FALSE


C:\Users\--->

 

@Flappie here you go mate, obvs changed the C:\ part

 

Link to comment
Share on other sites

Good. Anyway, I didn't know this crash message until now and you are already two users getting it. It may be some bug, not a problem on your PCs.

Do you keep getting the crash after today's update?


Edited by Flappie

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

Link to comment
Share on other sites

Updated DCS with today's update OB 2.9.0.47168, and also updated NVIDIA to 545.92 > the problem seems gone for the moment.


Edited by TOViper
  • Like 1

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

Hi all, been watching this thread as I had this on day one and it was very frustrating

I had a particular issue with the AH-64D and Syria/Sinai where I had created a quick cold start mission in the ME on either of these maps

I noticed that certain quick starts like Caucasus with the F-15SE were not affected

I noticed that being impatient and clicking on the loading screen (which was very slow) seemed to generate a popup (DCS has crashed dialog) although this could just be an issue where that dialog does not pop to the foreground over the app if it's unresponsive.

I noticed that my fans spun up like crazy (CPU hit 100% and my RAM, 32GB was exhausted)

I noticed that the DCS.log, even with a "good start" is full of errors and warnings like as below (this makes it very difficult to see the wood for the trees)  - I've attached my successful launch DCS.log - Process was, clear all logs, launch the sim, launch Instant Action AH-64D Cold Start - Sinai, Load into the cockpit and then quit to desktop.

ERROR   wInfo (Main): negative drag of payload "MK_82*28"

ERROR   EDCORE (Main): No suitable driver found to mount mods/terrains/sinai/models/modellighteffects/modellighteffects.texture.zip

ERROR   EDTERRAINGRAPHICS41 (15600):   missing object declaration: light_source_spot_red_stop

WARNING FLIGHT (Main): No taxiroad found on Ramon Airbase from 4 to 2

ERROR_ONCE DX11BACKEND (9956): texture '.' not found. Asked from ''
ERROR_ONCE DX11BACKEND (18040): Can't load 'Fonts/font_general_RU.dds' in texture array ''.

Has thankfully now gone away after;

  1. Run a slow repair with the Extra files checked
  2. Uninstalled via DCS module manager and deleted folders for 349th Range Targets (or whatever it's called) and Military Aircraft Mod
  3. Switched off all the new features like DLSS etc and made sure the LOD slider was back to default (I'd experimented with 2.0)
  4. Uninstalling graphics drivers (via device manager and apps/features), rebooting and then installing with a clean install the latest drivers (which I already had) - I had to do this several times as it didn't seem to totally remove the device driver (RTX4080)
  5. In Nvidia control panel ensure the Shader Cache Size was reset to Driver Default (from unlimited) in the Global 3d settings
  6. Clearing out the DCS shader folders
  7. Clearing out C:\Users\your-name\AppData\Local\Temp\
  8. Reset my page file to windows recommended (it lives on C:\ and my DCS is on H:)
  9. Run a slow repair with the Extra files checked again

Hope this helps those of you struggling

 

Cheers

James

dcs.log


Edited by hughesj2
Added point 2, Syria typo
  • Thanks 2
Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

Sorry, only just caught this thread. I have changed my motherboard and then done another full repair.

I can confirm now that I am able to play again. Don't know if it had anything to do with the older M/B or not, but I am also seeing a marginal frame rate increase

after the upgrade.

Thank you all for taking the time to look into this, and once again sorry for the delay in my response.

  • Like 1
Link to comment
Share on other sites

  • Recently Browsing   0 members

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