This tutorial will present the basics of using an ArrayMesh
To do so, we will use the function add_surface_from_arrays(), which takes up to four parameters. The first two are required, while the second two are optional.
The first is the
PrimitiveType, this is an OpenGL concept that instructs the GPU
how to arrange the primitive based on the vertices given whether it is triangles,
lines, points, etc. A complete list can be found under the Mesh
class reference page.
The second is the actual Array that stores the mesh information. The array is a normal Godot array that
is constructed with empty brackets
. It stores a
Pool**Array (e.g. PoolVector3Array,
PoolIntArray, etc.) for each type of information.
ARRAY_VERTEX= 0 | PoolVector3Array or PoolVector2Array
ARRAY_NORMAL= 1 | PoolVector3Array
ARRAY_TANGENT= 2 | PoolRealArray of groups of 4 floats. first 3 floats determine the tangent, and the last the binormal direction as -1 or 1.
ARRAY_COLOR= 3 | PoolColorArray
ARRAY_TEX_UV= 4 | PoolVector2Array or PoolVector3Array
ARRAY_TEX_UV2= 5 | PoolVector2Array or PoolVector3Array
ARRAY_BONES= 6 | PoolRealArray of groups of 4 floats or PoolIntArray of groups of 4 ints
ARRAY_WEIGHTS= 7 | PoolRealArray of groups of 4 floats
ARRAY_INDEX= 8 | PoolIntArray
The Array of vertices is always required. All the others are optional and will only be used if included.
Each array needs to have the same number of elements as the vertex array except for the index array. For arrays like tangents, an element is a group of 4 floats. So the array size will be four times the size of the vertex array size, but they will have the same number of elements
The index array is unique.
The third parameter is an array of blendshapes for the Mesh to use. While this tutorial does not cover using blendshapes, it is possible to specify them when creating a surface from arrays.
The last parameter is the compress flags which specifies which arrays to store with half as many bits. The values can be found in the classref for VisualServer under ArrayFormat.
For normal usage you will find it is best to leave the last two parameters empty.
Add an ArrayMesh to a MeshInstance. Normally, adding an ArrayMesh in the editor is not useful, but in this case it allows as to access the ArrayMesh from code without creating one.
Next, add a script to the MeshInstance.
_ready(), create a new Array.
This will be the array that we keep our surface information in, it will hold
all the arrays of data that the surface needs. Godot will expect it to be of
Mesh.ARRAY_MAX, so resize it accordingly.
Next create the arrays for each data type you will use.
Once you have filled your data arrays with your geometry you can create a mesh
by adding each array to
surface_array and then committing to the mesh.
In this example, we used
Mesh.PRIMITIVE_TRIANGLES, but you can use any primitive type
available from mesh.
Put together the full code looks like:
The code that goes in the middle can be whatever you want. Below we will present some example code that could go in the middle.
Here is sample code for generating a sphere. Although the code is presented in GDScript, there is nothing Godot specific about the approach to generating it. This implementation has nothing in particular to do with ArrayMeshes and is just a generic approach to generating a sphere. If you are having trouble understanding it or want to learn more about procedural geometry in general, you can use any tutorial that you find online.
Combined with the code above, this code will generate a sphere.
When it comes to generating geometry with the ArrayMesh you need to understand what goes in each array and then you can follow tutorials for any language/engine and convert it into Godot.
Finally, Godot provides a single method to save ArrayMeshes using the ResourceSaver class. This is useful when you want to generate a mesh and then use it later without having to re-generate.