A 2006 Rave

[wes616]

I know this site is usuall a bitchfest (I mean helping each other fix problems) but I wanted to give the guys at SWx a big round of applause. The Hole wizzard in 2006 is great. It's so much better being in the pannel than as a popup window, and it looks really cool too (reminds me a little of pro/e... but that was a long time ago.)

What do you guys LIKE about 2006. There has got to be more good stuff than problems (why else would we be using it). And I'm sure the people as SWx would love the praise :-D



Wes C.
------------------------------
Make a dent in the Universe... do something great...

 

[SBaugh]

I don't crash, Stability is there for me and 90% of Customers. Even though Testing is not Cost effective, Testing in the long run will pay for itself, because ify ou find it to be slower with your files then you have saved yourself a ton of lost time to slow downs. If you speed up with your testing then you will save yourself a ton of cost with a speed increase. Either way testing is required to determine if your files will work with the latest. I can tell you all day that SW06 is great, but you are the only one that can determine that with your files. You may have some or do something that I don't do and with your technique you might cause SW to crash more often. Only you will be able to determine that.

Best Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[dogarila]

Finally I decided to install SW2006 but I wanted to download SP1 first. SW site won't recognize my serial number as a subscription service customer although I know for sure is paid.

 

[wes616]

Netshop. Call your VAR.

Wes C.
------------------------------
In this house, we OBEY the laws of thermodynamics! - Homer Simpson

 

[PlasticFantastic]

Yesterday, I was working back and forth with a team member who was using 05. I was noticing that 06 offsets like butter. The sketch blocks are great for logos, and 06 opens up Illustrator files (!), and blocks have saved me a bunch of time designing linkages.

 

[Stoker]

SWX Improvements:
1) Display states - allow you to deal with view options (hide/show, shaded/shaded with edges/wireframe) independently of configurations.
2) Depth setting for section views in drawings - allows you to limit the visibility of parts that are past a specified distance.
3) Invert selection - finally !
4) Appearance callouts - how many times have we seen questions from people who can't figure where a color/texture has been applied?

PhotoWorks improvements:
1) Much better interface for locating decals. The drag handles make this so easy and give realtime display of the decal.
2) Help files have been updated with a lot of good info regarding the effects of various settings and their dependencies. Some examples are given with the settings used to create them. This is long overdue.
3) Decals can now be viewed in the part/assembly in addition to the rendered view.
4) Camera view is great for creating realistic closeups. Depth-of-field is a huge addition. You used to have to fake this by using gradient blurs in Photoshop. I have also not seen the problem of the PhotoWorks tab not becoming active when selected. This bug had been around since PWX 1, so I am hoping it is gone for good. Photoworks is getting some stiff competition. It is nice to see them finally start to keep pace with the rest of the rendering world.

No stability problems.

I have seen some mate errors that were not there before the upgrade.

Overall this is a very good release. They have come a long way since 2003...

 

[charbroil]

Stoker, I agree that the concept of Display States is a great addition to Solidworks, but I’ve already run into a couple of limitations with them.

1. Display States and Design Tables. Compare to Configurations in Design Tables...When you type in a new Config name, the Table creates a new Configuration. Sure would be nice to do the same for Display States.

2. Display States of Assembly Components. Compare to a Drawing View. If you are editing a drawing and right click a Drawing View to get Properties, there’s a familiar dialogue box containing a pullout for Configuration Name, in addition to a new pulldown for Display State of that Configuration. Awesome! Now try right clicking on a component in an assembly file. You get the good old Configuration Pulldown and would expect to see that brand spankin new Display State pulldown. But guess what, it’s not there!

I was really warming up to the idea of Display States but #2 killed my excitement. What’s the use of implementing something if it’s not fully integrated? Solidworks dangled a carrot in front of my nose and I followed it right into a wall.


System: Dell Precision 650—Intel Xeo @ 2.66 GHz with 1/2G RAM
OS: Windows 2000 SP3
Graphics: NVidia Quadro FX 500 128Mb (OpenGL set to Solidworks) V 6.14.01.4354
Version: Solidworks 2006, SP1.0
Motion Control: Spaceball 5000 V5.3.3 Firm 3.2

 

[cnova]

You may have some or do something that I don't do and with your technique you might cause SW to crash more often. Only you will be able to determine that.

Is there a "technique do's & dont's" book that I'm missing.

If technique can cause SolidWorks to crash, it was never mentioned in any of the training classes I've taken.
My technique has remained the same, but with SW06 I've gone from 0 crashes with 2005 to ~20 crashes with 2006 since we upgraded 6 weeks ago!


Stupidity is the basic building block of the universe. F.Z.

 

[smcadman]

cnova, I don't know about a ""technique do's & dont's" book", but there a few threads on SW best practices in this forum. You might also want to check out the FAQ's. As for crashing for 6 weeks now, you have to note that SP1.0 didn't come out until 10/11/2005, which is a little over a week ago. "Testing" SP0 is usually recommended before jumping in with both feet, but I let others find most bugs and let them get fixed in SP1.0 before I install.

Flores
SW 2006, SP1.0