I wonder when we’ll next get an update about this issue…
1 Like
Hello there, could you please let me know what you see in the “Memory” tab for Windows Task Manager when this happens?
Also, if you could provide a log associated with this that would be appreciated.
1 Like
None of these are my screenshots, so I’ll ask around.
1 Like
It disappeared and has reappeared again. Very odd how this keeps on happening
2 Likes
A bit irrelevant but I find it extremely weird how concrete is one of the only original materials with a reasonable resolution. Why aren’t all the materials a similar resolution, and why is concrete the only one with its own reflection map?
As Roblox have recently announced 8k user-uploaded decals, it would be nice for their materials to also have their resolutions upgraded, at-least to 2k.
1 Like
The problem is still occuring.
5 Likes
This problem is still occuring with player avatar textures, such as classic t-shirts (the front torso decals) and classic shirts and pants.
Stop compressing textures when unnecessary. It should be a bare minimum to not roll out a broken feature when its not finalised, especially when it only harms users’ experience.
I am not sure whether this issue occurs for materials, decals, or materials in experiences though, but if it does its not as extreme as before.
2 Likes
Can confirm this issue still does occur for materials and custom materials
not decals though
but another thing is this happens in studio now.
1 Like
as if it couldn’t get any worse, occuring in studio is the last place it should ever occur.
its kinda ironic that this post has the fixed tag on it, even though its not even fixed and now its occuring in studio.
4 Likes
Ah yes, Roblox forcefully claiming my post as fixed against my will and control, very shady.
I see they also locked my ability to edit the post title too, so I can’t signify that it is in-fact very much not fixed.
1 Like
They have silienced you.
Also another strange thing about this bug is that the spawnpoint decal is affected while the custom decals arent.
1 Like
I started having this happen after I restarted studio sometime recently. This happens with custom decals and image textures too, both in Studio and Client, even if the image has low resolution.
1 Like
As the last roblox staff to reply to this post, can you please address these issues, such as my post incorrectly being marked as fixed and the issue clearly getting worse?
I’d also appreciate if you can ensure that developers are notified of this issue and that the correct procedures are taken to ensure this issue is rectified.
Hold on, could y’all try these 2 fflags to see if it fixes it
Here:
{
“DFFlagTextureQualityOverrideEnabled”: “True”,
“DFIntTextureQualityOverride”: “3”
}
I currently have these fflags on but it doesnt seem to fix it all, not sure if they changed how these fflags work.
Another thing i forgot to say is, these used to work and it actually fixed the problem.
But now it doesn’t.
Also please dont pin this as a solution this is just a question.
They don’t work, I checked earlier. Even after changing the texture quality level in the Bloxstrap launcher settings, the textures remained at the same quality level. Perhaps Roblox could have changed something in the system that is responsible for textures and images, which made it impossible for these FastFlags to interact with textures.
This problem is still occuring.
Edit:
I have gladly came back with a fix, does require 2 fastflags though.
DFFlagSkipHighResolutiontextureMipsOnLowMemoryDevices
DFFlagSkipHighResolutiontextureMipsOnLowMemoryDevices2
Insert both of these fastflags into your fastflags list and set them both to false, still kinda sucks that this requires fastflags though.
4 Likes
About the last staff that replied to this post, he hasnt replied to ANYTHING for a hot minute when i mean a hot minute about 6 months.
2 Likes
I think the only chance you’ll get a response from a staff is resposting it, since this has the fixed tag on it the staffs assume its actually fixed.
2 Likes