[ Play Quicktime file ] noise_test.mp4 [ 6.39 MiB | Viewed 52688 times ]
vijay_thirukonda wrote:Notiusweb wrote:Finding the Displacement doesn't work right, as if the node is inactive/broken.
Texture-type works fine at first, but then goes dead after you change values.
Vertex, and Vertex Mixer, do not outright work at all.
Also noticing that Vertex does not have a "Level of Detail" Enum Value node, like the Texture Displacement has.
And, the default Height Value for displacement is "1.00"....wouldn't it be like .001 or something smaller, right?
Did you subdivide the mesh that you are trying to displace?. Vertex displacement doesn't need the level of detail pin. For most of the vector maps, the height scale will be set to 1, so I thought that would be ideal, but for the height map we need to tweak.
haze wrote:Dear all,
In the mean time, we look forward to your feedback on this release. If you have a V4 license or an all access subscription, you can test 2019.1 XB1 until the first stable release.
Please ensure that you have a NVIDIA driver version 419.x or newer.
.
Notiusweb wrote:vijay_thirukonda wrote:Notiusweb wrote:Finding the Displacement doesn't work right, as if the node is inactive/broken.
Texture-type works fine at first, but then goes dead after you change values.
Vertex, and Vertex Mixer, do not outright work at all.
Also noticing that Vertex does not have a "Level of Detail" Enum Value node, like the Texture Displacement has.
And, the default Height Value for displacement is "1.00"....wouldn't it be like .001 or something smaller, right?
Did you subdivide the mesh that you are trying to displace?. Vertex displacement doesn't need the level of detail pin. For most of the vector maps, the height scale will be set to 1, so I thought that would be ideal, but for the height map we need to tweak.
Hi,
Default Height-
I initially just was noticing compared to prior versions. 2018 has at "0.001", which works good for Texture Displacement, because I find often when I move values closer to "1.00", often that will bust up the mesh pretty severely displacement-wise, which, I rather enjoy actually...
but it sometimes is too extreme where it can stall the app because it is heavy duty processing wise, I guess.
So in 2019, the height is "1.00" for *both* Vector and Texture Displacement. Maybe if it was tweaked, say, "0.001" for Texture and then it would be "1.00", for vector, we wouldn't ever notice it.
Vector resolution-
Sometimes on a traditional texture displacement you might have different resolutions, so you might want it selectable at different sizes to achieve a different effect....
thought this might be the same for vector, but if by nature the vector is displayed at a max resolution (like as in "vector in Illustrator" vs "Photoshop raster") I see what you mean then.
2018 vs 2019-
The most important thing actually was that displacement overall doesn't work in 2019, as in if you do, say, set a texture displacement in 2018, and then set the same in 2019, the 2018 works and resets the render correspondingly when you modify any values, but not the 2019 one....so it's like the 2019 appears broken.
Thanks!
Return to Development Build Releases
Users browsing this forum: No registered users and 13 guests