Topic: C3D 2011

[Cathy]

Is the plan to also upgrade the hardware, and OS to 64 bit, along with the C3D?

We've been on 64-bit hardware and OS for a couple of years now.  It would be nice if the software could take full advantage of it. 

[kevinh]

I just recently updated my OS to 64 bit Windows7 and have seen a great improvement on the number of crashes within Civil 3D 2010.  I am not sure I can remember the last time it crashed since the upgrade.

[rkmcswain]

And if so, what is that going to mean for my VBA macros?  Will they run at all in 64-bit?

Yes, it's 64-bit, and yes your VBA macros will run, although in my testing they run ±10x slower and once you even load a vba routine, the entire application slows down.
See the second post in this thread: http://discussion.autodesk.com/forums/thread.jspa?threadID=695278

[Cathy]

Ugh.  Thanks for the info. 

[CHulse]

Has anyone tried the 32 bit version yet? I am a little afraid to try it...

[sourdough]

And if so, what is that going to mean for my VBA macros?  Will they run at all in 64-bit?

Yes, it's 64-bit, and yes your VBA macros will run, although in my testing they run ±10x slower and once you even load a vba routine, the entire application slows down.
See the second post in this thread: http://discussion.autodesk.com/forums/thread.jspa?threadID=695278

I found the same thing. I also, found that it locks up and am trying to isolate these lockups and report back on them soon.
I'm on Win 7 64 Core  i7 860 3.3 Ghz 8gig C300 SSD Sata 6 w/Nvidia GTX 470. C3D 2010 more stable right now out of the gate in comparison to 2011,
but I'm getting my feet wet, so that will change. One lockup was when you put in a "0" in the points editor for the XY Scale instead of a min. 1.

MJP

[mjfarrell]

One lockup was when you put in a "0" in the points editor for the XY Scale instead of a min. 1.

MJP

I'm still on what shoulod be considered a very weak system here (Vista) and the Zero scale issue does NOT produce a lock up here.

(see attached)

[sourdough]

One lockup was when you put in a "0" in the points editor for the XY Scale instead of a min. 1.

MJP

I'm still on what shoulod be considered a very weak system here (Vista) and the Zero scale issue does NOT produce a lock up here.

(see attached)

Mike
   Well, mine when I accidently did it, it stayed in that dialogue box and wouldn't stop looping and wouldn't release.
Probably just selective erroring just for me. Be curious if anyone else finds this one. Maybe this is a Win 7 64bit thing.

MJP

[mjfarrell]

could also be a(n) OS or version specific fault, if I read correctly you are running 64 bit version on Win 7, this version is 32 bit Vista...I love having too many variables to really solve an issue

[Jeff_M]

My turn for a guess, MJP. DId you have a number of points selected when you edited the scale to 0? If so, it will try to set each & every one of the selected points to 0, giving an error for each one. This could lead one to think it was in an infinite loop if you had thousands of points.

I should add that this has been an issue for all versions, I believe.

[mjfarrell]

hmm, I just tried it in the Points Editor...with a few points selected no error.

the last test, I was in the Description Key Editor...so I did the test wrong(bone head)....either way no lock up here

[Jeff_M]

Did you get that message box more than once, Michael? That's the 'error' I was talking about. Now try to change the scale for 1000 points...

[mjfarrell]

Did you get that message box more than once, Michael? That's the 'error' I was talking about. Now try to change the scale for 1000 points...

nope....just one...I clicked it went away....let me dig up a 1000 points to play with and try

I tried with 2803 points selected...entering ZERO scale produced one error 'enter scale greater than zero' one click dismisses it....

[Jeff_M]

Selected in the drawing and edit one of them, or selected all in the Edit Points panorama and used the r/c header to edit all of them? I've tested this in 2009-2011 with identical results.

[mjfarrell]

Selected in the drawing and edit one of them, or selected all in the Edit Points panorama and used the r/c header to edit all of them? I've tested this in 2009-2011 with identical results.

now THAT begits one a spate of errors just foul enough to send one into a rant....seeing as how long it has been around...interestingly enough I've some how avoided need to scale my points after insertion, in this fashion. 
So my setting that to happen in my Descriptor Keys and simply reimporting my points has saved me all along....