ContentId that references file on local machine do not properly update

Bug Reports Studio Bugs
,
1

If you upload File.png, but then replace File.png with a different file, under the same name, that change will not show in Studio until a relaunch.

2

It doesn’t seem like a bug. Many programs (like Blender) cache local images. Especially since Roblox uses the temp id thing

3

octav is right, most programs use caches to optimize their loadings

4

That’s valid, what is there in terms of being able to reload this cache

5

Hi,

Could you provide a little bit more information on this? Some repros etc.?

Thanks

6

Min repro:

  1. Create ScreenGui with ImageLabel
  2. Use asset manager to upload some image locally (rbxassetid protocol)
  3. Reference that image in that ImageLabel.Image field, (ex; rbxasset://image.png
  4. Save a completely different image, but by overwriting the existing image.png. You’ll see that until you reload Studio completely, the image will remain the old file
7

Hi, this is more of a feature request as cache/texture refresh at this level for an already created asset is not currently supported. Will forward on there.

8

I’d probably oppose, it makes working with images stored on the local machine (rapid prototyping before publishing to production) extremely difficult.

This isn’t a feature, it should be a given, if I update a file under the same name, same file extension, more often then not with minor changes, that update should be reflected, it’s a part of the core functionality of the existing feature, not a new one altogether

9

Its not a feature request in Studio, its a feature request in the engine. The engine has a certain set of assumptions, and one of them is that certain types of objects aren’t going to change. In this case, it does, but in order to refresh the object everything down to the texture has to be swapped out. So its not a simple ask.

10

I’m not quite sure where textures come into things, nor objects, this is for Images and Sounds primarily, Models are not my primary concern, although if models are supported in this manner (Not something I have researched thoroughly) then yeah they’d be of some concern

11

The behavior you describe is called “Hot-Reloading”. It isn’t “a given” in most places. Websites, for instance, do not reload when the underlying HTML file is changed (which you can check for yourself by creating and opening an HTML in the browser), or changing a .txt that’s open in Notepad in a second Notepad window. For most Roblox assets, i.e. ones uploaded to the website, it doesn’t make sense to support hot-reloading because that only creates extra loading time and network pressure.

“Images” are textures. “Textures” are just the terminology in computer graphics, AKA a buffer of pixels on the GPU. “Object” is also just a generic term, not necessarily Instances.

1 Like
12

All these facts be as they may, I still stand by my opinion that you should not have to reload your studio session in order to get the update to your asset which is neccesary to continue your development- as it trumps the usefulness of the feature

It is livable with, but I can name many who will circumvent the hassle and simply use a tool like Asphalt, and clog the cloud with repeat uploads of the same asset instead

1 Like