Il serait utile de pouvoir créer un groupe de pièces qui calcule automatiquement la surface totale à partir des pièces qui le composent. L'objectif serait de pouvoir étiqueter ce groupe directement sur les plans, à l'image du fonctionnement des zones CVC qui regroupent des espaces. La surface totale serait mise à jour automatiquement dès qu'une pièce est ajoutée, supprimée ou que sa surface évolue. Ce besoin est particulièrement présent dans les projets de logements, où il serait très utile de pouvoir afficher, avec une seule étiquette, le numéro du logement, son type (T2, T3, etc.) et sa surface totale, sans avoir recours à Areabook, à Dynamo ou d'autres extensions, qui alourdissent considérablement le workflow pour une fonctionnalité qui pourrait être gérée nativement dans Revit. Show More

When publishing sheets from Revit to Autodesk Forma (ACC), there is currently no option to control the visibility of view crop boundaries. While Revit provides this functionality when printing sheets, the same setting is not available during cloud publishing.  Our team uses visible crop boundaries on interior elevations to outline the extents of each view. See sample image not showing crop boundary in published sheets.   Providing a way to either inherit the Print dialog settings or offer similar options within the publishing settings would help ensure consistency between printed and published documentation.   Show More

The ability to Connect MEP Systems across Linked models, is perhaps the biggest MEP Systems limitation that has yet to be addressed. It's been almost 10 years, since this idea was posted. MEP Systems and Connections Across Linked Models - Autodesk Community Show More

Description: Currently, Revit provides native System Types for ducts and pipes, allowing users to assign systems such as Supply Air, Return Air, Chilled Water, Domestic Water, etc. Each system can have its own graphic overrides without relying on view filters. However, conduits do not have an equivalent Conduit System Type. Electrical BIM users must rely on view filters, shared parameters, or manual graphic overrides to distinguish different conduit services such as: Power Lighting Fire Alarm Data CCTV Access Control Public Address BMS ICT Security Systems For medium and large projects, maintaining numerous filters across multiple view templates is time-consuming and difficult to manage. Proposed Enhancement Introduce a native Conduit System Type similar to Duct and Piping Systems. Each Conduit System should support: User-defined system names Automatic graphic overrides Line color Line pattern Line weight Material assignment Automatic inheritance to conduit fittings and bends Scheduling by Conduit System API support for automation Expected Workflow Example: Power Conduit System → Automatically displays Red Fire Alarm Conduit System → Automatically displays Green Data Conduit System → Automatically displays Blue The user should only need to select the required Conduit System before modeling. Revit should automatically apply the corresponding graphics without requiring view filters or manual overrides. The graphics should work consistently in: Wireframe Hidden Line Shaded Consistent Colors Realistic Plans Sections Elevations 3D Views Benefits Eliminates the need for multiple view filters. Reduces project setup time. Improves model readability. Provides consistency with Duct and Pipe Systems. Simplifies BIM standards. Reduces coordination errors. Improves productivity for Electrical BIM teams. This enhancement would significantly improve electrical BIM workflows for airports, metro projects, hospitals, commercial buildings, industrial facilities, data centers, and other large infrastructure projects where multiple conduit services are modeled. Show More

for electrical circuiting, other than Power, there is a demand being able to have parameters defining the Load Name. This would make sense because the actual Loadname simply contains "Fire Alarm Spacename Spacenumber ".  Proposals: A: the assigned Connector Description, which can be even instance-driven (would probably need the assigned Instance-parameters also assigned as Project-parameter) B: Connector Description and Space Information   same for security devices and other non-Power connectors Show More

I would like to share a feature idea that I believe could significantly improve the design workflow within Revit by integrating AI-assisted building code guidance directly into the modeling environment. One of the more challenging aspects of architectural design is ensuring that a project remains compliant with the many applicable building codes and zoning regulations as the design evolves. While experienced architects develop a strong understanding of these requirements over time, designers still spend a considerable amount of effort researching code provisions, verifying compliance, and revisiting decisions when project parameters change. I was wondering whether Revit could eventually incorporate an AI-powered Code Compliance Assistant that would continuously analyze a building model throughout the design process and provide real-time guidance based on the project's applicable codes and regulations. At the beginning of a project, the user could define parameters such as: Project location Applicable building code edition (e.g., IBC, IRC, local amendments, or other national codes) Zoning regulations Occupancy classification Construction type Building height and number of stories Intended building use As the design develops, the assistant could automatically recognize changes that affect code requirements and notify the user of potential implications. For example, increasing the occupant load, changing the occupancy classification, adding additional stories, or modifying the building footprint could immediately trigger reminders about relevant code provisions before they become larger design issues. Rather than functioning solely as a final code-checking tool, the assistant could act as an intelligent design companion throughout the project. Potential capabilities might include: Continuously monitoring the model for code-related design changes. Identifying applicable code sections based on the current project conditions. Alerting users to potential issues involving egress, accessibility, occupancy, fire protection, building height and area limitations, travel distances, stair requirements, parking, setbacks, and other measurable design criteria. Explaining why a particular requirement applies and how recent design changes affected compliance. Suggesting possible design modifications to resolve potential conflicts while leaving all final decisions to the design professional. Recognizing that building codes vary significantly between jurisdictions, another useful capability could be allowing users to select from supported code libraries (such as the International Building Code and related model codes) while also providing the option to upload local building or zoning regulations. AI could then assist in interpreting those documents and incorporating applicable requirements into the project's ongoing design analysis. Beyond simply identifying violations, I believe one of the greatest benefits of such a system would be its educational value. By explaining the reasoning behind applicable code requirements as the model evolves, Revit could help architects, engineers, and students better understand how design decisions influence regulatory compliance. I understand that elements of automated code checking already exist within the BIM industry and that AI-assisted design tools are rapidly advancing. However, integrating these capabilities into Revit as a seamless, real-time, and context-aware design assistant could significantly reduce coordination time, minimize costly redesigns, and improve the overall design experience while supporting—not replacing—the professional judgment of architects and engineers. Show More

It would be beneficial to be able to combine several color schemes in the same view, as composites. Would be great for QC. Show More

Problem Revit 2027 removed the contextual Options Bar that appeared while creating Pipes, Ducts, Conduits and Cable Trays. In previous versions of Revit, the most frequently used creation parameters were available in one compact location directly below the Ribbon. This included values such as: Diameter / Width / Height Elevation Justification Level Offset Other tool-specific creation options This interface allowed MEP designers to modify these parameters instantly while modeling, without moving the cursor away from the drawing area. In Revit 2027, these settings have been split between the Ribbon and the Properties palette. Some options remain on the Ribbon (such as Offset), while others, including Diameter and Elevation, have been moved to the Properties palette. As a result, parameters that used to be available together are now scattered across different parts of the interface.   Impact For MEP designers, this is a significant workflow regression. When designing piping, ductwork, conduit or cable tray systems, sizes and elevations are changed continuously throughout the day. It is common to switch between multiple pipe or duct sizes and elevations hundreds of times during a project. The previous contextual Options Bar provided immediate access to all of these parameters in a single location, making modeling fast and efficient. The new workflow requires additional mouse movement, extra clicks, and constant switching between the drawing area and the Properties palette. This slows down daily modeling without adding any new functionality.   Suggestion Please restore the contextual Options Bar for MEP creation tools (Pipe, Duct, Conduit and Cable Tray), or provide an option that allows users to enable the classic workflow. This is not a request for a new feature. It is a request to restore an efficient and well-established workflow that many MEP professionals relied on every day. The previous design significantly improved productivity by keeping all frequently used creation parameters in one place during modeling. Bringing it back as an optional interface would preserve the benefits of the new UI while allowing experienced users to continue working efficiently.   Summary One of the key goals of Revit 2027 was to improve performance and streamline the modeling workflow. However, removing the contextual Options Bar has had the opposite effect for many MEP users. It was one of the most efficient parts of the interface, providing immediate access to frequently used creation parameters during modeling. Restoring it as an optional feature would preserve the modern UI while allowing experienced users to maintain a fast and efficient workflow. Show More

Feature request!!! TAB STACKING so I can stack certain tabs/windows on top of each other if they all correspond to a certain designation or project (e.g. Project building A stacked tabs) or (e.g. Family tabs/windows - Ref.level, View 1, 3D, Back side, Left ... etc ... all are stacked as a tab group) I can't tell you how frustrating it is trying to find my Project B files among my Project A and other Family tabs I have open ... PLEASE IMPLEMENT THIS IMMEDIATELY! Don't even have to give me credit for the idea but it would be cool. Just need this feature more than the air I breath!!! Show More

The graphics overrides menu offers a short cut to Object Styles. Why not offer Manage Links, too? Well that's the idea   Show More

I started working with Revit in 2009 and there is one thing from the start I don't understand. Gridlines. When I have a view 1:100 or 1:200 I don't want the gridbubbles to be the same size. When I make a view 1:200 I want my gridbubbles to be a bit smaller. When I have a 1:500 I absolutly want them to be smaller. A workaround I have is the following. I copy the grid to a new project, make the gridbubbles smaller and link that model. A good, clean, easy, workable solution? Noooo.....  I propose the following    In the View Properties should be an option to change the gridbubble type. So change type by view Show More

Imagine you have a DWG file created in some exotic specialist software that creates blocks using the world origin off the African coast as insertion point. Zoom to extents will leave you with an invisible dot on a blank canvas. So you draught a window selection over the whole viewport in order to select what you know must be there somewhere. Sometimes you get lucky an zoom in on the pin that magically appeared and find geometry. The geometry dances around while you zoom to welcome you to it. Now you unpin the DWG (because you humbly appreciate that revit will complain otherwise) and initiate the move command. You select a base point for this that you think you can roughly locate near your Project Base Point. In order to see it, you zoom out again until it drifts into your viewport and click it. This idea is to put an entry "Move to Project Base Point" into a linked CAD files context menu. Show More

Outil légendes Bonjour, Proposition d’idée d’amélioration des légendes : Avoir la possibilité de pouvoir appliquer dans les légendes des filtres de remplacement. Très utile pour des plans de repérage de cloisons et autres. Avoir la possibilité de choisir des vues de face (élévations) pour les éléments sols et faux-plafonds, dans la même logique des plans de repérage. Legend Tool Hello, Proposed improvement idea for legends: Have the ability to apply view filters (visibility/graphics overrides) within Legend Views. Very useful for partition wall keymaps and similar drawings. Have the ability to choose elevation/front views for floor and ceiling components, following the same logic used for keymaps. Show More

Family parameter formulas are awesome. But I feel like half of them basically consist of "if(x > y, x, y)" of "if(x > y, y, x)". This makes sense for more complex logic like "if(a > b, x, y)". But it becomes tedious when you're writing something like "if(x > y + 3 * a, x, y + 3 * a)" (in which case y + 3 * a should probably be delegated to its own parameter or we're setting a yes/no with x > y + 3 * a, but if it's only used once then I don't want to introduce that extra complexity).   My suggestion is to introduce statements like "min(x, y)" and "max(x, y)" to take either the smallest or largest of the two, or the first of either when they're the same. This would be in line with having a roundup() and rounddown() next to a simple round(), where you could technically add or subtract 0.5 to or from the input to get the same result. We also have pi(), tan() and atan() functions, so I believe min() and max() functions or something similar would be justified.   Especially with nested formulas (3 layers of nesting is no exception) this would improve readability and maintainability. Show More

Issue: When a revision is manually added through Revisions on Sheet, it should appear in the sheet’s Latest Revision / revision date field even when the revision Cloud and Tag are hidden. Current behavior appears inconsistent when Cloud and Tag visibility is turned off. The revision can be added to the sheet, but the sheet schedule does not always report it as the latest revision. Use case: For issued drawing sets, we need sheets to show an issue entry such as: Revision Schedule: No.| Date | Description __ | 2026-06-29 | Issued for Permit without requiring a visible revision sequence number, cloud, or tag. The sheet list should still report the latest issue date, for example: Sheet Schedule: Sht. | Name | Latest Revision AE101 | First Floor Plan | 2026-06-29 Using an Alt+030 blank revision sequence appears to work, but Revisions on Sheet should be enough to drive the sheet’s latest revision data. Show More

  現在、姿図付の建具表を作成しようとしております。 姿図に自動集計した個数を表示させたいのです。 これまでは別のBIMソフトを使用しており、そちらでは可能であったため Revitでも同じことが出来ると大変助かります。 Show More

When a project uses a projected Coordinate Reference System whose underlying geographic CRS is not WGS84 (for example, British National Grid / EPSG:27700), Revit displays the Survey Point (and location) latitude and longitude in that geographic datum (e.g. OSGB36). While this behavior is technically correct, it is not obvious to users and can be misleading. I presume most users would expect latitude and longitude values to be expressed in WGS84 because that is the standard used by Google Maps, GPS, web mapping applications and pretty much anything unless you explicitly set it to display non-WGS84 latitude/longitude (given the software even allows it).   Proposed solution I propose Revit UI is standardized to display the latitude and longitude values in the UI (Survey Point, location) in WGS84. Alternative could be also to display both native datum and WGS84 latitude and longitude; make the display CRS configurable; or at least label the non-WGS84 latitude and longitude to minimize confusion.   This would improve interoperability with common mapping tools, reduce user confusion, and make Revit's georeferencing workflow more intuitive. Show More

Revit topography needs to be updated so it can manage vertical faces when topography is created from a linked DWG that has a TIN mesh.  Also, the fidelity of the topography boundaries is poor. When generating topo for a road and batter with tight bends that turn back on themselves from a linked DWG the topo tool is unable to accurately define the edge of the road / batter and will often infill the area between across the curve in the road, resulting in a lot of post processing of the topography.  Show More

Wenn ich einem Bauteil einen Stil zuweise werden dadurch Parameterwerte in das Element geschrieben wenn ich anschließend wieder „Stil: (Keine)“ auswähle, dann werden die durch den Stil eingetragenen Werte nicht automatisch gelöscht. Und ich kann auch nicht nach Stilen filtern. Ist das Problem bekannt? Kommt hier von Revit eine Lösung in der nächsten Version? Show More