So how can I make sure that what I see is correct before I make another change? If I make another change before what I see is correct then the newer change is prioritized, and if I keep making changes, the oldest changes never appear at all.
Reduce the frequency of changes depending on the distance from the camera. Try to keep it under 1000 total individual changes a minute.
1 Like
Maybe this should just be in bug reports. It’s not updating colors and I’m changing colors, and there’s no lag. It just isn’t updating what to show.
https://i.gyazo.com/7d7db761d5c3583c797db76d8d0e53f1.gif
1 Like
Could you do this with a surfacegui instead?
3 Likes
It’s not a bug, you are simply submitting more work than the clustering system is able to process. The “there’s no lag” part is because the clustering system is working as intended on a tight time budget. Realtime is real.
1 Like
It’s sort of a bug in that we don’t prioritize updates correctly right now so you can permanently starve portions of the map by doing per-frame updates to other portions.
New clustering system would change everything sufficiently that I don’t think we’ll be focusing on fixing this though.
1 Like
Instead of setting part.BrickColor, try pooling the parts and CFrame them so they switch places when needed. This should result in less expensive part updates
2 Likes
I replaced the part system with just a gui with a ton of frames. I’m noticing creating new frames is super slow and just changing their color is fast.
1 Like
You’re still doing a geometry update when you CFrame something. CFraming anchored parts may even be more expensive.
1 Like
Setting .CFrame doesn’t get throttled like BrickColor, Transparency, Size, and other properties do
3 Likes
It does still get throttled though.
1 Like
New parts being created also don’t show up, it isn’t just changing color that lags behind.
1 Like
CFraming different size parts extremely fast instead of setting mesh.Scale proved to be much more efficient for my game’s rain system:
https://devforum.roblox.com/uploads/default/original/3X/1/e/1e0cdebad1bfe5eb144a19bc5ce95d01a8d2f39d.gif
I’m pretty sure properties like BrickColor, Material, Transparency, Size, mesh.Scale, mesh.Offset have problems updating, while CFrame is the fastest
6 Likes
Ah yes, changing the CFrame causes the clustering system to use dynamic clusters for moving parts, which have far less capacity… So if you try to force updates by wiggling the parts, that will also proportionally increase the number of draw calls, and no, it won’t solve the geometry generator throughput problem.
1 Like
That’s correct - CFrame currently is the only “fast” property in that you can change it every frame without really heavy code kicking in. Everything else is expensive.
We’re working on a new system that would make most properties cheap to update. But for now you’ll have to live with the limitations of the existing system.
37 Likes
Sorry for bumping this old thread, but is this still the case?
I’m making a chunk terrain system using triangles. I will be using PartCache so that I can reuse triangles from an old chunk, but I will still need to resize the parts. How costly to the performance is resizing a lot of parts at once?
14 Likes
Has this been implemented?
I’m getting Frame rate drops when Cloning 50 Parts at once which is concerning because I don’t think it should be doing that
8 Likes
Has this ever been implemented so far?
3 Likes
ofc Blitting and object is way faster than Instantiating it anew
We are all still wondering out here.