It used to be that when we used the enscape material editor in Revit, we could tweak materials on the fly and immediately see the results in Enscape. But in the newer versions of Enscape, most changes in the material editor will cause a reloading of the scene (enscape and revit are locked while the model re-exports). This is really slowing us down when tweaking materials.
I should note that you should test this is a real production model, not a small test project. Updating times for materials in Revit go up (sometimes exponentially) with the complexity of the project. If you test this on a small sandbox project it might update so fast that you don’t even notice it, but in the production model I’ve been working on this morning, I’ve spent 90% of my time for Revit/Enscape to update.
Bump. @Demian_Gutberlet is this a known issue?
@Pieter_2 , please pardon the delay - This behaviour could be normal depending on the circumstances. How large is the main project in terms of mb/gb with which you experience this? And also, what are the system specifications of the machine you’re running the scene on? (GPU, CPU, RAM suffices)
-
The Revit model size is approx. 500mb (BIM360)
-
GPU: NVIDIA GeForce RTX 3070 Laptop GPU
-
Processor: Intel(R) Core™ i7-10875H CPU @ 2.30GHz 2.30 GHz
-
RAM: 64,0 GB
The older behavior where I could tweak materials without having constant reloads in Revit was much more efficient to be honest.
Thanks @Pieter_2 - Is there a chance for you to send the project over? I have a rather similar system so I’d really like to check it out myself if possible to determine if this is normal. (Via wetransfer.com and the link through a DM would for example)
I sent you a download link through the DM!