There are a variety of formats that the Forge viewer supports. The Model Derivative API enables translation of more than 60 different types of source file formats. Yet, there is one format ubiquitous in the architecture, engineering, and construction (AEC) industry that does not find its place in the list—RFA. There could be various ways to visualize RFA files in the viewer; the most common is: conversion to a format that's supported by Forge, though it's not the fastest or most effective. In this class, we'll look at a workflow that can help developers optimize up to 90% of their Forge credits usage. Accomplishing this requires building a headless Revit plug-in using the Revit API, preparing it for the Design Automation API, processing the outputs using the Model Derivative API, and finally rendering individual Revit families in the viewer. We'll also look at how we can give end users the ability to switch between multiple family types, as well as access the Instance and Type parameters directly in the Forge Viewer.
- Discover the different formats the Forge Viewer supports, and why the RFA format is a limitation and currently is not supported.
- Learn how to design a workflow for visualizing Revit families and their family types and accessing parameters in the Forge Viewer.
- Learn how to render hundreds of Revit families in the Forge Viewer and optimize for loading time and Forge credits usage.
- Learn how to create headless Revit plug-ins to enable a cloud-connected workflow using the Design Automation for Revit API.