Yes, I'm talking 4. It doesn't do auto/continued moves until you hit the end turn button. It then does the auto/continued moves. If any of those ships you have on auto or multiple turn movement orders encounter anything, you no longer have the option of reacting to it before the AI goes even though technically it was still your turn while those moves were taking place. If any still have movement left for any of these continued move units after they finish, you then have to move them. Unfortunately, after you finish that last order, it doesn't then do another end turn button. It just goes. 3 did have an option to enable that second end turn button (really it was disabling the auto end turn option) when I was actively playing it.
This really is game breaking for me. I have already lost 3 colony ships due to them moving after the end turn and not giving me the opportunity to wake a nearby ship/fleet that I placed to safeguard the area for just such a possibility. I shouldn't have to manually move each unit every turn to avoid this. In this same vein, why don't the auto explore, survey, and continue movement units wake up when spotting an enemy so I can use the rest of their moves to move the other way or attack (if capable)? I thought they were trying to get away from all of the micromanagement. Why have multi-turn movement and auto explore/survey at all?
Now possible solutions other than putting back the option for the second end turn button would include having the auto/continued moves occur at the start of your turn or providing a move all function that can be done before hitting the end turn button. Perhaps the first End Turn button could just be a blue move all button then the end turn button appears after all units have been given orders. When I hit the end turn button in a turn based game, I expect that it's now the AI's turn - not that I will then have more of my own units move.
For now, I guess I'll either micromanage my moves or rely on reloading a lot, which I don't like to do - feels a little like cheating.
@SchismNavigator Thanks for your patience and listening. Maybe some of these suggestions will help.