Distance to origin: can it cause problems?
-
can a general slowness in a model have to do to its long distance to origin?
-
Not that I've experienced, but it does create the clipping issue and other visual glitches.
-
Yes, it can in my experience. It will cause very odd laggy behavior. Just feels like the model is not feeling well
-
@chris fullmer said:
Yes, it can in my experience. It will cause very odd laggy behavior. Just feels like the model is not feeling well
and will the model start behaving normally as you move it closer to the origin? or, conversely, is it the same to move the origin closer to the model?
-
In my experience, when geometry is somewhere in outer space, it does not only clip horribly but is also very sluggish. Performance drops and often even the geometry seems to be weirdly distorted.
If you have something like this, you need to move it to the origin. Unfortunately moving the origin does not help.
There is another solution however; turn it into a component (now the component origin will be close to the geometry), right click and "save as..." If you open this component as a normal model, it will behave normally as its origin is the original component origin.
I use this methdod when for whatever reason I need to keep the original location of the parts (because other pieces are coming in and need to keep the relative position or anything).
-
@gaieus said:
In my experience, when geometry is somewhere in outer space, it does not only clip horribly but is also very sluggish. Performance drops and often even the geometry seems to be weirdly distorted.
If you have something like this, you need to move it to the origin. Unfortunately moving the origin does not help.
There is another solution however; turn it into a component (now the component origin will be close to the geometry), right click and "save as..." If you open this component as a normal model, it will behave normally as its origin is the original component origin.
I use this methdod when for whatever reason I need to keep the original location of the parts (because other pieces are coming in and need to keep the relative position or anything).
csaba,
great tip! just turning the whole model into a component changed things radically for the best. my model is now flying as it had no weight.
perhaps you do not always have to "save as" and reopen it.
-
Thank you for that tip!
I just ran into a model today that is acting sluggish.
There are objects located quite a ways away from the origin.
I will make it a component first thing in the morning.
paul
-
And I was asking a while back if anyone knew how far was too far? (when you start noticing the negative effects)
We already know how small is too small, don't we? -
@edson said:
just turning the whole model into a component changed things radically for the best. my model is now flying as it had no weight.
perhaps you do not always have to "save as" and reopen it.
Hm. I do not know what the reason for that is as it does not seem to be logical - unless the new SU 8 feature, "working axes" has some effect here.
@mitcorb said:
And I was asking a while back if anyone knew how far was too far? (when you start noticing the negative effects)
We already know how small is too small, don't we?I really cannot tell. When I am far, I am very far (hundreds of kilometres away from the origin). Clipping can hit in when you are just hundreds of metres away and will increase as you are getting farther. But that is just the first symptom.
-
Don't do it. Google themselves even say so.
Depending on the distance from the origin, and simply speaking, the accuracy of the lines themselves can actually become inaccurate due to the software running out of decimal points from the origin. It's not as bad in SketchUp but all programs suffer this and some tend to be better at it than others. I know that Maya is shocking at this when you have drawings kms away from the origin.
Advertisement