Revit 2022 Crashes while making changes in Material Browser

[neniapoloh]

My Revit crashes when I am making changes in Material Browser, especially while duplicating a material. First it freezes and after about 10 seconds it just disappears fast. No warnings or error reporting window. Just swift crash. I've installed everything again, updates are up to date and graphics card has been updated. Using BIM360 Cloud. This has now been going on three moths or so. Any ideas what next?

[sdbrownBECK]

It doesn't matter if Enscape is running only installed, move the addin out of the addin folder and I bet you wont crash anymore, move it back and it will crash.

[DrakeCanyonArchitecture]

Which brings us to another issue, we should have the ability to turn add-ins off and on without having to go into the folder structure to move files back and forth to do so.

[Quinn_Knudsen2]

Can confirm that this does not work. Material browser seemed to run more smoothly, then crashed immediately once I clicked out of it. Same end-result. 

[sdbrownBECK]

Quinn,

That is interesting, all of our people who have this issue if enscape is removed it goes away.  So you may have a different issue.  We also found pyrevit along with enscape causing conflict and performance issues.  Not specfic to the material browser though.  

[DrakeCanyonArchitecture]

I know this to be true (as @Quinn_Knudsen2 mentioned) now that I think of it because I was walking a friend of mine through some material edits online last week and the same happened to him, and he has never used either of the add-ins that you mentioned (Enscape and Pyrevit). I had him change a fill pattern on a material and 'poof', Revit disappeared.

[rwiancko]

This was happening to me a lot, but Enscape has never been installed. Haven't had it happen in 2023 Revit though.

[esosa.osayamwen]

Do you mind sharing your pc specs, might be an issue with an old graphics card because Revit is trying to render a 3d view using realistic mode? 

[Quinn_Knudsen2]

(Alienware m15)

Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz

32.0 GB (31.8 GB usable)

Windows 10 Enterprise

NVIDIA GeForce RTX 2070 Max-Q

[Quinn_Knudsen2]

Bump. Still a constant problem. 

[esosa.osayamwen]

I never even thought of bumps. But I have just been recently having my Revit 2022 crash as well on this new project when I change/making edits to materials. And I found that there was a curtain wall family with multiple instances of that material so every time I made a change/edit to that material, all those mullions would have to go through all that change 

[DrakeCanyonArchitecture]

It happened to me again today. How do we get Autodesks attention? I've lost a lot of time and work due to this. It would be nice to know that they are aware and looking for a solution.

[barthbradley]

---

@DrakeCanyonArchitecture wrote:

How do we get Autodesks attention? 

---

Open a Support Case through your Account Portal.  

[sdbrownBECK]

We have been working with both autodesk and enscape on this.  We have now verified that even uninstalling ALL addin's we can still make revit disappear by duplicating a material asset.  The tricky thing is it may take 10 or 12 duplications vs only 2 when enscape or pyrevit is installed.  So something has changed from 2021 to 2022 that causes this.  We can't reproduce the crash in 2021.  If you watch task manager you will see the material asset renderer or something like that running.  I'm curious if that app, that basically offloads the rendering of the asset is the culprit.  I found that if I make sure to close the asset tab before closing the material i can switch between materials quicker, but after a crash it will crawl while trying to render those assets, before a crash you can switch from material to material very quickly.  So what autodesk has asked us to do next is uninstall revit and the material library and reinstall it.  We will do that next week.  I don't think it will help as we have multiple machines that this occurs on and even on our remote desktop which is "clean".  Anyway combined our company has spent at least 40 hours purely troubleshooting trying to find an answer and haven't yet.  

My workaround to teams is awful, but I can't think of another workaround.  The workaround is to have 2021 open, create and maintain all materials in a project in 2021, then transfer those to your 2022 model when you are ready.  Otherwise you will crash and lose work.

[DrakeCanyonArchitecture]

I haven't tried this at all as it just crossed my mind but I wonder if you could save all the materials that you commonly use to your own library and unload all the autodesk materials that are installed ootb. I just wonder if some of the materials themselves trigger this. I may try this tomorrow when I'm back at my machine. I've never tried to unload all of the ootb materials, but it almost feels like this could cause some issues in itself when certain families are looking for the materials that are assigned to them. This is a pretty messy issue.

[Quinn_Knudsen2]

I'm curious if this works.

I've tried Purging all unused, but it didn't actually get rid of much. Completely deleting them might help. Although, this would be a bandaid fix. The problem of the Material Preview Generator spiking CPU will still exist. 

[sdbrownBECK]

So we have identified the issue with autodesk and they can reproduce it.  Its NOT enscape.  It happens when duplicating an asset.  So the solution we have now, is do not duplicate an asset, if you need to change the appearance of an asset instead replace it with one of the OOTB "locked" assets, then just rename it under the information portion of the asset dialog box, then update the image maps as desired.  So far this works all the time and since the OOTB assets are locked you won't mess them up. I hope this helps.  

[jessglowacki]

The best way to reduce the amount of computer memory and cpu is to go into the material library and change the settings to be text view instead of the default!  Has worked wonders for load time and performace on projects in the cloud our not...

[Quinn_Knudsen2]

Just as an update - I'm back doing another rendering project in Revit 2022 today, and Revit is back to crashing when using the material browser. Even escalations with an autodesk team member have ended with no result. It's absolutely ridiculous. 

[sdbrownBECK]

Autodesk put out a solution, and so did it, the key is to NOT duplicate assets. But use the library feature or just replace the asset with one close, rename it and then update the image maps as needed.  

Option 1 - From Autodesk

According to the team, instead of duplicating asset maybe we could try replacing the asset from asset browser in the same type as suggested in the steps below:

1. In the Manage tag, click Materials.
2. Select a material in the list, say Aluminum.
3. Activate the Appearance tab and in the upper right, please remember the appearance name, let's call it "Satin", click replace button. Then asset browser is opened.
4. In asset browser, create lib1.
5. In asset browser, search "Satin", right click on the searched out "Satin", add to "lib1".
6. Select "lib1", Rename the "Satin" to "Satin1"
7. Go back to material editor, click replace button, select to lib1, click replace on "Satin1".

In this workaround, the replaced asset is similar to the duplicated asset.

[alek.gilotLYP5E]

1. It was never solved, the crash continue , the solution doesn't work at all for anyone, It a bug program , assuming no fix will come for 2022 ?   , as always  keep paying for no improvement for 10 years (since Autodesk buy Revit ) 
2. and as usual blame the other compagnie like "enscape",or "pyrevit"  there is absolutely no relation in this bug but  the crap the programmers did at Autodesk ,    soo  NOT SOLVED  ,   any fix in the future for  Revit 2022. ? 
3. "replace it with one of the OOTB "locked" assets" nope within a family just material "by default"