Revit 2024.1 is here - What's you thoughts?

[handjonathan]

This week has seen the launch of the latest update for Revit. Revit 2024.1 builds out capabilities for design and documentation, interoperability and data transfer, and insights and analysis introduced in recent releases. 

Image courtesy of Paul Aubin Consulting.

Check the product help for full documentation for Revit and Revit LT 2024.1 under the “What’s New” tab.

What's your thought on the latest enhancements?

[trombeNZ]

The "interoperability" referred to in the header......

Does not seem like much of anything has changed really since I started with Revit in 2002 except perhaps PDF.

The  almost total focus on proprietary means,  to only allow easy connections with other AutoDesk products is still hugely disappointing. 

I have Revit LT collaborators. 

Why do Autodesk continue to prevent any useful means for LT users to access any form of rendering such as the DXF workflow out of LT to something like Twinmotion ?

Revit LT while  lower cost and restricted is still a premium BIM product on the market for working in a professional capacity and is intended to be so.  In today's working environments which are many and varied,  LT users need some means to work across other programs like Twinmotion or other rendering /limited fly through animation products  - Lumion, D5 Render as examples,  because what we all do is so varied and entails regular and constant iterating and the use of rendering and animation sources is a basic element of our design work, ever more so today.

You are actually holding them by the neck - that is not customer support and driving means to support industry, that is only purely proprietorial restriction when you are the largest and most influential and controlling vendor in the world and in our design  world totally,   dominant of the entire industries.

You control virtually everything.

LT users are no less important in the overarching eco system of what we all do and preventing them from accessing a 3rd party plug in or making sure they cannot use any other means to produce renders or a walk through, is pretty poor.

How about looking at that aspect of Interoperability? 

Therefore as yet no noticeable change for 2024.1

[RobDraw]

So, what do you think about the changes made in the update compared to before the update?

[mohammed.rahman]

Cutting and digging Toposolid with void geometry and abolishment of the Building Pad both are nonsense ideas

[DanChristian]

Since upgrading to 2024.1, I constantly get the following error:

"Schema Conflict when Loading a File"

Is there a fix for this?

[RobDraw]

I've seen a similar error from an add-in. We don't use the schema, so we let it load. If you use the schema, you'll have to figure out the best course of action. 

[DanChristian]

Thanks Rob.  The only add-ins I use are Enscape and Align.  I guess, I'll just ignore the error and hope I don't lose anything.  

[RobDraw]

The schema is settings for something. If you aren't utilizing that schema, overwriting it won't cause you to lose any settings. You don't have any choice as hitting cancel doesn't allow the project to open.

[HVAC-Novice]

I had that schema error recently the first time (2024.1, but that may have been coincidence). I had issues with binding a linked file and tried some meddling. I didn't even know what schemas are...  i don't know if that was the point where i re-started the project (I was in the vert beginning and the linking of an old project was the start...). I cannot tell if that error is because of the 2024.1, or because of my linking/binding and meddling. i hope this was a one-off due to specific circumstances. 

Balkanarchitect did a nice feature intro to 2024.1  Before watching the video i didn't know about zooming the properties and browser. This is nice. Also the tabbing through the browser is nice. And they fixed the truncated family names when editing very long names. 

Overall I like the introduction of just a few new features with every SP. Less chance for issues. I kind of wish they would get away from the annual versions and do a new release with fewer changes every 3 months. 

[lglielmi]

I think it's crazy that we are not able to model timber connections, and we need to modify the material behavior in Steel. In 2024. 

[rciGST6J]

A couple of us in our office are also getting this exact error this morning. I updated to 2024.1 on Friday at the end of the day, and was unable to open the file this morning. My colleague had the same error, but hadn't yet updated to 2024.1. We installed the update on hers, and were able to open it shortly thereafter. After a few hours of working, she got the same error when trying to synchronize. In all cases, choosing to continue loading the file just crashes Revit. I am still able to work, for now at least. 

The model is hosted in Autodesk Docs as a cloud model. No Revit links, just a couple of DWGs. The Structural consultants has access to the model but is not in it, as far as I'm aware. We're not using any add-ins. 

This seems like a bug. Unfortunately, it's completely stopping my colleague from working on this project. I've already looked at the previous solutions to this issue in past releases, but nothing seems applicable. Is Autodesk working on a hotfix?

[GlynnisVP]

We are also now receiving reports of the new error. I see in the Update notes that there were changes to the API that might be the source of this problem. @handjonathan we need to escalate this with the Autodesk team and ask our mutual customers to refrain from the update until this can be better understood.

Glynnis Patterson

www.ideatesoftware.com

[rciGST6J]

@DanChristian , @HVAC-Novice , @GlynnisVP : I spent about an hour on a call with an Autodesk support agent, Lance. He was extremely helpful and we went through a bunch of possible solutions. Ultimately, the error seems to have gone away, so here's what we did in case it works for anyone else:

• If someone can open the model, go into the Purge Unused dialogue and get rid of any unused Extensible Storage Schemas. In our case, there were two.
• Synchronize and close the model.
• Open and audit the model, sync it and close again.

This did not immediately solve our issue, but for some reason after about fifteen minutes my colleague was again able to open the model without the error popping up. It has also disappeared for me, and Lance (who I had added to the project to replicate the issue). 

This is all anecdotal, but I'm not going to look the gift horse in the mouth. If anyone else is having the same issue, try running through these steps. If it doesn't work, let me know and I'll try to think of any other random things we did that may have fixed it. 

Lance is also looking into it on his end, so hopefully we'll have some more clarity soon. 

[HVAC-Novice]

thanks for posting this solution. I googled to find out what schemas exactly are and do. But I couldn't really understand what they do. Could someone explain what they do? 

Based on your advice, I went into one of my projects (that did NOT have an error)  and purged 4 schemas. I don't know here those came from.

I then went into my template and the purge dialog didn't show any schemas. I guess that is good. but wonder, where do they come from? 

I then went into another project that actually originally caused my error. But I had-re-started that. That also didn't have any schemas to be purged. I know the purge dialog only shows unused items. Are there any schemas I can see? 

The help explains a lot about re-instating the schema folder... but it isn't clear to me what schemas are. Is there any pro-active cleaning or purging we should so? 

I found this article describing issues upgrading to 2024.1. I'm someone who upgrades very quickly. But now I think I should wait a month or so before upgrading. 

[rciGST6J]

I hadn't heard of schemas before getting this error either. As I understand it, when you load an add-in (this includes built-in ones, like eTransmit, Batch Print, Formit Converter, etc.), it creates a "schema" within the model that defines the configurations for that add-in. It generates this schema upon first load, and gives it some gibberish name. This specific error is coming up because the same name is being applied to different add-ins for some reason, which confuses the program. Normally telling it to continue would just overwrite the schema with the current one, but this was causing crashes. Someone who knows the program deeper than I do can correct me on any of that, of course. 

I suspect this error has something to do with an API change in the update. I've been using Revit for about a decade and never had this happen, so I don't think it's a common thing you need to be proactive about. 

I would recommend holding off on most updates for at least a couple weeks, though (for basically everything, not just Revit). I also think that the audit may have been the critical part of the "solution", not necessarily purging the schema. Lance recommended auditing weekly, more or less often depending on how many people are in a model and how much it's changing. It realistically only adds like a minute to your file open, so that seems sensible.

[RobDraw]

Try disabling add-ins to eliminate/confirm them as the source of the problem.

[loboarch]

Here are a few troubleshooting topics related to this situation in 2024 and 2024.1
https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-38030A32-0460-4A2A-92D8-B698C0B01161
https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-40B0224D-9925-449B-84D0-8241EA15849A
https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-A8A5E4FD-8671-4B00-B3E6-CB4707D80744

These schema conflicts are occurring in most cases when opening more than one model in a Revit session and there is a duplicate definition for the schema already in memory. These troubleshooting topics all give basically the same solution of just opening one model at a time in a single session of Revit.

[HVAC-Novice]

Here another potential issue that is new (to me). I started by loading an oob family into my project. The original name was "Light Gauge Zees". Then I renamed it in the project to be "S_Metalbuilding_Profile_Zee". by default the save-as used the original name. i manually also changed it in the save-dialog to my new name. then somehow in the project it changed back to the old name (Light Gauge Zees). I then renamed it again in the project, saved again and made it the new name in the save-as again. And now the name of the family in the project. it i slike a ghost playing tricks on me. 

And no, I didn't close my project and forgot to save it. I had a similar issue some days ago, but counted that as a fluke. I don't recall that ever being a problem. 

anyone else having problem re-naming families in the project? 

Now I did a "reload" by clicking on the family in the project (while it still had the original light gauge name), manually selected that saved family with the correct name, and the family in the project now appears to have the correct name. 

I can't tell if this is a 2024.1 issue, but I don't recall having such issue. the above is my standard procedure when I edit a new family from an oob family and how i standardize naming. I sure would have noticed if that would cause frequent issues. 

[Alex.Page.NZ]

Also, regarding the schema bug, it also happens when updating the whole project in BIM360 so can't get around the bug using methods explained. Also, it corrupted the model, and when publishing it through BIM360 the dreaded  broken link symbol appears.

[RobDraw]

Can the comments about the Schema warning be broken out to another thread? Someone can link to it as a separate discussion. Just a suggestion as I am following this closely.

At this point, I would like to add that I have experienced this issue in Revit 2022. As recently as within the last couple months. It could be happening as people are getting updated. (We don't always all do it at the same time.) It just hadn't occurred to me at the time. My research revealed that it was definitely related to add-ins. The information in the error message (as illustrated below) before indicates the source of the schema, which is one of the add-ins we use. I too, had to research schemas and came to the conclusion that we weren't using it.

When I consider it could be related to Revit updates, it does make sense. I know it's not happening when the add-ins get updated. I plan on asking everyone to let me know the next time they see the message. When it happens, I should be able to confirm if it's an add-in or a Revit update.

Another working theory is that the conflicting schema is in a link.

@loboarch,

Does Revit generate Schemas?

If so, can you check to see if the source of the schema in the above message is Revit or, as suggested above, different add-ins generating schemas with the same ID?