![]() ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |