Sub D and stuff
Posted: Sat Mar 13, 2021 9:15 am
Firstly thanks to Matt for setting this place up, looking forwards to some CAD agnostic discussions!
I thought I’d start with sub d toolsets and how we have grown into these. Back in the day, we bought into Modo as a rendering tool to accompany Solidworks, with also the vague hope that we could do concept work in it. For various reasons this didn’t work out. Primarily because Keyshot happened, and TSplines proved more useful to our workflow. Not to mention the sheer complexity of the Modo interface which I never took to, and the guy working for us who did, left!
So began our expenditure in sub d toolsets!
TSplines with Rhino 5 was our core tool for this type of work for years. We designed many products in it, and it always tickled me to see comments on “you can’t use TSplines and Rhino for final A class surfaces”. Oh really...
Designed 100% in Tsplines and Rhino, tooled from data.
Anyway, moving on a year or two I invested in Power Surfacing for Solidworks, which in the early releases promised much but was as flakey as hell. Half the time the subd didn’t convert properly. I was used to something better with TSplines. So Power Surfacing languished on the hard drive for a few years getting very little use.
By this time Fusion 360 had appeared (and as a pre beta tester I bought into it in version 1 for peanuts). I had hoped Fusion could eventually replace Solidworks but early versions were even more unstable than a Solidworks beta. So no. But the TSplines implementation improved release by release.
As Autodesk had bought T Splines and pulled the plug on Rhino, it meant Rhino had to develop their own subd engine. We tried using this in the betas but decided not to use it until it was released (which it is in Rhino7, more later)
A few years ago, we picked up some toy design work, so we used Rhino5 and Fusion to do early versions of these guys
[/attachment]
The trouble with doing this work is you need lots of revision phases so going Rhino/Fusion/Solidworks/Keyshot etc was a pain, so we started to look for alternatives. At the time Creo had switched to subscription only so I bought a network license of Creo 4 with Style (ISDX). Creo has a fantastic feature in all versions called Freestyle. It is an amazingly effective tool for sub d work, as you can control the edge sharpness from creased to smooth. Anyone using TSplines, or PowerSurfacing, or the Rhino versions knows that you need to add control curves to the form to control the sharpness of an edge. Creo doesn’t. You just select the edge and set the sharpness you want. Less control curves means lighter surfaces. (Looking at videos of the new SolidEdge subd toolset it appears to do the same).
So we attempted to move all toy and surfacy work to Creo. Unfortunately Creo’s other tools are not great. Drafting is, well, dismal. Assembly and in context modelling, pre version 7, was tricky without expensive AAX add ons. Version7 improved things a lot, but of course Covid then hit and the reality is we haven’t used it much in the last year so we are dropping it and reverting to Rhino7 and Fusion and....Altair Inspire Studio (which is available at a bargain subscription price).
The Altair software is quirky. It is not like others, but it is exceptionally powerful and has the sane edge sharpness controls as Creo. The built in rendering is also fantastic so frees up our Keyshot seats.
So what have we learned?
The biggest lessons are, sub d is a small part of our toolset. We don’t use it on every job, but when we need it, nothing else will do.
You can get to a mid level standard in sub d quickly, but to get to using it for production release surfaces needs lots and lots of time and tweaking. There are no shortcuts in this game.
There is no point in using pure sub d tools like Modo or Blender for doing our kind of work. It’s a wasted effort. We can conceptualise faster in nurbs linked subd, and then there is no reworking needed when we move into design freezes.
Cost has bugger all to do with functionality. I’ve seen Imagine and Shape, the CATIA sub d module. It is no better than anything else we use. The toolsets in Rhino, Altair Inspire, Fusion are all low cost. We kept Power Surfacing for Solidworks and it is a lot better these days but would I pay the asking price just to run it inside SolidWorks now? No. Get Altair and export as a parasolid.
Finally, there is the 3D EXPERIENCE question! Readers on the Solidworks forum know my thoughts on this. 3D Sculptor (the 3DX sub d x app) is rubbish. It is a toy. It offers nothing that these other apps don’t already have. If your thing is staying with one supplier and one platform then that’s fine, but let’s not pretend these apps are state of the art. They are nowhere near it.
So what will we end up using in 5 years? No idea. I just know we’ll not be changing to one system. Ultimately the tools are only as good as the user, which is why I value user skills over software capability any day.
I thought I’d start with sub d toolsets and how we have grown into these. Back in the day, we bought into Modo as a rendering tool to accompany Solidworks, with also the vague hope that we could do concept work in it. For various reasons this didn’t work out. Primarily because Keyshot happened, and TSplines proved more useful to our workflow. Not to mention the sheer complexity of the Modo interface which I never took to, and the guy working for us who did, left!
So began our expenditure in sub d toolsets!
TSplines with Rhino 5 was our core tool for this type of work for years. We designed many products in it, and it always tickled me to see comments on “you can’t use TSplines and Rhino for final A class surfaces”. Oh really...
Designed 100% in Tsplines and Rhino, tooled from data.
Anyway, moving on a year or two I invested in Power Surfacing for Solidworks, which in the early releases promised much but was as flakey as hell. Half the time the subd didn’t convert properly. I was used to something better with TSplines. So Power Surfacing languished on the hard drive for a few years getting very little use.
By this time Fusion 360 had appeared (and as a pre beta tester I bought into it in version 1 for peanuts). I had hoped Fusion could eventually replace Solidworks but early versions were even more unstable than a Solidworks beta. So no. But the TSplines implementation improved release by release.
As Autodesk had bought T Splines and pulled the plug on Rhino, it meant Rhino had to develop their own subd engine. We tried using this in the betas but decided not to use it until it was released (which it is in Rhino7, more later)
A few years ago, we picked up some toy design work, so we used Rhino5 and Fusion to do early versions of these guys
[/attachment]
The trouble with doing this work is you need lots of revision phases so going Rhino/Fusion/Solidworks/Keyshot etc was a pain, so we started to look for alternatives. At the time Creo had switched to subscription only so I bought a network license of Creo 4 with Style (ISDX). Creo has a fantastic feature in all versions called Freestyle. It is an amazingly effective tool for sub d work, as you can control the edge sharpness from creased to smooth. Anyone using TSplines, or PowerSurfacing, or the Rhino versions knows that you need to add control curves to the form to control the sharpness of an edge. Creo doesn’t. You just select the edge and set the sharpness you want. Less control curves means lighter surfaces. (Looking at videos of the new SolidEdge subd toolset it appears to do the same).
So we attempted to move all toy and surfacy work to Creo. Unfortunately Creo’s other tools are not great. Drafting is, well, dismal. Assembly and in context modelling, pre version 7, was tricky without expensive AAX add ons. Version7 improved things a lot, but of course Covid then hit and the reality is we haven’t used it much in the last year so we are dropping it and reverting to Rhino7 and Fusion and....Altair Inspire Studio (which is available at a bargain subscription price).
The Altair software is quirky. It is not like others, but it is exceptionally powerful and has the sane edge sharpness controls as Creo. The built in rendering is also fantastic so frees up our Keyshot seats.
So what have we learned?
The biggest lessons are, sub d is a small part of our toolset. We don’t use it on every job, but when we need it, nothing else will do.
You can get to a mid level standard in sub d quickly, but to get to using it for production release surfaces needs lots and lots of time and tweaking. There are no shortcuts in this game.
There is no point in using pure sub d tools like Modo or Blender for doing our kind of work. It’s a wasted effort. We can conceptualise faster in nurbs linked subd, and then there is no reworking needed when we move into design freezes.
Cost has bugger all to do with functionality. I’ve seen Imagine and Shape, the CATIA sub d module. It is no better than anything else we use. The toolsets in Rhino, Altair Inspire, Fusion are all low cost. We kept Power Surfacing for Solidworks and it is a lot better these days but would I pay the asking price just to run it inside SolidWorks now? No. Get Altair and export as a parasolid.
Finally, there is the 3D EXPERIENCE question! Readers on the Solidworks forum know my thoughts on this. 3D Sculptor (the 3DX sub d x app) is rubbish. It is a toy. It offers nothing that these other apps don’t already have. If your thing is staying with one supplier and one platform then that’s fine, but let’s not pretend these apps are state of the art. They are nowhere near it.
So what will we end up using in 5 years? No idea. I just know we’ll not be changing to one system. Ultimately the tools are only as good as the user, which is why I value user skills over software capability any day.