At what point do people typically find Enscape maxing out when working with Revit? I have a huge model of a well know London landmark project that sits at around 4GB but when I open Enscape it crashes at 73% and doesn’t even get to open up.
I’m using a monster PC with an NVIDIA Quadro 16GB card, 64GB of memory and have had to ‘reluctantly’ revert back to using Lumion Pro 9 which works fine, albeit a little slow due to model complexity.
Enscape is great but a little disappointing if I cannot use it on bigger jobs?
When is a Revit file too big for Enscape!?
- RB_Design
- Thread is marked as Resolved.
-
Can you turn off less important elements, or subcategory of element. For example: Door handles is what we call a 'polygon offender' because the number of polygons it uses is way out of proportion to the small visual field they occupy.
-
All non essential elements, including those not seen in the desired image are turned off. The model is also cropped to include only the region itself. Turn off any more and there’s no point in using the model.
The problem is that the space is so vast and yet includes so much (previously a famous Power Station in South London!) that even chopped down, the model is still huge and I feel, too big for Enscape.
-
I had the opposite experience where Lumion buckled early on a Stadium Job but Enscape worked flawless at about 3+Gig on a much lower speck comp than yours
I certainly did a good purge before there where about 11 linked files.We commonly use Enscape with 1-3 gig files without any issues.
-
Michael Ruehr Just out of curiosity, how long does Enscape take to load your model?
There's this model I'm working here, about 400MB with 2 linked files (50MB each), and Enscape is taking 15 minutes to load it - we also have a good hardware here, so I don't think it should be the problem. My guess is that the texture maps we're using are really heavy. Could it be it or is this initial loading time is normal?
-
Have you send Feedback after failing to open the model? The log files should give us an indication if you're really limited by your system's resources or if something else goes wrong.
-
It could be your material maps. You can test this by creating a phase to temporarily disregard all materials (just white or greyscale). Can you open the model? You may want to downsample any 4k textures to 1k or 2k to save memory.
-
Can you incrementally build the scene up, loading links 1-by-1, to isolate the culprit, to focus your troubleshooting?
Knowing the project, the models aren't built like-for-like, so whilst I also shudder at the thought of turning off door hardware, if you've MEP models loaded, there'd be my first go to to kill off sub-cat. junk. Likewise sub-nested .dwg content hidden in .rfa. All the usual bad stuff in Revit hurts Enscape considerably - but then, so do a lot of proxies.
I'd also echo Phil's thinking that render assets are playing a huge part - but more again in terms of parity between the models than mega texture maps.
Q. Is this for an entire site walkaround export? On sites that scale and style I'm surprised you're not going the teleported panaroma route.
In the end, there's always putting in a purchase order for that Titan.
-
I have multiple projects with surely over 4 GB of rvt file. Enscape export to exe is 1 GB and never had a memory issue.
Rendering on PC 32GB RAM, nvidea RTX generation. Rendering time can be 10-20 min, but that is ok for todays hardware. -
Thanks for the feedback. I attempted to load it up gradually and believe the culprit to be a ceiling panel file (the ceilings across 6 storeys are broken up into several thousand small panels! ?). I managed to get everything loaded and saw it briefly in the Enscape window before it crashed again.
I’ve requested the standalone from the Architect so I can circumnavigate the problem. Wasting too much time on loading and continuing my hate for all things Revit! ?As for that Titan...?
Glad to hear it's working finally (hopefully). As for the 'Titan', I wouldn't bother with anything less than the newly released 3080 or 3090 cards (the latter being the 2080ti or Titan equivalent this generation, though it's possible they could release an even faster variant in another year or so and call it 'Titan'). As of now though, the 3090 will knock the socks off of any Titans, and comes with 24 GB of VRAM to boot ( the cards appear to be around 50% faster than their previous generation predecessors, even more so when you start factoring in RTX performance).
-
Interesting thread, and helpful to boot. I'm also running into lags, and some crashes, but our models are nowhere near the size mentioned above. The latest one is only about 280 mb, but utilizes a few (10+) linked in models of about 10 mb each for a Multifamily project. These are then copied around the project. I'm using only about 22 assets of trees, cars and people. I was rendering a few shots the other day with full materials w/o difficulty (ultra), and then I changed the cameras position, and out of nowhere, i get the 'this is taking too long' error (and yes, sent the feedback immediately). Enscape and Revit crashed.
I've restarted & reloaded, tried doing a 'white' render - I was able to get (2) renderings - but I then moved as before - and every time I try to render I run into this 'too long' error now. This then crashes Revit and I have to restart the machine; I can't even just restart Revit as it locks up the access to the Browser or Properties panels ?!?
Is there a limitation on how Enscape looks at or handles Linked models, even if out of view?
I've upgraded the Nvidia drivers to the latest/ latest Enscape Build/ Revit is 2018.3 -
Machine is an HP Z640 Xeon w/32gb ram with a Quadro M4000 video card / Win 10 pro
below is not a render, but a screenshot of a sample image of the model.
PS - Hey Phil Read - (If you see this) Long time no talk! Hope all is well! -
Recently, I've been experiencing more crashes with Enscape than ever before. I have a quadro RTX 5000 Max Q card in my laptop with 16 gigs of VRAM, which until recently could operate our largest models quickly and render without problems. The problems started somewhere towards the end of the 2.7 builds, through 2.8, and has continued into the latest 2.9 preview.
One interesting symptom to note... when launching Enscape or changing view settings that cause it to re "print" to the engine, sometimes my entire system will freeze until the process is finished. This never happened in the past. By freeze, I mean audio output would stop, mouse would freeze position on screen, etc. Eventually it usually recovers and resumes normal operation within 1-3 minutes.
I know that I push the limits on textures and model details, which is why i buy the best hardware available (within reason), but Enscape used to handle it without issue.
FEATURE REQUEST....
A tool in Enscape to generate an exportable listing of all the textures in use in the model, providing their name, path, and pixel dimensions. This would help users realize when they are using something that's too big, not found, or not necessary.
The tool could also report how many polygons are active in the chosen view in Enscape
Pretty please?
-
Whilst I like the suggestion of (some) "scene analytics" for troubleshooting - I fear it's the very addition of extras to Enscape in recent versions that have probably added to the bloat and erratic-crash behaviour - AXYZ library assets, RTX, BIMmy-query & coord. stuff are all great (when/where required/desired) - but personally I'd rather push back for a leaner approach - with more focus on scaleable controls (for larger scenes / weaker spec. environments) ala sliders for geometry tesselation, draw distances, hidden-element suppression, etc...
In other words; (I believe) render material asset management (Revit, Rhino, or otherwise) needs to be handled at pre-authoring side (as in, it's far too late to wait on Enscape to tell you you've 100mb textures in your scene)
This extends beyond the production environment - where we might all be rocking big rigs when end-clients often do not. And whilst yes, I/we can send a client an .exe with helper notes to "dial back to draft" - it's not as customer-facing as preparing the like for them in the first place, in the same way we might downsample larger presentation document formats for viewing on "weaker" (less powerful) hardware. Same-same for HD v 4K, etc.
A tool in Enscape
