SpawnAsPlayerObject can't set client spawn position above 255 on the y axis.

[Digital-Kyle]

Description

SpawnAsPlayerObject can only set position < 256 meters on the y axis. Other axis seem to work fine. This only happens to connecting clients, not the host. NetworkTransform is attached to the player, with Owner as the authority. I've also tested this with interpolations off on the rigidbody and network transform component.

Here is the code I'm using to spawn player network objects:

Vector3 spawnPosition = testSpawnPosition;
GameObject playerGO = Instantiate(player, spawnPosition, Quaternion.identity);
NetworkObject netObj = playerGO.GetComponent<NetworkObject>();
netObj.SpawnAsPlayerObject(clientID, true);

testSpawnPosition works at (0,255,0) but not at (0,256,0).

I've also encountered another similar bug when using an object pool. The server can set the spawn position when it's the object's first time being spawned (using SpawnWithOwnership). But every other time it's spawned, it defaults to it's first given spawn point. I solved this by adding a SetPositionClientRpc to the ClientNetworkTransform sample script, and sending the correct position right after spawning. I kinda don't want to do that every time I spawn an object, but if that's the way it is, I'll do it. I'm guessing this same fix will work for players.

Reproduce Steps

1. Start a hosted game
2. Instantiate a player network object and set their spawn position to 0,256,0 before spawning
3. Spawn the player network object with SpawnAsPlayerObject

Actual Outcome

Spawn position defaults to 0,0,0 when spawn position is above 255 on the y axis.

Expected Outcome

Spawn objects above 255 with correct position

Environment

• OS: Windows 11
• Unity Version: 6000.2.6f2
• Netcode Version: 2.6.0
• Netcode Commit: idk how to find this
• Netcode Topology: Distributed Authority

Additional Context

Video demonstration: https://youtu.be/RlVHg-r4M3Q

[NoelStephensUnity]

Hi @Digital-Kyle,

There shouldn't be any limitation on any position axis as far as spawning and NetworkTransform goes.

Here is a sample project that offsets scene geometry, the camera, and such by 4096 Unity world space units on the y-axis and then proceeds to spawn the players and any balls spawned by the players (space bar) by 4096 Unity world space units on the y-axis.
There are two types of setting position examples in the sample:

1. When the player prefab is spawned, it uses a spawn offset value to apply the offset prior to the NetworkTransform running through the spawn sequence (PlayerMotion.cs).
2. When the player spawns a sphere (space bar), it instantiates and spawns with the added 4096 y-axis offset value.

SpawnFar.zip

Here is a video of the project running:

SpawnFar.mov

Take a look at the project provided and see what the differences might be in how you are instantiating and spawning and possibly any other scripts/components that might be clamping the y-axis.

Let me know if you resolve your issue after reviewing over the included project or can replicate the issue with the provided project (if so please send back the modifications so I can look into this further).

[Digital-Kyle]

You're right. I just tested a number of different things on your test project, I was unable to recreate my problem. Thanks for getting back to me so quickly! I will look deeper into my setup.