Independently from the feedback above, I am also curious to understand more about the bottleneck between Revit export and model loadup in Enscape. NVIDIA drivers are up-to-date as of today as well. I am on an Alienware R15 with an i7-7820HK, GTX1070 and 32GB RAM.

I have immediate use for some of the features in more recent versions of Enscape and would prefer to use the most current build, but unfortunately I am finding that impossible with respect to usability for some reason. and the difference in smoothness of navigation once the model is opening is night and day (and that's an understatement). After crippling startup times and completely unusable lagginess in recent and current (as in today - 5/23/19) Enscape builds, I just rolled back Enscape to 2. nearly all of our bitmap textures are now under 1600px square and 1mb, and most are much smaller, with perhaps 6 exceptions that might be 3000px square and 2.5mb. For what it's worth, we have recently gone through all of the textures in this model to eliminate large file sizes and resolutions. While I understand the ongoing status of texture resolution and downsampling treatment in each release, either this is a huge issue for the model I am working on currently, or there is something else at play. I do not expect Enscape to work magic in processing such large amounts of data, but it seems like lately my load times have increased substantially and I would like, at a minimum, to develop an understanding of why. I am using Enscape to render complex Revit projects with several Revit links and large numbers of RPC Entourage coming from Archvision.

Enscape revit slow