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: rprivittB3TTG

OK.  So if you do a fresh resize of the model using your form's slider, then open your iProperties dialog box to the Physical tab, then click the Update button, it is not changing the Mass value being shown there, correct?  Have you tried clearing any overwritten value from that Mass text box, then redoing this process to see if it is any different, just in case the overwritten value is 'static'?  If you keep getting the same results, and the cut process isn't changing the Mass of the part, that is definitely a troublesome issue.

 

If you believe that equation is producing the proper Mass value for you, then I don't think you would need any iLogic at all.  All you would need to do is create that user parameter with that equation in it, then set that parameter to be exposed as a custom iProperty by clicking the checkbox in the 'Export Parameter' column of the parameters dialog box.  That automatically created a matching custom iProperty from that parameter.  That iProperty will automatically be updated every time the parameter's value changes.  But the update won't go the other way (updating the iProperty won't update the parameter).  You can then right-click on that parameter's row in the parameters dialog, then choose 'Custom Property Format...' to customize how you want the custom iProperty to be formatted/displayed.

 

If needed, it would be fairly simple to create an external iLogic rule that would:

  • create the user parameter (NewMASS)
  • set its equation (assuming the 'LENGTH' parameter already exists)
    • 'LENGTH' appears to be a 'Model Parameter', is it already named this way in all other models to be processed?
    • if not, but the parameter exists with a different name, we may have to deal with that in the code
  • expose that parameter as a custom iProperty
  • set the custom formatting for that custom iProperty

Does this sound more like what you would want/need going forward?

Wesley Crihfield

EESignature

(Not an Autodesk Employee)