I gave it a try.
The assembly I'm working on is in another assembly.
So I open the latter and no problem.
I'm a little lost ^^.
I had the same problem recently,... incomprehensible. up-to-date driver... I had just recorded QD I had this problem... I could reopen, turn off the PC... Nothing helped, the only solution I found to solve my problem was to make a take-away composition, give it to my colleague who opened it without problems, re-record and give it to me... The problem was solved...
But my drivers were up to date...
Hoping it helps you.
2 Likes
Fab camp.
For you it worked. for me it's worse ^^.
He put me in the assembly right away.
while on my job there was none. .
Mystery mystery.
Do you have any toolbox elements?
1 Like
Gt 22.
No toolbox for me.
1 Like
Is it possible to see the feature manager thank you
1 Like
What version of Solidworks do you have, and which Sp????
1 Like
Do the symptoms recur regardless of the display mode (shaded, wired, etc.)?
1 Like
I did a new sub-assembly on the buggai as well but no improvement on my first one.
Here is my creative abre
and I'm in Solidworks 2016 SP2
edit: Stefbeno.
yes I have the same thing in filirary as in shaded
sans_titre3.png
It is absolutely necessary to switch to SP3 which solves many bugs!!
2 Likes
I may have found a cause.
When I do a double click wheel for a zoom at best, I can't see anything. So I think there must be a lost element somewhere that I can't find.
Even if I delete all the elements of my assembly, when I zoom in at best (double click roulette) I am super far from my original assembly.
test by removing your symmetrical component
symmetrical sheet metal components among others
often put the souk ;-(
1 Like
WG 22.
I deleted my systems and nothing helps.
I think I'm going to have my assembly to redo.
Updating to SP3 2016 is mandatory!
It's normal that you have more bugs in SP2 version...
2 Likes
Problem already encountered on versions prior to 2016.
Radical solution: insert the assembly affected by "spasmophilia" into a new assembly, decompose the latter, then record by overwriting the old one.
Well, a few downsides between the assembly functions, configurations, constraints... which evaporate as a result of decomposition...
To see, if your assembly allows it, if this walkthrough solves your problem
1 Like
I'm seeing if I can mgr in SP2 according to PDM.
for the moment I have redone my assembly from scratch ...
Thank you to all of you.
A little feedback from a school that had had the problem, it came from the constraints and from one or two in particular.
He had put them all in a deleted state and then reactivated them one after the other while moving the assembly to see which one was bugging him.
3 Likes
Indeed @Drix49, it also brings back memories of Solidworks 2012 now that you talk about it!!
Kind regards
1 Like
Drix 49.
Indeed I tried to insert it in an assembly and no more bug on the other hand I didn't know that you could break it down :/ .
In any case, thank you all.
Hello
I also have this problem on a regular basis, as unpleasant as it can be, it seems that it is only visual.
I found that it was usually due to the collision between two complex surfaces belonging to two different parts stressed to each other. The solution is to find the surfaces in contact, and to release one of the two parts and then recreate new constraints.
1 Like