When I import an object(no UVs)into TG and add displacement(Force displacement set) then add a population, the pop ignores the new added displacement and conforms to the original shape before displacement.
I'm not 100% certain of the issue you're describing, but the way to get a population to be displaced would be to add the population first, then go into the object generator that is inside the populator and add displacement *there*. You can, alternatively, connect an already-modified object generator to your population but you have to make sure you select "member of a population" for that object.
- Oshyan
Quote from: mhaze on March 28, 2016, 09:28:48 AM
When I import an object(no UVs)into TG and add displacement(Force displacement set) then add a population, the pop ignores the new added displacement and conforms to the original shape before displacement.
maybe it needs to be anchored to the displacement shader?
Now that is a smart idea (serious).
Good point!
Can't be done displacer is inside the object!
A basic example file to test?
Here you go, moss is on file sharing.
Quote from: mhaze on March 30, 2016, 01:32:42 PM
Here you go, moss is on file sharing.
and where would one find the Boulder then?
Yes "BoulderV1.obj" .
I suspect from a test I'm running that the displacement happens at render time as the boulder I have that I'm testing on shows nothing in preview but is hanging something fierce in the render. I made a .tgc of your boulder's shaders and applied them to mine to try and get close.
oops
Well I had to use a different moss as Moss1 rendered black, but in my example with Moss2 it confirms that to me as Displacement happens at render time I doubt there's a way to populate as yet on that displacement.
I managed to crash TG3.4 by substituting Moss1 from the more folder, it populated then TG announced it was crashing. Odd.
All that being said that's a cool base boulder...thanks for that for my collection, hee hee hee
You're welcome.
I still use Terragen 3.3 so not sure if all i say below is true.
I tried your file. Not quite sure but it looks like there is some funky thing going on.
If you put the displacement node in the "Mesh displacer" input of the boulder object you will get displacement.
But for the population to accept the displacement you have to check the "Flip normals" box 2 times.
This is what i used at least. There might be other ways too (see below).
It is like if Terragen can't refresh the object to the new displacement.
Not sure if this a problem related to your object.
You can look at the files below.
I put 3 example files in the zip.
To see what i try to say better try this:
* Open the "Boulder test_03.tgd" file and make a render.
* Now open the "Mesh_displacement_Power fractal shader" and change the displacement amplitude to "3" and render ones again.
There will be no change. It will render the same.
* Then disable and enable the "BoulderV1.obj" object node and render ones again. The render changes only now (a smaller more
erratic displaced object with correct population).
To see the new displacement you need to kind of manually refresh the object.
Not sure if this is your problem but there is a bug probably.
Quote from: Kadri on March 31, 2016, 06:58:04 PM
Not sure if this is your problem but there is a bug probably.
Nicely solved Kadri....
Thanks for looking at this - It shouldn't behave this way so I still think this is a bug!
Quote from: mhaze on April 01, 2016, 04:03:20 AM
Thanks for looking at this - It shouldn't behave this way so I still think this is a bug!
agree