Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Hi @danielius_samsonas.  Transparency status is also recorded and controlled by the DVR's, just like visibility and appearances.  So, this sounds like it will require some 'preparation' steps.  The best way to enable that level of control and functionality, keeping with your example situation, would be to open that sub assembly directly, then create at least 6 custom DVR's directly within that sub assembly.

  1. DVR1 = Both components Visible, neither is transparent
  2. DVR2 = first component Visible, second not visible
  3. DVR3 = second component Visible, first one not visible
  4. DVR4 = first component visible, and transparent, second component not visible
  5. DVR5 = second component visible and transparent, first component not visible
  6. DVR6 = both components visible and both transparent

Then save that sub assembly file.

Then, back in your 'main' assembly, you can set each instance of the sub assembly to one of those DVRs that exist within it, and can record that component's DVR setting status in the currently active DVR of the main assembly, so that the main assembly's DVR remembers what DVR that occurrence is set to.  No ModelStates need to be involved in that process, because ModelStates primarily effect 'suppression' (also parameter values & iProperty values, among others).  All that could likely be done entirely by code also, but would likely be much more complex code, due to how many sub assemblies, and how many different specific names that would be involved.  But that's a bit difficult to judge from my outside point of view, not being familiar with your exact file set.  I generally create all the DVR's I will need as I am originally creating/designing our individual model files though, instead of trying to do so from the perspective of a higher level assembly at some later point in time, by code, which makes processes like that a lot easier to manage.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)