I am using the awesome new resolutions for rasterizing LW procedurals, namely Crumple. (for water) I'm using 16k mode. It's rendering quick. The issue is, it doesn't seem to matter what speed I animate the procedural. Every frame Octane outputs animates the texture at a, way too fast, speed. It looks like maybe the raster is doing it's own seed-per-frame? I end up with a spastic stuttering mess. Any ideas? (video attached) If it helps, I've noticed the rasterized version is not 1:1 with the VPR version. If I plug the node in to Octane it doesn't look the same as it did in VPR. I have to adjust the scale a lot. Knowing that, I adjusted the speed of the animation. Again, no change. Seems like a bug in the raster. It really should be 1:1 with VPR to start, actually. That might be a clue. I've attached the content as well.
***UPDATE****
So it really was having to use DRASTICALLY smaller animated number. 1mm on Y axis to get the crumple to "animate and swim" properly. Wow. Still, finally getting better looking water in Octane! More like LW water! YAY!
Rasterized procedurals acting "crazy." ?
Moderator: juanjgon
Be aware that the rasterized texture on the Octane side is not going to match the LightWave native rendering at all because well, in LW it is a true procedural while in Octane it is only a texture map projected over the object surface using an Octane texture projection node or the object UVs. The rasterization only builds a 2D texture map in the 0..1 UV space that works in Octane like any other texture from file.
Thanks,
-Juanjo
Thanks,
-Juanjo