@sheeps I tried changing the settings in one of the two I had and the same behavior occurred. Right now I'm down to one module in all my missions and it seems fixed but I'm still paranoid about it coming back so although I consider this solved, I'll need another day or two to really know for sure.

I should have clarified, Sheeps. I have not tested the effect of two modules with vanilla. I'm personally feeling like this specific issue is not caused by any one thing, but a culmination of mission start errors that cause ALiVE to fail to initialize properly. Now, why debugging makes the civ obj module work correctly when this happens I have no clue.

But, based on Highhead's advice - to eliminate startup errors by removing unnecessary mods and removing duplicate civ population modules - the problem *seems* to go away. So I suspect it was all of the above done in tandem which made this problem occur but again, I've yet to test the duplicate modules theory independently.

I'd personally start by removing some of those dependencies man. See the other thread. I haven't heard of half of those mods. Not saying they are an issue because I haven't seen the mission yet though.

Again, like I said above, I don't mean to imply at this point that ARP2 objects is the cause of this particular issue. Although removing it (and thus its 'scope' startup error) temporarily fixed the problem, it came back, leading me to believe a multitude of startup errors and duplicate processes were the culprit.

This is just a guess on my end but I also won't deny that ARP2 definitely causes initial loading screen issues and also load time problems as well (those went away for good by just dropping the dependency). So while not inherently incompatible, it has its issues and I'd still deter people from using it if their missions aren't super clean from the get-go. This is just based on my observations from how my missions were effected by it.

Yeah seems like it.

That whole Kunduz mission needs a rework anyway. The editor won't allow me to place objects where I want them, but only in an approximation of the general vicinity (which is obviously horrible for building your own base). Meaning, I can place an object on let's say a 5x5 foot grid, but not exactly where they need to be.

So I definitely need to scrap any remnants of DonbassCZ's bases to hopefully get my editor performance up and either build my own (ugh. I usually do this anyway and I enjoy it but Kunduz needs them built from literally scratch) or wait for someone else to do it for me when custom compositions come to Workshop. I was hoping I could salvage at least part of his work but it bogs editor performance down to a crawl at times too.

Fortunately this thread helped me solve the problem in all of my missions which all use BIS assets so now they are actually pretty much done! :) Thanks Highhead. I really mean it that I appreciate the help a lot.

@DaVidoSS Did you try to disable surface snapping?

I did not! Had no clue you could do that. LOL! Thanks! Do you know offhand where I can do that? Under settings I'd presume?

*big hug*