Terragen 4.4.60 is the latest Frontier Build for Windows and Linux (render node). If you're on Windows and you have a license of Terragen 4 Professional or Creative, use the Check for Updates feature in the application to get links to the latest 4.4 build.
This version is available to anyone whose maintenance includes v4.4.x builds. That means you can download it even if your maintenance expired as long ago as the 21st of March, 2019.
We're behind on the Mac builds as we're adjusting to new security requirements on macOS Catalina. Please be patient and we'll bring the Mac up to speed as soon as we can.
Here's the change log:
Build 4.4.60 (Frontier Build)Overhauled the bump mapping and lighting system that's used on ray traced objects to improve image quality and accuracy. Recent 4.4 builds had some bugs that were caused by changes to address some long-standing issues. The new system in 4.4.60 fixes those bugs and also maintains solutions to some long-standing issues.
- Fixed some bump mapping and lighting bugs that were introduced in 4.4.46: incorrect lighting positions; incorrect normals on highly curved or highly displaced surfaces.
- Bump maps don't affect the lighting position anymore, because this was causing severely unrealistic distortion of shadows.
- Bump maps affect the data that shaders use for non-lighting. For example, altitude constraints work with bump mapped surfaces. This works with negative bump too.
"Smooth polygons at terminator." This is a new checkbox on the Surface Shaders tab of object readers, and it is enabled by default. It fixes self-shadow artifacts at the lighting terminator of polygonal objects where the smooth normals are inconsistent with the geometric normal.
"Darken bumps at terminator." This is a new checkbox on the Surface Shaders tab of object readers and non-displaceable object generators. It is enabled by default. It approximates self-shadow of bump maps at the lighting terminator to reduce the chance of seeing a sharp line where the surface falls into shadow.
Fixed a bug that occurred when "Ray trace objects" was off. Objects whose render method was "Default" were being rendered with both the rasteriser and the ray tracer. The correct behaviour in this case is to render with only the rasteriser. The bug may not have been noticed with objects that have positive displacement.
"Cloud base (min)" and "Cloud top (max)" readouts on the Atmosphere Node List are updated when a cloud layer's depth is changed.
Spot the Difference
