LogoLogo
ThreeKitDeveloper HubForumsSupportStatus
  • Guides
  • Documentation
  • Releases
  • Platform Documentation
  • Project Data
    • Platform Landing Page
    • Basic Concepts
      • Environments
      • Organizations
      • Attributes
        • Arrays
      • Tagging
      • Naming Conventions
      • Players
      • Branching
      • Alerts and Warnings
      • Supported Browsers
      • ThreeKit Platform Architecture
    • Catalog
      • Items
        • Item Bulk Edit
        • Item Variants
      • Data Tables
      • Item Rules and Logic
      • Publishing
    • Assets
      • Asset Management
        • Importing Assets
        • Exporting Assets
        • Folders
      • Asset Editor
        • Editor Layout Modes
          • Layout Editor
            • Local vs Global Transform
          • Logic Editor
      • Nodes
        • Common Properties
          • Node Tags
        • Helpers
          • Nulls
          • Model References
          • Connectors
        • Lights
          • Point Light
          • Directional Light
          • Spot Light
          • Area Light
          • Hemisphere Light
          • Shadow Plane
        • Cameras
        • Shapes
        • Annotations
        • Layout Containers
      • Scenes
      • Materials
        • Physical Material
        • Proxy Materials
        • Multi Material
        • Gem Material
        • JSON Configuration
      • Textures
      • Canvases
      • Composites
    • Operators
      • PolyMesh Operators
        • Array
        • Bend Deformer
        • Map Override
        • Stretch
        • Physics (Collision Detection)
      • Material Operators
        • Falloff
        • Tiling Override
        • Triplanar Mapping
        • Template Override
      • Image Operators
        • Canvas Composite
        • Canvas Fill
        • Canvas Linear Gradient
        • Canvas Text
        • BlackWhite
        • Posterization
      • PostEffects Operators
        • Bloom Pass
      • Comp Layer Operators
        • Vray Normals Properties
        • Vray Bump Normals Properties
    • Stages
      • Stage Effects
        • Turntable
    • Logic
      • Conditions
      • Actions
      • Queries
        • Node Queries
        • Metadata Value Query
        • Asset Query
        • Datatable Query
      • Custom Scripts
    • Virtual Photographer
      • Create Renders
      • View Renders
      • V-Ray Integration
    • Augmented Reality
      • AR Settings
  • Org Setup
    • Admin & Security
      • Org Profile
      • Users & Permissions
        • Threekit Sign-in
        • Members
        • User Profile
      • Tokens
      • Service Accounts
      • ISO Certification
      • Org Migration / Data Transfer
    • Jobs System
    • Orders
      • Orders List
      • Configurations
    • Analytics
      • Advanced Buyer Analytics Reports
      • Player Views
    • Project Settings
      • Features
      • Languages
Powered by GitBook
On this page
  • Description
  • Usage

Was this helpful?

Edit on GitHub
  1. Project Data
  2. Assets
  3. Nodes
  4. Helpers

Model References

Model nodes allow us to reference other model assets inside a Scene or Model Asset for a nesting setup.

PreviousNullsNextConnectors

Last updated 1 year ago

Was this helpful?

Description

This node is the workhorse of scene setups, setups, and modular configurations where the final product is built from components that exist as separate model assets. A Model node is simply a reference to a model asset.

The modular approach allows us to reuse model assets across multiple products, or within . This means that we can upload separate files for each product or components, and reuse them within different configuration setups.

For example, let's say we need to build a sectional configurator, and we need seat, arm, chaise, and pillow components. Uploading a separate file for each one of these individually as a model asset allows us to reuse these components to build the more complex sectional setup.

The advantage with this approach is that only one asset needs to be downloaded for all seat components, one asset for all arm components, and one asset for all pillow components. This means a faster initial load time, and also ease of maintenance. If updates are necessary for the mesh of the seat component, then only the seat model asset needs to be updated.

Usage

The model node can only be used inside Scenes or Model assets, and can only reference model assets.

The model node can only be used inside Scenes or Model assets, and can only reference model assets.

It can be created in one of two ways:

Through the Helpers button in the main toolbar:

Through the right-click menu in the Scene Graph, when you right-click on an existing node:

The Asset property of the Model node will hold the referenced asset.

This property can be set through logic using the action, or the action.

In a modular configuration setup such as the sectional example, these Model nodes can be created through a script using the function from the , and placed at specific locations in the 3D space.

Add Node
Scene API
set model
set property
Modular Components in a Sectional
Modular Sectional
Create a Model Reference Node
Create a Model Reference Node through the Right-Click Menu
Set Model Action with the Model node
template asset
template assets