Tweak viewport nullspace check (#35037)

* Tweak viewport nullspace check

WorldPos being 0,0 is sussy-a.

* a

diff --git a/Content.Client/UserInterface/Systems/Viewport/ViewportUIController.cs b/Content.Client/UserInterface/Systems/Viewport/ViewportUIController.cs
index ffee14ad9a3ba44317c9f50a5a1e3b2dcae3e2d4..338b5fc7e5b793cf188f5883181c1b3f32513b5f 100644 (file)
--- a/Content.Client/UserInterface/Systems/Viewport/ViewportUIController.cs
+++ b/Content.Client/UserInterface/Systems/Viewport/ViewportUIController.cs
@@ -6,6 +6,7 @@ using Robust.Client.Player;
 using Robust.Client.UserInterface;
 using Robust.Client.UserInterface.Controllers;
 using Robust.Shared.Configuration;
+using Robust.Shared.Map;
 using Robust.Shared.Timing;
 
 namespace Content.Client.UserInterface.Systems.Viewport;
@@ -95,8 +96,11 @@ public sealed class ViewportUIController : UIController
         _entMan.TryGetComponent(ent, out EyeComponent? eye);
 
         if (eye?.Eye == _eyeManager.CurrentEye
-            && (_transformSystem is null || _transformSystem.GetWorldPosition(ent.Value) == default))
-            return; // nothing to worry about, the player is just in null space... actually that is probably a problem?
+            && _entMan.GetComponent<TransformComponent>(ent.Value).MapID == MapId.Nullspace)
+        {
+            // nothing to worry about, the player is just in null space... actually that is probably a problem?
+            return;
+        }
 
         // Currently, this shouldn't happen. This likely happened because the main eye was set to null. When this
         // does happen it can create hard to troubleshoot bugs, so lets print some helpful warnings: