eonite opened this issue on Jun 22, 2009 · 59 posts
eonite posted Fri, 26 June 2009 at 8:28 AM
Quote - I managed to get it to be a meta node too- yeh!
That`s good news. Metanodes are a really powerful option in the function editor.
I have also noticed that when you use MetaNodes, even if you can have really complex functions inside, the function itself becomes very stable. Never had crashes because of using Metanodes (although ungrouping Metanodes can be a disaster).
Quote - (only a couple of crashes, I think one may have been because I included the input node in the meta node by mistake, still - shouldnt crash)
I had a number of crashes because of un-publishing a parameter, but never because I included an Input node. Btw. in my Metanode version I included the Input node as well.
Quote - I'm not sure about needing a different scaling factor for the procedural terrain. If we want a different relative scale for the HF terrain we already have the parameters in the brightness/contrast node and the smooth map node. Why do we need an extra variable? I thought it was important to keep the same scaling for both terrain types.
You mean the Brighness/Contrast node underneath the Texture Projection Map node? This one merely scales and offsets the altitude. But the size of the procedural terrain remains the same.
IMO being able to scale the size of the procedural function separately makes sense.
It`s only important to have a common scaling factor for the heightfield and the blend area.
Quote - I must admit I dont yet fully understand the values in the smooth-map node. Where does the '22' come from...
t took me some time to understand it either, but now it`s clear to me. Below is a way to learn how it works.