Still no solutions to these endless crashes...
C'mon Autodesk? Anything? Got to admit that this is making Solidworks look better all the time.
The product team has been away for the holidays for the last week or so. I'll have one of the guys look up your crashes in the database and see if there is any advice we can offer.
Did you put in an email address? - can we just search for upperconsulting.com in the database, or are you using another email address?
Short of sitting down at your actual computer, working on your actual models, using the same work processes, its very difficult to track down the cause of such problems. Not much help that others are unable to replicate the problem either. The only thing that is left is, as you say, throwing darts at board. Now, stupid question time: what visual style are you using?
Edit: as well, are you using SQL Server as your backing database?
Hi dgorsman and thank you for your input.
I often use realistic visual style but also use 2D wireframe quite a bit as well. I know it sounds funny but I sometimes think that I must be working too fast for AutoCAD to keep up. I do tend work quite fast. I also use a fair amount of copy/paste to insert 3D components into my overall model. I would say that 20% of my crashes occur when I paste a 3D object into another drawing. I have theorized that possibly AutoCAD is not managing it's cache data as good as it could.
In addition, some of our full models can get up to 20 Mb or more in size. Which brings me to my next theory that my NVIDIA Quadro 2000 Graphics Card is not able to keep up. (just a theory).
AutoCAD has always been a bit dodgy with the enhanced visual styles for navigation. I see them more as a static, rendered viewport use. The Quadro 2000 is really an entry-level pro card, a pricier high-end version (theres a few $10K models out there, believe it or not) is needed for navigating around with those settings. 3D realistic is *very* taxing, and when you have those 20 MB models on top of that you will defiintely be crashing left, right, and center. As a rule of thumb, I keep AutoCAD DWG files at around 5 - 7 MB for best performance, using a combination of blocks, XREFs, and level-of-detail controls. I *strongly* suggest you use Navisworks for real-time visualization and use wireframe for design work.
If you are grabbing those 3D objects from a set of source files, its a good idea to do a blanket AUDIT on all of them, plus do a COPY operation inside the source file. I've had a few 3D solids created by users which looked and AUDIT'd OK but when moved or copied, threw a command line error. A little slice-n-dice identified the problem bits which were then reconstructed into clean, non-crashing solids.
Yes, but only because it is the fastest and most efficient way to navigate. And again, I work pretty fast doing 3D modeling. I have, however turned off the "enable orbit auto target" but that has not really had any impact either way. When in a larger model I often go to wireframe before using orbit along with turning off layers not needed at that time.
GOT ANOTHER QUICK QUESTION WHILE YOU ARE HERE...
I do a lot of screen shots of our models for the client and for contractors. To make them more printer friendly I usually change my background from black (my preferred bg) to white. After finishing the screen shots I always switch back to a black bg. Is there a variable or quick toggle for this without having to go to tools>options etc.? I have searched more than once but cannot find anything.
There is bug having to do with "enable orbit auto target" but it's apparently not the same thing you're running into. I'll have someone look at the crash logs next week and see if there are any clues.
I don't know of a shortcut way to switch back and forth between white and black background. Perhaps someone has written some lisp to do this, but I don't know of it.
Ok, one of our developers looked at the crash logs. A number of these were fixed in 2014 SP1. You might try applying the Service Pack and seeing if that helps.
Also, if you could get access to the Beta and see if we have resolved any issues. It will also help us set the priority to fix if it's still in this year's beta. The link to sign up for the beta is here:
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register