Yes, real-time CSG limit also got increased to 5k.
It mostly is a combination of us wanting to move somewhat conservatively and CSG rendering assets not being as optimal as mesh rendering assets in terms of data storage (doesn’t affect rendering performance, but may slightly affect the asset download bandwidth). We need to consolidate these at which point we’d remove the difference.
We haven’t implemented mesh LOD yet - it’s on our roadmap for next year. We decided to reevaluate the limits because:
- Developers want to push for higher detail content, and in many cases they are working around the limit by splitting the meshes into separate pieces - which doesn’t help performance anyway
- With instancing available on most devices, the extra memory/performance cost of larger meshes is less significant
Having said that - echoing the comment from @Aotrou, don’t make all your meshes 10k just because you can now Triangle count is still important for performance. When automatic mesh LOD ships it’ll be easier of course.
That’s a lot of triangles! Out of curiosity, what is the purpose of having limits? Is it just for reducing file size for the sake of loading them into the game?
I had mean’t the ‘upcoming’ LOD, but yeah, great update either way. However, will this have any affect on the collision fidelity? Will the collision be any more accurate to the actual mesh, or will that be a separate issue and potential update?
Just my unofficial opinion, I would think having limits serves as a guideline for what is reasonable for the engine. Although there are always ways to get around this such as splitting mesh parts, I would think the limit is saying ‘This is what you should keep the count under, when using a reasonable amount of mesh parts’
Because without a limit, a new developer might upload a 200k poly, and then wonder why the bandwidth is dead for their game.
Also, the mesh parts have the uploaded to Roblox initially and then downloaded per client when playing, so the limits help keep that from being overwhelmed.
Does this apply to V1 as well as V2 CSG?
That’s a separate issue - collision geometry is computed based on a simplified mesh representation. We have a long term plan of improving the fidelity & performance of collision geometry for CSGs & MeshPars but nothing this year I’m afraid.
That’s… an interesting question. I’m not quite sure, I’ll have to look into that.
No - V1 should still use the old limit for V1 which is 2500 triangles. V1 is deprecated and you shouldn’t really be using it - we plan to remove it next year.
A lot of users still use V1 instead of V2 as it has better smoothing; any news on that front?
Thanks - this helps. We’ll need to look into what it would take to support this in v2 and how to best do it.
I feel like at that point you should probably just be using blender
Blender can be a far more intimidating tool. Many engines include mesh capabilities out of the box.
Blender is just very complicated to get started with, and even though I’ve already started on blender, I still prefer modelling in Roblox.
NEVAR! We refuse
10K triangles? That’s awesome! This will make working with meshes so much better.
Closed to prevent bump posts