Yes, it lacks a lot of advanced features, but the basics are there - guessing 85% of what I need in the type of work I do. âLiteâ is a good analogy. Where itâs missing more sophisticated constructs, Iâve generally been able to derive what I want from basic building blocks or rather approachable FeatureScript. Iâll bet the models I work on arenât as elaborate as yours.
I agree it has a long way to go before it gets anywhere near feature parity with Solidworks. But frankly some of whatâs missing is bloat I donât want (e.g. my motion simulations are pretty basic, I donât touch plastic deformation or flow simulation, I tried the electronics design tools once and coming from an EE background found them a joke). Qualitatively, Solidworks kind of feels like they kept âtacking onâ new stuff (at times compromising the integrity of the platform before going back and fixing it - most of the people I talk to avoid âSP0â releases like the plague), whereas Onshape feels nascent but more well thought out (not surprising since they started from a clean slate) and Iâd say benefits from a more consistent UX. While Iâve still only done a few projects with it (so youâre right, I havenât yet truly said âgoodbyeâ), I find it offers a pleasant and intuitive design experience with more predictable productivity. For someone new to parametric design I would absolutely point them toward Onshape first before recommending Solidworks (although if they can afford the latter Iâd strongly encourage them to try both). I wonât argue itâs superior, but I do think itâs more approachable.
One area where I did hit a major show-stopper was performance involving huge collections of pattern instances (here body patterning in Solidworks offered a significant edge, provided you know in advance how to correctly approach the problem). Instead of being told âopen a ticket with your VARâ the nice support guys at OnShape quickly reproduced the issue, confirmed it as something needing improvement and presumably added it to their development queue (granted Iâm still waiting for a fix). I didnât need to fight off accusations about hardware validation, which graphics card is installed in my PC, conflicting software, etc.
Thereâs certainly a large swath of things Solidworks does better than Onshape, but theyâre slowly narrowing the gap. e.g. Once upon a time I wouldnât have touched it for anything to do with Sheet Metal, apparently now theyâve got that. I would have used it for my recent BabyForm2 project (reduce open-source âfrictionâ by using a tool anyone can get at for free), except that I needed to be able to work while traveling / on plane / without internet (that being my main biggest complaint about their platform).
My general impression is if you know what youâre doing in Solidworks youâll find it superior and think OnShape is a bit of a toy. But if youâre starting out and want an intuitive albeit smaller toolset thatâs easy to get started with, Onshape fills that niche nicely.
As for bugginess, I describe some examples in my article and more can be found by searching around the Solidworks forums (Iâve posted a few myself). I will say the team seems to be doing a bit better on the stability front these days.
I donât want to dive too much into specific examples here, but I will mention unreliable undo buffering is one that really killed me once, corrupting hours worth of work on a SLDPRT file. Maybe there was a deterministic explanation but it didnât feel that way. I now find myself being a bit less liberal with CTRL+Z and CTRL+Y, and I keep a rolling set of previous point-in-time backups just in case. (From the perspective of a software engineer, thatâs the sort of cognitive overhead a user simply shouldnât have to deal with).
Hyperbole from other frustrated users isnât hard to find in the Solidworks forums.
Sorry if I come across as insulting software youâre passionate about. These are just my views from my own experience :-). Iâd love to hear about where you find OnShape sorely lacking.