It is a well known problem in Revit models that linked or imported CAD files with extents that exceed 20 miles, particularly common with geolocated Civil 3D files, will cause Revit to truncate the accuracy of all objects in the model, effectively corrupting the model. There is no way to undo the damage that is done to the Revit model once a CAD file like this has been imported. Linked cad files on the other hand will not do permanent damage and can be repaired simply by removing the link. The effects include but are not limited to inaccuracies when visually aligning objects, problems with the display and printing of hatches, errors in rotating linked files, etc. This is a common problem with large, inexperienced design teams because there is almost always someone working in the model who is unaware of the problems caused by importing CAD geometry, and when it happens, the project must suffer with the consequences for the remainder of the project which are rarely catastrophic, but constantly annoying, more so because they are completely avoidable, if inexperienced staff would simply ask questions when they don’t know what they are doing.
In any case, I’m wondering if anyone knows whether this truncated accuracy has any appreciable effect on Enscape rendering. We’ve been dealing with a problem recently where an Enscape model has been repeatedly crashing. We suspect it is the usual suspects of out of date GPU drivers, rendering without a section box, and image maps that are too large, but this particular model was also corrupted by an imported CAD file and I’m wondering if this may play a role in these crashes.