This is a reference node, meant to be assigned a model asset through configuration. This will ensure that they will render at the correct scale with the other vrscene components under the Vray Axis System listed above. Any other models that were imported either through a vrscene Model upload, or FBX uploads can be drag-and-dropped here. It is meant to be used with referenced assets from the Asset Library. This node contains a scale that will get applied to any children added under this node. As shown on the Properties panel of the scene node, this camera is also automatically set as the active camera for this scene asset. This camera contains the same transform and focal length as the render camera in the vrscene, along with the Vray Physical Camera properties if those exist. Under this node you will find the various models and lights that were detected in the vrscene file. If custom nodes were detected with the TK_ prefix in their name, they will also be displayed on this node for configuration. If it contains lights, then it will also showcase an operator for setting up the light-linking. This is the vrscene node that contains all the information about the objects, materials, and lights in the uploaded vrscene. It is required to ensure the Vray components will render in the correct spot with the correct orientation and scale. This is a transform node that accounts for the differences between the transforms of assets in the different 3D applications. On the left side, in the Nodes section, you will find the following hierarchy of nodes created automatically by the import process: Here is an example of the basic output contents of a scene generated through this import process: The import process will extract the mesh, material, textures, and render settings data into a vrscene node inside the scene asset, while the camera information will be extracted separately into a ThreeKit camera node. In the case where the user uploads a vrscenezip that contains multiple vrscene files, it will create a single Scene asset, with multiple vrscene nodes inside that asset, for each vrscene file included in the zip. The option to import the vrscene assets as Scenes will automatically create a scene asset for each vrscene or vrscenezip added. Here, the user can choose what the originating 3D tool was, along with a choice between importing the asset as a Scene, Model, or Material extraction, as shown in the screenshot below: When dragging and dropping the vrscene/vrscenezip files onto the Asset Library on ThreeKit, the user will be presented with the import dialog box. There are, however, a few things to keep in mind about re-uploading/updating these assets, to ensure a trouble-free experience. It is essentially very similar to the import process for any other type of assets. The import process is probably the simplest and most straightforward step in the workflow.
0 kommentar(er)
