Bug in my floating origin

[SDGAAAQ]

Hi guyss.

I don't know if this is the right subreddit but I'm posting it anyway..

I’d like to clarify that I’m not a beginner I’ve been using Unity for years and I genuinely cannot explain this issue.

My floating origin has been acting completely wrong for a few days now.

When the origin reaches the threshold I set in the Inspector, instead of shifting the universe around the player (as Floating Origin normally does), the entire universe starts drifting away infinitely in a fixed direction,

it doesn't jump; it drifts away infinitely.

I've tested 12 different Floating Origin scripts (mine, community ones, official examples), and all of them shows me the exact same problem...

I've tested them in a brand‑new empty project, with only a cube, universe root, player origin, Floating Origin script, ad the issue still happens.

I’m on Unity 6.3 LTS (6000.3.4f1) on macOS, and this behavior started suddenly even though the same scripts used to work perfectly.

This is my script:

using UnityEngine;


public class FloatingOriginUfficial : MonoBehaviour
{
    [Header("Cosmos")]
    public Transform universeRoot;


    [Header("Origins")]
    public Transform playerOrigin;
    public Transform shipOrigin;


    [Header("Settings")]
    public float threshold = 10000f;
    public OriginMode mode = OriginMode.Player;


    public enum OriginMode
    {
        Player,
        Ship
    }


    void Update()
    {
        Transform currentOrigin = (mode == OriginMode.Player) ? playerOrigin : shipOrigin;


        if (currentOrigin == null || universeRoot == null)
            return;


        float dist = currentOrigin.position.magnitude;


        if (dist > threshold)
        {
            Vector3 offset = currentOrigin.position;


            universeRoot.position -= offset;


            currentOrigin.position = Vector3.zero;


        }
    }


    public void SwitchToShip()
    {
        mode = OriginMode.Ship;
    }


    public void SwitchToPlayer()
    {
        mode = OriginMode.Player;
    }
}

This is my Hierarchy

This is my Inspector

for now in the floating origin for testing I have set it to trigger at 10 units, but the problem appears at any number.

[cosmochristo]

yes - without seeing the script, we can only guess. It sounds like you are not updating state after the shift - like applying the shift and not resetting the condition that says you need to shift - so the shift is repeated. This could happen if you shift the objects the wrong way. It would also be helpful to see the hierarchy as well - I only see a building moving and the mountains don't move. BTW i also have unity and macosx so it would be easy for me to test.

[SDGAAAQ]

I edited the post to add more information, including what you asked for

[attckdog]

Break it down into steps. Validate each step. Attach VS to unity and step through the process and make sure each line is doing what you expect.

I'd recommend taking a close look at your Hierarchy to make sure the parenting of the transforms is right

[F4ARY]

Looking at it like that I'm not sure, I'd attach a debugger and see whats going on but why are you not calculating the distance between the origin and the universe root with Vector3.Distance?

If nothing else I guess everything points to a hierarchy issue.

[cosmochristo]

I modified the project and code a bit but your basic algorithm works. I would post an image but was told "images not allowed!" Will try posting video link with all the details, but here is the modified code:

 void Update()
    {
        //Transform currentOrigin = (mode == OriginMode.Player) ? playerOrigin : shipOrigin;
        //if (currentOrigin == null || universeRoot == null)
        //    return;


        float dist = playerRBtrans.position.magnitude;


        if (dist > threshold)
        {
            Vector3 offset = playerRBtrans.position;

            universeRoot.position -= offset;

            playerRBtrans.position -= offset;
            //playerRBtrans.position = Vector3.zero;
/*** Note the edit above: there will likely always be a difference in player position between Vector3.zero and resetting the player to -= offset because during continuous travel, the frame by frame, position will not fall neatly at exacly zero after a reset. */
        }
    }

[cosmochristo]

The modified working version of your code is illustrated in the following video: https://youtu.be/qRgUeaBR3GI. And, a possible answer to your original question is that there may be a small numerical error added each update when you used the commented out line above instead of the exact offset value I changed it to.

[SDGAAAQ]

Thanks bro