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: claudio.ibarra

I just did a couple more tests related to this, and in a Part with 2 ModelStates, and 1 FinishFeature.  I am able to change the 'appearance' by changing the FinishFeature.Appearance property's value to a different Asset object.  But even though I can get the parameter associated with that feature by looping through FinishFeature.Parameters (indexed by Integer only), access is denied to change that parameters value.  I even tried to manually enter 'edit mode' of that feature, then open the parameters dialog, just to see if we could change the parameter directly while the feature was in that state, but it will not allow both dialogs open at the same time, and the FinishFeature object does not have an Edit/ExitEdit type methods to enable that process anyways.  So in conclusion, if using a FinishFeature, we can only change the Appearance by editing the FinishFeature, not by changing a parameter value directly.  And while MembeEditScope was set to active member only, and I edited the FinishFeature to a different appearance while different ModelStates were active, those individual ModelStates did not have a different value for that Finish Parameter, and simply switching back and forth between the two ModelStates afterwards did not change their appearance.  I tried the same thing with DVRs...I had two of them (Primary and View1), edited the FinishFeature's appearance differently while the two different DVR's were active, and afterwards, switching between the two DVR's did not change their appearance.  And when opening the ModelStateTable in Excel, those Finish Parameters were not even listed in the table.  So, I believe the long standing route of just using different DVR's, without FinishFeatures, is the way to go here.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)