cancel
Showing results for 
Search instead for 
Did you mean: 

Reoccuring asset visibility issue in Desktop Editor around missing assets / rate limiting

virtualpebble
Member

Hi!

I'm regularly getting an issue that leaves all my assets in Horizon Worlds missing, showing up as exclamation marks. This will happen and be present for a couples days, even after restarting my computer. The same thing will even show up in other worlds on my headset while this is going on, and seems like it's maybe linked to my account.

Is there a workaround anyone has found for this issue, perhaps a way to clear the cache or avoid apparently requesting missing assets?

The issue from my application logs:

2025-04-30 13:45:26Z 46336 I [standaloneassetmanager::fetchassetsutility] Request 1546188227331 for asset versions: 9140429309385770, 9335116479867725
2025-04-30 13:45:26Z 46346 W [settings] AssetGraphQL: Failed to retrieve assets. Query name xfb_social_vr_asset_by_id. Response body: {"errors":[{"message":"Rate limit exceeded","severity":"CRITICAL","code":1675004}],"extensions":{"is_final":true}}.
2025-04-30 13:45:26Z 46346 W [standaloneassetmanager::fetchassetscallbacks] Null asset handle recieved
2025-04-30 13:45:26Z 46346 W [standaloneassetmanager::fetchassetscallbacks] Null asset handle recieved
2025-04-30 13:45:26Z 46346 I [standaloneassetmanager::fetchassetscallbacks] Complete asset batch 1546188227331
2025-04-30 13:45:26Z 46348 W [asset] WbStandaloneAssetService: Exception while fetching asset. Retrying fetch. Asset Version ID: 9335116479867725
Data-{exception:System.AggregateException: One or more errors occurred. (The given key was not present in the dictionary.) ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
--- End of inner exception stack trace ---

 

1 ACCEPTED SOLUTION

Accepted Solutions

virtualpebble
Member

It seems to be related to the texture mapping process when importing an FBX. Removing materials from my Blender export and adding textures after import instead fixed the issue.

View solution in original post

1 REPLY 1

virtualpebble
Member

It seems to be related to the texture mapping process when importing an FBX. Removing materials from my Blender export and adding textures after import instead fixed the issue.