The Revit Reader provides access to visualization data stored within a particular Revit file. A file does not need to have a particular extension to be read correctly by HOOPS Exchange however the file extension of Revit files that you can expect to be loaded by HOOPS Exchange is:
Our readers are updated to the latest released version within 90 days of the release of the authoring software. You can see the exact version supported in the current release here.
RFA files (i.e., Revit families such as Doors and Windows) are supported. They are instantiated through Exchange’s prototype mechanism.
HOOPS Exchange currently does not support B-rep.
The triangle information is parsed and provided via HOOPS Exchange.
Revit views are supported.
However, Exchange does not support all the features available in Revit.
HOOPS Exchange currently does not support Markup.
Textures and Materials
HOOPS Exchange supports textures with Revit. Also, colors on wires, faces, tessellation and Brep are supported.
Generally, Revit files reference textures which are part of a Revit installation.
This installation path is automatically added by Exchange _only_ if at least one custom path is provided into the texture search directories attribute of the read parameters (
This means that if you want HOOPS textures from the default installation path, you must add at least on value to
m_ppcSearchTextureDirectories, even an invalid path such as en empty string.
HOOPS Exchange reads Revit metadata (properties) with their units.
Revit is only available on 64-bit Windows and 64-bit Linux.
In Exchange, geometry is always represented as solid. In Revit, geometry may have different representations (e.g., pipes can be wireframe or solid), and this setting can be changed in Views. Exchange does not support this concept.
Files with imported DWG parts are supported, but the visibility by default and per view will always be set to visible, even if visibility is set to another value in the original file.