You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the WorldGenerationTest.unity scene, you're generating some huge mesh without setting Mesh.indexFormat to UInt32(the default value is UInt16), which causing meshes with vertex count > 65535 fail to render normally.
Unity doc here: https://docs.unity3d.com/ScriptReference/Mesh-indexFormat.html
However, using UInt32 indices format instead of UInt16 will probably drop performance and need more memory (for example, X-5 Z-3 ChunkSlice#4, which has 101920 verts and 221400 triangles, cost around 6.5MB for indices using UInt32 or around 1.5MB using UInt16). So a better solution might be split your huge meshes into sub-meshes(verts < 65535) and still using UInt16, if you have time, you can have a try about this :)
The text was updated successfully, but these errors were encountered:
that is something that i already did when i was bruteforcing the entire brick model rather than the shown faces xDD And then i never thought of it again xDDD
The thing is, i belive it throwed me an error back then. Why isn't it doing the same in those cases?
PR: #2
In the
WorldGenerationTest.unity
scene, you're generating some huge mesh without settingMesh.indexFormat
toUInt32
(the default value is UInt16), which causing meshes with vertex count > 65535 fail to render normally.Unity doc here: https://docs.unity3d.com/ScriptReference/Mesh-indexFormat.html
However, using UInt32 indices format instead of UInt16 will probably drop performance and need more memory (for example, X-5 Z-3 ChunkSlice#4, which has 101920 verts and 221400 triangles, cost around 6.5MB for indices using UInt32 or around 1.5MB using UInt16). So a better solution might be split your huge meshes into sub-meshes(verts < 65535) and still using UInt16, if you have time, you can have a try about this :)
The text was updated successfully, but these errors were encountered: