<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Revit 2027 in Revit Architecture Forum</title>
    <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082372#M367208</link>
    <description>&lt;P&gt;Having only lightly followed the AI/Agentic discussions on the Dynamo side, I'm not really looking forward to that being embedded in core Autodesk products. There is already pretty vocal pushback on these user forums as-is on having to learn supplemental programming languages or API-level information to deal with specific design requirements or workarounds (why isn't it in base Revit, we're paying for a complete software, not everyone at a company should be technically-oriented, etc. etc. etc.). This is swinging harder in the opposite direction by saying 'look how easy it is to come up with your own solutions!'. Personally, I don't mind access to new solutions being made easier since I'm barely angled towards the technical end... but I don't think the standard expectations of the software are really met yet to address people that just want to go into work, do design work, and go home.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IFC parameter mapping tool sounds great. Want to see more of this. The more that model formats can be interchanged safely between products the better for widescale adoption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would *love* to sit down with some structural engineers and find out if the last three years worth of design push into structural calculation methods actually reflects/supports their normal workflows. Each update seems saturated with structural changes, but the majority of structural consultants I come across are still using Revit at a minimalistic level. I assume they're waiting for a critical point where enough needs are met to full pivot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm curious about the updates to the HVAC Zoning rebuild (I never quite liked all the custom UIs to work with setpoints, the more information directly viewable in Properties palette or Type editing, the better), but indifferent to the energy modelling guide. But, considering that this means that HVAC modelling has changed&amp;nbsp;&lt;EM&gt;again&lt;/EM&gt;, I'm getting fatigued with keeping track of the current 'correct' workflow. Also concerned about how model updates that jump to 2027 will break. There's already statements in those patch notes that certain things won't transfer to the new version.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2026 16:38:20 GMT</pubDate>
    <dc:creator>RLY_15</dc:creator>
    <dc:date>2026-04-08T16:38:20Z</dc:date>
    <item>
      <title>Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082039#M367199</link>
      <description>&lt;P&gt;Is anyone excited about the new features at all?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe I'm missing something, but this is a release that makes me even consider skipping this version. Unless the SP bring more tangible features. R2026.4 is so stable, I don't see the reason to risk upgrading. And I'm the person who &lt;U&gt;used to&lt;/U&gt; upgrade shortly after release (until I got burned by the schema issue).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like Autodesk looked at the "ideas" forum and decided, "let's just do some AI instead, this is the fad of the week anyway".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And if a feature is called "Preview", does it mean it doesn't work well yet?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Curious to hear if anyone tried R2027 and thinks the new features are really that great.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.autodesk.com/view/RVT/2027/ENU/" target="_blank"&gt;https://help.autodesk.com/view/RVT/2027/ENU/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I plan to upgrade (if at all) end of the year. But from what I see now, there isn't a single killer feature worth risking moving away from stable R2026.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 12:57:22 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082039#M367199</guid>
      <dc:creator>HVAC-Novice</dc:creator>
      <dc:date>2026-04-08T12:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082080#M367202</link>
      <description>&lt;P&gt;I wish we had the luxury of making the choice, but when you are a consulting engineering firm, we have to use whatever version the architect is using.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;This means we have to maintain, and be fluent in, all versions that we can legally run.&amp;nbsp; We have active projects that ae still in 2021 and have not yet been upgraded (again, we can't upgrade until the architect does....) and we have to maintain our templates and library in the oldest version.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;What an administrative nightmare....&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 13:29:17 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082080#M367202</guid>
      <dc:creator>apjones</dc:creator>
      <dc:date>2026-04-08T13:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082314#M367207</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/775056"&gt;@apjones&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;I wish we had the luxury of making the choice, but when you are a consulting engineering firm, we have to use whatever version the architect is using.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;What an administrative nightmare....&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Fortunately, we are upstream and I can force downstream designers. And usually the new features or bug fixes warrant annual upgrade. I plan to upgrade in December, but often bugs in the old version force me to upgrade sooner. But R2026.4 just seems perfect so far. I don't see a reason to&amp;nbsp; upgrade soon. Those new features resolve no single problem for me, and I don't know if Autodesk is capable of AI, if they aren't even capable to let me re-number views on a sheet without me using Dynamo.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wish they found a way to get rid of versions and make it a rolling release. BUT I also don't think Autodesk can mange that. One problem with working in different version is, if I create a new family, or schedule or some other great idea for a project in R2026, i also would want to implement that in older projects if they haven't bid out yet. Problem is, if that older (but not bid yet) project is in an older version, i either have to manually re-create my new feature, or not take advantage of it. And I do develop a lot of new stuff.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 15:59:22 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082314#M367207</guid>
      <dc:creator>HVAC-Novice</dc:creator>
      <dc:date>2026-04-08T15:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082372#M367208</link>
      <description>&lt;P&gt;Having only lightly followed the AI/Agentic discussions on the Dynamo side, I'm not really looking forward to that being embedded in core Autodesk products. There is already pretty vocal pushback on these user forums as-is on having to learn supplemental programming languages or API-level information to deal with specific design requirements or workarounds (why isn't it in base Revit, we're paying for a complete software, not everyone at a company should be technically-oriented, etc. etc. etc.). This is swinging harder in the opposite direction by saying 'look how easy it is to come up with your own solutions!'. Personally, I don't mind access to new solutions being made easier since I'm barely angled towards the technical end... but I don't think the standard expectations of the software are really met yet to address people that just want to go into work, do design work, and go home.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IFC parameter mapping tool sounds great. Want to see more of this. The more that model formats can be interchanged safely between products the better for widescale adoption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would *love* to sit down with some structural engineers and find out if the last three years worth of design push into structural calculation methods actually reflects/supports their normal workflows. Each update seems saturated with structural changes, but the majority of structural consultants I come across are still using Revit at a minimalistic level. I assume they're waiting for a critical point where enough needs are met to full pivot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm curious about the updates to the HVAC Zoning rebuild (I never quite liked all the custom UIs to work with setpoints, the more information directly viewable in Properties palette or Type editing, the better), but indifferent to the energy modelling guide. But, considering that this means that HVAC modelling has changed&amp;nbsp;&lt;EM&gt;again&lt;/EM&gt;, I'm getting fatigued with keeping track of the current 'correct' workflow. Also concerned about how model updates that jump to 2027 will break. There's already statements in those patch notes that certain things won't transfer to the new version.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 16:38:20 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082372#M367208</guid>
      <dc:creator>RLY_15</dc:creator>
      <dc:date>2026-04-08T16:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082576#M367221</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;P&gt;&lt;SPAN&gt;Having only lightly followed the AI/Agentic discussions on the Dynamo side, I'm not really looking forward to that being embedded in core Autodesk products. There is already pretty vocal pushback on these user forums as-is on having to learn supplemental programming languages or API-level information to deal with specific design requirements or workarounds (why isn't it in base Revit, we're paying for a complete software, not everyone at a company should be technically-oriented, etc. etc. etc.).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm curious about the updates to the HVAC Zoning rebuild (I never quite liked all the custom UIs to work with setpoints, the more information directly viewable in Properties palette or Type editing, the better), but indifferent to the energy modelling guide. But, considering that this means that HVAC modelling has changed&amp;nbsp;&lt;EM&gt;again&lt;/EM&gt;, I'm getting fatigued with keeping track of the current 'correct' workflow. Also concerned about how model updates that jump to 2027 will break. There's already statements in those patch notes that certain things won't transfer to the new version.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I'm using spaces and zone/Equipment parameters based on what &lt;A href="https://rippleengineeringsoftware.com/" target="_blank" rel="noopener"&gt;Ripple-HVAC&lt;/A&gt; does. That seems to be more robust and independent on what Revit decides each year. the whole energy simulation is pointless since no legal body or LEED will recognize Revit results.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AI can be good, but I have no trust Autodesk can do it. They probably just subscribed to some ChatGPT or so. I'll judge it when I see it, but based on the total disregard of users' wishes, I'm not optimistic. I hope I'm wrong. But today everything is called AI. Last year ever feature was "green", now it is "AI". The owners probably pressed the&amp;nbsp; CEO to "do AI like everyone else".&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As for Dynamo etc..... all dependencies seem to change every year. This is horrible for maintainers that only code occasionally. A full time developer can handle it. Remember, we are architects and engineers, not full time coders.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And simple requests from the ideas forum should be part of the software we pay for. Autodesk sells a car without steering wheel, but they give us some wrenches for us to built some sort of steering mechanism.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They should stop adding more features like AI, or energy, or carbon or structural, and just implement every year 100+ of the top "ideas" that users requested that will benefit most disciplines or make some modules useful.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And you probably are correct about structural, it likely isn't correct enough to be used for design. And structural engineers likely rely on proven 3rd party tools. Whenever I work with structural engineers, none uses Revit for structural calculations.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 19:15:05 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082576#M367221</guid>
      <dc:creator>HVAC-Novice</dc:creator>
      <dc:date>2026-04-08T19:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082773#M367226</link>
      <description>&lt;P&gt;Oh, the Issues Management also looks interesting. Ignoring the branding fatigue that is Bim360-&amp;gt;AutodeskDocs-&amp;gt;FormaDesignCollaboration, a non-Navisworks location to publish coordination topics seems like a no-brainer good value add.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rule-base numbering also seems good but 100% there will be tripups when the architect sets their Room rules to remove gaps after element deletion, and the corresponding MEP space + any sequential spaces wind up with numbering mismatches. Also curious what the interaction will be with Room numbering versus embedded doors/windows.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 22:05:57 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14082773#M367226</guid>
      <dc:creator>RLY_15</dc:creator>
      <dc:date>2026-04-08T22:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14083250#M367232</link>
      <description>&lt;P&gt;There are some nice things, but overall, I'm not jumping for joy. I haven't been for years, I might add.&lt;/P&gt;&lt;P&gt;We tend to start using the Revit version in the year it's version number shows. So we started using Revit 2026 this year. As&amp;nbsp;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/775056"&gt;@apjones&lt;/a&gt;&amp;nbsp;says - you not always have a choice on using a particular version.&lt;/P&gt;&lt;P&gt;AI is inevitable and it could be useful - if it's smart enough. Calling it &lt;EM&gt;Autodesk Assistant&lt;/EM&gt;&amp;nbsp;makes me shiver. That &lt;EM&gt;Assistant&lt;/EM&gt; you have to use / bypass if you want to create a service request isn't exactly helpful...&lt;/P&gt;&lt;P&gt;And Forma of course. My guess the Big Plan is Revit becoming more and more of a sort of front-end for &lt;EM&gt;the cloud&lt;/EM&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2026 07:12:10 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14083250#M367232</guid>
      <dc:creator>Simon_Weel</dc:creator>
      <dc:date>2026-04-09T07:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Revit 2027</title>
      <link>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14083255#M367233</link>
      <description>&lt;P&gt;The only feature that I find &lt;STRONG&gt;somewhat&lt;/STRONG&gt; interesting is the &lt;A href="https://help.autodesk.com/view/RVT/2027/ENU/?guid=GUID-1121752C-EAB2-411F-A549-66E599A820B8" target="_blank" rel="noopener"&gt;"enhaced stairs risers/threads numering"&lt;/A&gt;.&lt;BR /&gt;And honestly, when I saw it on the roadmap I thought they would include it in the Revit 2026.4 update&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;(I actually don't understand why they didn't design the tool this way from the beginning)&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2026 07:15:58 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-architecture-forum/revit-2027/m-p/14083255#M367233</guid>
      <dc:creator>arq_42</dc:creator>
      <dc:date>2026-04-09T07:15:58Z</dc:date>
    </item>
  </channel>
</rss>

