Returns true if the Mesh is read/write enabled, or false if it is not.
When a Mesh is read/write enabled, Unity uploads the Mesh data to GPU-addressable memory, but also keeps it in CPU-addressable memory. When a Mesh is not read/write enabled, Unity uploads the Mesh data to GPU-addressable memory, and then removes it from CPU-addressable memory.
You can set this value using the Read/Write Enabled checkbox when importing a model to Unity. To set the value to false at run time, set the markNoLongerReadable argument of Mesh.UploadMeshData.
In most cases, you should disable this option to save runtime memory usage. You should only enable it under the following circumstances:
- When you read from or write to the Mesh data in your code.
- When you pass the Mesh to StaticBatchingUtility.Combine() to combine the Mesh at run time.
- When you use the Mesh to bake a NavMesh using the NavMesh building components at run time.
- When you use the Mesh with a Mesh Collider, and the Mesh Collider's transform has negative scaling (for example, (–1, 1, 1)).
- When you use the Mesh with a Mesh Collider, and the Mesh Collider's transform is skewed or sheared (for example, when a rotated Transform has a scaled parent Transform).
- When you use the Mesh with a Mesh Collider, and the Mesh Collider's Cooking Options flags are set to any value other than the default.
Notes:
When Unity creates a Mesh from script, this value is initially set to true.
Meshes not marked readable will throw an error on accessing any data arrays from script at runtime.
Access is always allowed in the Unity Editor outside of the game and rendering loop, regardless of this setting.
See Also: StaticBatchingUtility.Combine.
#pragma strict
function Start() {
var mesh: Mesh = GetComponent.<MeshFilter>().sharedMesh;
print(mesh.isReadable);
}
using UnityEngine; using System.Collections;
public class ExampleClass : MonoBehaviour { void Start() { Mesh mesh = GetComponent<MeshFilter>().sharedMesh; print(mesh.isReadable); } }