Last active 1 hour ago
Interesting. Does this test hold true with vanilla?
Does a mission with just ALiVE and CBA and no other mods or outside scripts save and exit properly?
@Nichols I realize this is probably not helpful and not scientific but if in doubt, try to save the exact same mission just without any trace of VCOM and see if it behaves normally.
Obviously that’s not ideal and doesn’t solve anything but it will narrow it down and possibly get the mission at least saving so you can play.
I’ve never seen this error. Is this one of those really huge maps basically made for just flying and not doing infantry on? Either way, how big is this map?
The only suggestion I have is to start removing mods from the mission until you figure out which one is causing the issue. If that fails or doesn’t suit your time constraints, I guess you could try a new object needed to use support, such as a compass or LaserDesignator and see if it starts working again.
I almost axed this thread for spam lol.
How are you determining it’s not working? Do you have the Asymmetric AI Commander module debugged while periodically looking at the map for “IED” objective markers?
I’m sure it’s possible to script it, but I don’t script so I’m really not your guy here. Definitely an interesting idea, I just personally have no knowledge of how you’d accomplish this myself.
Non-virtualized placed editor objects, such as vehicles, will always load where they were placed in the editor. If you use ALiVE persistence, and if a human enters as driver and exits the vehicle, it will load where it was moved to.
If no one ever gets in and out of the vehicle as driver, it will load where it was originally placed in the editor.
Virtualizing these objects, which I don’t recommend, will always ensure they get placed oddly because they are spawning into existence when a player is near. Will it be close to where it was placed? Yeah. But it probably won’t be perfect which definitely sucks when you have things parked in a tight space.