Render definitions
Connect model and dataset features to application renderers.
A render definition connects a feature to an SDK renderer. It contains an identifier and the geometry types that renderer is expected to support. It does not contain a material, prefab, shader, or renderer implementation.
Both 3D models and datasets require render definitions and matching renderers.
Definition and renderer
| Content | Example definition | Geometry | Renderer responsibility |
|---|---|---|---|
| Placed GLB | model | Point | Load the asset and apply placement |
| Places dataset | places | Point | Instantiate and style point visuals |
| Routes dataset | routes | LineString | Construct visuals along each line |
| Areas dataset | areas | Polygon | Construct visuals for each polygon |
A Point alone does not tell the SDK whether it represents a model or a dataset
marker. The definition identifies which renderer receives it.
Create and assign a definition
- Open the project's Render definitions page, or create a definition while configuring a dataset layer's mapping.
- Enter an identifier and select the geometry types it supports.
- Assign the definition to the appropriate geometry type in the layer.
- Register a renderer with the same identifier in your SDK application.
Identifiers are unique within a project and contain letters, digits, underscores,
or hyphens. Matching is case-sensitive: places and Places are different names.
In Lens Studio, the renderer exposes definitionName. In Unity, it exposes
DefinitionName. Both renderers also declare their accepted geometry types.
Geometry support
The platform accepts six geometry types: Point, MultiPoint, LineString,
MultiLineString, Polygon, and MultiPolygon.
Declaring a type in the platform does not implement it in an SDK. Check the
renderer implementation before selecting multiple types. In particular, a
renderer for LineString does not automatically support MultiLineString.
The SDK managers check that a renderer exists for every definition in the manifest. An unused definition can therefore still cause a missing-renderer error. Keep your project's definitions aligned with the renderers available in the application.
Changing mappings
Changing a dataset layer's mapping rebuilds its generated data. Existing running SDK instances do not automatically receive that change. Once conversion is ready, restart the Lens or refresh the Unity manager to load the updated project.
Do not delete a definition while layers still refer to it. Update the layer mappings first.
Implement a renderer
- Lens Studio SDK — documentation coming soon.
- Unity SDK — documentation coming soon.