We will release a change to remove ThumbnailConfiguration objects during the character loading process in the coming weeks. Once we have a date, we will be sure to give you a heads-up before officially removing the feature.
These instances are used to configure accessories thumbnails and don’t have a use-case at runtime. Removing these instances will reduce the bandwidth needed to replicate an avatar by reducing the number of instances inside avatars. As an avatar with a maximum 17 accessories (including hats, layered clothing, hair and eyebrows/eyelashes) could have up to 51 instances just for thumbnail configuration, this will reduce the worst-case number of instances in an avatar by a large number.
ThumbnailConfiguration instances will still be inside accessories when using InsertService:LoadAsset to insert them. If your workflow does rely on ThumbnailConfiguration, as an alternative, you can insert Avatar assets using InsertService as part of your workflow.
We don’t think this should have a negative impact on experiences because we don’t think experiences are using these ThumbnailConfigurations inside avatars.
Please let us know if there is some use case we are unaware of and if your game does use these instances.
You misunderstood, they are not removing the feature that allows you to set the thumbnail for the accessory.
To sum it up, they are removing unneccessary “Instances” which are ThumbnailConfigurations whenever your character model loads in to the game. That is done in order to save bandwith in packets that are sent to your client, resulting in less lag.
There hasn’t been an update on this in 4+ years and I’m wondering if this is still planned for release? This would be a great improvement to character loading.
We would still like to fix this, but we don’t have any current plans. We ran into some problems when we originally tried to ship this and other work has taken higher priority so we haven’t gotten a chance to go back and fix this.
If you use InsertService:LoadAsset() and you don’t need the ThumbnailConfigurations, you can destroy them before moving the accessory into the world. For example:
local asset = game:GetService("InsertService"):LoadAsset(14339718570)
local thumbnailConfiguration = asset:FindFirstChild("ThumbnailConfiguration", true)
if thumbnailConfiguration then
thumbnailConfiguration:Destroy()
end
asset.Parent = game.Workspace
We are planning on releasing this on Wednesday, 17th of January. We expect this shouldn’t negatively affect any games, but if it does affect your game, speak now!
