Mission Restart Bugs

[Grinch]

So here are a couple bugs I've never seen before.

 

I have a MP mission that is set to load the same mission after 5 hours via trigger. Upon reset, all static units (SAMs, ground forces, etc.) do not spawn at all. Only groups with waypoints upon mission start spawn and begin their routes. If the map is loaded manually, everything spawns as it should by mission design.

 

Continuing the trend of weirdness, some units that are supposed to spawn later after triggers are initiated, spawn upon start. For example, an AWACS that is set to spawn after a certain condition is met, spawns at start without that trigger being met. It appears on the F10 map, moves, but cannot be reached via the radio commands.

 

Anyone seen this stuff before?

[ENO]

I've had some weird stuff happening of late also... but I'm not sure I could put a finger on exactly what's making it happen.

 

There are a few instances where it's like MIST doesn't initialize and my only way around it is to resave a new version of the mission- not a big deal... but then those failed triggers you're talking about...

 

Question for you- did you build the mission on one computer then move it over to the server computer? I've found that doing that without saving a new version can create weird anomalies in the past.

[Grinch]

Yes. The map was built on a separate computer, moved to the server, renamed, and the trigger updated to reflect the renamed file (and therefore saved in ME on the server).

[ENO]

I've followed all proper conventions as well but I'm finding lately that things are acting strange. Most of my reported issues now are crashes- one just the other night resulting from a restart. Haven't submitted that one yet mind you!

 

We used to have crashes on restarts all the time so I seldom used the function- so I didn't use them. Hope they figure it out.

[Grinch]

Any of the ED testers out there have any input?