We use parameter-driven 3D text within Revit families to communicate important model information to our field teams. The displayed 3D text is associated with instance parameter values and displays correctly in the source Revit model.
When these models are processed and viewed in Autodesk Forma for Construction, we have encountered cases where the 3D text displayed on an element does not match the parameter value or text displayed in the source Revit model.
Autodesk Support has confirmed through Case 02310075 that the current NWC processing workflow does not fully support the nested parameter data hierarchy involved in this workflow and that the behavior has been shared with the product team.
The primary concern is data integrity rather than simply missing parameter information.
If a property is unavailable in the viewer, a user can recognize that the information is missing. However, if parameter-driven 3D text is displayed but contains an incorrect value, a field user may reasonably assume that the displayed information is accurate.
We would like Forma's model processing/viewer to preserve the relationship between nested family instance parameters and parameter-driven 3D text so that the displayed geometry accurately represents the source Revit model.
At minimum, if this relationship cannot currently be preserved during processing, the viewer should avoid presenting incorrect parameter-driven information as though it were valid.
This would improve confidence in Forma as a reliable model reference for field workflows.
