In such a situation, the connector cannot detect that the other arrays are uniform over timesteps, and will therefore generate a duplicate copy of data for every array at every timestep to be sent to Omniverse. This is useful in a case where for example only the texcoord array changes from one timestep to another, and all other arrays stay the same. Enabling a checkbox in front of an array makes it time-varying, otherwise it is considered uniform. obtain a separate copy of their data in USD or Omniverse at every single time step - and which arrays are uniform and therefore only have one copy of their data, applying to all timesteps. The Temporal Arrays filter defines which specific field arrays are time-varying - ie. “Omniverse Connector Temporal Arrays” Filter For surface geometry these arrays end up in the corresponding USD as primvars, but for volumes they are converted to grids in OpenVDB. Using the Pass Arrays filter permits you to extend that with any per-point or per-cell field array residing in your dataset. By default the Connector only sends render data arrays to Omniverse as explained before. This filter functions exactly as the normal Pass Arrays filter found in ParaView, but instead specifies exactly which field arrays of a dataset are transferred to Omniverse. This allows users to allow additional field arrays to be included within the output of the rendered models, or manually specify which arrays are time-varying for animated datasets. The Omniverse Connector render view is required for the two filters mentioned below. This render data will be collected for each timestep viewed by the user and stored in the USD, alongside the data of previously viewed timesteps - unless the actor’s data does not change over time. Specifically, for all visible ParaView actors in the view’s pipeline, their render data arrays (such as point, normal, texcoord and vertexcolor) or rendered volume fields will be converted to USD, and optionally sent over to Omniverse. The Omniverse Connector render view works just like a normal render view, except that everything visible within this render view is sent over to an NVIDIA Omniverse™ Nucleus server, or a local USD file. They consist of a custom Omniverse Connector render view, two filters, plus a toolbar in the View > Toolbars menu option which is enabled by default: A condensed list of Features is also available.īelow you will find a short description of the components which NVIDIA Omniverse™ ParaView Connector Plugin adds to ParaView. See Install Instructions and the sections for a walk through in configuring and using the connector. Now, depending on the use case, ParaView users can choose the workflows and pipelines that work best for their needs while maintaining up to date revisions for all downstream consumers of their work. As a result, a user will be able to edit and sync their ParaView data with any OMNIVERSE® Connect applications, or just import it into applications supporting USD or OpenVDB. The NVIDIA Omniverse™ ParaView Connector offers a toolkit for ParaView users to send and live sync their model(s) to an NVIDIA Omniverse™ Nucleus Server, or alternatively locally output them to USD, along with OpenVDB in case of volumes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |