Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
WCrihfield
in reply to: jdasilvaS39UQ

I honestly haven't messed with the new ModelStates that much yet, because I didn't use the level of detail settings that much either, in favor of using the design view representations.  But basically the main purpose/use of LevelOfDetail representations was to help conserve system/session memory by not loading components into memory when they were set to suppressed in that level of detail.  So, essentially you could create a level of detail representation of your main assembly in which most of the components were suppressed, then specify that representation when opening that assembly, and it would be similar to opening the assembly in Express Mode, but even better, because none of those components would be loaded into memory when you opened the assembly.  So, since the new ModelStates are the direct replacement of LevelOfDetail representations, I'm assuming they can be used much the same way, but with way more uses/functionality now.  In short, yes, if you wanted to take advantage of this scenario, since all new part/assembly documents only have the 'Master' ModelState, you would have to create one just for this purpose in each document.  May be too much work for your purposes here, plus it complicates things a bit.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)