Upgrade object after editer ?

[bla bla 2]

Hi, how we can upgrade to object, to level after have edit much of time ?

Cheers, 

[Dune]

Ha, another Bastien riddle 

[bla bla 2]

Lol, I mean if you can import an object and add something in addition to the same object, just filename ?

[Dune]

Still a bit of a riddle, especially the last words. You can import and populate on an object....

[j meyer]

Do you ask, if it's possible to change the geometry of a model you already use in
a scene and import the altered mesh back into TG under the same name and thus
keeping your already set up shaders in TG?
If so, the answer is yes.

[bla bla 2]

Do you ask, if it's possible to change the geometry of a model you already use in
a scene and import the altered mesh back into TG under the same name and thus
keeping your already set up shaders in TG?
If so, the answer is yes.

Yes  , and how ?

Cheers,

[Dune]

Ah, Jochen, you're smart.

But you have to be careful if you do this; I occasionally change an object, save it under the same name, but when opening an older file that has this object, it loads the old one. I guess it depends on the settings you saved with the old one.
Then I have to go into the population and import 'the same' tgo again, replace, and then it has the right shaders.

[j meyer]

The model in your scene should still be an obj (not saved as tgo).
You can take your model and change the geometry or add to it, just
make sure that you don't change any of the materials/shaders in
your modeling software. Count and names have to stay exactly the same.
That's essential here.
Save your model again under the same name and replace the old file with
the new one.

Ulco - might have to do with the model being saved as tgo. I only save as tgo
for sharing other than that it's more versatile to keep them obj and save a tgc,
which saves some more parameters anyway.

[Dune]

You're right, Jochen, it's the settings saved with tgo that gives the re-import trouble. I hardly ever save as tgc, somehow that seems 'less of an object'. Crap of course.

[bobbystahr]

You're right, Jochen, it's the settings saved with tgo that gives the re-import trouble. I hardly ever save as tgc, somehow that seems 'less of an object'. Crap of course.

I save all buildings and autos with glass parts as .tgc whether they're .tgo  or .obj as both have windows which need to be loaded separately and .tgc is a workaround to grouping for me.

[KyL]

What you can do is simply do "versions" of your object by adding a _v01, _v02, ... everytime you change your model.
Most of the time I like to do that with the scene used to create the object, but the final exported .obj stays with the same name. That way every time you open Terragen you always have the latest version.

One important thing to keep in mind is that when you do this, the internal network of the object stays the same as the first time you loaded it. So if you add or remove shaders, change part names or things like that, you will have to delete the obj reader and create a new one.

A .tgo export a compiled version of the object as well as the internal network. It's quite useful if you are done with one object as it will load much faster than obj files and bring all its shader with him!

Hope that helps!