CAD Forum

I am just going to rant here..

I don't expect an answer, for >10+ f@#king years this issue has plagued me like a curse.

Through multiple versions of software across several Windows OS'es and several machines,

this damned issue is relentless. I have seen this since forever. No VAR has ever been able to provide anything more than suggestions for rebuild.
I have never been able to positively guarantee this will not occur.
It would have to be the single most frustrating thing I have ever experienced with this bloatware that consistently fails to reliably deliver a core functionality without considerable frustration and time wasting.
It can occur across the board without rhyme or reason.
Opening old drawings. Creating new drawings. Regardless of which version created in, or last saved in.
I have had easily a half/dozen tickets in the system to repair this.. And again, today several times on 2022 FFS..!?!?!

Thank you for hearing me , my rant is done....

I had a sImilar experience, open a drawing and it suddenly explode in my face, not replicable, I rebuild the file, close and reopen and the view are fine again like nothing happened...

2022 sp5

Hey Damo, lucky you, I've ran into very similar issues

There's a few things you can look into.
-Make sure all files of the assembly are in the current version.
-View quality can sometimes cause this. IDK why but sometimes SolidWorks sets the view quality to draft and setting it back to high quality fixes this. I spoke of this in a thread on the previous forums of SolidWorks a while ago. This is the view quality I speak of Check these two out, if it's still occuring, check if you have something that is rebuilding constantly. If so, see if you block the featuremanager of that part if it fixes the issue. If it's an assembly, find out what's causing it within the assembly.

Do you have flexible assemblies? This sometimes caused this to us.

I've also seen it a number of times, but never found a cause. A Ctrl+Q rebuild will occasionally fix it, but when that doesn't work I can usually fix it by copying and pasting the sheet, then deleting the original one.

Glenn Schroeder wrote: ↑Thu Oct 05, 2023 9:01 am I've also seen it a number of times, but never found a cause. A Ctrl+Q rebuild will occasionally fix it, but when that doesn't work I can usually fix it by copying and pasting the sheet, then deleting the original one.

Glenn, your idea of copying the entire sheet is a new approach I've not thought of.
I'll be adding this to my list of tricks for next time.

AlexLachance wrote: ↑Thu Oct 05, 2023 8:49 am Hey Damo, lucky you, I've ran into very similar issues

There's a few things you can look into.
-Make sure all files of the assembly are in the current version.
-View quality can sometimes cause this. IDK why but sometimes SolidWorks sets the view quality to draft and setting it back to high quality fixes this. I spoke of this in a thread on the previous forums of SolidWorks a while ago. This is the view quality I speak of

Check these two out, if it's still occuring, check if you have something that is rebuilding constantly. If so, see if you block the featuremanager of that part if it fixes the issue. If it's an assembly, find out what's causing it within the assembly.

Yup.. I've done this too.

Sometimes cycling thru different view options will fix it.
Sometimes rebuilding the model in modelspace will fix it.
Sometimes it a matter of deletin the view and recreating is required.
Sometimes restarting the software will overcome.
Sometimes none of the above.

AlexLachance wrote: ↑Thu Oct 05, 2023 8:49 am Do you have flexible assemblies? This sometimes caused this to us.

OMG.. This is a fun one all of its own. I have had multiple run-ins with this particular fun aspect. Usually it is just a flare=up in the feature tree of mates that don't realise, or seem to forget, what they are meant to be doing. Generally a simple Ctrl-Q fixes this.
I do like flexible assemblies, and I do use them. But this was NOT the case this particular time.

Even so, all workarounds aside, It kills me any of this is necessary for a core function of the software that remains troublesome across so many variables, for so long.
It's enough to drive a sane man to violent destruction..

Thanks guys.