Best Of

@jeff_peachman

As you probably know, Onshape is based on the same kernel, Parasolid, as NX. In theory, anything that can be modeled in NX can be modeled in Onshape. Of course NX has decades more development and has many niche tools that Onshape doesn't. It also costs a lot more and takes an IT department to manage it. There are several aerospace companies using Onshape at the moment.

In a perfect world, I wish Onshape had more sophistication in some areas, but after 30 years of using Creo and Solidworks I refuse to use them again because Onshape solves certain pain points so much better:

• Never loosing work
• Getting new functionality every 3 weeks that other companies charge an arm and a leg for
• Having those updates be almost pain free and automatic
• Not having to worry about managing a PDM server
• Being able to add custom features, and write them
• The way that Onshape manages history, versions, branching, merging, reference updating
• The stability and uptime of Onshape on AWS
• Much more explicit control over how my top down design references work

@jeff_peachman :

I wasn't able to completely understand what you're trying to build (and how), but I was able to draft up a conical isogrid pattern in a few minutes.

apparently, there's custom feature called isogrid… (custom features of onshape are awesome and often fill in the few gaps that i felt were there from NX)

I've used NX for 11 years as well, but would hate to go back now, for reasons @S1mon detailed.

sometimes you just have to find the right way to get things done…

https://cad.onshape.com/documents/8d962e7b553bd4c5c3cbcdb8/w/a2abda4690d856374195b87b/e/c49c46b320825770ae8b0183

would not be able to do this with NX. wouldn't have the custom feature, and couldn't have as easily shared my file with you…

(what version of nx are you on etc.)