Isolate/Unisolate Defect

[ca_steve_foobar]

There appears to be a defect in the Isolate/Unisolate functionality. This is an intermittent defect. Sometimes all assembly components display correctly in Hybrid Mode when the root assembly Activate is on. Other times, some of the sub-assemblies do not display correctly even though all sub-assembly components have their individual visibility turned on. Toggling the Isolate/Unisolate option for a sub-assembly, often suddenly corrects the display problem.

There may or may not be an interaction with the Activate Icon defect I created just prior to this defect.

I'm on Windows using an AMD RX570 series graphics card with the latest drivers, but I doubt it is a graphics card display issue.

[dsouzasujay · Accepted solution]

Hi @ca_steve_foobar ,

Thanks for reporting this.

Since the behavior is intermittent, could you please share a few additional details to help us reproduce it?

• A short video showing the incorrect visibility state and how Isolate/Unisolate restores it
• The affected Fusion dataset as an F3D or F3Z
• Your exact Fusion build number
• The exact sequence of steps leading to the issue, including which component/subassembly is activated or isolated
• Whether this happens only in Hybrid display mode or also in other display modes
• Whether you can reproduce it in a newly created assembly or only in this particular design

Since you mentioned a possible relationship with the Activate icon issue, please also let us know whether the visibility problem occurs only after activating/deactivating components.

With the dataset and video, we should be able to better understand the component visibility state and try to reproduce the behavior.

[ca_steve_foobar]

I'm sorry but I don't remember what model I was working on when I noticed this. I don't seem to be able to reproduce it in the latest version that was just released. I would suggest we close this. If I notice it happening again, I will be more careful to document it with screen captures and save the design I see the issue in.

[dsouzasujay · Accepted solution]

Hi @ca_steve_foobar ,

Thanks for the update.

No problem at all. Since you are no longer able to reproduce the issue in the latest version, we can go ahead and close this for now.

If you notice the behavior again, please feel free to reopen the discussion or create a new post. A screen recording, screenshots, and the affected design file would be very helpful for further investigation.

Thanks again for following up and letting us know.