So I have disabled LevelOfDetail because I have made a custom renderer that compresses the objects and loads them in when in view. It’s very efficient memory usage, the map is procedurally generated and the objects are compressed to a point and a reference of their source object. The renderer organizes them into sections based on a grid of a certain size then the client invokes the server with the camera cframe, viewport, the sections in view (only those locally rendered by streaming enabled), and frames per second. I say this because I’d prefer to optimize the memory throughput as much as possible and having copies of models with different LOD is inefficient and redundant in my case.
I noticed this with testing in a live game, the objects would render in and flash from a LOD compressed model to the normal version. I checked the LevelOfDetail and it is disabled. So, thus I am reporting this as a bug.
Expected behavior
I’d expect that when I have LOD disabled there shouldn’t be compressed imposter models flashing.
this bug has nothing to do with my environment. It’s an internal issue. Why are models with LOD disabled still rendering imposter models with streaming enabled? I’d would’ve more appreciated it if you minded your own business literally and leave the action of responding to ROBLOX staff…
Please provide a simple repro place demonstrating the issue. I have tested internally and I don’t see LOD being shown for models that have LevelOfDetail set to disabled.
I would also expect to see numerous other reports from creators if model LOD was being rendered for all models even when disabled, so it is likely there is something special/unique about your situation. Without a repro place we can’t help investigate your issue.
A Roblox staff member has already responded with more or less the exact same reasoning I had but I’d like to nitpick your words a bit, since you felt the need to defend providing almost no actual info
no one can answer that question for you if you don’t provide a reproduction place in your own environment. No one else is going to have the exact same setup as you and it is naïve to think that others (whether they be Roblox staff or not) can innately understand what the issue is just from seeing you talk about it. You didn’t even provide an example video or pictures. Even if others would be able to reproduce it via effort, it saves time and vastly increases your chances of a bug being fixed if you make it as easy as possible for others to see the issue.
Closing this topic as we didn’t receive any more info on the situation. Please feel free to post another bug report if you run into this issue again and please make sure to provide any files/info that might help our engineers find the root cause of the issue. Thanks!