Avatar Not Loading With Assets And Long Respawn Time

Bug Reports Engine Bugs
#1

Reproduction Steps

  1. Join an experience.

  2. Your Roblox avatar will often not load its assets and will spawn as a noob. Additionally, respawn/reset times have become often extensively long at the moment.

Syst Info:

11th Gen Intel(R) Core™ i7-11800H @2.30GHz, Intel(R) UHD Graphics, NVDIA GeForce RTX 3050 Ti Laptop GPU

Expected Behavior

I expect my Roblox avatar to load its appearance as normal and to respawn within a normal timeframe.

Actual Behavior

Your Roblox avatar will not load its assets and spawn as a noob. When you reset, the duration to reset will be longer than normal. See this video showcasing the issue and a view of my browser console and experience console: youtu.be/uQlS8ce7xoA

  • No server or client sided error outputs in the console of the experience

  • The website outputs three errors shown on the video, they are:

edc66704bd1974195d8c60f4a163441bec82f1bcb11c492e7df07c43f45a4d49.js:16

   GET https://graph.facebook.com/?id=https%3A%2F%2Fwww.roblox.com%2Fgames%2F7298704154%2Fview%3Frbxp%3D13238212&scrape=true net::ERR_FAILED 400

Untitled-Game:1

   Access to XMLHttpRequest at 'https://graph.facebook.com/?id=https%3A%2F%2Fwww.roblox.com%2Fgames%2F7298704154%2Fview%3Frbxp%3D13238212&scrape=true' from origin 'https://www.roblox.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

Uncaught ReferenceError: gigya is not defined
at Object.t [as loadIcons] (159e88100f75cc6a27bdd7e62550e317.js:109:394)
at 159e88100f75cc6a27bdd7e62550e317.js:94:674
at dispatch (4a481e857787c241b22259659a0674a7.js:12:9669)
at r.handle (4a481e857787c241b22259659a0674a7.js:12:5691)

However, these were obtained before joining the experience, on the page of the experience, and I don’t think it is relevant to the issue. No errors were outputted on the website when I joined the experience.

  • I observed that memory usage and ping was unusually high for an experience that just contains a baseplate

  • And it seems as though the avatar subdomain and its API is failing which is probably the cause (avatar.roblox.com)

avatar.roblox.com/:1

   GET http://avatar.roblox.com/ 503 (Service Unavailable)

Workaround

Rejoin/Reset, there will be a chance your avatar spawns with the correct appearance.

Issue Area: Engine
Issue Type: Other
Impact: Very High
Frequency: Often
Date First Experienced: 2022-09-03 07:09:00 (+03:00)
Date Last Experienced: 2022-09-03 00:09:00 (+03:00)

On a side note, I would recommend a failsafe alternative to avatar fetching as emphasized in: Alter the default process for fetching player avatar appearances.

I especially like metatablecatmaid’s solution to this problem.

3 Likes
#2

Roblox is aware of this:
Roblox Status

1 Like
#3

Thanks for the information!
We are aware that some players are having issues related to joining experiences. Our engineers are actively working on it.
You can follow the status of this incident here: status.roblox.com

3 Likes
#5

it happens in studio too

The game takes forever to load, and some scripts of mine dont work because I dont have my avatar

oops, didnt mean to reply

#6

I’ve seen this happen at random for the past few weeks, but figured it was a latency issue on their end. I have seen it happen in the Studio also, doing a play test, you blow your character up on purpose to test out how the death event is handled and your character just sits there for about 10 seconds and then everything works with the event after the weird delay. Didn’t know this was affecting everyone, everywhere. :upside_down_face:

#7

Also characterappearanceloaded keeps waiting forever, dont know if this is an expected behavior though.

#8

Just to add, don’t try to view the “Avatar” section in Studio under Game Settings, it will hang Studio. Don’t ask me how I found out. :rofl:

#10