02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

HeightmapImportSettings

class

Editor/Vixen.Editor.Assets/Terrain/HeightmapImporter.cs:19

csharp

public record class HeightmapImportSettings

How a raw heightmap is read.

Read the guide page for this →

Remarks

⚠ Not empty, unlike the other importers here, because a raw file carries no header. A .r16 is width × height × two bytes and nothing else — there is no dimension, no endianness and no scale in the file, so every one of them has to be a setting. That is what makes it a raw format and it is why World Machine asks the same three questions on export.

Fields and properties (4)

public int Version
The importer's own version. Bumping it invalidates every artefact that importer produced.
public int Width
How many samples the file is, on a side.
public int Height
And on the other side.
public bool BigEndian
Whether the samples are big-endian.

Used by (3)

HeightmapImporterVixen.Editor.Assets
TerrainAssetImporterTestsVixen.Editor.Assets.Tests
TypeRegistrationVixen.Editor.Assets