My entire community is stuck due to this isse. I posted about it months ago, please let the engineer team to have the option to revert to the older UI instead of having a developer stuck for over six months for a fix, this is critical at this point.
They can then be as agile as they like taking their time, and then publishing the new version again when it works.
I will follow up again on this issue – apologies for the inconvenience
Ah nice. We are now back to even more limited space. Why is that every time Roblox Studio has an update, a feature is either removed or broken? I’ve said it before and I’ll say it again, please don’t mess with something if it isn’t broken. How long has it been now? almost 6 months? I hate to say it but this is why Roblox Devs haven’t been on or have even quite Roblox entirely because they are sick of something always getting messed up behind their backs.
The fact that this is still an issue baffles me. The old UI worked fine, we didn’t need this new one, you simply fixed something that wasn’t broken. The only reason for this UI update was having everything written in Lua, like the toolbox (IIRC, I might be misremembering)
At this point I’ll just have to publish a new module (thus having another old-ish module unupdatable) and go through all of my code to update it to the new one, and then tell everyone else who uses it that I have contact with to use the new one instead of the old one.
It might be possible to find the endpoint that is used to update models and then use that directly to update the content on the back-end. That way you don’t need to keep pushing new models. Whatever is more convenient to you.
This new asset configuration is just a complete waste, no one wanted it, the old one was more than useable and was pretty good, the new one is worse, has a few bugs like the one you mentioned, and even freezes quite often(I have a beefy pc which nothing other than studio freezes on)
Four months from my last reply to this thread and this issue still isn’t fixed. I’m unable to update modules for groups I work for without re-uploading them and changing the required ID. This has gone on for way too long, but I wouldn’t even be surprised if it surpasses a year since this thread was created at this point. Currently, we are forced to upload them as new models, meaning more assets in our inventories, consequently making this problem worse!
How is it that you can justify this toolbox update when this is clearly a massive flaw? Not to mention the other issues with it, such as: "Search by User" option in Toolbox does not show assets for some users - #4 by un1ND3X.
This update should’ve been reverted the moment issues like these were discovered until a fix was implemented. Finding the endpoint and manually uploading the model through that is inconvenient and terrible UX. This shouldn’t just be downplayed because it only affects some users who have uploaded a larger amount of assets. I’d still much prefer that it’s reverted until a proper fix is put in place.
There has been a large number of requests for it to be reverted, but they have all been ignored without even a reason as to why. I understand that this update means all widgets are ported over to Lua (which is great). However, as with any update, it shouldn’t be pushed until it’s fit for use - and this clearly isn’t!
Please, give us one good reason why you won’t revert it. You have completely disregarded all requests for it to be without good reason.
The reason is likely going to be engineering-related. It may be too costly in terms of maintenance / testing to keep both the Lua and Qt versions of the functionality alive at the same time across many months. Just the fact of a feature being alive means it is eating up engineering time in some part of the process.
Other than that it’s very hard in engineering to predict how long something is going to take or how easy something is to fix. Judging from the responses above it seems like they have been investigating and trying to fix it from the week it was reported. Probably just unfortunate that the fix took way more tries / more effort than they thought.
Maybe they would have reverted it if they knew it was going to take this long, but that’s hindsight.
I understand that, however, it would still be nice to have some clarification from a Roblox engineer as to why this decision was made. As you’ve said, they’ve clearly been working on it, but for an annoyingly long time now and I feel it should be made more of a priority.
On the other hand, you previously mentioned finding the endpoint for model updates. However, I’m unable to find any endpoint other than the model upload one which doesn’t allow for overwriting of old models (the only parameter is the file to upload). I’ve also tried looking at the traffic from studio in Fiddler, but nothing seems to show up. Do you, by any chance, know the endpoint used?
About a month ago, I found that this model upload dialog issue was fixed. When I went to upload to an older model a few days ago, I found that this issue has reared its head again.
This is incredibly frustrating. Why is it that this window has taken so long to fix? I’ve had to use an older version of Studio from almost a year ago just to be able to upload over older models because the new window has prevented me from doing so, and security checks were implemented to prevent people from overwriting the upload dialog’s script for a workaround.
How in the world are you using an older version of Studio when they update it every week? I would like to know because older Studio is MUCH better than this newer broken version.
I have an older version that I saved locally. If you use the RobloxStudioBeta executable instead of the RobloxStudioLauncherBeta executable, then Studio will open without updating.
Yikes, wanted to upload a newer version of my Raycast module for the community, but I can’t since I can only see 2 models in my overwrite asset window. I hope this becomes fixed soon. Last time I tried overwriting, my window had only about 5 models in that window.
This issue is still happening and makes me unable to update my older models without creating new ones. It should be fixed asap, as it’s extremely inconvenient to overwrite models now especially when your game relies heavily on inserting ~70 models which have to be kept up-to-date.
Currently the list displays just 25 most recent models in my case. I would suggest adding a search bar to this GUI to locate older models even faster, it would be a great addition.
I submitted a fix in Studio that should come out with release 426 this Wednesday. I’ll reply again when the controlling flag is flipped and the fix is live.
On behalf of the engineering team, I wanted to apologize for this issue taking so long to fix. It was a pretty complicated problem, and the engineer with the most context in this area fell ill with the flu, delaying the fix even more. They deserve credit for the heavy lifting. I just fixed that last piece of it in their absence.
The flag was flipped in the last 20 or so minutes, and I have confirmed that the fix is now live.
I’m currently experiencing this issue again and have for a few months despite the fix, and I’ve had to use older versions of studio to update older models. The UI refuses to scroll past a certain amount of assets. The furthest down I can scroll in newer studio builds is to the start of this year, around the 15th of January.
I have a lot of models in my group, so a lot of the things I’m trying to update are buried under a couple hundred models. I’ve noticed that when more models are created, one model from the bottom of this “list” is taken off of the amount of models that can be updated.
For example, let’s say I have 2 models at the bottom of this list. One is named “X” and the other is named “Y”. “Y” is the older model, with “X” being right after it. If I upload a new model named “Z”, I can’t update “Y” anymore because “Y” is no longer showing up under my group models tab.
I’m sure this can be fixed, because I had been experiencing this problem earlier in the year, and then it got fixed, but for a few months now, it’s been broken again.
The same think has been happening to me as well. Cant do it with animations either
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
