C3D 2012 Slow Toolspace Prospector/Settings items

[Jeff_M]

In the same vein as this: http://forums.autodesk.com/t5/AutoCAD-Civil-3D/C3D-2012-Figure-Style-Slow-to-Respond/m-p/3005214#M15..., I have run into the same slow response when selecting the Parcels in a Site in Prospector.

I first noticed this in my own drawing containing 4 sites, 3 of which have 1 - 6 Parcels, and the other has 170 or so Parcels. When I selected the word "Parcels" in the large Site, C3D went into a limbo state for approx. 7 minutes. I received a phone call just after I figured out it was not going to let me do anything so I just let it sit. I did open Task Manager and saw that acad.exe was consuming 100% of one of the cores. Much to my surprise, during said phone call, I watched C3D come back to life and the Graph View showing the parcels at the bottom of Prospector filled. As soon as I clicked the word Parcels again it again went into that limbo state. I can click any other branch in a Site without a problem, but clicking on Parcels will 'freeze' C3D everytime.

I can duplicate this in any one of the Parcel* tutorial drawings as well.

Then I tested with another C3D Profile and it has no problems selecting Parcels. So I switched Profiles using Options to my usual profile. Selected Parcels, this time it did 'hang' but only for a few moments. Clicked another SIte, clicked Parcels, hung for 2 minutes or so.

So it looks like I've narrowed it down to being Profile specific, but I'm not sure what I could have changed in the 'bad' one to make it 'bad', as I just created it last week from a copy of the 'good' one.

[gunnarl]

We are experience the same lag when trying to make edits/changes in the toolspace on multiple machines at my office. It's about 5-15 seconds after clicking in the fly out before it populates the item. It is taking quite a long time to edit my structure and pipe numbers, data, etc. I'm hoping it will get fixed with a SP or hotfix SOON, along with all the text editing issues many of us have had.

Gunnar

[Dave1982]

Since the move to 2012 I have experienced nothing but slow responses and hang times. The prospector is completely unuseable, I have just resorted to throwing away 3 days worth of ground and profile modelling and starting again in 2011 Civil 3D.

This has caused a missing deadline, at the current rate I will be keeping with 2011 and cutting my losses on the 2012 release until AutoDesk release some proper fixes before selling a product that clearly has bugs.

Don't even get me started on the view frames and sheet sets, this has always worked fine but not in 2012.

[hgohel]

Dave1982,

A hotfix has been released for a performance bug in AutoCAD (and verticals such as Civil 3D), you can find it on our support>download pages for Civil 3D 2012.  Please be sure to install that.

As for the Plans Production tools in Civil 3D 2012, I would like to get you started, because we aren't aware of any changes from previous releases that you should have encountered.  If there are, we would like to know about them.  If the issues are particular to SSM and not C3D plans production, then it may be a more general issue that perhaps would be more suited to the AutoCAD discussion forums aslo.  Do start a new thread for this topic so it can get the attention it deserves.

Regards,

[Dave1982]

Thank you Himanshu

I will be sure to try the hotfix, will this speed the prospector up?

It is apparent that there are many users of 2012 experiencing the same issues so I'm sure your development team are on it? The 2011 release was great, no issues with speed in the prospector which was a very useful toolspace, unfortunately as mentioned, the new 2012 release has rendered the prospector so slow that it has become unusable.

[hgohel]

Dave, the performance hotfix is an AutoCAD hotfix which will improve overall performance (that many customers have reported here), but it is not a Civil 3D fix and will not resolve Prospector-specific issues.

We have logged some defects about Prospector (there are several threads about this, search for tag=performance) and yes, are working on it.

[JRedell]

Just wanted to say thanks for this thread coming up. I've been fighting with the Prospector most of the day and finally did a search and came up with this thread and who would have thunk that just hitting the CTRL key brings C3d back to life. It's like a C3d face-slap! Super glad it's not just me having these problems with 2012. Come on Autodesk, put more effort into releasing quality upgrades every few years instead of this yearly crap you're feeding us.

[AlmasSuljevic · Accepted solution]

Just FYI: The hotfix is released yesterday. See if you can apply it from here: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=17751015&linkID=9240698

[JRedell]

When I try to download that hotfix, it shows as a .txt file. Can you check it out and let me know if it's just something weird on my end?

[klugb]

Ditto,

I even tried to rename it to a ZIP file, no go.

[gould62]

I tried the 32-bit file as well, no go....

[Jeff_M]

It just downloaded fine for me, must've fixed the link.

[Jeff_M]

Almas, I accepted the hotfix post as the solution, but there's now a new minor annoyance I don't recall seeing before. In the gridview at the bottom of Prospector, when I select the Pipes or Structures for a PipeNetwork, scrolling through the items is very laggy. It seems like any other type of object listed in the gridview is snappy, but not these 2 items.

Thanks to the DevTeam for releasing this Hotfix. My Left hand was getting tired of sitting on the CTRL key...

[AlmasSuljevic]

Hi Jeff_M,

I just sent you a private message through this interface asking for files. Did you get it?

[neilyj666]

The hotfix seems to be working........

[Jeff_M]

Yes, Almas. Message received. No need to look further, I loaded the same drawing in a non-updated C3D install and experience the exact same lagginess (is that a word?). So as the devteam suspected, it's not related to the hotfix.

[klugb]

I have the same issue with our pipe networks displayed in the toolspace preview at the bottom. On our larger networks it's 30 seconds before it displays.

This (For us) was not because of the hotfix. It was like that before and is still like it after.

The hotfix DID correct the other problems with the "CTRL" fix. THANK YOU!!

[DPK2011]

Glad I found this. This issue was causing bunch of problems (the delays) with my AutoCAD Civil 3D 2012 users. I also now have the glitch of the profile grid not repopulating. Any workaround for that??

[hgohel]

@Jeff_M, klugb, DPK2011 and others -

Regarding the slow performance of pipe network information in the grid view, please see message #15 in this thread.  We have logged it as a defect, but a resolution for that is not included in the hotfix mentioned above.

[O.Maille]

I have applied the hot fix and some of the drawings that were previously crashing now work when opening strutures panel. Unfortunately I still get frozen when trying to select the pipes or structures, most recently under the following conditions;

Just finished drawing pipe network and selected pipe/structure in toolspace while draw dialog is open.

Pipe selected and try to open pipe/structure in toolspace.

Had created an alignment and then profile view including pipes in both cases.

It does work sometimes but these are the two most recent situation i can recall. Generally the stability of civil has always been poor but from 2010 onwards the general staility has been better but UI linked crashes seem more frequent.

Not sure what case numbers you guys wil assign  this but I'm sure you can re-create the issues

[Dave1982]

I am not sure what the outcome of this will be, it is months since I posted a problem on here and I just hope that AutoDesk are working hard to rectify the problem prior to the 2013 release, editing the pipes and structures in the toolspace/prospector is a complete no go area, it hangs up and on some occasions crashes my machine, people pay a lot of money for this software and to release it with a problem as big as this causing lost time and work is really not good enough.

Telling people to use the ctrl key to fix isn't a permanent solution so I just hope that the developers take these posts seriously and realise how frustrating this problem is, I can't believe it is taking this long to find a resolution to a problem that wasn't there in 2011, surely you just backtrack and see what has changed between the two releases?