Random components suddenly transparent

[RobinMahler]

As the title says, I'm having this issue right now after having edited a design file with ~20 components.

I went back in the timeline to create some features, for which I isolated and activated certain components, but the components that are now transparent are partly the ones I isolated and partly others.

I tried setting their opacity to 100%, changing the material and also tried disabling the "Active component visibility" option, to no avail.

The only way to get them to be fully visible again is to actviate them. If I then go back to activate the design they're part of, everything else pops in and the 5 components become transparent again.

The behvaior is the same on nvidia and on AMD GPUs.

[TheCADWhisperer]

@RobinMahler 

Can you File>Export your *.f3d file to your local drive and then Attach it here to a Reply?

[RobinMahler]

I can't share the file publically (technically under NDA), so I tried to send it to you via DMs, which didn't work because it seems you disabled the DM feature. Not sure what to do now

[TheCADWhisperer]

---

@RobinMahler wrote:

 Not sure what to do now

---

Pinging @jeff_strater 

[RobinMahler]

No updates yet. Parts are still transparent and I can't get them to show up normally.

This is a pretty significant issue along with the random jumping of the view point once the mouse leaves the screen 😞

[jhackney1972]

Can you capture a screen shot of the condition and post it?  By the way, you can attach models to Private Messages even if the one you were trying to write to is allowing Private Messages.

[jeff_strater]

I understand not wanting to share the design, but hopefully you understand that, without it, there is not much help we can offer.  I have not seen the behavior you describe before, so I cannot explain why it happened, or how to fix it.

If you export it as F3D or F3Z and re-import it, does the imported copy retain the bad behavior?

[RobinMahler]

Exporting and re-importing it didn't fix the issue. I went back a few iterations from before this happened and made all subsequent changes anew. The part is fixed now but I still don't know what happened to it previously.