I find 10-15 minutes more practical. AutoSaving every 3 minutes will certainly slow you down too much, especially when you go into larger models.

15min is about the maximum before you get into a problem of if the program does crash, how much work needs to be re-done. Redoing 30min of work can be crushing (from personal experience). 15min of work is more annoying.

I would not revert entirely to auto save. That's bound to fail. Just remember to manually save every once in a while, especially after a major milestone in your model, because you also can't entirely rely on autosaves either.

Decrease the minimum on Network licensing.

How low? 2 would be nice. I have 6 potential users, who may jump between 7 computers depending on the task (one computer is a render or complex model computer for all to use). However, each user only uses the program in sparse bursts, only up to 3 at once, but I'm not allowed to have a network because 50 seats in a small office is insane. This becomes very annoying.

I will gladly pay more per seat to unlock network licensing.

Yes, I read through that post prior to posting this, but from what I read, it's not actually moving the origin in the model, just georeferencing the origin in GE.

Re-referencing the geolocation would not solve the main issue that I'm experiencing with the model being so far from the origin, which is that many Ruby scripts fail.

The above post was my personal account. (same person)

-Amanda

Does anybody know of a way to move both objects and scene views together to the origin.

I have a model that somebody else was working on before, and they changed the axis thinking this would fix an origin location problem.

They then proceeded to make a scene camera path for an animation of 37 scenes.

I'm now at the end of a long process and everything is going wrong while I was trying to render the animation. I unmasked the origin problem, but would like to avoid having to re-do all of the scenes when I move the model back to the origin.

Is there a faster way?