Large model crashes "Save to Roblox.." prompt, breaks publishing

I am currently unable to publish a model to update my game. Upon attempting to upload the model, the model upload widget crashes and displays an error to the output.

Model file included in private message to staff, although I suspect any sufficiently large/complicated model will trigger this issue

Repro Steps:

  1. Download MyGameModel.rbxm
  2. Insert it into ServerStorage of an empty place
  3. Right-click → Publish to Roblox → select “Model” as type
    [Crashes]

Expected behavior

I expect to be able to be able to upload the model and publish an update to my game. However, the window always crashes when selecting the “Model” option and I am unable to publish.

A private message is associated with this bug report

6 Likes

Hey - thanks for reporting this, we will look into it and get back.

Note that this issue appears to be specific to the model upload widget that is provided to users with access to UGC program uploading. I am able to temporarily bypass this issue by logging into studio on an account that does not have UGC access

How long ago has this been happening? I think this is related to a change I made but it was a very long time ago if this happens to be recent.

Do smaller models work? I think it only happens if you have a model with 10k+ descendants.

If you know how to set flags, you can set FIntAssetConfigDescendantsPreviewLimit to a very very high number to see.

I tried setting this flag to 10 million and did not see any change in behavior. Same error as noted in my duplicate report. (Unable to Publish a Model (attempt to index nil with 'ClearAllChildren'))

Individual cars and smaller models do seem to function, though.

Smaller models do work. This is a fairly recent change as 1-2 weeks ago it was working correctly. Please also see Hertz’s comment above regarding the limit flag

I made a thread without seeing if this issue was already a thing because I thought something as major as publishing a model couldn’t be broken for this long.

turns out it can be, and it’s for a week. my game relies on this method for content updates and now i cant do it.

Thanks all, I am looking into this today

1 Like

I just pushed the fix for this–it should take roughly 2 weeks to release.

In the meantime, setting FIntAssetConfigDescendantsPreviewLimit to a very very large number should fix it. I’m surprised to hear it doesn’t.

1 Like

on macOS
learn what a fflag editor is
maximumadhd’s mod tracker (w/ fflag editor) is windows only
set up a windows vm
attempt to install mod tracker
errors on installation and crashes
read up that bloxstrap has a fflag editor
installs bloxstrap
sets FIntAssetConfigDescendantsPreviewLimit to 999999999999
launches studio in VM (thankfully it works)
attempts model publish
still fails (assume bloxstrap only edits robloxplayer)

Is there an official or recommended method that i can edit this flag?

Just got the mod manager to work.
Edited the value to 99999999.
nothing

just published same model on an alt that does not have UGC access.

issue is more likely UGC related lol

Still unable to publish models in several games on my account. This is requiring me to log on with an alternative account that doesn’t have UGC access in order to restore my workflow, which isn’t feasible for all of the games I work on

Is there any way this can release sooner than in two weeks? The issue is breaking developer workflows

I pulled some strings and luckily this is one of the rare cases where we can ship updates without waiting for complete the Studio release cycle. The fix for this should be enabled now. Please let me know if you have any problems @berezaa @Crazyblox @144hertz

I am still having the issue on my end

Gah, can you show the top of the error? And confirm that this happens even after a couple retries, as well as making sure every Studio window is closed?

@berezaa Enough time has passed to where this should’ve been more stably released by now, can you double check again?

1 Like

The fix works for me! Thank you so much for the prompt action here, it’s greatly appreciated.

1 Like

Sorry for the late reply. Can confirm this is now fixed for me as well

1 Like