I've noticed this in every version, aswell... there may be a hard cap on a maximum number of phase stabilizers that work together as a group that needs to be raised. I noticed after I get a lot of planets with phase stabilizers in the same system, eventually they have to jump to a closer near by stabilizer (even though not using a regular phase lane, using a phase node to jump there) and then jumping to the destination also via phase node.

Ok. Autosave is in a perfect spot:

Autosave-20.stats
Autosave-20.save

Hotkey group #1 has my entire fleet. About 60% of my planets have phase stabilizers. Select the Marauder and activate 'Stabilize Phase Space'. Then order the rest of the fleet (NOT including the marauder) to one of my more distant planets that has a phase stabilizer node, and observe the path.

It should try to jump to an asteroid to the south before using that stabilizer to go to the final destination.

I can also confirm that the save shows funkyness.

At first, it worked exactly as stated. Ships went to the asteroid several jumps away despite being at a stabilizer node. When I built a stabilizer at the desert planet in between, they jumped from there.

However, when I built a stabilizer at the asteroid directly below the planet the fleet was at, it worked like it should. Ships would jump through the entire system using the stabilizer where they started.

I did a few hours of testing using the saves provided above and what I found is a bug that is definable and repeatable. The Phase Stabilizers all work as they should except for the last planet or planets that you colonize. Eventually even they work correctly, that is the only part that I was unable to pin down. I tried and eliminated half a dozen possible triggers . The closest I can come to a conclusion is that after a certain amount of time (somewhere in the neighborhood of 10-15 minutes) they begin to work correctly.

Nypyren confirms this with his update, which got me started on this investigation.

If you use Autosave-20 above (Reply 4) and follow the instructions, you find the fleet on a world that appears to be newly colonized. It already has a phase stabilizer constructed on it, so there is no need to select the Marauder and if you attempt to phase jump off, exactly what Nypyren says will happen does happen, its jumps 3 times to get to the nearest phase stabilizer and goes to its final destination from there.

Annatar11 and Kitkun both confirm this.

So a Phase Stabilizer built on a newly colonized planet will not work for outbound jumps, eventually it starts working. It started working for Kitkun after she built two more stabilizers, but like I said this wasn't repeatable.


This does not appear to hold true, it again has to do with the planet. If you take a Marauder to any planet that has been colonized for awhile, or any uncolonized or enemy world. It works perfectly 100% of the time. However if you colonize the world that it just seconds before worked, wait for its cooldown and try again. It reacts the same as a “Phase Stabilizer Node” it exhibits the buggy behavior. It appears that to the game, they are the same, whether its a physical satellite node or a temporary node created by the ship. It shows up the same in the info card.


I was unable to confirm or reproduce this. I jumped from every stabilizer on that map and never saw this behavior. I am not saying this isn't a part of the bug. But if I had to guess, I would say that because of the way the bug is, always at your newest planets and probably where you are most active it could easy appear this way.

I am not sure I understand what your saying here. Why would a theory be incorrect because you hadn't heard it sooner?



That planet was already colonized for some time before you built that stabilizer. They work immediately on those planets.



I followed the procedure in your post as part of the testing. It is not repeatable it doesn't happen right after that consistently. I had a similar experience with building a stabilizer on the planet next to it on the left. It worked immediately after I did it, but I couldn't get it to repeat.



Even though I did do hours of testing I can't say with certainty, what makes them start to work eventually. They do though, load the map, don't do anything else and come back in a half hour. They all the work.

I did not mean to infer that this was the final answer to this bug. It was just the closest I could come after repeated testing looking for a consistent trigger.