BRISCAD AXIS PROBLEM

KERLOO

I've one seriously problem and not sure your guys have the same as well.

For the briscad, normally i draw for a certain time, and need to flatten the drawing. some times if i dont flatten then the block object or others stuff will be onot in the same axis.

Is there any setting that i could do to solve this problem like forever instead of flatten the drawing everyday?

Louis_Verdonck

The OSNAPZ snap option might be a solution. When OSNAPZ = 1 the Z-value of entity snaps is replaced by the current value of the ELEVATION system variable. By default ELEVATION = 0. In this case all entity snaps will be forced to lie in the XY plane.

Roy Klein Gebbinck

If I look at the dwg you posted in another thread I see a number of blocks that contain entities with non-zero Z coordinates. Which is undesirable in a 2D drawing and the most likely cause of your problem. The _Flatten command does not fix these blocks (because the entities are in a plane whose normal is parallel to the view direction?) and because you snap to entities in blocks the problem is persistent.

You can try setting OSNAPZ to 1 (=ON) in your on_doc_load.lsp file.
To remedy the blocks would require a custom program.

Tom Foster

I think it's a bad habit that experts say e.g. "OSNAPZ = 1" instead of (or as well as) giving the plain-language name of the comand or button, like "In Snap settings/toolbar, click 'Ignore entity snap elevation'". Hard work i know, but if the aim is to spread understanding ...

Michael Mayer

Doesn't "2D Wireframe" Visual Style in Top Plan View prevent
from unwanted Z shifts ?
I am not sure but what would be its meaning else ?

Some more comfortable global options for a 2D Limitation like
a 2.5D snap or even 1D snap would be nice though.

I think it's a bad habit that experts say e.g. "OSNAPZ = 1"

For me Commandline Command Acronym input is also no viable
form of interaction with a Software.
It needs a talent for learning foreign language and memorizing
"vocabulary". While native english speakers may recognize some
meaning in the Acronyms, they may look totally arbitrary for other
language speakers and cultures.
(For me it takes quite some abstraction to recognize a "fsck" as
a "File System CheK")
And if I take a look at the localized Bricscad option, Acronym
(partly) translation doesn't make it any better.
The options variables make it even more complicated.
And Shortcuts, even in multi letter forms and Enter needed also
differ from common standards.
So Autodesk Commands ostracize casual users that use multiple
Software and are dependent from standard input methods.

While Tool Icons are quite "international", work reasonably around
languages and even cultures.
(Icons may be slightly different across Apps but so far I easily
found Tools like "Boolean Union" and such)
Where this isn't sufficient there are the Menus in plain text which need
only some standard understanding of the foreign language plus
the professional technical terms.

But I think the majority of users and target group on that forum
speaks fluently native tongue "Autodesk" and loves text and multi
letter acronyms as a form of Software interaction.

So "OSNAPZ = 1" may be a very adequate form of communication here (?)

DFLY

Ignoring Z is fine for when you are working on a drawing from a surveyor, or a messed up drawing from someone else.
But it shouldn't be necessary in a drawing you make yourself.
Sound like you should go into your block library (or wherever you keep your block files) and flatten the offending blocks.
To check them you can also view them from the side, but sometimes they can be out on the z axis by 10 metres or more.
If you are like me you probably have a block library of thousands of blocks, so best to fix them as you find them as you go about drawing.

Roy Klein Gebbinck

@Tom Foster
If I were to follow your suggestion the time I spend on this forum would increase exponentially and exceed the limits of what I consider acceptable. So, yes, I do assume a certain level of knowledge. But if somebody doesn't understand my contributions they need only point this out and I will be happy to provide more details.

Kerry Brown

@Tom Foster said:
I think it's a bad habit that experts say e.g. "OSNAPZ = 1" instead of (or as well as) giving the plain-language name of the comand or button, like "In Snap settings/toolbar, click 'Ignore entity snap elevation'". Hard work i know, but if the aim is to spread understanding ...

Tom,
With the hints given in the 2 posts previous to yours this is easy for you ...
And saves others in this Peer To Peer group wasting time ...

http://lmgtfy.com/?q=osnapz+BricsCAD

http://lmgtfy.com/?q=osnapz+bricsys

Regards,

Tom Foster

Speaking on behalf of myself as a one-time beginner who needed a lot of explantion, and of myself as an experienced user who still doesn't know the variables by heart, I have great difficulty on forums where particpants like to show how advanced they are by using 'expert' jargon.

I continue to get months of bafflement on such forums. Luckily, custom on this one is much better than others.

Kerry Brown

Our expectations of peer assistance is radically different.
I would never (almost never) ask a question without being able to demonstrate that I'd done my homework ...
and if I suggested to the person who took the time to respond that they should reproduce the available documentation just for me
I'd expect to be told to get knotted ... or slapped around the head with a fish.

Jason Bourhill

IMHO it would be useful if the forum included a tool to easily link to commands etc. available in HELP. e.g. OSNAPZ. Wouldn't need to be a direct link, could be just a search of help for that term.

This would allow the poster to keep things brief and allow others to drill into detail if they require.

Regards,
Jason Bourhill
CAD Concepts

Kerry Brown

Hi Jason,
The difficulty is that OSNAPZ is not a command and can't be called directly at the command line ,., it's a variable and doesn't have it's own page in help. it can be accessed via SETVAR

DoIt: SETVAR
Variable name or ? : osnapz
New current value for OSNAPZ [1 for ON/0 for OFf] <0 for OFf>:1

A search of help turns up 36 reference pages and the best seems to be help.bricsys.com/hc/en-us/articles/360006739434-Entity-Snaps which is the page you link to. Without it's own page ( or changes to the linking system ) it won't be immediately accessable via a link.

Kerry Brown

This "Inside BricsCAD V19" from here:
https://help.bricsys.com/hc/en-us
Download free books and guides
https://campaigns.bricsys.com/inside_bricsys_guidebooks

Around Page 277 has a decent mention.

Torsten Moses

Dear Kerry,

"The difficulty is that OSNAPZ is not a command and can't be called directly at the command line"

any system variable can be called directly at command line, just like a command :-)
many greetings !

Kerry Brown

@Torsten Moses said:
Dear Kerry,

"The difficulty is that OSNAPZ is not a command and can't be called directly at the command line"

any system variable can be called directly at command line, just like a command :-)
many greetings !

DUH! me
I probably tried with SNAPZ ....

Thanks Torsten, nice to have been corrected.

//======

I believe OsnapZ is not directly findable in help though. Some users will need to jump through some hoops to find the definition.

Regards,

Richard

@Tom Foster said:
I think it's a bad habit that experts say e.g. "OSNAPZ = 1" instead of (or as well as) giving the plain-language name of the comand or button, like "In Snap settings/toolbar, click 'Ignore entity snap elevation'". Hard work i know, but if the aim is to spread understanding ...

Tom, thank you for reminding us. I'm a former instructor (unofficial and many years ago) for a large EDU. I think you make a very good point and and I'm with you. I would rather have too much info at my fingertips when reading a topic, than not enough. The "Experts" who have posted that they do not want to muddle through the "extra" stuff can just skim through and allow it to be there to benefit newbies, etc. An "expert" can quickly pick out the meat of a topic or lesson and may have spent an extra 10% of time doing so. Meanwhile, the ones who are newbies have got a complete picture and have not wasted their time on the whole thread that they otherwise would be unable to understand. I hope I didn't step on any feet here... No offence meant.

Roy Klein Gebbinck

@Richard
I do not know if I qualify as an expert. But since Tom used the plural and qualifications that also apply to my contribution I felt I had to respond. I think you have misunderstood my objection. What I meant is that to write (not read) the additional information would require significantly more time than I am willing to invest.

Michael Mayer

I think all are right.

It would be nice for beginners and non Autocad background users
if answers would also offer common Menu and Pallette Tool terms.
And is ok to hint at.

Roy,
your expertise and condensed "Pro" answers are very appreciateted
anyway and always better than no Roy answer.

No one is forced to help or answer.
And anyone can do in the way and effort as he or she wants.

Kerry Brown

As far as I can see, Louis and Roy answered the OP in the first 2 replies. All the rest is unrelated to the topic.

The thing that peeves me is that no-one said thanks.

Regards,

Jim Canale

I move my 2D drawing views to model space and apply dimensions there, because I don't like the limitations of the tools for dimensioning in paper space. Also, I've noticed when using ordinate dimensioning, I'm not always able to select the correct UCS origin from the paperspace viewport. I understand that my 2D views will not automatically update if I move them to model space. I wish Bricsys would add that capability to the program.

At any rate, when I move these views to model space, they are locked in blocks. I find frequently that I cannot snap to intersections of lines, or measure diameters, or radii, until I explode the block, and flatten all the components of the block. So apparently the PROGRAM, not users have introduced Z axis offsets to the 2D objects.

Gary Adams

@Kerry Brown said:
As far as I can see, Louis and Roy answered the OP in the first 2 replies. All the rest is unrelated to the topic.

The thing that peeves me is that no-one said thanks.

Regards,

I second your comment!

Most of my time spent in this forum is as a lurker; occasionally I'll will ask a question. Invariably the same few people post answers (you know who you are), yet they rarely seem to get even a simple "Thanks" in return.

On behalf of all those who ask questions, get an answer (or answers), and fail to say thanks, I would like to say "THANK YOU for your time and effort!" to the forum regulars who provide a valuable service and serve as knowledge resources for the Bricscad community.

D_sharma

For me Commandline Command Acronym input is also no viable
form of interaction with a Software.
It needs a talent for learning foreign language and memorizing
"vocabulary".

Tom Foster

You can modify the acronyms to something that makes sense and is easily remembered. Once you have them, it's very easy quick input.