![]() ![]() the Kitchen.finish.2 option would have a room named "Kitchen" with metadata "finish.2" that would contain the faucets, cabinets and other desired assundries to drive accurate counts from that option. This with the options would make super simple counts for types VIA room metadata without having to create a myriad of other parameters. If a chase eats up 2SF it would be nice to have it report as such- otherwise rooms need to be in the Building Floor Plate layout for that level- defeating the benefits of the options in the Linked file. I still need to check if rooms in the unit plans react to new boundaries from the host model. ![]() Each time the master was edited it would generate those subtypes. and so on for all the combinations of the options from a check menu- then each of those files would accept as primary the option so there were no options in the generated files. That would allow fast switching between options and using the link name and info for QTO and counts and accurate areas, etc. I could use a master file to generate 'variant' subfiles and link those - that is the most likely scenario- or probably use Forge somehow to manage these subtype variants with save-as file names and resetting primary options. The core issue is generating the variations for the options in the links. ![]() Also each unit works as an independent object - so if depressed floors, or balconies are on different levels they track with the unit. but at least they don't add overlapping levels like shared groups do. Links Don't exactly host well to levels either. Easy options and switches- easy to flip, rotate and move around as needed. With each unit as a link- you create your own library of unit plans with other possibilities. Links unlike groups only take 1/20th the memory hit and are way more flexible. I have been toying with the idea of each unit as its own link for about a decade and decided to revisit it recently.
0 Comments
Leave a Reply. |