bcbmde

I recently graduated one of those schools that teach Autodesk products. I must say that Autodesk does suck, but... learning about profiles and work planes is directly transferable to the majority of other CAD applications (it's just a matter of figuring out how to get to the command). If I had been taught IronCAD in school, I would not have been able to readily pick up any other CAD application (where is my block and triball). On the other hand, I was taught AutoCAD, Mechanical Desktop, and I-DEAS, which made IronCAD seem like a dream. If the majority of students started to learn IC, they would jump into the industry and get lots of strange looks with even fewer job offers. Please do not hurt the students by teaching them the easy way to do things.

Perhaps a 'command line' text file of all non-camera scene changes since the last 'full save'. Kind of one of the beautiful things of AutoCAD and COSMOS was the ability to generate large models off of several lines of code...Not that IC has a command line, but there must be a way of storing the commands alone, without saving the actual computational changes to the scene...So in case of a crash, that is not 'operator error' then the whole command line file can be re-run automatically without user intervention, or the last command(s) can be removed and automatically run to a stable model where the CAD operator can hopefully continue on the path to enlightenment.

8000 parts...20x20x20 cubes...something 6.0 couldn't muster on this machine, 7.0.1 did in a breeze Great job

Perhaps in a couple of months I will be able to rate IC 7 more highly on the stability scale. My current instability problems could be caused by my IC 6 saved as 7 models.

G-code shouldn't change from one app to the next. I used to create G-code in I-deas and bring it into different CAM apps without problems.