Started by commorancy, May 26, 2013, 05:15:00 AM
Quote from: jaf on May 27, 2013, 09:20:22 PMJust my opinion.... A tgo is a Terragen object (or object population) to be placed somewhere in a scene. Where it is placed, the orientation, etc., is a function of the scene (tgd) file via user interaction. I think it would be counter productive to store the tgo position/orientation information with the tgo file, since it's unlikely one would want it to always load in the same position/orientation in different scenes. Knowing it loads to 0,0 makes it easy to find and move. I keep a text editor open just for the purpose of recording positions of objects as I build/replace them.  I forgot to add... it would be nice to have a copy all object data button (or right click node function) for each object, and maybe a save option.
Quote from: Oshyan on May 28, 2013, 03:31:44 AMAs jaf describes, this is basically by design. A TGO, like an OBJ, is intended just to store the object-specific (rather than scene-specific, or relative-to-scene) parameters. In fact, we are generally recommending that people save their objects and shader networks as clip files now *instead* of TGO as this preserves the OBJ editing capability that you might want, while also preserving the Terragen shader networks you have attached. Since you can save a clip file with just your object file or population in it and no other nodes/connections, it is functionally equivalent to saving a TGO, but has the benefits of saving position info, etc. that you seem to desire.- Oshyan