The Complete Revit to Inventor Conversion Guide

This guide is part of the RapidPipeline 3D Formats Knowledge Database. It shows how to convert Revit to Inventor, if you'd like to know more about the formats, please check out the following links:

• Learn more about the Revit format
• Learn more about the Inventor format

There are various ways to convert between Revit and Inventor. With RapidPipeline, you can easily convert and and optimize Revit files, at scale. It supports Inventor, as well as many other file formats (examples: 3dsMax, AutoCAD, CATIA, Creo, FBX, glTF, Navisworks, OBJ, PLY, Solid Edge, SolidWorks, STEP, STL, USD, USDZ, VRM), at high quality.

Below you can find a video explaining how to convert your files:

The Revit file is a format mostly used for Building Information Modeling (BIM) software for architectural design, engineering, and construction documentation.
The Inventor file is a format mostly used for Professional 3D CAD software for mechanical design, simulation, visualization, and documentation.

The following limitations should be taken into account when converting Revit files to Inventor format:

Revit Feature (not supported by Inventor)	Limitation Details
Texturing	Texturing: supported in Revit, but not in Inventor. Texturing describes the process or refining the visual appearance of a 3D model's surface through additional 2D or 3D data, defined in a different reference system. The by far most common use of texturing are 2D texture images, applied to model visual material properties the 3D surface. Other cases include the use of procedural 2D or 3D funtions that produce intensity or color signals, which are then mapped to the 3D surface. For the vast majority of these cases (all of them except for 3D procedural functions), a parameterization or "Texture Mapping" is needed, which maps the 2D content to the 3D surface. Coming from a 2D coordinate space with coordinate axes often entitled U and V (in contrast to XYZ, which are the 3D surface positions), this process of mapping is also called UV Mapping, and it can be done with a dedicated UV map, or through a live mapping (e.g., box mapping). In this example, a texture image is applied to the 3D model to give the control panel a realistic look. Without support for texturing, the panel would have to use a single material instead, or all controls (including text) would need to be modeled through 3D geometry, instead of a 2D texture image.
Texture Transforms	Texture Transforms: supported in Revit, but not in Inventor. Texture transforms describe transformation operations that are applied to 2D texture images or UV coordinates when using 2D texture data on a 3D surface. They can be used, for example, to make sure that material patterns are using real-world scale when rendered on the 3D surface. In this example, such a pattern is used and scaled with the help of a texture transform. Without support for this feature, the texture pattern shows up at the wrong scale.
Procedural Textures	Procedural Textures: supported in Revit, but not in Inventor. Procedural texture allow the modeling of surface details through mathematical functions, along with artistic control over various parameters. Typically, they are used for patterns like wood grain or other semi-regular structures. Since they are not using any pixels as source data, procedural textures have, in principle, infinite resolution and are very lightweight to describe. In this example, a procedural texture is used to model the look of a wooden material. Without support for this feature, in this case, the wooden parts won't show any visible details.
Embedded Textures	Embedded Textures: supported in Revit, but not in Inventor. Embedded textures allow the storage and exchange of an entire 3D model and its materials within a single file, by embedding the texture images directly into the 3D file (and not storing them as separate image files). Without support for this feature, textures have to be stored in separate image files, and referenced from the main 3D model file.
Normal Mapping	Normal Mapping: supported in Revit, but not in Inventor. Normal maps are used to model shading differences that are arising from small geometric details on a surface, such as fabric structures, visible gaps between bricks forming a wall, or rough rock surfaces. In this example, a normal map is used to model a fabric structure. Without support for this feature, the rendered fabric will look smoother than it actually is in the real world, as the fabric structure won't be visible.
PBR Materials	PBR Materials: supported in Revit, but not in Inventor. PBR materials enable Physically-Based-Rendering (PBR) for a standardized, photorealistic look of rendered images. PBR uses concepts like metallic-roughness or specular-glossiness properties and a microfacet-based modeling of the surface, using a concept called BRDF (Bi-Directional Reflectance Distribution Function). In this example, PBR materials are used to achieve realistic looking plastic and metal materials. Without support for PBR materials, only basic colors and shading can be used (for example, based on more simple shading models, such as the Blinn/Phong model).

Doing 3D conversion right, especially at scale, can be tricky, as 3D data is in general a rather complex (yet very powerful!) medium. This also applies to Revit and Inventor files - the conversion guide above provides a rough first idea about that. Once you know what you would like to do, tools like RapidPipeline can help you perform the necessary steps, and to even automate the process for thousands or even millions of files.

Especially when introducing pipelines and workflows at scale in an enterprise context, it is usually good to rely on dedicated tools and expertise, making sure you do not introduce any steps into your 3D workflow that are detrimental to the final output's quality, or that take your team too much time (and money).

If you're interested to hire dedicated expertise from the best in the field to help your company reach your goals fast and reliably, please do not hestitate to contact DGG. Being the creators of RapidPipeline, and ambassadors for open 3D standards for more than a decade, we have been building some of the world's most advanced 3D pipelines, having processed many millions of 3D assets.

Therefore, our expertise will help you to reach your goals faster, at scale, and with the least possible friction, since we are focused on maximum interoperability.

To get started with 3D data conversion and optimization today, sign up for a free account!

If you have any questions, feel free to chat with our human team.