Hi Michael,

The parts are away from the origin due to the large assembly they belong too. I cut and copy this position from my master wireframe and then I work on the part alone saves hiding many parts and isolating one part. When I finish the part I paste back into the assembly really easy no need to position.
This probably explains the bug and when I do a standalone test usually on a fresh part close to origin doesnt happen.


With the construction as it a sheetmetal part the work flow I use revolves around using planar surfs - I usually create a series of rectangles to give me base shape which I trim if needed I then join them and then apply radiuses as required and finally apply shell command to desired thickness works as a recognizably sheetmetal part in other programs like Solidworks Sheetmetal and Autopol.

In the many parts that I usually create the radius issue pops up every now and then with most of the radiuses being completed and only one random corner misbehaving.

thanks for your time - the ARC thickness script would certainly make Sheetmetal more streamlined within MOI.

Michael,
So for these "far away from origin" issues, does a "cplane" bring the object to a local coordinate system or do the underlying calcs still look at "world coordinates"?

Hi Burr, all actual calculations are done in world coordinates. Setting a cplane just changes the UI layer, everything that you create is still actually stored in world coordinates.

But it could be possible to internally move objects to the world origin, do the fillet calculation and move it back again transparently. That's probably something I ought to do for v4.

- Michael

Ok thanks michael!
I guess the other side of that is peoples particular setup and job at hand...
So i work in "inches".... But if i start modeling a 175 foot object (or i guess sci fi guys modeling 1000 foot spaceships), things start moving away from world zero...

Does changing my unit system to feet or meters or miles change that initial interaction with "how far away from zero" i am?

Is there something like a "scaled environment" where i could start a project with an initial declaration that i will be modelimg at "a larger scale"? (I guess that would mean i couldnt model detail then, because it was expecting BIG stuff, side effect......)

Hi Burr,

> Does changing my unit system to feet or meters or miles change that initial
> interaction with "how far away from zero" i am?

Yes, if it means you'll be using small numeric values, like say x = 10 in meters rather than x = 10000 in mm. But the only thing that matters is the number itself, that you're using less digits in the number values.


> Is there something like a "scaled environment" where i could start a project with an initial
> declaration that i will be modelimg at "a larger scale"? (I guess that would mean i couldnt
> model detail then, because it was expecting BIG stuff, side effect......)

Well there is an automatic mechanism that adjusts calculation tolerance to be a percentage of the object size so it adapts to the current object being operated on. But that's a somewhat different issue than losing fractional precision in arithmetic because of larger numeric values being used in coordinates.

- Michael