[1866] Possible regression of black screen while traveling issue: infinite loading loop after build 1865
needs more information
Riria Nee-chan
Related issue:
This may be a regression related to the black screen while traveling issue that was fixed in build 1853.
The previous issue caused the loading screen/rendering path to fail, resulting in a permanent black screen.
However, the current issue (observed since build 1865) behaves differently:
* The loading screen renders correctly.
* The "Connecting..." / "Initializing..." screens also render correctly.
* After that point, the client becomes stuck in an infinite loading loop and never completes the world transition.
Steps to reproduce:
- Travel to another world.
- During the transition, the client may become stuck in an infinite loading loop.
(The issue appears to occur more frequently while using a heavy avatar with many textures/assets.)
Expected behavior:
The world transition should complete normally, or the client should recover gracefully from a failed asset loading state.
Actual behavior:
The client remains stuck in an infinite loading loop.
Additional information:
The following log entries appear repeatedly while the client is stuck:
```text
VRC.DataModel.Textures.NativeTextureDownloader.DownloadTexture
with:
```text
HTTP/1.1 404 Not Found
The thumbnail for that image is not available
This appears to be related to the previous async/race condition issue, but the failure mode has changed.
Previous behavior:
* Loading/rendering path failed → permanent black screen
Current behavior:
* Loading UI remains active → async exception continues to occur → infinite loading loop
The issue occurs on both Unity 2022 and Unity 6, although the frequency may vary.
Additional logs:
This exception pattern is repeatedly logged while the client is stuck in the infinite loading loop:
```text
Cysharp.Threading.Tasks.UniTaskCompletionSourceCore`1[TResult].TrySetException (System.Exception error)
UnityEngine.AsyncOperation.InvokeCompletionEvent ()
```
This exception pattern was also observed during the previous black screen issue before it was fixed in build 1853.
The main difference is that the loading UI no longer fails to render, but the client does not appear to recover from the failed async operation or complete the world transition.
Log In
Riria Nee-chan
PS.
I was experiencing consistent world transfer failures with a specific avatar. Other avatars worked normally.
I recreated the avatar as a new Blueprint (new upload/new Blueprint ID), and the issue disappeared completely.
The avatar content was effectively the same; only recreating the Blueprint resolved the problem.
This may indicate that some Blueprint metadata or uploaded avatar state became corrupted.
StormRel
updated the status to
needs more information
Can you provide the avatar ID that seems to be triggering this?
Riria Nee-chan
StormRel I recreated avatar as a new blueprint and seems like fixed for now, maybe that was corrupted blueprint issue. will report back in a few days.
Riria Nee-chan
StormRel Update: Creating a new Blueprint appears to temporarily resolve the issue.
However, after some time, the problem eventually reoccurs even with the newly created Blueprint.
At this point, I have not been able to identify a specific trigger or consistent error pattern that causes it to return.
WubTheCaptain
Full output logs and a video may be useful to attach, if you can reproduce this issue.