Hi Jim,
Ok, sure many moons ago I had the basic NX Mach version as well, with a few modules (have to get the bill but it was freeform surface and animation)
I could get it to crash no problem. Fact, NX handles crappy data really well, period.
Yes, NX crashed less then and recently. ... than SW but my SW models/assys are/were fully controlled parametric masters. (and wave is not even close to what I was managing in the past and present, mainly dumb models, which is fine)...and yes, SW demands much more hardware ( i have a core i9 40gigs ddr5 ram, 3070 gpu)...and I've always bought the best i can afford (own/used SW since 98+)
Creo, on the other hand was least likely to crash and could handle much larger data sets with less hardware.
NX is very good with large data sets on minimal hardware! Again, it crashes...and, I have lost data (had to had IT pull an old version and lost the rest, yep)
Maybe it's because they manage the graphic engine pipeline and memory better, like Creo does? Or maybe it's the older unix code or "X Windows" interface from years ago. When I used Pro/e on WIndows NX on a RISC CPU or Sparc, I rarely ever crashed. But, as PTC moved towards greater integration with Windoze, it crashed more!
With so many Windows configs and quality - cpu/gpu/memory and the graphics drivers, these are the main culprits.
so, yah, the next wave we have is 100% cloud based BROWSER's. I'm not impressed using it (onshape), I'm still more effective without it but I get it and as per above, $ drives this and industry feeds off it.
It's funny like watching WALL-E ... recliners and sippy cups.
Jim Elias wrote: ↑Sun Aug 06, 2023 4:43 am
"Creo and NX are on another suite/cost level...", nope, that's missing the point of why I chimed in.
I'm not addressing the functions. My NX bundle license is the bare-bones NX10101, it does a few things which my SW-Prof won't do, and there are a few things which my SW-Prof does, which my NX won't do. On the balance that's a wash.
BUT -- NX is way more stable and runs way faster, on hardware that is much less capable (and thus much less costly), than is needed with SW. That's the crux of what I'm often addressing, and I've never seen an answer as to why this is, though it is indisputably so. If it's the "outdated" UI, then I would tell SW -- you've "modernized" your UI too far if it's causing you to resort to this level of resource piggery.
Creo: I guess Creo/Pro-E is fine, I haven't used it much myself. I have collaborated often enough with Creo-based teams and my impression has been that Creo is about at the NX level, because it looks like we tackle similar issues with similar methods. I haven't noticed that the Creo folks are able to do anything more than me and/or do it faster.