World-Machine v2.2 released

Started by Tangled-Universe, May 02, 2010, 06:09:56 AM

Previous topic - Next topic

Tangled-Universe

Hi folks,

World-Machine v2.2 is now available for Pro license owners. Standard edition owners will follow soon:
http://world-machine.com/blog/?p=173

It's a lot faster I've mentioned already!

Cheers,
Martin

cyphyr

Great news, I really should get more into WM since I own the pro version, maybe these new toys will give me the impetus I need :)
Richard
www.richardfraservfx.com
https://www.facebook.com/RichardFraserVFX/
/|\

Ryzen 9 5950X OC@4Ghz, 64Gb (TG4 benchmark 4:13)

sjefen

ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

sjefen

I noticed that when I build a terrain World Machine doesn't always use all my cores. Actually... it rarely does. When it is building the erosion it uses only one core and sometimes two. Why doesn't it use all my 4 cores? Is this how it is supposed to be?

- Terje
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

Tangled-Universe

Quote from: sjefen on May 03, 2010, 10:51:42 AM
I noticed that when I build a terrain World Machine doesn't always use all my cores. Actually... it rarely does. When it is building the erosion it uses only one core and sometimes two. Why doesn't it use all my 4 cores? Is this how it is supposed to be?

- Terje

Hmmm...here it works better I assume. During the beginning it always uses 1 core, but then also the progress indicator isn't counting. As soon as it starts to make progress it uses 4 cores here. However it does not always use all 4 cores for other tasks. When building big terrains it often uses 2 cores, but certainly 4 for the most demanding nodes.
I'm afraid I have no idea what to do about it. Perhaps you should report it on the forums of world-machine?

Tangled-Universe

Here's very quick WM2.2 + TG2 doodle...made this in half an hour total :)

sjefen

Nice ;). You gotta love the erosion of World Machine.
Are you using "Displacement intersection" in that image?

- Terje
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

Tangled-Universe


sjefen

I can tell ;)

Do you see those darker spots in the shadow area? They come along when you use "Displacement intersection".
I wonder if this is a GI problem or something ???

- Terje
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

Tangled-Universe

I think I can't see what you mean? Could you point me to those spots?

sjefen

They're not very strong, but I believe in you ;)
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

Zairyn Arsyn

i need to get back to using world machine again, its came along way since the last time i have used it,
just had'nt had time to fool around with it again.  :)
WARNING! WIZARDS! DO NOT PREDICT THE BEHAVIOR OF OTTERS UNLESS YOU OBEY BIG HAPPY TOES.

i7 2600k 3.4GHZ|G.skill 16GB 1600MHZ|Asus P8P67 EVO|Evga 770GTX 4GB|SB X-FI|Antec 750W
http://zlain81.deviantart.com/

Tangled-Universe

Hmmm...yes I see now...I saw the top left and right ones myself, but wasn't sure if you meant that, but yes you did.
I'm not sure if this is due to displacement intersection. Shall see if I have this TGD saved and disable displacement intersection.
But like you said yourself: they're not very strong.

sjefen

Yeah.... they're not too easy to see.

I am pretty sure it has to do with the displacement intersection. I have done some testing before and it always happens.
Would be cool to know if the same happens to you as well tho.

- Terje
ArtStation: https://www.artstation.com/royalt

AMD Ryzen Threadripper 1950X
128 GB RAM
GeForce RTX 3060 12GB

FrankB

Are you using slope constraints for the snow layer that uses intersection, Martin?
If yes, this is the answer, and secondly if you get much closer to any of these spots, you'll be able to see the issue more clearly.
Slope constraints and intersect = not a good idea.

Cheers,
Frank