I was expecting the worst, but I managed to render an image with no problem and even a video render seemed to go without a hitch. This cleared out some stuff but didn't really change how it behaved in SketchUp (as expected) ^tip don't even try to use 'remove duplicate faces' unless you have 3 weeks to spare. SketchUp Plugins | PluginStore | SketchUcation But, you have come this far already to have made it, so I guess you are already aware of that!Īnyways, I ran a basic CleanUp 3 on it (which took a 3 minutes)

Now obviously it is a big model - trying to render this many edges comes with the performance hit you might expect. So I've just been having a look at this alongside my day to day SketchUp tech support for the UK That way you can still apply the level of detail onto the individual buildings yet keep a somewhat 'light' and usable main model.Ĭontinuing on your current path (all geometry in full level of detail in one project) will sooner or later render your project unusable, which would be a shame. Plugins like Enerorth Reference Manager will help you to achieve that. I strongly suggest applying the basic principles of using SKP in larger projects - splitting up the different buildings into different projects to tie them into the main project using proxies. SKP is not made for high poly situations and tends to crash or become extremely slow when confronted with a workload of that magnitude. With that face and component count no wonder SKP/Enscape tends to be rather crashy. Afterwards I checked the statistics, this is what we got: First of all when opening SKP already detected a myriad of problems w/ the geometry it tried to fix (and succeeded). Downloaded the file, also have a rather beefy workstation though this file definitely brings SKP to a halt, didn't even dare to open Enscape.

Enscape rendering