Related issue: https://feedback.vrchat.com/open-beta/p/black-screen-while-traveling 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.