|
|
Example2.png (67,995 bytes) Example1.png (77,944 bytes) |
|
|
Chris has been poking around at this code for multiplayer I see. The Devourer notification click handler is public MouseHandlingResult ClickHandler() { if(planet != null) { if ( Engine_AIW2.Instance.CurrentGameViewMode == GameViewMode.GalaxyMapView ) Engine_AIW2.Instance.PresentationLayer.CenterGalaxyViewOnPlanet( planet, false ); else { World_AIW2.Instance.SwitchViewToPlanet( planet ); <====== } return MouseHandlingResult.None; } return MouseHandlingResult.DoNotPlayClickSound; } Looks like this goes to World, which makes a GameCommand to update the player's "currently viewed planets" |
|
|
So, any command that causes you to go to the same planet you are already on will potentially do this. Keep clicking, and more of them are likely to get caught like this. It's a problem with how it is trying to shut down the one planet and open it back up at the same time. I'll see if I can fix the central pipeline to not do this in general. |
|
|
Thanks! * If a player is already on a planet viewing that planet, and a further command was sent to view that planet again (as if they were not already there), then funky stuff happened in various places, including the wormholes getting half-initialized and not drawing properly in scale. ** To solve this, it simply doesn't do anything if you try to re-open your view to the existing planet you are already on. |
- Anonymous
