I am about to use six layers of FSS (fake stone shader) in my project and never really did so many.
A million dollar question then is - do lower placed (in the node network) FSS layers additionally displace those above?
I don't want to create a field of hedgehogs, y'know...
Just made a test with my eyes half closed and... it does. >:( Any way to avoid FSS layers interacting with one another?
I would suggest using the merge chain method as most file shares of others show. Some use one texture for all with color adjust, but you can disconnect that and use individual colors if you so desire.
This is mhaze's share...see the stones (rock) layer example
http://www.planetside.co.uk/forums/index.php/topic,23444.msg237239.html#msg237239
The Rock Color surface layer with a bold plus is for the terrain rock....go to the fake stone layer to see the chain merge I mean.
Another more complicated way is to use compute terrain as a mask or individual layers for each stone
Oh, I see. I think I get the idea behind it. Wonder if it'll work for six layers though!
I'll have a go at it tomorrow. Thanks luvs.
I have used it quite successfully in most of my renders.....I think haze has at least 6 rocks there
While we are on this topic.....I have to research, because I think I read about the new TG4 reading shader names and something about if you have a name one place it reads it the same blah blah blah....I think I am confused and will read up again....sorry
Quote from: N-drju on February 01, 2018, 05:17:13 PM
Oh, I see. I think I get the idea behind it. Wonder if it'll work for six layers though!
I'll have a go at it tomorrow. Thanks luvs.
There's a fine called
stone_shader.tgc example in the presets that uses 3 stones and you could easily multiply that x2...
The rock study did indeed help to keep the displacements under control! However, while mixing the stones was easy, mixing them with whatever terrain and textures are above is not...
Now, my stones are taking over the colors (and displacements...) of the terrain and color layers from above the network view... Tried the same mixer to join the two, but with no luck really. Need to check it again in the source rock study file I guess...
This is where you either....connect the whole pyramid of merges as a child to a surface layer with no restrictions.....then you can use Distribution shader for altitude and slope as fake stone mask, keeping in mind that the stones merged in one merge shader should be distributed to same altitude and slope.
If each stone is a different color and displacement, you need to disconnect the upper texture and color adjust nodes, (this is where your color and displace should then be connected to each stone respectively as stone surface shader)
Geek at Play has a tutorial on YouTube about using compute terrain, written for TG3, I think.
There is another link, old, by chronor, where fleetwood demonstrates distribution, This is in Terragen Support:
http://www.planetside.co.uk/forums/index.php/topic,14811.0.html
If Tangled Universe or any like artists have an explanation of stone distribution, I have not found it yet.
Edit afterthought....and then there is the painted shader, haha...many ways...
Ahhh, how silly of me - the whole color issue was due to "slope constraints" parameter being still on and a stray "merge shader" dangling where it was not supposed to be. Colors are good by now.
[attach=1]
Some minor artifacts do appear when using this method. But given the distance the camera will be at in my new render, this is pretty irrelevant.
Now I just need to check how that terrain displacement will play along with the stones. Though it should not have any influence actually... ??? Maybe I just start to get paranoic.
Wopsie! Looks like I'll have to move my whole terrain section under the stones! Otherwise the terrain form displaces stones that lay on the slopes... ::)
_______________
UPDATE
Okay... I'm kind of helpless now...
In order to stop the terrain interfering with the FSS layers (yes, it does mess the stones up) I moved the FSS surface layer to the top of the node network. Above the terrain.
This keeps fake stones intact, but... I can't use distribution shader for them anymore. ::) It seems that distribution shader will work only if it is preceded by the "compute terrain" node. Even if it works only as a mask. I tried to supplement compute terrain node on the top, before the FSS surface layer but it did not fool the program. Distribution shader is still completely useless...
And of course I can't move the stones to the bottom, because then, they will be affected by every terrain feature that's on the way. Ughhhh!
Usually one needs to smooth terrain on the surface shader that the stones are on, but I often find this eliminating subtle displacements I needed. An XYZ shader before the stones or plugged into their input also works sometimes. Fake stones are pretty hard if not working on a low smoothlike terrain, especially close-up. Distance is easier.
Quote from: Dune on February 02, 2018, 01:08:02 PM
Usually one needs to smooth terrain on the surface shader that the stones are on, but I often find this eliminating subtle displacements I needed.
Exactly. I have a very nice mountainous terrain that I do not wish to change. :-\ I guess I will just need to mask the rocky regions with painted shader and then plug it into the PF, because this is the only situation where the stones are not "kicked" but tilt along in agreement with the terrain.
I guess FSS behavior should be examined by guys at Planetside to see if some changes could be made. Perhaps "lean to terrain normal" as with populations? I'd love to have it!
Included is the picture and a clip file of some of my stones. If anyone would like to have a go, don't be shy an grab it.
The "victory conditions" are:
1. The stones retain the shape they have in the picture provided.
2. The stones are masked by PF which, in turn, is restrained to 135 meters.
Try it out and use the provided camera. Wonder if you are more lucky than me. :( As an added bonus, you get my nicely tailored FSS setup.[attach=1]
NOTE: Use it on the default tgd.
Are you approaching this as a contest? Your examples are great, but the clip I have does not yield the same.
Your question is the NWDA challenge? ;) In that case - no, I'm not taking part.
If this is a contest for you? No. Just request (cry, if you will) for help.
Well, that's the problem, you see. You get unchanged stone shapes only when you plug FSS to the first terrain layer. But then, it is impossible to distribute them via altitude or slope constraints. I have completely no idea why! It seems any altitude or slope distribution above compute simply does not work!
Also, the stones placed there, take on the terrain color, so in fact you need to transfer whole shader area above FSS! Which causes even more problems.
If you add these stones as child on a surface shader with smoothing on, after a compute terrain with small patch size (1-2m), it works quite nicely. Mask the fractal mask (of the stone) by distribution shader with set slope and altitude. That way you only restrict the stones, but not the colors (tha's what happens if you restrict the slope in the surface shader). Also (it may help a bit) attach a XYZ shader to input of the stone.
I did not quite understand where you were going with this as the setup I got your second camera came in underground, there is only 1 fake stone (not six like I thought you were wanting a setup for). So listen to Dune, I am sure you will get it eventually. :)
Quote from: luvsmuzik on February 03, 2018, 09:59:48 AM
I did not quite understand where you were going with this as the setup I got your second camera came in underground, there is only 1 fake stone (not six like I thought you were wanting a setup for).
Kind of misunderstanding. I did want to have six layers of non-interacting FSS and I did that thanks to your tip. However, later came a problem of how to prevent terrain messing up with the FSS shape and that's where discussion continued. It's probably my fault - I should have created another thread to separate the two issues.
Oh, okay.
It has just been my own personal experience that fake stones need to be piped as a child of a surface layer to avoid taking the surface of the terrain. If stones are added as displacement, they take on the color/texture of that layer. There could be a way to avoid that, not sure.
You must keep in mind when making your scene that when you assign altitude and slope to surface layers, if you want stones there make your stones a child of that layer.
Think how when you add a new surface layer you should see a white blanket over everything, then as you restrict altitude and/or slope you should see white triangles in your preview window where your restrictions are. When you add the stones as a child, uncheck the color option for the surface layer. Examine all tabs in layer controls. making sure something else is not interfering with your stones. (Like displacement at 100 or something, ha!)
This does not mean you cannot mask a layer, I was giving you a simple explanation.