Recent Posts

Pages: [1] 2 3 ... 10
1
Image Sharing / Re: ground
« Last post by bobbystahr on Today at 12:56:26 AM »
Yup, that's ground for sure...nice
2
Image Sharing / Re: Guillemot rock
« Last post by WASasquatch on July 22, 2019, 10:02:51 PM »
I always think the PT versions are better with lighting and shadows. May just be me. Love the shelfing.
3
Image Sharing / Re: textures test
« Last post by WASasquatch on July 22, 2019, 10:01:39 PM »
They look pretty decent in TG minus some amplitude issues. Did you make these?

Very deserty.
4
Image Sharing / Re: textures test
« Last post by Beep the Meep on July 22, 2019, 09:50:09 PM »
5
Image Sharing / textures test
« Last post by Beep the Meep on July 22, 2019, 09:28:14 PM »
6
Image Sharing / Re: Valley and stream.
« Last post by WASasquatch on July 22, 2019, 08:57:42 PM »
You'd be shocked to by what nature creates that we find as erroneous displacement here in Terragen. Often I'll knit-pick both clouds and displacement, and take a walk through the woods (always interesting cliffy stuff and erratic boulders and stuff) and be immediately corrected by nature doing all sorts of absurd geometric shapes, even in clouds that I often pass up in seeds as (bad).

Granted, straight tears into the huge void that is a the planet is another story. lOl

The trick really, is mixing these types of noises with other noises, less noises, etc, to create a realistic continuity. When I find something interesting in nature, it isn't repeated over and over. :P
7
Terragen Discussion / Re: Temp output file naming
« Last post by Oshyan on July 22, 2019, 07:38:27 PM »
For temp output this is not user editable at this time. However as described in the change log you can use several new variables in your *regular* file output names and you can control how/where they're used (in the Sequence/Output tab).

${BUILDNUMBER} // e.g. 4.4.09.1
${CAMERA} // the name of the camera at the moment the frame started rendering
${IMAGETYPE} or IMAGETYPE // e.g. tgSurfDirect, tgCloudRgb etc. If used for the main output it will insert tgBeauty
${LAYER} or ${RENDERLAYER} // the name of the render layer at the moment the frame started rendering, if one was connected
${RENDER} or ${RENDERER} or ${RENDERNODE} // the name of the render node at the moment the frame started rendering
${RENDERSECONDS} // render time in seconds, e.g. 134
${RENDERTIME} // render time formatted with hours, minutes and seconds (e.g. 1h07m24s), or without the hours if shorter than 1 hour, e.g. 02m14s
${TGDNAME} // the name of the last saved or loaded TGD file at the moment the frame started rendering (or "Untitled"), without the path and without the extension

If you want to always have your custom file naming setup, just use "Render All to Disk" instead of the regular Render button.

- Oshyan
8
Correct, because those files (including the key file) are all kept in a central app data folder for each major version of Terragen (2, 3, 4).

- Oshyan
9
Terragen Discussion / Re: Temp output file naming
« Last post by WASasquatch on July 22, 2019, 07:13:27 PM »
....

Comes in handy when one opens a old scene and wants to get a quick idea of how long the render took. (●'◡'●)

It does. I always enter render times into saves so I can see how the software is improving over the years if it at all.
10
Terragen Discussion / Re: Temp output file naming
« Last post by jaf on July 22, 2019, 07:09:01 PM »
Yes.  I've been manually entering that data, plus number of cores/threads/signature (I keep all my signatures so I can identify the hardware and drivers I used) into the project settings (lower left corner of the UI) for a few years.  Wouldn't think that would be too hard to implement.

Comes in handy when one opens a old scene and wants to get a quick idea of how long the render took. (●'◡'●)
Pages: [1] 2 3 ... 10