This image says it all. Right now, only the "Free End" option for leaders allows snapping to the endpoints of the leaders. This should also be a default for "Attached End".    Show More

I would love to be able to access loaded families while in the Type Properties for System families.  Quite often I'm editing something like wall sweeps, or hosted profile sweeps, railings, etc. and need to load or edit a family that's selected in the System Family.  So I have to hit OK multiple times to get out of whatever dialog box I'm in, go find the profile or other loaded family in the Project Browser, then make my way back to whatever family I was previously editing.  If we could access loaded families, or anything else in the Project Browser, while a dialog box is open, it would be a huge time-saver. Show More

Hello,   The implementation of phasing within View Filters is great, but it would be very useful in some scenarios to be able to make these relative. Right now, you have to select a specific phase for your Filter Rules. This can be handy, but having some relative options would also be very useful.   If we would like to implement some standards around visibility of things based on phasing, we would want to set this up within our template. We don't know what a project's phases will look like down the road, but we might know that this filter should override ANYTHING that is considered "previous" to any given view. If we could select an option for "Phase Created: is less than: Current Phase of View" this would solve having to create duplicate filters for the same thing OR ensuring that a user is adjusting the filter to the latest phase each time, etc.    Most things about phasing and phase filters on views is relative to that view, it only makes sense to make the View Filters have the same options. Show More

Please implement the filtering method used in view filters for schedule filters. I've seen so many similar ideas: Like "OR" filters, ability to create more filters than the defined in the schedule, and others. If it were implemented like the view filters, it would solve all those issues, and many more. I mean, so many schedules are used for data control and project model healthy, and what better way to achieve this than to being able to use the same filters in both views and schedules. Show More

Working on a (metric) project's with units set to metres, it is counter intuitive to have these units in centimetres when adjusting material textures. The idea is to make the material editor honour the host project's units. Show More

When adjusting photo textures within the material editor, it would be helpful if generic formulas worked the way they do in all other number savvy fields in Revit.  Show More

Enable different revision sequences to be identified using different colours. Useful for identifying when each change was made. Show More

Most improvements in new Revit versions, while beneficial, often consist of minor adjustments that could easily be included in an upgrade or service pack. Adopting this approach would allow more time and focus for deeper, more meaningful enhancements. It would also help standardise the software version used across different projects. Currently, the constant release of new versions leads to several issues: Projects often rely on different Revit versions, creating inconsistencies; Multiple installations take up significant disk space; Upgrading families and project files becomes more complex; Opening older projects can be confusing or problematic. Additionally, a typical construction project — from early design stages to completion — usually spans around four years. This means users often end up having at least four different Revit versions installed simultaneously, just to keep up.   One ideia could be to release a new version every two years for example. Show More

Automatically create room elevations and axonometric views giving a view crop offset and the type of view. Show More

When modelling a curve or arc one often ends up with the exact opposite of one's intentions.   In this illustration, hitting space would turn the blue marked arc into the black one and vice versa. Show More

Our current PCs are powerhouse machines capable of incredible calculations, yet Revit lags unbearably. No optimization is done, and no performance improvement is possible in the current state of things. The software wallows in its own mediocrity, and Autodesk does nothing to change that.   I always hear the same advice: reduce file sizes, split buildings to use less memory, etc... But actually, no. It’s completely illogical.   Would you tell a video editor to reduce the resolution of their video files so the software can handle them? Would you ask a graphic designer to use fewer colors because Photoshop is lagging? Would anyone ask you not to exceed 60 km/h with your new car because it would start stuttering?   A professional software like Revit, which has a monopoly and is so expensive, should work properly. Users shouldn’t have to adapt. A 1 GB file is nothing exceptional today; we are asked for more and more data, so it’s normal for file sizes to increase. Here, every day, Revit crashes because it can't convert a slightly too large IFC file, for example. If I read correctly, the software still runs on a single core while our CPUs have at least 8. The capabilities of graphics cards are completely unused (as proof, it’s often recommended to disable hardware acceleration, which is absurd...). It's still run on DX11.   Should we just keep quiet and accept it?   Maybe a lot more clients should complain to Autodesk because the situation is clearly abnormal—and it has been for decades. We are tired. We should coordinate, maybe for a week, so that everyone calls the hotline, just to overwhelm their useless customer service and express our dissatisfaction—maybe then they’d finally do something instead of resting on their laurels and cashing in checks. (A competitor is really needed to shake things up.)   Show More

When inside the family editor, you often need to constrain a value to a parameter. Users are currently required to click the field next to the value, invoking a new window and selecting or generating the appropriate parameter. The idea would be for Revit to accept if a parameter name is entered into the value field. It would complain if the parameter entered were inappropriate or would offer to make one if it did not exist yet. Show More

If the level head is turned on to the right side in a view, a multiple line level name looks fine, but if it is on the left side, then being right justified is wrong (in my opinion).   I want the text to justify dependent on which end it is on.  So if the left side is on, it should justify to the left, so the text remains up against the symbol.  On the right side, it should right justify so it is aligned up against the symbol on that side.     Most of the time with single line level names, it doesn't seem to be an issue, only with the occasional longer level names.      Show More

Hello, Everything is in the title. Each time you rotate or mirror a family, all its tags are deleted in all views. It's a pain to figure out which views were affected, then re-add the tags one by one, remembering which tag was used in each view, etc. There's no reason to delete them, as they are linked to the family. No matter the orientation, the parameters remain the same. Show More

Hello, The idea is simple: do not reset the zoom after canceling a command. You are drawing, making adjustments, checking if everything looks good. You press Escape when you finish, but the view resets to the one from the last click. Very annoying. Show More

The feature that appeared in 2025 for multiple alignment of labels and text is great, but why not apply it to all categories? For example, being able to distribute walls without having to create an temporary array or EQ dimension (and then delete the dimension, with the resulting message "do you want to keep the constraint?"), or to quickly place a series of furniture and align it... It shouldn't be difficult to implement, because the pyRevitPlus plugin already does it, but it would be nice to have the OOB option. Show More

In the contextual menu for families: New option to create a filter directly from each type of the family. Useful for creating filters by type. Show More

Quando o Revit finalmente levará a sério as atualizações da Parede Cortina? Como profissional que trabalha com sistemas de fachada há anos, devo expressar uma frustração crescente compartilhada por muitos na indústria: o sistema de parede cortina do Revit permanece altamente limitado e desatualizado, especialmente quando comparado a concorrentes como o Archicad. Estamos em 2025 e ainda não podemos realizar operações de usinagem (furos, ranhuras, entalhes) em montantes, nem tratá-los como famílias paramétricas totalmente independentes com vários materiais. A geometria do montante ainda está restrita a um único perfil extrudado com um material aplicado no nível do tipo, impossibilitando a representação de detalhes técnicos ou de nível de fabricação. ➡️ No Archicad, montantes podem ser manipulados como objetos sólidos verdadeiros, com operações booleanas e modelagem livre. No Revit, somos forçados a confiar em soluções alternativas usando famílias genéricas, componentes aninhados ou scripts do Dynamo para obter o que deveria ser uma funcionalidade nativa. Pedimos à equipe de desenvolvimento que priorize as seguintes melhorias: Habilite vários materiais dentro de montantes, com controle por região. Permitir operações de usinagem direta em montantes (cortes, vazios, furos) dentro do ambiente do projeto. Forneça a opção de converter montantes em famílias separadas e editáveis pelo usuário, para detalhamento avançado. Melhore as condições de junção de montante, incluindo chanfro, chanfro e junções verticais/horizontais personalizadas. Essas são necessidades do mundo real para arquitetos, engenheiros e designers de fachadas - e foram negligenciadas por muito tempo. O Revit fez grandes avanços em muitas áreas, mas o conjunto de ferramentas da parede cortina fica significativamente para trás. Com forte apoio da comunidade e atenção técnica da Autodesk, este sistema pode finalmente atingir o nível de flexibilidade que o design e a construção modernos exigem. Show More

Scope boxes aren't fully exposed in the API. They don’t even have their own class; they belong to the Element class. They also don’t have parameters like width and length. So, please create a subclass like ScopeBox  and a constructor which takes a BoundingBoxXYZ object as it's argument. EDIT: I did not know there was already an idea with the same concept, and I couldn't find a way to delete this post. so, for reference, this is the link to the existing idea. SCOPE BOXES [Control visibility & size via API] - Autodesk Community Show More