Jump to content

Recommended Posts

Posted

I downloaded my Mig-29A module and was able to play it for half a day, then I turned DCS off, and then when I restarted DCS and tried to load any mission that has the MiG-29A module in it, it would then take forever to load and then crash every time.  This only happens in VR and only with the MiG-29A module for some reason. Everything else works fine. I have attached my crash logs in hopes that someone can help

dcs.log dcs.log.old dcs.20250919-184054.crash

Posted

Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.

It might be worth a try.

Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted
Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.
It might be worth a try.
Did you backup your logbook first?
People might be pissed if they just randomly delete it.

Sent from my SM-A536B using Tapatalk

Posted
4 minutes ago, MAXsenna said:

Did you backup your logbook first?
People might be pissed if they just randomly delete it. emoji6.png

Sent from my SM-A536B using Tapatalk
 

I did not. It crossed my mind, but I looked for the file and my foggy head couldn’t find it. Then I realised I don’t mind it gets reset so I just deleted the folder anyway.

  • Like 1
Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted (edited)
1 hour ago, Baseline said:

Same problem for me too. Running the Pimax Crystal Super.

Game crashes just before I try to click the fly button.

Yep I’m running on the Pimax crystal super too

Edited by Redacuragsr
Posted
1 hour ago, Raven (Elysian Angel) said:

Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.

It might be worth a try.

I had black screen too, the plane loaded partially first, then black screen and crashed.  I did a repair, reinstalled all my Pimax stuff but it’s still doing it.  I’ll try deleting the mission editor folder and try it again.  Thanks for the idea.

Posted
I had black screen too, the plane loaded partially first, then black screen and crashed.  I did a repair, reinstalled all my Pimax stuff but it’s still doing it.  I’ll try deleting the mission editor folder and try it again.  Thanks for the idea.
If you want to keep your flight records. RENAME the folder.

Sent from my SM-A536B using Tapatalk

  • Like 1
Posted (edited)
2 hours ago, Makakas said:

 

Disabling secondary shadows fixed it, thank you!

1 hour ago, MAXsenna said:

If you want to keep your flight records. RENAME the folder. emoji6.png

Sent from my SM-A536B using Tapatalk
 

Good idea, but renaming the folder didn’t fix anything for me, however when I turned off secondary shadows everything went back to normal 

Edited by Redacuragsr
  • Like 1
Posted
Good idea, but renaming the folder didn’t fix anything for me, however when I turned off secondary shadows everything went back to normal 
Good to know!

Sent from my SM-A536B using Tapatalk

Posted (edited)

Hi! I had the same issue on Pimax Crystal OG. Can confirm, turning off the Secondary Shadows fixed it.

Edited by Dentedend10

Alienware Aurora R10, Ryzen 5800X3D, RTX4080, 32GB RAM, Pimax Crystal, Winwing F18 throttle, VKB Gunfighter F14 Stick, VKB Modern Combat Grip, Logitech Rudder pedals, DOF Reality H3

Posted

Myself and friend had the same issue.  Both using Pimax Supers.  Turning off Secondary Shadows fixed it as well.

9800X3D (5.21GHz Turbo), RTX 5090 OC 24GB, ASUS ROG Strix X870E-E GAMING Motherboard, G. Skill Trident Z5 DDR5 RAM 96GB (2x48GB), Crucial P3 Plus 4TB PCIe Gen4 3D NAND NVMe M.2 SSD, Virpil Alpha Joystick with FFBeast FFB base, T-50CM3 Throttle, MFG Xwind rudder pedals, Pimax Crystal Super VR.

Posted (edited)

Same problem. Pimax Crystal. And turning off secondary shadows helped as well.

Looks like it's VR specific. Crash log is the same every time

OS-Version: 10.0.26100 () 0x100-0x1
0x00000000000a2782 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x42
0x00000000000a121b (GraphicsCore): render::SecondaryShadowmapModule::SecondaryShadowmapModule + 0x2AB
0x00000000000a2b96 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x456
0x000000000005d0e2 (GraphicsCore): render::BaseRenderingPass::prePass + 0x22
0x000000000005c627 (GraphicsCore): render::RenderGraph::lightsPrePass + 0x67
0x000000000016d8e4 (Visualizer): smSceneManager::regLua + 0x11C4
0x0000000000156ef4 (Visualizer): smCamera_Implement::getClipRegion + 0x1CC74
0x000000000014076c (Visualizer): smCamera_Implement::getClipRegion + 0x64EC
0x000000000015b602 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
0x00000000000331e1 (edCore): ed::thread::_get_current_thread_id + 0x71
0x00000000000037b0 (ucrtbase): wcsrchr + 0x150
0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17

 

Edited by Andrei

AMD R7 5800X3D | Aorus B550 Pro | 32GB DDR4-3600 | RTX 4080 | VKB MGC Pro Gunfighter Mk III + STECS + VKB T-Rudder Mk4 | Pimax Crystal

| A-10C II | Ка-50 | P-51 | UH-1 | Ми-8 | F-86F | МиГ-21 | FW-190 | МиГ-15 | Л-39 | Bf 109 | M-2000C | F-5 | Spitfire | AJS-37 | AV-8B | F/A-18C | Як-52 | F-14 | F-16 | Ми-24 | AH-64 | F-15E | F-4 | CH-47 | МиГ-29 | C-130

NTTR | Normandy | Gulf | Syria | Supercarrier | Afghanistan | Kola | Germany | Afganistan

Posted

No problem for me so far (but Quest), turn off all mods and check it again. From what I see it applies more to Pimax owners, so maybe there is some software problem with the update from Pimax?

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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