Topic: C3D 2013 bug

[sinc]

I think the default AutoCAD functionality only works if you create the annotative objects in a paperspace viewport.  It doesn't work if you want to create MTEXT/MLeaders/Dimensions in modelspace.

[huiz]

The option to align objects to Layout is off course only visible in a Layout. In Modelspace the objects are aligned to WCS, in a Viewport they are aligned to the Layout.

Scaling objects is setting the annotation scale which can be set in Modelspace and also in Viewports.

I've had no troubles with this system but it is quite difficult to understand. But that is setting label styles in Civil3D also.

[sinc]

I am not seeing that.

Also, C3D labels pay absolutely no attention to Annotative styles.  They use their own independent methodology, since they existed before core AutoCAD got Annotative Styles.  C3D Labels ALWAYS use the text height set in the C3D Style, and ignore the Annotative settings in your text.  It really doesn't matter what you have "Annotative" set to in your Text Style...  C3D only honors the setting in you C3D Label Style.

[Chris]

Speaking of C3D 2013 bugs, is anyone having an issue with panning and zooming within drawings?  at our office, if we want to pan or zoom transparently, it is extremely slow, we basically have to start a command, then pan or zoom around to eliminate the lag.  If we watch our resource monitor, as we are panning and zooming, the network traffic on our machines shoots through the roof, when we stop panning or zooming, it drops back down to almost 0 levels.  I think I've heard of this before, but cant remember how to resolve the problem.

[mjfarrell]

This suggests that you stop 'panning' and 'zooming' and start using the toolspace to 'Zoom To' the objects you are interested in.

[CHulse]

Not all objects appear in toolspace though...

[Chris]

This suggests that you stop 'panning' and 'zooming' and start using the toolspace to 'Zoom To' the objects you are interested in.

this applies to panning and zooming in any drawing, even in paperspace drawings, where one might zoom into create a leader or note or any other annotation.  zoom to is not a practical solution for this problem.  I can zoom extents and zoom window faster.

[huiz]

Speaking of C3D 2013 bugs, is anyone having an issue with panning and zooming within drawings?  at our office, if we want to pan or zoom transparently, it is extremely slow, we basically have to start a command, then pan or zoom around to eliminate the lag.  If we watch our resource monitor, as we are panning and zooming, the network traffic on our machines shoots through the roof, when we stop panning or zooming, it drops back down to almost 0 levels.  I think I've heard of this before, but cant remember how to resolve the problem.

Harware acceleration might help here.

[Chris]

its off right now.  Turning it on doesnt seem to affect the problem.

[Craig Davis]

I've found this very annoying also.

Rotated UCS works fine. well until Autodesk broke it in this version.

Hopefully a fix soon. Driving me nuts.

[Craig Davis]

I've had no troubles with this system but it is quite difficult to understand. But that is setting label styles in Civil3D also.

Only problem I've mainly had with text annotation is when using CHSpace to bring text objects from the model into a layout. If the text doesn't have a 1:1000 (we use m units in modelspace) annotation it disappears.

You would think that Autodesk would know if you're bringing text from model space into paperspace that you'd want the text to be visible so it should automatically add the correct paperspace annotation scale to it. Don't have to do it much but annoying when you do.

[Chris]

This suggests that you stop 'panning' and 'zooming' and start using the toolspace to 'Zoom To' the objects you are interested in.

this applies to panning and zooming in any drawing, even in paperspace drawings, where one might zoom into create a leader or note or any other annotation.  zoom to is not a practical solution for this problem.  I can zoom extents and zoom window faster.

Sorry I didnt post back my solution sooner.  Come to find out after much digging, we had a standards file that was attached to our old drawings that was removed after we switched to 2013.  so all those old drawings were looking for a file that didnt exist.  I added the standards file back into our support paths and the problem went away.

[Mark]

Here's one for ya. This has happened now 4-5 times, same point. Start the LINE command, switch to 'PN enter '40' as the start point. Looking at the screen shot you'll see where the line actually starts.

[mjfarrell]

Here's one for ya. This has happened now 4-5 times, same point. Start the LINE command, switch to 'PN enter '40' as the start point. Looking at the screen shot you'll see where the line actually starts.

yes, however is that a (mal) function of the command or is it related to the point label style on that point?

where is PN 40 really at?

[Mark]

Here's one for ya. This has happened now 4-5 times, same point. Start the LINE command, switch to 'PN enter '40' as the start point. Looking at the screen shot you'll see where the line actually starts.

yes, however is that a (mal) function of the command or is it related to the point label style on that point?

where is PN 40 really at?

What is a 'mal' function? The coordinates of 40, at the node, are the correct coordinates.