2009 anybody?

Has anyone tested 2009 yet?
What's good/bad?
Best regards
Jeppe

 

I have been using it. The big draw is supposed to be speed. I am finding
the user interface is a bit more jerky than 2008. I haven't gotten to
any big assemblies or parts yet.

It hasn't crashed yet.

The standalone rendering package is pretty neat.

There is a lot of new/changed stuff in the API and the API help. Seems
like they are moving away from VBA and hence from user friendliness. The
API help is not as straightforward as it was before at least for
non-programmers. Another round of redoing old macros.

TOP

 

For now VBA6 is still supported but they are making it pretty clear that
VB.NET, C#, C++ and a few other flavors are the way to go in the future.
There are subtle differences between VBA6 and VB.NET. You can
edit/record macros in C# I believe.

The way the objects are handled has changed. The naming of some common
ones has changed. The changes would have more meaning to a programmer
than to you or I.

TOP

 

SolidWorks 2009 still can't edit a non-native solid like Solid Edge
with ST can.

SolidWorks 2009 still sucks at collaboration / trying to understand
someone else's design intent.

Jon Banquer
San Diego, CA

 

Gee, how good is SE with SW models?

Only for non-SW users like you.
Seems to work for everybody else.

You ever find out how to drill those two holes?

 

Solid Edge with ST edits SolidWorks files faster than SolidWorks
itself!



Jon Banquer
San Diego, CA
http://jonbanquer.blogspot.com/

 

Can you please elaborate on how it 'sucks' at collaboration and
understanding design intent? Or at least how SE doesn't 'suck' at
collaboration or understanding design intent?

and no, I don't want to see a bunch of URL's to the answers..

 

SolidWorks only tool to try and figure out someone else’s design
intent is to use its roll back bar. You don't have any way to map the
history tree to see all the complex relations that are often created
in SolidWorks.

Solid Edge with ST doesn't use a history tree in the ST part of the
product. You have features but it doesn’t keep or need a history. That
means that complex geometry updates don’t
need to rebuild by going through a history and solving one by one.

Strongly suggest you start watching some video links on my blog and
understand what the future is because history based modeling is going
to be history.

After you do this I also strongly suggest you contact Siemens and ask
for a 30 day demo CD of Solid Edge with ST.

Jon Banquer
San Diego, CA
http://jonbanquer.blogspot.com/

 

Clearly you know nothing at all about design OR "design
intent" OR how to use SW (or anything else)
But we knew that.

 

Tell somebody who cares!!!!!!!
Or better yet move you sorry arse over to the Solid Edge forums.

 

Solid Edge with ST edits SolidWorks files faster than SolidWorks
itself!



Jon Banquer
San Diego, CA
http://jonbanquer.blogspot.com/

 

What happens to the histroy, surfaces & parametrics?

BTW, Once you translate the data FROM SW TO SE
(losing much of it) you no longer have a "SW file"
so you are again clueless & lying.

 

http://p-hamilton.blogspot.com/2008/10/key-capabilities-of-history-free.html

"Jon, I agree with you. For the situations that you bring up:
interroperability, teamwork, and many others like concept design,
rapid design cycles, unexpected change - history is a disaster.
Strangely enough though, many companies still cast their vote of
approval for the stuff with every dollar they spend on it."

Jon Banquer
San Diego, CA
http://jonbanquer.blogspot.com/

 

Some newbie has problems spotting a clueless idiot.
So what?

 

http://p-hamilton.blogspot.com/2008/10/key-capabilities-of-history-free.html

"Jon, I agree with you. For the situations that you bring up:
interroperability, teamwork, and many others like concept design,
rapid design cycles, unexpected change - history is a disaster.
Strangely enough though, many companies still cast their vote of
approval for the stuff with every dollar they spend on it."

Jon Banquer
San Diego, CA
http://jonbanquer.blogspot.com/