All,
Good afternoon! I've had a rather strange time with a particular asset that appears to have a "safety" value hard coded into it. I'll let the video show the issue in more detail, but essentially I setting a minimum size with some construction geometry and Reference parameters. However, when the design scope changes, the resulting new minimum values (Reference parameters) do not appear to update, almost as though the value is hard coded into the asset when it was published. Any thoughts on how to get around this? Please see the video below and I've included a copy of the asset as well. If you have any questions, please do not hesitate to contact me. Hope all is well and have a most blessed day!
Peace,
Pete
Solved! Go to Solution.
Solved by petestrycharske. Go to Solution.
All,
Good afternoon! Has anyone had any thoughts on this? I'm finding that I can do something similar using the volumes of solids, but it is much more cumbersome. Is there a way to use the reference dimensions to do the comparison. I'll revisit the code and play with the order a little bit, but was just curious if anyone noticed anything that I was doing wrong. If you have any questions, please do not hesitate to contact me. Hope all is well and have a most blessed night!
Peace,
Pete
All,
Good afternoon! After doing some experimentation, I think I've figured out how to drive the reference parameters the way that I need them to work. In order to clarify the explanation, please see the Screencast video below. The fix involved creating some reference (construction) geometry that was driven by the reference parameters and then setting up the "Model Parameter Change" iLogic trigger. This seems to be doing the trick and made the asset much less complex than trying to compare the volumes of individual solids. If you have any questions, please do not hesitate to contact me. Hope others find this useful and have a most blessed day!
Peace,
Pete