Once you upload a new model version with the same name and it is recognized by the cloud as a newer version, you are no longer able to delete the different versions.   Since I have been experimenting with updating the model and keeping the Assets linked to the different elements we are getting to a point where a specific project has 20 almost identical versions of the same model.   The workaround in order to go back to the original version is to download the first source file and upload it as the newest. That in turn creates an unnecessary duplication of files and added storage.      Show More

Description: When publishing a Revit Cloud model, 3D and 2D views are generated for the Forma Viewer, along with a Revit file that can be downloaded via Forma Data Management. Currently, the selected publishing settings are not reflected in the exported Revit file. Expected Behavior: Publishing settings should be directly applied to the generated Revit file: Publish without links → exported Revit file contains no link paths Publish selected views only → exported Revit file contains only those views Additional feature: Ability to automatically remove unused properties (parameters) to further clean and reduce the file Current Behavior / Issue: Exported Revit files still contain links (including missing link warnings when opening the file) Unnecessary working views remain in the model No simple way to automatically clean up data Cleanup must currently be done manually, which is especially cumbersome with Cloud models: Creating an editable copy of a Revit Cloud model is not possible in Forma The file must be downloaded and cleaned locally instead Additionally, processes must ensure that this locally cleaned version is not uploaded back into Forma, as it would no longer be linkable as a Cloud model (external resource) Business Impact: We regularly need to deliver cleaned Revit files to our client throughout the project lifecycle. “Cleaned” means: No missing links No internal working views Reduced and well-structured properties At present, this process is time-consuming, error-prone, and difficult to manage. Benefits of Implementation: Significantly more efficient delivery workflows Reduced manual post-processing effort Improved data quality and consistency Elimination of workflow breaks between cloud and local environments Better usability of Revit Cloud models in deliverable scenarios Show More

Details: Currently, when NWD models are published and processed in Autodesk Forma (Model Coordination Module), the Object Colors feature cannot be applied using properties that belong to parent (composite) objects. According to Autodesk Support and Engineering, NWD files are translated as composite objects, and the current Object Colors functionality only recognizes properties available at the individual element level. As a result, users cannot color-code model objects using metadata stored in parent objects, which significantly limits model visualization and analysis workflows. Proposed Enhancement: Enable the Object Colors feature to access and use properties from parent/composite objects when working with NWD models. This would allow users to create color schemes based on attributes inherited from the composite structure, similarly to how the information is organized in Navisworks. Business Impact: Improve visualization and model analysis for NWD-based workflows. Support construction planning, commissioning, progress tracking, and system-based reviews. Preserve valuable metadata already available in Navisworks models without requiring model restructuring. Reduce manual workarounds and model reprocessing efforts. Increase adoption of Autodesk Forma for organizations that rely heavily on Navisworks NWD deliverables.   Show More

It would be a very useful feature to be able to manage transparency of certain files/objects in the federated view to highlight the design models. More control in general how models and hidden object ++ is shown in the viewer. Also nice if it was possible to save viewpoints exactly as shown in the viewer for most files with the settings for the hidden object and so on.  The saved viewpoints will be better in this way. Show More

There used to be an option in the Display settings to turn off section hatch patterns and this has now gone, it makes it difficult when reviewing clashes / interferences in detailed areas where the surface hatch pattern covers everything.  Show More

Requesting Autodesk to enhance the search function in the Model Browser to allow all property and item fields to be searchable in the 3D Model Viewer. Currently, you can only search for objects in the Forma Web version. The ability to search for all properties when selecting commodities in the model is essential for construction automation workflows.  Show More

Requesting that Autodesk implements certain features from the web version of Forma into the Forma Mobile App. In the web version of Forma, you can change the frame rate from 30 to 60 fps. The web version also lets you expand the properties menu so that you can see all of the property values clearly. You can change the background color within the 3D model viewer to a different color. Can Autodesk look into integrating all three of these features into the Forma Mobile App?  Show More

Requesting that Autodesk incorporates a search function inside of the 3D Model Viewer in the Autodesk Forma mobile app. We would also need the ability to highlight a property and copy and paste the property value into the search field. The option to search, and highlight / copy and paste is available in the web version but is not accessible in the mobile app version of Autodesk Forma. Additionally, all objects, items, and properties in the model should be searchable. Show More

I feel like I run into this all the time in construction: getting DWG files from Revit models. Currently, you either have to coordinate this setup on the front end with your AOR/EOR so they export DWGs from the RVT, or you have to physically open the RVT file in Revit and export the DWGs manually. It would be amazing if Forma could acquire, export, or push DWG files directly. I could see this working in two possible ways: Export DWG files from PDFs. Export DWG files from 2D and 3D sheets/views within the Forma file. Whether this is added as a checkbox in the export settings or introduced as a new DWG export option, I think it would be a very useful feature for construction teams. Show More

DWG 3D solids & TIN surface tranparency display settings does not carrying through to Forma.  This is a major limitation for using Civil tools, DWG based Assets and the Forma Data Management Model viewer.   Show More

I would like to change the default 3D-view when viewing a Revit model in Forma. Normally the first 3D-view is the default 3D-view (In my project this is not the case) but i want to chose a specific view whitout renaming. Show More

We create “empty” coordination models in Revit (all discipline models are linked) and do not use the Model Coordination module, as we work with different levels than those used in the individual discipline models. Additionally, these coordination models include 2D floor plans, which we also use in the Forma Viewer to display within the 3D model. To make effective use of automated publishing via Design Collaboration, this “empty” coordination model must contain a change in order to actually be published at the scheduled time. This change currently has to be made manually every time (open the Revit model, synchronize, close the model). We would like to have a setting that allows the model to be published automatically whenever there are changes in the linked cloud models. This would save us a significant amount of time in organization and daily work. Show More

I would like there to be an option to keep the folder structure intact while sharing models and drawings using design collaboration. For example if my project is composed of many areas and each team is working with a subfolder for each areas it would be much better to preserve that structure instead of the actual system where all models of a single team get put in a single folder all together. As an example if I have a working structure such as  Team 1/ Area1/ Models/ Drawings/ Area2/ Models/ Drawings/ Area3/... I would like to see this structure in both the shared folder and in the consumed folder for each team. I also think that giving this option would help in other cases where there is a need to keep a logical structure to the data. Show More

So, because revit only manages 1 oficial location per model (even though it can save several and we can load them and see diferent options in each) we sometimes have to export of the "complete" model combination from a view in Revit to NWC to be able to properlly compare the project, As single model compare is insuficient because of this. After all, a model may not be changed, but if it is relocated in the main file, that is a very important change that we need to be aware of that. Now, you may say that if the models are real Cloud models and are published with links then we can have that prepared view and use it for compare, but the problem is that for the other teams to link the project using Bridge and Desktop Connector all files with nested attached models needs to be published without links for this to work. (PS: This is another even bigger wish - stop the export with or without links option and have both at the same time!)   So that option is not possible and we have to go back to the NWC export alternative... After we do that we need to convert the NWC to NWD (why?? We also should be able to directly compare NWC files without having to waste time opening Navisworks and resaving). The problem is, even though the files and links are always the same (they are just getting updates) and directly model compare of the original RVTs are ok, we are seeing that in NWD compares the GUID of the elements get's so confused that we get a lot of new and deleted element that are not really deleted or new, and the ones that changed can be changed from a window in one building to a window in another (when we know for a fact that that is impossible - because they are different links). So the conclusion is that the NWD compare is so unreliable that is mostly useless. I should have made the test to export the same NWC twice and see if he stills flags anything as changed, but wherever this issue is being introduced, it's needs to be addressed and solved, one way of the other (the other being the publish without links issue). Because right now, we are unable to do a proper compare in these cenarious - and the Compare is FUNDAMENTAL for everyone's work.     Show More

So as you can see in the image below of a Compare in ACC/Forma of an rvt model, the red color for the removed elements are pretty wild... We have red, orange, purple, so many times I have to isolate them like in the image to make sure what I think is red is really "red" and not Yellow, than can also be random, varying from orange too to light green...  It's possible that object collours (from systems) may be interfering with the compare colors, and that could be desirable in some cases, but without real control this seems like a bug that is counter productive. It could be nice if a transparent slider could be provided to allow us to have the best of both worlds per user taste in that moment.     Show More

Would it be possible to allow users on the Forma app to adjust the precision settings of measurements and properties to be able to see 2 or 3 decimal points when viewing a model? This setting is already available on the web version, but it is not available to the foreman who are viewing the model from an app out in the field. Show More

Product Area Preconstruction → Takeoff → Sheets & Models   Problem / Current Behavior In the Preconstruction Takeoff Sheets & Models viewer, the search function only scans the currently active sheet/page. Sheets are treated as individual pages, even when they originate from a multi-page plan set. This behavior differs from the Files tool viewer, where: Multi-page files are searched across all sheets Results can be returned from any page in the document set As confirmed by Autodesk Support, this limitation is tied to how the Takeoff viewer currently treats sheets as single-page entities rather than part of a plan set.   Why This Is a Problem For estimators and preconstruction teams: Users expect plan searches (e.g., “Wall”, “Footing”, “Detail”) to return results across the entire drawing set, not just the current sheet. Having to manually open and search each individual sheet creates friction and breaks estimation workflows. This discrepancy between Files and Takeoff search behavior causes confusion and training challenges. One of our general contractor customers specifically raised this as a significant workflow issue during a live call.   Requested Enhancement Introduce an option to: Search across all sheets in the Takeoff set, not just the active page OR Provide a toggle similar to the Files viewer (e.g., “Search current sheet” vs “Search all sheets”) This would align Takeoff search behavior with user expectations and with existing functionality already available in the Files tool.   Business Impact Faster takeoff workflows Reduced estimator frustration Improved consistency across ACC modules Stronger adoption for firms transitioning from Files-based workflows into Preconstruction Takeoff Show More

It would be nice to see the pins in all view types when working within revit. I will create exhibits from floor plans or sections because the additional need for detailing easier to convey a problem or a solution and having the pins visible in all view types would be beneficial.  Show More

When a new model gets uploaded to ACC it can take over 30 minutes before it can be added to the Model Coördinator in ACC. This is a stupid amount of time if I can upload and view the individual model in less then 30 seconds! Show More