NeedzWD40 Posted 5 hours ago Posted 5 hours ago Description: setting a ground vehicle with a selectable magazine to 0 results in an access violation of weapons.dll and subsequent crash at Spawn Units phase of mission load. How to reproduce: Create a mission and place a vehicle with a magazine (M1A2, T-90, T-80) and set magazine to 0, then launch the mission. Mission will crash and log will show weapons.dll violation. Test mission and crash log zips attached. dcs.log-20251128-213121.zip Ground Vehicle No Magazine Crash.miz
sleighzy Posted 3 hours ago Posted 3 hours ago Can you please remove your mods and run a repair of the game and see if you can replicate this again. Another user has a similar stack trace, and some common mods to yours, so would like to confirm whether or not mods issues with this, or pure core game problem. 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
NeedzWD40 Posted 3 hours ago Author Posted 3 hours ago 17 minutes ago, sleighzy said: Can you please remove your mods and run a repair of the game and see if you can replicate this again. Another user has a similar stack trace, and some common mods to yours, so would like to confirm whether or not mods issues with this, or pure core game problem. I can run a separate go without mods later (I'm in the middle of mission editing right now) as that was my original thought. I had one mod that I thought was the issue and removed it but it remained, so I plugged it back in. It wasn't until I thought maybe some changes from the CH assets pack might've been the issue, but changing those units didn't help. It wasn't until I noticed that I hadn't altered the T-90 payloads from the previous mission iteration that I put the the two together since the loads were exceeding magazine capacity. A different mission had no such units but did have 100mm guns with the AP ammo removed which also resulted in a crash. Adding ammunition to these magazines (even 1 round) resulted in no crashes, so a quick test with the mission in the first post to test the theory seemingly proved it. It's entirely possible mods are the culprit, but I was tearing my hair out trying to figure out the stability problems and was at my wit's end when I tried the above. Set a bunch of my mission editing back, so testing without mods will have to come later. 1
sleighzy Posted 2 hours ago Posted 2 hours ago 2 minutes ago, NeedzWD40 said: A different mission had no such units but did have 100mm guns with the AP ammo removed which also resulted in a crash. Thanks for the quick response. Yeah keep us posted when you get around to trying without the mods. Can you also update your post description to include the 100mm guns if you've identified that this was also an issue so a complete track of them can be kept if others run across this issue. Cheers. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
NeedzWD40 Posted 1 hour ago Author Posted 1 hour ago 53 minutes ago, sleighzy said: Thanks for the quick response. Yeah keep us posted when you get around to trying without the mods. Can you also update your post description to include the 100mm guns if you've identified that this was also an issue so a complete track of them can be kept if others run across this issue. Cheers. I probably should've cleared out the hooks location, as all I did was get the mods out of that folder. I'm not convinced that mods couldn't be a potential source of the issue, but the crash still followed in the test mission without them. Thing is, the stability is inconsistent, as sometimes with mods it crashes and sometimes it loads up fine; without mods is the same. The only consistency I can find is that ensuring no ground unit has 0 ammo magazines keeps things stable on the weapons.dll front. In any case, attached is a crash log without mods. dcs.log-20251129-013734.zip 1
Recommended Posts