decentraland / decentraland/unity-explorer
[QA] Genesis Plaza | Avatar gets tied to buildings and elevated endlessly after teleporting back to GP from another scene
- Dominant language
- C#
- Stars
- 23
- Forks
- 17
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 101
Description
### 🛠️ Build version:
v0.156.0-alpha-release/2026-07-13-889485f
### 📔 Issue Description:
After visiting scene (1, 95) - Meta Gamimall, jumping onto a platform and staying idle, then teleporting back to Genesis Plaza (0,0), the avatar becomes stuck/attached to nearby buildings and is elevated endlessly upward, moving together with them as if parented to a moving hierarchy. Live-event display elements also glitch (mirrored/flipped text) around this time. Player.log shows 45 repeated "BoxCollider does not support negative scale or size" warnings tied to the (-3, -2) parcel immediately after the teleport-triggered reload, with the affected object's transform hierarchy nesting up to 13 levels deep under itself (`POOL_OBJECT_Transform/POOL_OBJECT_Transform/...`), suggesting a pooled scene object is being re-parented onto itself instead of being cleanly reset.
### 👣 STR:
1. Go to (1, 95) - Meta Gamimall
2. Jump onto a platform and stay there for a while (idle is fine)
3. Teleport back to Genesis Plaza (0, 0)
### ✔️ Expected Result:
Avatar returns to Genesis Plaza normally, unattached to any scene geometry, with no visual glitches on the promo/live-event boards.
### ❌ Actual Result with evidence:
- Avatar gets tied up to buildings; avatar + buildings move together as a set, with the avatar elevated endlessly upward. Only workaround found: fully close and reopen the client.
- Live-event display boards ("Worlds"/"DCL Store" promo panels) render mirrored/flipped.
- Player.log (Player-prev.log) shows a burst of 45 "BoxCollider does not support negative scale or size" warnings at 11:39:32–11:39:41, immediately after the teleport back to (0,0), with `POOL_OBJECT_Transform` nesting depth reaching 13 levels in a single hierarchy path — not present on the initial GP load or a later walk-in reload of the same parcel.
### ➗ Reproduction:
##### ❓ Unknown - (reproduced once in the available log; needs a few more repro attempts to confirm consistency and whether it's teleport-specific vs. also triggered by walking back)
### 🖥️ Operative system and additional Notes:
macOS, Apple M3 Pro chip.
Two client instances were open during testing — Player.log (short session) only captured the outbound trip to (1,95); Player-prev.log captured the full round trip and contains the evidence above. Note: AVATAR, AVATAR_ATTACH, and SCENE_LOADING log categories are suppressed in this alpha build, so the avatar-parenting behavior itself isn't directly confirmed in text logs — only the pooled-object hierarchy corruption and the visual observation are.
Possibly related (different symptom, same GP-return trigger pattern): decentraland/unity-renderer#6191 "Assets Not Loading Upon Returning to Genesis Plaza."
Recommend filing the mirrored live-event board glitch as a separate bug since it looks like an unrelated rendering issue (likely billboard/UI-plane facing).
[Player.log](https://github.com/user-attachments/files/30006390/Player.log)
[Player-prev.log](https://github.com/user-attachments/files/30006388/Player-prev.log)
https://github.com/user-attachments/assets/80b2ec6f-5e99-41c9-81c0-901aa50d2db5
https://github.com/user-attachments/assets/1221638e-c7ae-41f0-93ba-d010f2cbc751
Contributor guide
Research direction
Reproduce the route from (1,95) to Genesis Plaza and compare the initial load, teleport return, and walk-in reload. Start with Player-prev.log around 11:39:32–11:39:41, focusing on the repeated collider warnings and nested POOL_OBJECT_Transform hierarchy; use Player.log and the attached video evidence for comparison. Done means the return no longer attaches or elevates the avatar and the pooled-object warnings and visual glitches are explained or resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- desktop, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100