OK, this one has got me scratching my head.
I've seen it happen before, just can't for the life of me recall how to fix it or what causes it.
I was sent an assembly a user created where he has subassemblies created by a few others inserted and for whatever reason, the componenets do not show up. If you select the file in the browser tree, the wireframe of the file shows up and if you throw it into Edit mode, the files show up as normal. It's when you finish the edit that the files go back to invisible.
I've checked everything I can think of and the files should all be visible.
I can select Master LOD, parts all show as visible, iProperties Occurances show the files as visible, nothing is shrinkwrapped or the like. The user has about 5 subassemblies out of about 8 that show up this way.
Any ideas?
Solved! Go to Solution.
Solved by CelticDesignServices. Go to Solution.
Let me add a little more info on this.
This issues seems to be happening within this one assembly file.
If I insert any of these sub-assemblies into a new assembly template, they come in fine.
Resolved it sort of.
Found that the Default View Rep of the main assembly was the driver in all this.
Creating a new View Rep or activating the Master View Rep solved the issue.
So the user will simply create a new View Rep and delete the Default one.
I tried the above solution to no avail. I was working in an upper level assembly and refreshed 2 subassemblies from the Vault... and as soon as I did the visibility issue occurred. I had not been having problems myself, but the person who submitted these two subassemblies into the Vault has been having problems.
Even if the above solution is workable for someone it stills is not acceptable to have to delete and recreate view reps... often they take a lot of work to create.
Understood. Yes, this work around was just that for this one instance.
I've found the same type of thing happening but it was due to a previous user setting the "Slice Graphics" or the "Section View" setting in the file and saving the file at that setting. Once those were set back to the default settings, the issue was resolved.
Not sure if that's the issue you're seeing but it would be one of the first things I'd check.