SP2 Drawing bugs?

Sense installing SP2, I'm having lot of trouble with drawing views disappearing in drawings. The only way I can get them to come back is to turn the view into a shaded view and then turn it back to wireframe.

Also, section views are partially disappearing and only appear when you make them shaded. I have all approved cards and drivers.

Anyone else seeing this?

Reply to
McBurger
Loading thread data ...

Same thing here just reported it to our VAR a total PIA

Cheers Dennis

Reply to
cadman800

I have seen this behavior in SP1.1. Unfortunately it has been with some assembly drawings that were too large to send to Tech Support.

Ricky Jordan

McBurger wrote:

Reply to
Ricky Jordan

Same here. SP2.0

WT

McBurger wrote:

Reply to
WT

If you mean by disappearing that object lines dissappear with only dimensions showing, this has been going on since sp0. I did get an SPR for this. It is a real PITFA when opening a drawing to print, you have to view every drawing sheet and make sure that the views are complete.

Reply to
Jo

I have seen it also.

WT

McBurger wrote:

Reply to
WT

It says a lot about the quality at SW Corp?

.. (were regressions and bugs provide job security, per sp..)

Reply to
Paul Salvador

wireframe.

I have seen this since SW2000 and always thought it was some intermentent video card problem. Never knew the real reason views did this.

Reply to
tjones2

Yes, I've seen that one. I also started seeing another drawing bug with 01.1 that wasn't there in 0.1. Shows up when you have 2 parts which butt up against each other. Used to be when you would cut a section right through the point where they meet, you would (correctly) see the face of the part in front of the section line. Starting with sp01.1, you don't see ANYTHING from either of the 2 bodies that meet-but you see the bodies behind . If you go back to your model and hide the part behind the section, then it displayes correctly. THat works for that section, but if you then want to cut a section through at 90°-you're screwed because one of your parts will be missing.

I made a simple example of this and sent it to my VAR. He confirmed it March

7th and sent it in th SW. I checked and it is still broken in sp2, so I called my VAR again for a follow-up. His reply was that nobody at SW had `picked it up' yet. In other words this was confirmed 3 weeks agi by my VAR and submitted but nobody at SW has even looked at it yet. They must have a real mess on their hands back there if regressions like this are getting ignored.

Our subscription $$$$ at work.

jk

Reply to
jk

SolidWorks performance and release quality isn't any better or worse since all this nonsense and marketing trash talk about thousands of beta testers improving the release quality, and reducing the number of SP's so the ones that are released are of better quality. ya da ya da da

I'm not suggesting it is the beta testers as they have given their own time and efforts to improve the product. The responsibility lies squarely with SW management. This organization needs some heads to roll from top down and not bottom up (modeling technique).

Kman

Reply to
Kman

I beta tested 2005 and found LOTS of bugs. To be honest, most of them did get fixed prior to release. But, on more than one occasion, I sent in a bug report and received the response " That particular issue is indeed not working as intended. However, the same issue exists in SW2004. You will need to submit an enhancement request through our website to have this issue looked at."

A *(#@)&%0 enhancement request??!! It made it sound as if one of their strategies is to ignore the problem for long enough that it survives multiple releases at which time it can be considered a "product feature". This time around I am not testing 2006 as I don't like the feeling that I've wasted time.

Reply to
Brian

"Brian" > all this nonsense and marketing trash talk about thousands of beta testers

Why fix the last release when they can hook everyone for another year of maintenance and keep the chump money flowing. SolidWorks just keeps churning out the new releases, some features good, some half working and others broken or regressed. Seems like 2005 just came out and they are already promoting 2006 and all the baggage that goes with it. Many of the bugs are so obvious that it seems inconceivable these issues would not have been addressed prior to release. From my own experience, I would prefer SW issue patches every week if necessary. At least users wouldn't have to be disabled for months before the problem is addressed.

SolidWorks should continue to support past releases to fix known bugs which users have already paid for with maintenance dollars. SolidWorks side steps this by disassociating annual release with the annual subscription payment. If a person pays 2004 maintenance in full, then they should be eligible for all 2004 updates and SPR releases. And we all know this is not how they play the game.

Kman

Reply to
Kman

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.