assembly has display problem. while if i open it's sub-assembly, the display is correct.
Any solution? Thanks.
shaded with edge mode is showed as this
shaded mode is like this:
Thanks all for your thoughts.
i found the solution !!!
1) it's the problem of the specific assembly file. i delete all the parts in the assembly and created new part there, it still displayed wrongly. so i think i should leave that assembly file and try to move everything to a new assembly file.
2) so i created a totally new assembly file, insert the whole problematic assembly file. everything is displayed completely normal.
this issue is with this specific assembly only. other parts and assembly are opened correctly.
I already tried to save this assembly as another name, the problem is still there.
how to save the assembly?
can you post your computer spec along with the video card including its driver ?
Is the one part set to transparent?
Is this an imported assembly?
Could be some bad/flipped surface normals, file translation errors.
I am with Glenn, this looks like transparent or more likely to me, Envelope.
Check the properties of the part/assembly showing odd and see if it is an envelope.
I've encounter this similar type of problem before when i was in SW2017 SP3 where an specific assembly showing that type of your problem but if i open other assembly there is nothing wrong only the one assembly is problematic.
SO: Use your VAR that what they are paid for,
I send the assembly to my VAR and they say nothing is wrong (I hope they diagnose it) they advised me to:
1, Update my graphics driver
2, Update SW to SP4
3, Registry Reset (But Back up your registry first before resetting so that you can return where you can from)
4, Last resort Clean Uninstall (I do not recommend this)
But most off all contact your VAR so that you will get money back guarantee
While that "solved" your problem this time, all it really did was go around the problem and left it there. I would suggest that if that assembly can still be had you should so a pack and go with it and send it to your VAR to determine what the problem was. It is likely you will have the problem show up again and it would save time for you next time to have a correct solution rather than just closing and starting the whole assembly over.
Retrieving data ...