mod conflict 2.9 update and missing assets?

[SullyFUBAR]

Updated to 2.9 today and jumped into working on a mission. When previewing I've noticed that some static objects and ground units that I've placed on map have disappeared. They show up in the mission editor but vanished once the mission is launched. I am running mods (mostly CH assets) but the objects that are missing are things like Armed Barracks, Road Outpost, T-72b, ZU-23 etc. Is anybody else running into this? 

TEST_SANDBOX.miz

[Flappie]

Please disable your mods temporarily and see if vanilla units are back.

[RWC]

I have the same issue with the SC, it just dissapeared from my build mission ! This after the major update.

I posted a message too here : 

 

[SullyFUBAR]

On 10/19/2023 at 3:18 PM, Flappie said:

Please disable your mods temporarily and see if vanilla units are back.

Thanks again. it was a Mod. Specifically the PGL-625 SPAAGM from Currenthill. 

[Flappie]

Thanks for your feedback.

[OrdinaryPilot]

On 10/30/2023 at 9:33 AM, SullyFUBAR said:

Thanks again. it was a Mod. Specifically the PGL-625 SPAAGM from Currenthill. 

Is this still an ongoing issue with the PGL-625 even after he packaged everything by country? @SullyFUBAR

Or did you just have the old PGL-625 mod folder enabled alongside CurrentHill's China asset pack?

I've been having the same issue and I'm not sure if it's the PGL-625 or something else causing it.

 

 

I've worked for over a year on two campaign missions centered around Guam and all my work is in jeopardy because of this stupid problem.

Edited March 6, 2024 by OrdinaryPilot

[SullyFUBAR]

My specific issue was caused with the 2.9 update and having all the mod assets individually, this is what allowed me to identify which mod was causing the issue. I removed it and didn't add it back until CH's country packs came out. I removed all the old CH mods and added the new country packs and haven't had an issue with them since. Other then that, I have had a lot of conflict issues with the Gripen mod and CH's mod packs. If you have the Gripen mod or other weapon mods (ones that add new missiles or bombs to mod or ED planes) I'd try removing them and seeing if it helps.  

[OrdinaryPilot]

2 hours ago, SullyFUBAR said:

My specific issue was caused with the 2.9 update and having all the mod assets individually, this is what allowed me to identify which mod was causing the issue. I removed it and didn't add it back until CH's country packs came out. I removed all the old CH mods and added the new country packs and haven't had an issue with them since. Other then that, I have had a lot of conflict issues with the Gripen mod and CH's mod packs. If you have the Gripen mod or other weapon mods (ones that add new missiles or bombs to mod or ED planes) I'd try removing them and seeing if it helps.  

I had already removed the JAS-39, J-10A, and a ton of other mods and it continued happening. So I just went and renamed my DCS Saved Games folder to something else (so it would create a new one), repaired DCS with the utility tool (and had it delete all the extra files, which I backed up), and tried starting up a new mission with just a Nimitz carrier in it and the carrier spawned just fine this time when test flying. Then I went and re-added the mods I was using batch-by-batch and tested it out in the mission editor again and didn't encounter any further problems. I've been able to re-add every single mod (besides the JAS-39 and J-10A that I had already deleted) and now my campaign mission that I worked so hard on spawns the units just fine. I still don't know what mod was causing it, if any, or if the game directory was somehow just corrupted and needed a repair.