I have set up two kill encounters next to each other in a kill all situation. One is a sphere and one is a cube.
for some reason the cube now only appears once your ships reaches the waypoint, (both in testing and when published) then it just appears next to you. At first when i made the mission it was ok and the ship spawned about 25k away but now it will only appear when you hit the waypoint. Im not sure what i have done to set this situation up.
i have not set any triggers on the Cube and im not using a reach marker. It is just a normal kill encounter and set to appear immediately and im not sure why its not appearing sooner.
i have tested other cubes in this mission and others and they all work fine.
ive noticed something however. now remember i have set this up as a kill all encounter and i think that is part of the problem.
the first objective is to destroy the cube (although the cube is positioned further way than the sphere so most people would complete this objective second).
the second objective is to destroy the sphere (but again its the first one you reach) this objective also has a dialogue box attached to it after you destroy the sphere.
now if you kill the sphere first, and read the dialogue then the cube does not spawn until you hit the way point. it then spawns about 1k away from you.
if however you bypass the sphere and go directly to the cube then it spawns normally from about 25k away. destroying the sphere first for some reasons seems to hamper the cub's ability to spawn at the correct distance.
whilst switching them around seemed to work, it then made two npc contact freighters (who were near the sphere) only to spawn after i had reached the marker, just like the cube was.
i moved the freighters just to the left a bit of where the problem was and it looks ok now.
it almost seems like the actual map is bugged for that area just to the right of where the freighters are now causing ships not to spawn correctly regardless of whether they were part of the objective.
this is probably getting very confusing right now. ill try and confirm whether the vulcan map itself is bugged tomorrow. ill try and set up some ships spawns there to see if the area itself is the problem.