Welcome to Autodesk’s AutoCAD for Mac Forums. Share your knowledge, ask questions, and explore popular AutoCAD for Mac topics. Well that fixed that issues but now the program keeps on crashing everytime i open it. I did disk repair and reinstalled it but nothing seems to work. The term “stability” is sometimes used as a euphemism to refer to how many bugs a program has. I don’t use the word in that way. To me, stability is a measure of a program’s basic ability to keep functioning without crashing or corrupting data. A program can have a thousand tiny irritating bugs and still be very stable. Another program might have only one bug, but if that causes it to crash a dozen times a day, taking down your data with it, then that is very unstable. So, given that definition, how stable is your AutoCAD, or vertical AutoCAD variant? How often does it crash, or mess up your drawings? How does that stability compare with your experience of earlier releases? How does the stability of plain AutoCAD compare with that of its vertical siblings? Please add your comments. If this proves a popular topic, I may run some polls. My two cents are here, FWTW: Until AutoCAD 2011, I had pretty much always felt that if AutoCAD crashed, it was the user’s fault for triggering it, and it was simply a matter of noting what caused it, then avoid doing that in the future. ![]() N64 emulator mac dmg. I’ve always tried to practice good drawing ‘housekeeping’ (purging and keeping the file size as small as possible) which has also been beneficial, IMO. But it seems that in the current version of AutoCAD, the programmers just yanked the previously working and well-behaved code for CLOSE, and replaced it with the code for the ABYSS-DITCH command: DIVE! Or so it seems. I believe that the 32 bit AutoCAD 2011 seems to be far less stable than versions in the past. After switching to 64 bit, I believe the stability has increased, but not by much. A lot of our problem here seems to be our third party civil software, which seems to crash AutoCAD at least 1 in every 10 commands evoked, if not more. But I tend to attribute that to poor programming on the release of a 64 bit program. I would say crashing isnt consistent, and there is no way to determine what steps to avoid to prevent the crashes. When it comes to loosing data, I’m just in the habit of saving every couple of commands. I do seem to experience crashes much more often when closing out the software when I have multiple drawings open. ![]() In my experience, 2011 is fare more stable than previous versions (please note that we have totally customized AutopCAD, so it is possible some of our cutomization was crashing previous versions, as I completely reviewed all of our LISP Routines before installing 2011 on any system besides mine.) I have also found that installing VBA causes 2011 to run substantially slower and crash more often, so any of our VBA routines have been rewritten using LISP and OpenDCL and we do not install VBA. Now 2011 was still crashing a bit more than I would have liked on certain systems, I have since installed the service pack on those systems first and the crashes have gone awayI haven’t even heard of a crash since then. My system has crashed a few times since installing the service pack, but it has always been due to me testing a LISP routine that I was working on and an error in it. I don’t believe the blame of a less stable release can be placed wholly on the software vendor or it’s programmers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |