« In upFront.eZine this week: we benchmark cloud rendering, and wonder how much it'll cost | Main | Clashing headlines »

Jun 20, 2012

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Kevin Quigley

Ralph I tend to base my business critical decisions on fact, assessment and impact on my business. At this point in time nobody outside SolidWorks knows what is coming. Not you, not Matt Lombard, not me. Like a lot of SolidWorks users I am interested in what is coming but I'm not losing sleep over it and I'm not overly concerned. I will make my judgements when I know exactly what the offer is. Until then I'm happy with SolidWorks and have no great desire to jump ship, with all the upheaval that brings.

Ralph Grabowski

We do know some things about SolidWorks V6, from what executives have told us over the years:
- it is based on Enovia, meaning all aspects of models/dawings are stored in a single database
- it uses the CGM kernel for compatibility with Catia
- it will have a subset of Solidworks commands
- it has been shown running on several OSes and a variety hardware formfactors

Jon Banquer

Solidworks V6 will do very well if it meets the following conditions:

It ditches the Siemens legacy code software components that don't make full use of multi-core processors that are currently used in SolidWorks (they are also used in Solid Edge ST) and replaces them with constraint solvers and a kernel that can take full advantage of all the cores in a multi-core processor.

I cover the CAD multi-core processor problem in detail here:

http://cadcamtechnologyleaders.blogspot.com/

It combines both direct modeling and history based modeling in a seamless user interface... something that Solid Edge ST does very poorly.

It allows better CAM integration than legacy code SolidWork allows... meaning a CAM add-in needs to be able to create its own Assembly file rather than ride on top of a SolidWorks Assembly file which is the case now with legacy code SolidWorks.

I see no reason why SMB's won't switch to SolidWorks V6 if it's designed and marketed properly by Dassault.

Tim Neumann

Just got done with a Solidworks trial,and being a 2D user for 18 years I actually caught on with it faster than Inventor or Solidedge.

Now with this business of it being on shaky ground maybe I better temper my enthusiasm before trying to convince my boss to spend serious cash on a package which may be orphaned in a year or so.

So would it be better to wait or just look into one of the other mid-range packages?

Jon Banquer

Tim,

In my opinion there are no easy/good answers at this point. If I were in your position I would look at a newer, non-legacy code application like SpaceClaim and see if it has got enough functionality for your application. It is my opinion that SpaceClaim is in the best position of any existing application to change kernels or to adopt newer software components that make full use of multi-core processors. I also feel that SpaceClaim has the best user interface of any CAD or CAM application I've ever used.

Ken

Tim, you really need to do a thorough test of potential candidates utilizing a typical project using your full change process. Demos are useless and just "trying" out the software usually does not go deep enough to find the "gotchas". People who do thorough testing usually make much different choices than those who just go with a demo and/or a shallow trial. It also matters greatly on the type of work you do as well. Also, beware of anybody who leads you down a specific path by pure opinion, as it is not somebody you should be following...

Ulrich Hanisch

Jon, the last time, I´ve seen SpaceClaim, they have used an ordinary ribbon UI as known from MS Office. I don´t know just 1 user who is happy about ribbon UI. I personally hate ribbon UI. It´s boring, one need very much mouse action to toggle between different areas of the features and functions, and I´m sure, that I´m very much faster using my customized SWX GUI - and having much more features and functions as in the SpaceClaim package.

Jon Banquer

Ulrich, just because an application uses an MS Ribbon bar doesn't doom it to failure or guarantee it's going to be good. The SolidWorks Command Manager actually mimics what the MS Ribbon bar does.

Suggest you try using SpaceClaim hands on to see for yourself just how good its user interface truly is.

Bookkeeping Sunshine Coast

This is all too confusing, I think Solidworks need a lesson on their Public Relations. Their announcement seemed vague and they seem to be unenthusiastic about their product.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

Advertisements


Search This Blog


  •  

Translate

Thank you for visiting!