How to be sure to enter Z ccordinate??

I am trying to make some drawing symbols in 3D.

Most of the time it is OK, but some times I am not asked about the Z ccordinate (The height of the 3D object)

Is there a system seting somewhere that controls this?

It seem that the auto depth is half of the last used value for that, when I lok in the properties for the box.

I cannot unfurtunaly not edit any of the values here.

 

Comments

  • Forgot to tell taht it is V12.1.4.1 I am using.

     

  • The base of 3D entities is created in the XY-plane of the current UCS, unless you use entity snaps.

  • Hi Svend,

    You may want to take a look at these three commands oin GeoToools which have been designed to input 3d z values without having to resort to the .XY entity snaps.

    http://www.4d-technologies.com/geotools/manual/draw_tools.htm#EASY3dpoint

    The commands are GT_EASY3DPOINT, GT_EASY3DFACE and GT_EASY3DPOLY.

    It is a common frustration in CAD of not being able to enter the Z coordinates with ease.

    These three commands are soon going to be part of FREEWARE in GeoTools. 

    Regards
    Rakesh Rao

     

     

  • I use entity snap for X an Y coordinate, but BC assumes some small number for Z coordinate. This Z coordinate is also wrong when it sets it by BC.

    Is there a system setting where I can force BC to ask about the Z coordinate.??

     

  • Svend,

    Yes, by entering .XY when Bricscad is asking for a point, you are forcing only X and Y from the picked location. Z coordinate will then be asked by Bricscad. Does this answer your question?

    - rakesh

  • I use the BOX command from the toolbar and point out first corner of a 2D square, then the opposite corner of the 2D square.

    Then normally BC will ask about the height. I type in the height or dept e.g. -14 to make it 14 mm deep from the XY plan.

    The problem is that some times it does not ask about the Z coord depth, but selects some (wrong) No. to be the Z coord.

    I cannot change that size in the properties.

     

This discussion has been closed.