reported earlier A-10A switching aircraft causes crash

[plott1964]

Has anyone else had the problem of game crashing after update and when switching between aircraft (RALT+J), specifically the A-10A and another A-10A or any other aircraft. I just started noticing this problem after the last update and have worked with ED support to no avail.

Reaching out to the forum for help.

[Flappie]

Hi. Could you please send in the latest zip file from your "Saved Games/DCS.../Logs" folder?

[plott1964]

This is what I send ED support:

https://www.digitalcombatsimulator.com/bitrix/components/bitrix/support.ticket.edit/ticket_show_file.php?hash=1fe2ad3652e98b60646ecf31c91bd626&lang=s1&action=download

I can send a link to the track file if you wish.

 

Edited February 27, 2024 by plott1964

[Flappie]

7 hours ago, plott1964 said:

I can send a link to the track file if you wish.

Yes, please do, because I cannot access your link for I'm not part of ED (I know, the "ED Beta Testers" titel can be misleading).

[plott1964]

Thanks Flappie.

I apologize. I thought I had that for the .trk file link available. I do not. The ED Team did not ask for that one. I will have to dig up the specific track file associated with the attached logs. I save everything I can. But, as you know, track files are not always 100% accurate.

 The attached logs are what I originally sent four days ago.

dcs.log-20240223-050245.zip dcs_post_troubleshooting.log

Edited February 27, 2024 by plott1964

[Flappie]

Many thanks. I see you experience the "IndirectLightVolumeModule" crash. It's reported internally. Users started having this crash with the Hind, and I've seen it recently with the Spitfire. And now, the A-10A. I guess we can say it's global.

2024-02-23 05:02:44.065 INFO    VISUALIZER (Main): get cockpit shading params from /models/Cockpit_A-10A.edm.lua
2024-02-23 05:02:44.093 INFO    WORLDGENERAL (Main): loaded from mission Scripts/World/birds.lua
2024-02-23 05:02:44.121 INFO    VISUALIZER (3812): cockpit ILV loaded
2024-02-23 05:02:44.181 INFO    EDCORE (22644): try to write dump information
2024-02-23 05:02:44.417 INFO    EDCORE (22644): # -------------- 20240223-050245 --------------
2024-02-23 05:02:44.419 INFO    EDCORE (22644): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.19045)
2024-02-23 05:02:44.421 INFO    EDCORE (22644): 
2024-02-23 05:02:44.424 INFO    EDCORE (22644): # C0000005 ACCESS_VIOLATION at 0000000000000005 00:00000000
2024-02-23 05:02:44.426 INFO    EDCORE (22644): SymInit: Symbol-SearchPath: 'H:\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'plott'
2024-02-23 05:02:44.428 INFO    EDCORE (22644): OS-Version: 10.0.19045 () 0x100-0x1
2024-02-23 05:02:44.430 INFO    EDCORE (22644): 0x0000000000000005 ((module-name not available)): (function-name not available) + 0x0
2024-02-23 05:02:44.433 INFO    EDCORE (22644): 0x00000000000579e7 (enlight): render::IndirectLightVolumeModule::addUpdatePass + 0x357
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
2024-02-23 05:02:44.435 INFO    EDCORE (22644): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71
2024-02-23 05:02:44.436 INFO    EDCORE (22644): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2024-02-23 05:02:44.436 INFO    EDCORE (22644): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14
2024-02-23 05:02:44.803 INFO    EDCORE (22644): Minidump created.

 

Though I've already succeeded, it's very hard for me to reproduce this crash. If you have any idea about how to get it to crash systematically, I'm all ears.

[plott1964]

Systematically?

For me, it's fly any mission with the A-10A and then attempt to switch aircraft (RALT+J). It doesn't matter which aircraft or if you are about to fly into the ground or not (which is usually why I'm switching). So, getting it to be systematic is pretty easy.

I did have the same issue last night in the F-15C, so as I was originally thinking it may have been based on the FC3 updates that ED did. But, I still had the same problem even after I reverted back to 2.9.2.49629 OB [previous version].

The ED support team has been unable to duplicate. That's why I'm reaching out here.

Tell me more about the "[IndirectLightVolumeModule] crash" and how to troubleshoot.

Also, be advised that I have also had VR issues with Open Beta MT since a few updates back.

Edited February 27, 2024 by plott1964

[plott1964]

I did see in this thread: 

..about updating the BIOS and ED also suggested that and I did update. But still having the same problem.

All the previous steps that have been followed:

• Boosted pagefile size
• Stopped all apps except DCS
• SFC scan found corrupted files and repaired successfully
• Updated BIOS with latest update
• Updated to latest version of DCS

No unofficial mods were added for the test and it still crashed after RALT+J selection. My solution at this point is to choose to not switch aircraft.

Edited February 27, 2024 by plott1964

[Flappie]

Hey, you're right, this is the same kind of crash. It dates from November, I was active in this thread, and I just can't remember it.

I tried RAlt+J-ing a dozen of times but cold not reproduce the crash. Can you please attach your options.lua file from "Saved Games/DCS.../Config" ?

RAlt-J.trk

[plott1964]

At work right now. I will send the file and replay your track this evening. How does that options.lua file get changed?

I have been doing a lot (troubleshooting) with the sim, so I want to ensure you'll get the right data.

Edited February 27, 2024 by plott1964

[Flappie]

DCS stores most of your custom settings in the options.lua file (graphics, gameplay, misc, special, audio...).

Edited February 27, 2024 by Flappie

[plott1964]

here you go.

options.lua

Here's the link to the logs with the track file included:

https://drive.google.com/file/d/1p7LVWgaIjTmCWRK9wpr0QXZpZip9saCt/view?usp=drive_link

BTW - we are talking about OB MT primarily.

Edited February 27, 2024 by plott1964

[Flappie]

Thank you. I retried RAlt+J-ing in my MP mission without getting a crash. I'll see if I can reproduce the MP crash I know about (changing slots).

EDIT: Nope. This bug is a tricky one for me.

Edited February 27, 2024 by Flappie

[plott1964]

Not having the problem with the OB stable version. MT version is now causing severe lag and stutter, even after a slow repair. I honestly can not even get past the main menu in OB/MT.

Edited February 28, 2024 by plott1964