Game crashes every time after the newest update

[Silent Film]

I launch the game, start a single player mission with the new MiG-29A Fulcrum in the Caucasus map, the map loads, then the aircraft starts loading, and at Spawn Objects, the game crashes to desktop, three times in a row.

dcs.log-20251129-071513.zip

dcs.log-20251129-080350.zip

dcs.log-20251129-081414.zip

[sleighzy]

Is this a mission you've made yourself? You've hit a known issue that is currently being investigated caused by units within a mission having 0 magazines / ammo. Has happened for a few users recently.

Can you check your mission for any units with ammo value of 0 and update this, can set even just a value of 1, and see if you still get this issue.

If this is not your mission, or you are unable to open the .miz file in the mission editor and update yourself, then you may need to contact the person who created the mission to let them know.

 

2025-11-29 08:03:50.005 INFO    EDCORE (Main): # -------------- 20251129-080350 --------------
2025-11-29 08:03:50.006 INFO    EDCORE (Main): DCS/2.9.22.17790 (x86_64; MT; Windows NT 10.0.19045)
2025-11-29 08:03:50.007 INFO    EDCORE (Main): E:\DCS World\bin\Weapons.dll
2025-11-29 08:03:50.008 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff04d4122a 00:00000000
2025-11-29 08:03:50.010 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\DCS World\bin;', symOptions: 532, UserName: 'milos'
2025-11-29 08:03:50.011 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1
2025-11-29 08:03:50.012 INFO    EDCORE (Main): 0x000000000011122a (Weapons): wBarrel::SetExternalMissile + 0x9A
2025-11-29 08:03:50.014 INFO    EDCORE (Main): 0x0000000000111479 (Weapons): wBarrel::calculateMountingPos + 0x29
2025-11-29 08:03:50.015 INFO    EDCORE (Main): 0x000000000010b235 (Weapons): cLauncherRocket::setDiffInitStatus + 0x50C5
2025-11-29 08:03:50.016 INFO    EDCORE (Main): 0x00000000000e521e (Weapons): cLauncher::postInit + 0x2CE
2025-11-29 08:03:50.017 INFO    EDCORE (Main): 0x00000000000ef897 (Weapons): cLauncherGun::postInit + 0x17
2025-11-29 08:03:50.018 INFO    EDCORE (Main): 0x0000000000136dd0 (Weapons): wWeaponSystem::postInit + 0x70
2025-11-29 08:03:50.019 INFO    EDCORE (Main): 0x00000000001444a8 (Weapons): wWeaponSystemManager::add_weapon_system_manager + 0xC88
2025-11-29 08:03:50.019 INFO    EDCORE (Main): 0x00000000000e8a3e (Transport): woCar::initObject + 0x1AAE
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000f1307 (Transport): woCar::setColumn + 0x777
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000dda07 (Transport): woCar::create + 0xB7
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000c2c71 (Transport): wcColumn::createPathAndUnits + 0xC21
2025-11-29 08:03:50.021 INFO    EDCORE (Main): 0x00000000000c1baa (Transport): wcColumn::create + 0x2DA

 

This is the original report with the same stack trace, as per others as well: 

 

Edited 8 hours ago by sleighzy

[Silent Film]

2 hours ago, sleighzy said:

Is this a mission you've made yourself? You've hit a known issue that is currently being investigated caused by units within a mission having 0 magazines / ammo. Has happened for a few users recently.

Can you check your mission for any units with ammo value of 0 and update this, can set even just a value of 1, and see if you still get this issue.

If this is not your mission, or you are unable to open the .miz file in the mission editor and update yourself, then you may need to contact the person who created the mission to let them know.

 

2025-11-29 08:03:50.005 INFO    EDCORE (Main): # -------------- 20251129-080350 --------------
2025-11-29 08:03:50.006 INFO    EDCORE (Main): DCS/2.9.22.17790 (x86_64; MT; Windows NT 10.0.19045)
2025-11-29 08:03:50.007 INFO    EDCORE (Main): E:\DCS World\bin\Weapons.dll
2025-11-29 08:03:50.008 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff04d4122a 00:00000000
2025-11-29 08:03:50.010 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\DCS World\bin;', symOptions: 532, UserName: 'milos'
2025-11-29 08:03:50.011 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1
2025-11-29 08:03:50.012 INFO    EDCORE (Main): 0x000000000011122a (Weapons): wBarrel::SetExternalMissile + 0x9A
2025-11-29 08:03:50.014 INFO    EDCORE (Main): 0x0000000000111479 (Weapons): wBarrel::calculateMountingPos + 0x29
2025-11-29 08:03:50.015 INFO    EDCORE (Main): 0x000000000010b235 (Weapons): cLauncherRocket::setDiffInitStatus + 0x50C5
2025-11-29 08:03:50.016 INFO    EDCORE (Main): 0x00000000000e521e (Weapons): cLauncher::postInit + 0x2CE
2025-11-29 08:03:50.017 INFO    EDCORE (Main): 0x00000000000ef897 (Weapons): cLauncherGun::postInit + 0x17
2025-11-29 08:03:50.018 INFO    EDCORE (Main): 0x0000000000136dd0 (Weapons): wWeaponSystem::postInit + 0x70
2025-11-29 08:03:50.019 INFO    EDCORE (Main): 0x00000000001444a8 (Weapons): wWeaponSystemManager::add_weapon_system_manager + 0xC88
2025-11-29 08:03:50.019 INFO    EDCORE (Main): 0x00000000000e8a3e (Transport): woCar::initObject + 0x1AAE
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000f1307 (Transport): woCar::setColumn + 0x777
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000dda07 (Transport): woCar::create + 0xB7
2025-11-29 08:03:50.020 INFO    EDCORE (Main): 0x00000000000c2c71 (Transport): wcColumn::createPathAndUnits + 0xC21
2025-11-29 08:03:50.021 INFO    EDCORE (Main): 0x00000000000c1baa (Transport): wcColumn::create + 0x2DA

 

This is the original report with the same stack trace, as per others as well: 

 

Yes, I have made the mission. I have set enemy tanks not to fire at ground units, but it seems it only means they've got zero shells, because there is no dedicated command which would say "don't shoot at ground units". When I set them to have some shells, now the mission works, but they immedietaly fire shells at my ground units, like JTAC, and destroy them. I need some tanks not to shoot at ground units, so my missions are not fully playable right now.

Also, I have encountered with a minor glitch with the new MiG-29A Fulcrum. When it is on the ground, the HUD is of solid color instead of being transparent.

[sleighzy]

44 minutes ago, Silent Film said:

Yes, I have made the mission. I have set enemy tanks not to fire at ground units, but it seems it only means they've got zero shells, because there is no dedicated command which would say "don't shoot at ground units". When I set them to have some shells, now the mission works, but they immedietaly fire shells at my ground units, like JTAC, and destroy them. I need some tanks not to shoot at ground units, so my missions are not fully playable right now.

Also, I have encountered with a minor glitch with the new MiG-29A Fulcrum. When it is on the ground, the HUD is of solid color instead of being transparent.

How big and complicated is your mission? Could you attach the miz file here, if you don't mind sharing, so we can replicate this problem further.

For your other problem one workaround for that could be to create a zone, and then have them shoot at zone. Means they can shoot close to your troops, but not directly at them. It's what I do when I want a firefight, but don't want everybody to kill everybody.

[Silent Film]

2 minutes ago, sleighzy said:

How big and complicated is your mission? Could you attach the miz file here, if you don't mind sharing, so we can replicate this problem further.

For your other problem one workaround for that could be to create a zone, and then have them shoot at zone. Means they can shoot close to your troops, but not directly at them. It's what I do when I want a firefight, but don't want everybody to kill everybody.

Sure, it is my regular training mission, I've got one copy for each jet. But in all my missions, I've got some tanks that I don't want to shoot ground units. I haven't tried that shoot at zone option, if that zone can be very small, then I might try it, although it's a pain in the butt to modify all tanks and add zones in all missions.

CAUCASUS MiG-29 hot start MORNING.miz