Ok, so I'm a heavy heavy corridor user for all sorts of unorthodox approaches, and end up with lots of targets, etc. It seems that somewhere between conceptual design and final design, the grading files with these objects have ALWAYS hit a wall: saves slow to minutes, opening files goes from seconds to 3-4 minutes, and changes to the alignments, assemblies, and profiles go from 1-2 seconds to 1 minute per change.
Well, I was done after struggling with a deadline yesterday - was determined to figure it out by isolating the assembly type that was causing the problem (I assumed some sort of targeting was causing the problem.) So I went into each and every corridor and turned off all the regions, profiles, and alignments. I then tried making edits and they were a flyin'. I expected I'd turn it on one corridor at a time to find the culprit. What actually happened is that I got through turning them all back on and it was still snappy and responsive!
Now, I think the culprit may be when I'm blowing apart and replacing assembly parts, copying assemblies and making what if scenarios once corridors are built. Doing this, I often erase pieces that the corridor has stored target data, etc. for and I'm guessing that somehow turning off and back on the region is purging junk from the corridor. I may be wrong, but in the latter part of DD all the corridors are built and I'm usually doing some heavy manipulation of the assemblies.
My hope is that some of you find this a fix to your issue, and that we can continue to monitor where it is happening and figure out the actions that trigger the problem. Of course, ideally the C3D team at Autodesk could take the info and find a quick hotfix for it. Since there are major changes to the corridors in C3D 2013, I'm curious if this problem is fixed in 2013 - haven't had a chance to try it there yet.
When you say performance gets better if the region are hidden makes me wonder, since you said heavy heavy..., could your codeset styles be dragging you down?
I had switched to a very simple codeset. I did notice that a lot of the feature lines reset back to defaults (some had been manually changed) when the regions were turned off and back on. I had null display codesets on most. After turning all off and back on, it didn't matter how busy the code sets were, it was still snappy.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register