12/11/2023 0 Comments Sketchup make components unique![]() ![]() I have not taken the time to recreate the issue with fresh files, as it would be a fairly involved piece of work to recreate, but I am willing to give it some effort if it could help fix a problem in the software. ![]() I appreciate that all of this is difficult to follow, and I would be willing to upload my files for inspection and further discussion, but as a result of performing and saving this “Make Unique” manoeuvre in my work file, then saving it to my DC file, I no longer have the non-unique sub-sub-sub-component to do any testing with, and you won’t see the effect I’ve described. After I did that, all parts of my derivative DC imported as expected: the problem sub-component was given an unique name and all it’s attributes appeared just as I had saved them in the derivative DC file. I was able to fix the problem by using the “Make Unique” command on the problem sub-component.It might be the case that the component-stomping behaviour only happens to the most deeply nested sub-components of a hierarchy of nested components.I cannot say for sure, but I don’t think I intentionally made that sub-component unique in my derivative file, so it’s not entirely clear to me why it did not also experience the same sorts of problems. Another highly-edited sub-component of the derivative DC experienced no such interference from it’s counterpart in the original DC. ![]() Even though the problem sub-component had been edited in my work file, and the whole DC saved to its own file, once imported (in the presence of the original DC) that one sub-component’s attributes were stomped and it inherited the attributes of it’s original counterpart. The other sub-components which had been edited in the derivative DC imported with uniqueified names (Jamb#1, #2, etc.) as expected.The formulas changed to those of the original’s counterpart, and even after changing the name in the working file and then re-importing it, the name, formulas, etc. Everything about the derivative component worked as it did in the working file where I made it, except that one sub-sub-sub-component was seemingly swapped for a corresponding sub-component in the original DC, holus bolus.Here are some observations I made while experimenting with importing these components: The derivative DC was consistently altered by the presence of the original when imported into a new file, but the original seemed not to be so influenced by the derivative if imported second. I was able to recreate this effect inside a new file by importing the two DC’s in different orders. To make a long story short (well, maybe I’ve already passed that mark), I determined that once having imported the original rectangular Window DC into my house model, the derivative Raked Window DC inherited at least one of the sub-component definitions from it’s rectangular ancestor. One component of the imported Raked Window DC had some unexpected dimensions. Once the geometry and formulas were all working, I saved my Raked Window DC to it’s own file, then imported it into my house model. Among other things, I changed the name of the DC so that once installed in the house model I would be able to easily distinguish the raked derivative from the rectangular original, and I made one of the side jambs unique so that they could have different lengths and renamed the two jambs (including “left” and “right” in their names). I then needed to build a derivative of the basic window model (in this case, one with a raked top), so I opened my Window DC working file, saved it as another working file, and edited the Window DC to have the features I needed. It all worked as expected and saved me a lot of time generating detailed measurements of the parts for multiple sizes of my window design (so far so good). My workflow for creating and using DC’s like this window model is not to build the complex DC in situ in the full house model, but to create a working file in which I build my DC in the context of some critical elements like bits of framing, trim, etc., then once it’s all working as expected, I save the DC as a separate file, then import it into my house model and create all the various instances of it as needed inside the main model. The Window DC contains a bunch of sub-components which resize and reposition themselves, and several of the sub-components contain nested components, with a maximum of 3 levels of sub-components. I built a rectangular window Dynamic Component for an architectural model I am working on. I have encountered some unexpected behaviour while creating and importing dynamic components, and I am not sure whether I have stumbled on a bug, or whether my mental model of how these things work is not complete enough to anticipate SketchUp’s behaviour in a fairly complex (and possibly unusual) situation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |