Missing HSR Data for ... Error when Uploading UGC Layered Clothing

When uploading UGC, specifically Layered Clothing, I often experience the error message reading “Missing HSR data for ItemName.WrapLayer. Please try again.”

It seems other creators have been experiencing this error for quite some time, but I don’t see an official bug report for it and it’s been ongoing for quite some time now.

Here is a picture of the error message.
image

Copying and pasting the asset into a different Roblox studio instance solves the issue and it lets you upload the item fine. No modifications had to be made to the item itself.

5 Likes

Hi, I have just had this problem. If you take a note of the settings under the WrapLayer component of either the imported 3d Model or the accessory you have created using the AFT. Then delete the WrapLayer and recreate with the same settings. Note that this is normally called HandleWrapLayer after creating the accessory.

Hi, thanks for the report. The “MIssing HSR data” error is shown to prevent broken assets from being uploaded. If you see this message, please try uploading it again or run the Accessory Fitting Tool on the asset. We are working on a fix for cases where this error is shown incorrectly.

1 Like

Hi, thanks for the response.

I have never received this error where I had to reupload the asset or run the accessory fitting tool to fix it. Simply relaunching studio fixed the item for me every time- does this mean that all these errors are being incorrectly shown (as I’d assume there are no changes to the asset through simply relaunching studio)?

I have been trying to fix mine for about an hour straight. I am getting very aggravated. I have tried importing in a new studio, I have tried reimporting, I have tried re-doing the accessory fitting tool, I have tried everything in the book. What is wrong?

Hi all, apologies for your experience. The cause is a timing issue: a layered clothing item’s HSR data is produced by a background job in Studio, and publishing can get ahead of it, so the upload doesn’t find the data and errors out. Nothing repairs that state on its own, which is why relaunching Studio or moving the asset to a fresh instance often clears it. @Junozy, to your question, the error isn’t spurious; when it fires the data genuinely isn’t there, so the check is correctly stopping a broken upload.

The bug is that publishing can outrun generation at all, and your observation that it hits an assortment of items at random matches that exactly. For now, leaving a few seconds between your last edit and publishing, uploading one item at a time, and relaunching Studio then reimporting and refitting all reduce how often you’ll hit it, though because the cause is timing, none of them are reliable.

I don’t have a quick fix to offer today, longer term we’re designing a replacement for HSRData that removes this race entirely,

2 Likes

Thanks for the update and information. I will keep an eye out for the HSRData replacement update, hopefully in the near future :slight_smile: