Can't Export from Terragen 2

[Mohawk20]

Hmmm, annoying!
Have you tried combining the output of multiple camera angles? (I know the object file size will increase, but it's still worth a try.)


Or you could try the other method Oshyan wrote about, plugging your fractal terrain into the 'Shader' input of a 'Heightfield Generate' and then export like you did before.

[Cephei]

Hmmm.... That Seems confusing, So bare with me while my mind attempts to comprehend this.

In theory, if I was to have 4 Cameras Each pointing to a single spot (The centre of the scene) and a fifth camera pointing down from the top, down; then Link all of them to the render... I would come out with that very scene... but with all sides, no holes or missing sides... just a single model.

As for Oshyan's method. Jee I would love to try that... but I seem to have err... well... misplaced my Fractal terrain, Seriously... the Fractal terrain is neither in the Terrain nodes nor the graph... so I'm a tad lost. :dumbfounded:

[jo]

Hi Cephei,

Try looking for it in the Node Network view list. It could perhaps be inside another node. It would be interesting to know if it is, if it is then it's a problem we should try and address before release.

Regards,

Jo

[Mohawk20]

If you attach the tgd to your next post I could set up the nodes for you, and then I can tell you where they were hiding as well 

[Cephei]

Be my guest....

Wait how do I attatch the file?

[neuspadrin]

See where you type replies? just below there should be a "additional options". clicky.  Choose file, and post.  It allows you to upload most file types that are important to share, with only a limitation of a file that is below 512kb

[Cephei]

Ah thank you!
Here it is...

And btw, I can no longer open it... I don't know why... TG2 crashes everytime I open it.

[neuspadrin]

switched one set of nodes, heres my switch. switched the output of heightfield into the input of mountains, not to blendshader of mountains.

Also set the render camera to not be wayyyyyy off in space far far away.  Can you open now no crash?

[Cephei]

Damn you're good!
Yep it works perfect now! no problems. And yea the camera thing I just wanted to have a good full view of the planet .

Thanks a lot!, I'm going to retry the export... see if it works any better! .

EDIT: Alrighty yeah I checked the model out in max, still has a few holes but the outcome is far greater than my previous attempts, Thank you very much Neuspadrin!

[Oshyan]

The holes are no doubt due to it being camera-dependent. Using the Heightfield Export LWO method should work better.

- Oshyan

[fxmodels]

As I said, your terrain is procedural, as opposed to a heightfield. All you did now was export a new and flat heightfield.

What you have to do is this.
Right-click in the node network and from the menu select 'Create other' -> 'Lwo micro exporter'.
The new node (gray coloured) should have appeared somewhere near the mouse cursor.
Double-click it to change it's settings.
next to 'Filename' is a blank field and a 'save' icon. Click the icon. Browse to a folder you want to save the lwo file in, and name the file to your liking, but make sure you add .lwo at the end as that doesn't happen automatically.

Now go to the render tab of the main window. Select the renderer you want to use (eg. 'Full Render'), to change the settings.
In the lower left you have some tabs, go to the last tab called 'Sequence/Output'. If you purchased Deep+Animation you can render a sequence here, but you can also add a Micro exporter.
To do that, check the box of Micro exporter (and you can uncheck the box above that if it's checked).
Than click the '...' button on the other side of the blank field.
Go to 'Assign micro_handler' -> '"/Lwo micro exporter 01"' (the lwo exporter we just created).
Now that's done.

Last thing we need to do is place the camera in a spot that overviews the area you want to export.
The should be like the image you posted above, so that's good.
Now set the resolution to something square, like 512x512, and the render detail to 0.5.
(I once exported at full render size and detail, but the file was so large LightWave could not handle it...!)

If you have steep cliffs or overhangs, do multiple renders/exports of top and side views to capture all vertexes, as the micro exporter only creates vertexes that are visible in the render.
You can render again at higher settings with the Micro exporter box unchecked to create a top view image map if you want...


I hope you have all the information you need now.

Hi ... I tried this LWO micro exporter just as you outlined and all I get is a 1k lwo output file which when I try to load it by importing it into Cinema 4D say out of memory, which to me means that the exporter is not functioning properly or I did something wrong. I followed your instructions above exactly.
Any ideas? Oshyan?  Someone?
Thanks,
Marc
fxmodels.com

[Mohawk20]

Erm... 1k? 

That is a bit strange.
I don't know how that could ever make you run out of memory...

Oshyan? Matt?

[Oshyan]

It sounds like the export process might be stalling or crashing. What is your detail level and resolution? Did you allow it to complete the rendering process?

- Oshyan

[fxmodels]

It sounds like the export process might be stalling or crashing. What is your detail level and resolution? Did you allow it to complete the rendering process?

- Oshyan

Hi Oshyan,
My res is set for testing at 512x512, and the detail level is .50625...
Here are my settings directly:
http://www.fxmodels.com/CG/TG2-SettingsForMicroExport.jpg

I rendered the image, then looked for the exported file and it was there, but was 1k in size as an LWO and there was a 2k LWS file too. On the sequence/output tab, I unchecked the Extra Output images, checked the micro exporter  and set it to the lwo micro exporter 01 that I had available. I am on Vista 32.

I am anxious to see this work and am pleased that it looks like this is exporter is available.
Thanks Oshyan,
Marc

[fxmodels]

Erm... 1k? 

That is a bit strange.
I don't know how that could ever make you run out of memory...

Oshyan? Matt?

I agree... I am thinking it is exactly the opposite. Perhaps it is a divide by zero type error along the way...