Sometimes views on a completed drawing disappear and become a set of rectangles with dashed lines around them. What's hapopening and hoow do I prevent it???
Can you provide a picture ..?
I have had this happen two different ways myself. It normally happens to me in the form of what seems to just be a bug and a rebuild will bring my views back. The other reason would be that your drawing lost its link to the part/assembly. If someone accidentally or on purpose changed the file name or location of the part/assembly the drawing is referencing. You can always check your drawings references to make sure they are going to the correct file and location if in fact it isn't just a bug.
It's a bug in the software. I usually change the display style back to the other style and then it works
I have this issue a LOT. I hope SW corrects the root cause (currently using 2013). But, in the meantime, thanks for the <CTL> Q solution. I have been clicking on each view, changing to Draft Quality, and back to High Quality to fix each time. <CTL> Q is much faster
Has there been any fix on this bug?
I am experiencing the same problem quite often.Deepak Gupta
A ctrl + q normally fixes it.
Not sure if this is bug or we need to rebuild the drawing.
Still seeing this issue in 2020 running SW 2018. My computer gives me hints that it may be underpowered for some assemblies and details and that may be the true issue. Just wanted to share the experience and some hardware information in case this is always an ongoing improvement;
Hit "reset sketch visibility" and got my sketch back but none of the annotations. Closed without saving and re-opened and everything was as it should be! Keep up the good work Dassault Systèmes.
I have this same very annoying behaviour. Ctrl - Q does not fix it. This is no good! Please SW fix this!
Found some kind of workaround but this is no solution when printing many drawings in one go to pdf. Must now check every drawing when printing.
View is re-generated when I tick a "Surface Bodies" -box and then I can tick it back again.
View is also showing when I tick "Draft quality" -option, but the printout is unusable while the print quality is too poor.
I've had this happen to me today, and it is something I've had off & on over the years. Currently on SW2019 SP4.0. CTRL-Q did not refresh this time so I came searching the Forums. Draft Quality is the only way I can get them back. Toggling back to High Quality makes them disappear again.
fwiw, this has been a thing for ages. i don't even know what i normally due to fix it because it happens so often i don't think about it.
prob do a force rebuild though.
Yeah, I've seen this when resources start to get stretched thin and for reasons I'm not wholly clear on, Solidworks drawings are hogs for VRAM. It seems like if you have an incomplete rebuild this can lead to a dirty update to a view and sometimes the graphics will drop out. Usually the answer is to hide the view and show it.There aren't a whole lot of prophylactic measures you can take. Top-down assemblies and parts that use move/copy bodies operations seem more susceptible.
I have noticed that opening a drawing in Detailing mode generally improves performance across the board so take advantage of that.
first, i would like to specify using "Ctrl+Q" and thinking it's the normal "rebuld" is a bad habbit,
Ctrl+B is the normal rebuilt.
(too many people condiser Ctrl+Q as the standard rebuild and use all all the time)
for this view-bug, it seems exist since some years,
but as you all know, we are working with "Bugidworks"
and we can't expect all the bugs to be repair... that's not Dassault's intention..
the work around of "Ctrl+Q" is not perfect here,
if you have a big DRW, it will rebuild everything (maybe even the 3d, i don't remember well)
"why Force-Rebuild all the views, if you only need to repair-rebuild one view ??"
just do a "view rebuild" Tapani Sjoman give one way to do it.
here is a simplier way : right-click on the view "hide" (if SW ask for children: say no)
right-click on the view "show"
I experienced this problem few times, too. I noticed it happened on cropped and section views or on cropped and detailed views or croped and alternate pos. views. In my case, it looks like the problem was when more than an operation in the wiev is involved at the same time (section - crop - detail - alternate pos.).
Most of cases I found the 'hide/show view' suggested by The Merovingien to be working!
Retrieving data ...