Even though AD considers their work on the colour palette to be done since version 2024, there is still room for improvement. Maybe these should be individual ideas, but I cannot be bothered right now. Hovering over the base colours should indicate HSV and/or RGB values of the swatch. The user defined colours should behave similarly but could also show a name if was picked from a colour book. Should a user defined colour accidentally match one of the base hues, the indentical swatches should be marked. The value fields should anticipate tuples like 240-120-10.   Show More

The workplane viewer inside revit shows that it really is the workplane viewer. The next bit of information is that the currently active workplane is.... Do not get me wrong, the name will come, but you need to drag the window larger to read it. If you are using a localized version of revit the matter gets worse depending on the words for work and plane they came up with in the target language. This idea is to remove the string 'workplane viewer' from said viewer as the nuggets of info following it, give it away anyway. Show More

Currently in all Revit versions, anyone can use the Move command, with Disjoin option checked, to move and unpin any pinned model elements silently without any warnings. This does NOT align with Revit Help Documentation which states "when a modeling element is pinned, it cannot be moved. To move or delete it, the element must first be unpinned using the pushpin control."   This defect often causes pinned/protected model elements to be unexpectedly moved, unpinned, and potentially deleted. There is an old post from 2021 already talked about this issue.  https://forums.autodesk.com/t5/revit-architecture-forum/move-command-moves-pinned-elements/m-p/10745795#M96126   This introduces a big loophole in the project production workflow, and could cause rework and confusion in model submission. It also adds unnecessary challenges to the Digital Project Delivery workflow.    I highly recommend Autodesk Revit team fix this issue asap.  Show More

Currently, the Reset to Crop command always resets Grid and Level extents to the Model Crop Region. Although the Annotation Crop Offset can be adjusted numerically, Datum Elements (Grids and Levels) completely ignore the Annotation Crop and always extend to the Model Crop Region. I understand that Datum Elements are intentionally associated with the Model Crop because they are not purely annotation elements. Autodesk Technical Support has already confirmed that this is the current intended behavior after consulting the internal team. However, this request is not asking to change how Datum Elements work. Instead, I am requesting an optional documentation workflow enhancement that would allow users to choose which crop boundary should be used when executing Reset to Crop. Suggested Implementation When using Reset to Crop, provide an additional option such as: Reset Datum Extents To: Model Crop (Current Behavior) Annotation Crop (New Option) or alternatively, add a View Property: Datum Extents Reference Model Crop Annotation Crop This would work in a similar way to how Grid Extents can already be switched between 2D and 3D. Why This Is Important Architectural documentation frequently relies on: Enlarged Plans Callout Views Dependent Views Detail Plans In these views, the Annotation Crop usually represents the desired drawing composition rather than the Model Crop. Currently, Grid and Level extents must be manually adjusted in nearly every enlarged view because Reset to Crop ignores the Annotation Crop. Providing this optional setting would: Reduce repetitive manual work Produce cleaner documentation Improve drawing presentation Speed up sheet preparation Improve BIM documentation workflows Most importantly, this enhancement would remain fully backward compatible, since the existing behavior could remain the default option. Testing Performed The current behavior has been verified in: Revit 2025 Revit 2026 Brand-new blank projects Floor Plans Callout Views 2D Grid Extents In every case, Reset to Crop always follows the Model Crop Region and never the Annotation Crop. Final Note This Idea is not requesting any change to the fundamental behavior of Datum Elements. It simply proposes an optional documentation feature that would allow users to decide whether Reset to Crop should reference the Model Crop or the Annotation Crop. This small enhancement would significantly improve documentation efficiency while preserving the existing Revit workflow for all current users. Thank you for considering this suggestion. Show More

In previous releases of Revit there was an options bar that automatically appeared when modeling piping. Here, you could type in the diameter, elevation, and hit apply a few times to easily create risers with all options being conveniently right next to each other. With the new release of Revit 2027, I asked the AI assistant how to make this menu appear and it said this feature was intentionally removed. Could this be added back in? I feel like it made life much easier.  Show More

Currently, the Break option in a Revit tag label only creates a new line when the parameter immediately following the break contains a value. When optional parameters are used, the line break may not work as intended. If the next parameter is empty, Revit skips it and continues to the next parameter containing a value. However, if that parameter does not have the Break option enabled, the content remains on the same line. The proposed enhancement is for the Break option to define the tag layout independently of whether the following parameter contains a value or not. When a break is enabled, the next parameter  should always start on a new line, even when one or more parameters between them are empty. This would make tag composition more predictable and allow tags containing optional parameters to maintain a consistent layout without requiring multiple tag families or complex workarounds. Show More

Restore the ability to resize duct, pipe, conduit, and cable tray runs along with their fittings using the Modify Multi-Select ribbon. Previous versions of Revit allowed users to select connected segments and fittings and modify their sizes simultaneously. In Revit 2027, users must resize the straight segments and fittings separately, adding unnecessary steps to a common MEP workflow. Reinstating this functionality would improve efficiency and provide a more consistent editing experience for MEP designers and engineers. Show More

In workshared Revit models, certain settings that are effectively personal workspace preferences are shared between users through the project. As a result, engineers and designers frequently open a model only to find that aspects of their workspace have been changed by whoever worked in the model last. Examples include Project Browser expansion states, selected family types, and other session-specific workflow settings that do not affect the model, project standards, or deliverables. These settings provide little or no collaborative benefit when shared, yet they create daily workflow interruptions and force users to repeatedly restore their preferred working environment.   Autodesk should review which settings are currently shared through worksharing and move any non-project-critical, user-specific preferences to the local user profile. Settings that impact project standards, model content, or coordination should remain shared, while settings that only affect an individual's workflow should remain personal. This would reduce user frustration, improve productivity, and create a more consistent experience across multi-user projects. Show More

• Real-World Requirements Conduit routes frequently change because of coordination, site conditions, equipment locations and cost-driven design changes. Designers need to adjust important XYZ positions along a conduit route without disconnecting the system and redrawing or reconnecting affected sections. • Current Revit Problem Changing the elevation of a conduit segment, fitting or connected item can move the entire connected system, including elements that are already correctly positioned. For example, where conduit connects two manifolds, changing the elevation of the first manifold will also move the conduit and the second manifold. To make a local adjustment, users may need to disconnect the system, reposition the required elements and then redraw or reconnect the conduit. • Proposed Solution Introduce an Edit Conduit Path mode using editable control points. Users should be able to: Adjust the X and Y position, reference level and offset of individual points. Keep selected endpoints, fittings or equipment fixed. Add or remove control points. Edit routes in plan, section, elevation or 3D. Maintain spacing when editing parallel conduit runs. When a point moves, Revit should automatically recalculate the affected conduit length, angle, bends and connections without moving correctly positioned elements. • Benefits This would make conduit modelling faster, reduce manual disconnection and redrawing, improve coordination and preserve conduit properties, connections and scheduling information. Show More

The AISC added steel shape sizes with its release of the 16th edition that was issued in 2023.  Those sizes are not available when you use the "Load Autodesk Family".     Could we get the families updated to have all the current sizes added to Revit?    The database is available on the AISC website.  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

I always forget what the current WorkPlane is and i model elements 3 stories up or 5 levels down from my current plan view. And of course i can't see them, since the the current Workplane is not my current plan view. It would be so helpful to read the name of the current WorkPlane on the Status Bar !!! And the WorkPlane's name should be green colored while the current Workplane matches the current plan view, yellow if is visible in the current view but id doesn't match the current plan view, and red colored if the WorkPlane is not visible in the current view. Show More

Change Detail Level by Filter.   When creating a filter, allow a different detail level to be applied based on filter. Show More

It would be nice to have corner grips on view controls to adjust two sides at once. Applicable to crop regions, section boxes, section and elevation extents, etc... Show More

Can the "Autodesk Project" in the Revit homepage be listed above the "Recent" option as a default?     Show More

Simply put, if I have View A and View B, then if I place a callout on View A and have the callout reference View B, the callout should be able to automatically inherit the size, shape, and position of View B's crop.   This should be optional, of course. But 95% of the time, this is the behavior I want. I don't want to have to go manually fix the callout every time the size of View B is adjusted slightly. Alternately, a similar effect could be achieved if I could bind the callout for View B to a scope box (presumably the same scope box that View B is bound to).   Going further, it might be superior to disentangle callouts from views, treating callouts and views as entirely separate objects, allowing callouts to reference any view of any type (even switching a callout from one view to another if necessary) and to automatically take on the size, shape, and position of the referenced view if desired.   It is reasonable to ask why any of this is necessary - just create the callout directly the first time, so it is associated with an enlarged view. I have three reasons for making this request: Sometimes I need an enlarged view to be associated with a different level than the parent view. Currently, the only way to do this is to make a second view (View B) and then put a Reference Other View callout on the overall view (View A). But this requires that I manually update the size, shape and location of the callout, which is tedious. Sometimes people create a view that should be an enlarged view with a callout, but this was either not apparent at the time, or they simply didn't realize this. In those cases, it would be helpful if a callout referenced to the view would behave exactly as if the view had been originally created as a callout. From a UX standpoint, it just seems weird that a callout set to Reference Other View behaves in a totally different manner than a callout connected to a view at the point of creation. Well, that's all I've got to say. Thanks for reading. Show More

Raster printing is Not Great.  I think most of us want the following upgrades to raster printing:   1) Vector printing should handle more features.  Depth cueing and shadows are the two biggest pain points for most users.   2) When raster printing must be used, the embedded image should be higher quality.  Revit internal PDF export is the worst, creating fuzzy JPG embeds.  Printing to PDF through Bluebeam creates higher quality embedded images, but it's still a fuzzy mess.   3) Hybrid raster-vector printing.  Render as much as possible through vector graphics, then use a raster underlay for what cannot be done through vector.   4) Raster printing always prints WYSIWYG, but vector printing has quirky behavior occasionally.   Perhaps this will all be fixed (wiped away like a bad dream) when the new rendering engine is stable, mature, and ships to replace the current rendering engine.   ---   The below links are all threads about raster printing.  While these threads are not necessarily all about identical issues, and some threads contain nuances not captured in my summary above, these are all threads complaining about raster printing.  This thread exists to rally together all past votes and make the complaints easier to see.   https://forums.autodesk.com/t5/revit-ideas/exporting-elevation-with-depth-cueing-enabled-as-vector-during/idi-p/14055525 https://forums.autodesk.com/t5/revit-ideas/vector-printing-with-raster-underlay/idi-p/7565402 https://forums.autodesk.com/t5/revit-ideas/vector-shadows-in-hidden-line-prints/idi-p/6330690 https://forums.autodesk.com/t5/revit-ideas/raster-printing-change-embedded-jpg-images-to-png-format/idi-p/11389094 https://forums.autodesk.com/t5/revit-ideas/add-to-raster-printing-message-information-on-the-use-of/idi-p/9207269 https://forums.autodesk.com/t5/revit-ideas/wysiwyg-amp-vector-printing/idi-p/7085229 https://forums.autodesk.com/t5/revit-ideas/vector-option-for-export-to-pdf/idi-p/12764115 https://forums.autodesk.com/t5/revit-ideas/print-nwd-nwc-links-on-revit-sheets-as-vectors-pdf/idi-p/7908186 https://forums.autodesk.com/t5/revit-ideas/vector-atop-raster-when-printing-with-coordination-model/idi-p/12084197 https://forums.autodesk.com/t5/revit-ideas/enable-pdf-export-with-black-lines-and-color-patterns-and-raster/idi-p/11762199 Show More

Revit currently only allows copy and paste between projects open in the same session. This makes it difficult to transfer elements when working with multiple Revit windows or versions. Other design software supports clipboard operations across sessions, and adding this to Revit would: Improve productivity for users working on several projects at once Remove the need for time-consuming workarounds like exporting groups or linking files Make Revit more consistent with user expectations from other design tools Please consider enabling copy/paste between separate Revit sessions to streamline workflows. Show More

i am often trying to fix views and being able to compare the details of a view template could be extremely helpful Show More