Enscape shaking when to far from rhino origin

Enscape General
, ,
1

Enscape shaking.PNG.jpg
Enscape shaking.PNG.jpg749×668 93.5 KB

Hi.

This is probably a well known issue, but its very irritating for every day use:

When building a rhino model for architecture projects, its based on real coordinates and origin (same as engineers etc).

That means that the origin is often far away from rhino´s origin which makes enscape shake and unusable.

The only fix is to move the geometry to rhino´s origin manually every time we open enscape.

This creates big issues when exporting/importing models to engineer team which we do every other week.

Any hopes for fixing this?

2

Distance from the origin is an issue with every 3D software, not unique to Enscape. For your sanity it is better to just plan on moving the geometry every time you get a model. Figure it out once and keep it consistent (20,000 ft in the x direction, 10,000 ft in the y direction, or what have you) and let the engineers know, so they can apply the same transform back the other direction.

3

Thanks for the advice rifkin. Unfortunately its very difficult to get all engineers to not have a “real” origin point. When you work with municipalities and a huge team of engineers the project have to bee in a real location. Otherwise everyone’s files would have to be moved to geo specific location at the end of a phase or a project. This would never happen :frowning:

4

Sure, I’m not saying the engineers need to change their origin point. I’m just saying when you import their information, figure out how far you need to move it to get it close to the origin. Keep track of that and keep it consistent.

Granted, communicating to a large team that your model needs to be moved to fit in their coordinates is not realistic, so better to just move it yourself before you send them back an export. Yes, it is a couple extra steps but shouldn’t be a huge burden if you are only exchanging models every other week.

If you want to get fancy you could set something up with blocks/references, you would have a working model and an “export” model, set up links and insertion points and you wouldn’t need to think about it much after that, it would just be a matter of updating links when you get new files or need to export.