In previous releases, when there are timecome tags on the track that a user wants to specify a location on, the timecode displayed in the GUI is based on the timecode tags, but the location that the TransportJumpCommand uses does not take the timecode tags into account. When making a TransportJumpCommand in the TransportControl module, the location value has the option of being set with ‘CUE ’ or timecode. DSOF-22271 TransportJumpCommand locations should use time adjusted by timecode tag when using timecode location.Please contact for feedback on this feature. To access, right click on a project folder in d3manager, select ‘Advanced project settings’ and then select ‘enableFbxMeshImport’. Object hierarchies found within the FBX file in Designer are currently not supportedįBX file format support can be used with the option switch enabled.It is important to note the following mitigations with this feature: FBX files imported with up to 3x UV maps are supported. Any FBX mesh will be imported with global positions, and non-triangulated meshes are triangulated on import. These can be used in the schematic, lux and heatmap renderers. The FBX file format can now be successfully imported into Designer as a single mesh, meaning that users can now export models without the need for conversion from their respective 3D tool of choice. New: The r21 release notes now include detailed feature overviews.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |