I was using a smoke texture for the flame particle effects for my jetpacks and starfighters. I got it from the Fusion Gatling Blaster gear. Then today, out of nowhere, it gives me a file does not exist error. This is the url:
We recently migrated some old uncommonly used assets to the website out of the app. Things should have still worked as normal but maybe there was an issue with the migration. @Xsitsu would know more.
I would suggest just providing the file here, and OP can upload it and use that. Developers should not rely on assets in the ROBLOX install which are subject to change, be moved, or be deleted at any time.
If thatâs the case then I can just tell the client to point to this texture when someone tries to use the old one which should allow us to get this fix out faster. Thanks for letting me know.
Are you going to do that every time the file structure changes in the install folder? That sounds like a hack. Using assets in the install folder was never supported to begin with. People should just upload the assets they want to use to ROBLOX â that way they donât have to worry about it changing or being moved/deleted. I could understand if this was a widespread issue, but thereâs no indication of that.
From what it sounds like, the asset AxonMega is using was taken from an old Roblox gear that points to a file in the content folder. The files in this folder are mainly used for things like CoreGui and textures for things like smoke and fire, but there are some cases where files that old gear use were present in this folder.
When we went through and were removing files from this folder we had to decide for each file if the file was safe to completely delete, or if it needed to be uploaded to the website so legacy gear/places wouldnât break. For example, we were still shipping Roblox with the original comic sans font from when chat was done entirely in C++ and we were still shipping the old, old Lua script icon. We were also shipping Roblox with assets like GunCursor.png that all of the tools in old games like Crossroads and SFOTH use. None of the actual Roblox code base uses GunCursor.png, so we didnât want it in the content folder that we ship Roblox with, but we didnât want to completely break these old games either. To handle this, we removed it from the content folder, but uploaded it to the website and then told the client to replace rbxasset://GunCursor.png with rbxassetid://. This way, any old games would download this asset from the website instead and would still be able to work.
The gear that AxonMega is talking about is one of these old legacy gear that we donât want to completely break. When I removed smoke.png my thought process was that it was only used by the Smoke objects and that this had been replaced with the newer .dds smoke file, so it should be completely removed, but as it turns out some legacy gear are still using the older smoke texture and need to be upgraded to point to the new one.
Maybe when I said âif people are still using itâ I gave off the wrong impression. I should have chosen my words better. What I meant was âif some places/gear on Roblox are still using itâ. If a developer was using the old BC hardhat icon that was in the 2010 leaderboard, then we donât really care because that icon was only supposed to be used in CoreGui and we havenât used it in years. However, if a developer took a piece of an official Roblox gear that was using the old smoke texture then we do care because this is legacy content that suddenly stopped working.
Ah, now I understand. Thanks for the explanation. Youâre right that this is a good idea for legacy gear â hopefully whenever theyâre updated (if theyâre legacy they probably arenât FE-compatible) that can be remedied and it can be fully removed at that point.
rbxasset://textures/particles/smoke_main.dds rbxasset://textures/particles/fire_main.dds and rbxasset://textures/particles/sparkles_main.dds are hard coded as particles so I donât see these paths changing any time soon. Just use these.
These are hard coded in C++ land which means that there is no promise that they will keep working. Donât use rbxasset:// paths in your games - or if you do, expect them to occasionally break without notice.