Support

Support Channels

Visit the Discord  channel for online support

Visit the Facebook group for online support

Contact support via Email

Software Release Downloads

These files are the full release version of the software and can be used for both installation or update.

TerreSculptor Terrain Software

TerreSculptor 3.0
Build 3.0.24.045 ▪ 2024-02-14 ▪ 135MB
Direct Links:

TS 3.0 on this Server (slow)

TS 3.0 Download (fast)

TS 3.0 Mirror #1 (fast)

TerreSculptor 2.0
Free use, no support, discontinued development
Smaller terrain 46000 x 46000, fewer Devices
No 2D Plane view, no enhanced Preview
No Biome menu, no Filter menu, no Geology menu
No Terrain Stack, no non-destructive editing
Fewer file formats, limited image file resolution
No Mapper Explorer, limited DEM support
Thousands of updates and fixes are in 3.0
2.0 cannot be upgraded to 3.0 in the store.
Build 2.0.24.016 ▪ 2024-01-16 ▪ 109MB
Direct Links:

TS 2.0 on this Server (slow)

TS 2.0 Download (fast)

TS 2.0 Mirror #1 (fast)

TerreSculptor Known Issues and Bugs

OpenGL driver very rarely crashes and results in a red X viewport when adjusting the Material Detail Texture tiling values.

See the FAQ page for common questions.

Support Archive

The Support Archive page contains links to older builds and versions of the software.


Troubleshooting

If you are experiencing issues with the TerreSculptor software please note the following items and troubleshooting steps.

The TerreSculptor software is successfully in use by more than 200,000 people since its initial release in 2016.  The free TerreSculptor 2.0 has more than 150,000 users.  TerreSculptor 3.0 has hundreds of users.  If you are experiencing any issues they would be extremely rare.  There have only been five people come forward with dotNET issues requiring technical support to-date.

Support contact: support@demenzunmedia.com

Software Bugs

If you encounter a software bug, the dotNet compiler will display an error dialog with a valid error description.
A typical compiler error would include such things as “Index was outside the bounds of the array“.
The compile error dialog looks like this image below and includes a stack trace text for the error.
Please collect and submit to the support email address a screenshot of the error dialog and the contents of the stack trace text.
It is also beneficial to have a list of the steps that you performed that led up to the error.

 

 

 

 

 

 

 

You can also submit a debug log file from the TerreSculptor software which may contain the error information.
The TerreSculptor log file is written every time the software is executed.
The log file can be found at the following location:

C:\Users\your_logon_name\AppData\Local\Demenzun Media\TerreSculptor

Startup Errors

If you encounter a STOP message during startup that states that there is an issue with the system CPU or Memory, that means that the Windows System DLLs on the computer are corrupted, and those API’s are returning null values.  This can also be verified by attempting to create a Windows Performance Counter on the CPU or Memory to see that it also fails.  In every case so far, only re-installing Windows seems to fix this issue.  There have been to date four people with this issue.  The CPU and Memory information is required for the TerreSculptor software to operate.

If you encounter a dotNet compiler error dialog during the startup phase of the TerreSculptor software, during the splash screen, that will mean that your Windows installation is corrupted.
There are a few things that you can do to try to repair the corruption, with a worst case of having to reinstall Windows.
A TerreSculptor log file can be submitted which may show the location at which the startup error occurred, which can help determine if it is a video driver or dotNet or Windows issue.

Disappearing Application

If you encounter the entire application window just disappearing without any error dialog, then that typically means that the dotNet system on your computer is corrupted.
There are a few things that you can do to try to repair the corruption, with a worst case of having to reinstall Windows.

Repairing Corrupt Files

In order to verify your Windows installation and repair any corrupt files, follow these steps.  These steps are for both Windows 10 and Windows 11.

1. DISM Repair (Deployment Image Servicing and Management)

Start an administrator level command prompt, then run each of these three commands one after the other, waiting until they complete:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

You should restart Windows after running these three commands.
If you get any errors listed as a result of these commands then you will have to Google the fix for it, it might mean a Windows re-install.
After all of those commands are processed, then use the System File Checker on the same administrator command prompt.

2. System File Checker

Start an administrator level command prompt, then run this command, waiting until it completes:

sfc /scannow

If SFC found and repaired corrupt files, reboot and re-run SFC over again and repeat SFC until there are no more corrupt files found.
If SFC found corrupt files and can’t repair them, then your Windows will have to be reinstalled.

3. dotNet Repair Tool

Download from the Microsoft website the dotNet Framework Repair Tool.  The dotNet Repair Tool is located on Microsoft’s web site here:

https://learn.microsoft.com/en-us/dotnet/framework/install/repair
or
https://www.microsoft.com/en-ca/download/details.aspx?id=30135

Run the file that is downloaded and follow the on-screen prompts.
Reboot the computer after performing the repair.

4. Re-run the TerreSculptor software

If TerreSculptor still just disappears when using it, then your Windows image is corrupt and non-repairable, and will require Windows re-installation.
You can try re-installing Windows 10 or 11 as an Upgrade over your existing Windows, while keeping all user data and apps. That will sometimes fix the issue.

Disappearing dotNet based software 99% of the time means that dotNet has corrupt files.
If there is an actual bug in a dotNet application, it will actually display a compiler error dialog with a stack trace to the bug as shown at the beginning of this troubleshooting section.
If you don’t get the compiler error dialog, it typically means the dotNet installation or Windows is corrupt.

Video Drivers

Some people have also had issues with specific video driver versions.
So if you are experiencing issues such as a disappearing or closing application, try going back to a previous video driver version.