topic Re: Working Units accuracy with zero decimals in Modeling

Working Units accuracy with zero decimals

Vinicius Lima — Thu, 02 Mar 2023 21:23:13 GMT

Hello everyone!
I Use Archicad since AC12, and its incomprehensive for me since than:
If you set in "Project Preferences" > "Working Units", to zero decimals (doesn't matter if it is in meters or centimeters or other unit), if you create a wall with 1.24m lenght for example, EVEN if Working Units was setup to zero decimals, the software accept this decimals (creating a dimension you can check it).
Archicad shouldn't ignore your decimal typing, if you setup Working Units to zero decimals, and create a wall with just 1m?
PS: I'm not saying that the decimals shouldn't exist in this setup, becouse if you create chanfered walls it will happen anyway, but in the input (when you type) it shound't happen with the "Working Unit" set do zero decimals.

Re: Working Units accuracy with zero decimals

runxel — Fri, 03 Mar 2023 00:39:20 GMT

No, you got that wrong. It works just as intended. This setting is just for display.

I wouldn't want my input to be cutoff or rounded randomly. (It also makes no sense? If you want less, just type less??)

Looks more like you should look into "snap to grid".

Re: Working Units accuracy with zero decimals

Barry Kelly — Fri, 03 Mar 2023 00:49:12 GMT

So let me try to understand this.

Your working units is set to meter with no decimals.

When you type (or stretch) a length of 1.24m, you want Archicad to only make the wall 1.0m long as per the working units?

That is not going to happen.

The Working Units is just what is displayed as you model (tracker) and in the dialogue boxes (heights/lengths).

Archicad still models with full accuracy - as you said if you trim angled walls there will be decimals.

If you want modules of 1m, then you set your snap grid to 1m and activate it so you can only work to the grid intervals.

Personally, I don't use grid snap.

If I want my wall to be 1m, I will type that in the tracker, so I get exactly 1.

If you are saying you do type 1 for the length and then you get a wall that is 1.24, then we need to look at the way you are doing this as it shouldn't happen.

If you are using the tracker for input, then you should get exactly what you type.

Barry.

Re: Working Units accuracy with zero decimals

Vinicius Lima — Fri, 03 Mar 2023 23:05:38 GMT

Hello guys. Thank you for your answers.
I just don't see any reason for you to use the measure tape (for example) and it gives you a wrong information, blinding you to a systemic error. I worked as a BIM Manager in an architecture office with more then 30 users, and people just type thinks wrongly (even with the tracker), and once you type one time wrongly, the domino effects goes on. We have tried the "Snap Grid" but it doesn't work if you have curves, and chamfer walls/forms. I still think that the Working Units as it is, induces the user to an error because it is hiding from you the truth, the real measure. Perhabs, the "Measure Tape" at least, should aways show with all decimals, being aside of the Working Units settings?

Re: Working Units accuracy with zero decimals

runxel — Sat, 04 Mar 2023 17:45:58 GMT

Okay, got that, but you're talking about different things.

The model quality control is not determined by how much you could see; there would need to be a cutoff at some arbitrary place anyway (Quick: Show us what 1/3 would look like as decimal, seeing all decimals of that!). So for QC what I did was having an expression evaluating the length of a wall and returning "good" or "no bueno". Then I have a schedule and I can quickly determine the walls that are odd.

Also everybody in my office needs to draw with the maximum available decimal places, and entering more than is visible is prohibited. It is about educationing the staff, too.

But letting the system doing something in the back not transparent to the user and basically overriding what they are drawing is clearly an anti-pattern.

Re: Working Units accuracy with zero decimals

BrunoH — Mon, 06 Mar 2023 13:10:21 GMT

To help solving that type of mistakes, for example, i have created a cotation set that clearly highlight acuracy problems and a GO that show static cotation problems. Every one in the office work with this.