• Welcome to World Machine Community. Please login or sign up.
July 17, 2019, 08:24:37 am


Read the Development Diary for an inside look at World Machine's progress!

Post reply

The message has the following error or errors that must be corrected before continuing:
Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Note: this post will not display until it's been approved by a moderator.
Other options
Please leave this box empty:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:

Shortcuts: ALT+S save/post or ALT+P preview

Topic summary

Posted by kardigans
 - May 03, 2018, 02:14:58 pm
Hi, building time generally releated to your CPU processing power and number of cpu cores.
I have a AMD Ryzen 7 2700 (eight core) and Grand Canyon example took 13 second.

WM definitely needs to handle the erosion calculations on the GPU. But this definitely complex engineering work. I do not think it will be in the near future.
Posted by WM_Moderator
 - April 30, 2018, 04:17:17 pm
WFab is right - I'll add that you can estimate the build time to see how things change as you increase and decrease the resolution. If you go to Project Settings, you can hit "Estimate Time to Build". Hope that helps!
Posted by WFab
 - April 29, 2018, 02:26:18 am
That's natural. The simulation nodes like erosion, thermal erosion, snow simulate nature's forces on your terrain. Takes a lot of time, computing power, and memory to accomplish.
Posted by dragonice501
 - April 28, 2018, 08:08:30 pm
Like the description says, for some reason the startup.tmd builds abnormally long, the erosion node to be specific. At 2049x2049 the build took 3m33s, and just to check i went and built the Grand Canyon example at its default 1022x2049 and it took 1m8s. Is their something i need to check or configure?