for a procedurally generated / modified mesh, when should Mesh.Optimize() be called? Before or after RecalculateBounds() and RecalculateNormals() etc?
Mar 15 '11 at 06:59 AM
Aug 06 '11 at 01:53 AM
Hmm, I guess it doesn't really matter but just to put them in some kind of logical order i would say: before. Never really used Mesh.Optimize() i create only very simple meshes procedurally. Maybe someone have more information on that.
Optimize() will recalculate the bounds for you, so there is no need to call RecalculateBounds() after doing an optimize.
Mar 15 '11 at 01:08 PM
jonas echterhoff ♦♦
why you should not include something like this in the main documentation. please let the online documentation show questions/answers related to each API in it's documentation page. unity's documentation should be much more detailed. however it's one of the best in middleware market of gameengines
it would be nice to have a http://php.net style documentation for unity
What about recalculatenormals?
Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.
Once you sign in you will be able to subscribe for any updates here
Answers and Comments
The best place to ask and answer questions about development with Unity. Check out our FAQ for more information.
To help users post good questions and use the site effectively we have posted a tutorial video. Please check it out.
asked: Mar 15 '11 at 06:59 AM
Seen: 1290 times
Last Updated: Mar 16 '11 at 02:17 AM
Bounds of dynamic mesh not updating
creating a mesh procedurally
Modifying Sub-Meshes at Runtime & MeshRenderer
"Carving" a Mesh
How to split a mesh?
How to assign procedural mesh to a collider
How to create a procedural mesh with multiple materials?
Determine whether or not model is "inside out"
Trouble recalculating 3D mesh's triangles after deleting verts
Memory problems with procedurally generated meshes