eonite opened this issue on Jun 22, 2009 · 59 posts
eonite posted Sat, 27 June 2009 at 1:25 PM
Thanks, ArtPearl for letting me know.
Did not test the position offsets of the Metanode. Have found a flaw in the function. Corrected it and now it should work properly.
You can download the corrected version here.
As for the flat mountain top: Within the function editor it seems there is a limit to scaling. Scaling, like setting the value to 2 or so is no problem but setting it to 5 is definitely too much. If really you need to have a mountain that is VERY high, like twice the height of Mount Everest, you can still scale the whole terrain as an object.
Quote - I see you got rid of the brightness/contrast node - what was your reason for it?
Because I used a Combiner in Add mode to add the procedural noise to the heightfield map. A Combiner has Amplitude and Offset which is equal to Brightness&Contrast.
Quote - Oh, thanks for explaining how to use the function node preview, that will come in very handy. My question was about much simpler aspect - if a node has a constant as an input which is calculated earlier in the tree, is there a way to examine the value in the node? for example - the value of the origin in the projected texture map?
The only way to check is examining by using the Function Node Preview. Btw. when you examine the Texture Map node with the Function Node Preview you can clearly see that there is a bug in this Node. The map keeps repeating in the positive Y-direction even though Tiling Mode is set to none...
Anyway, I don`t want to steal anymore of your time :-) Was great fun!