Before I waste any more time trying to get displacement to work in OctaneRender 2018.1.3 for LightWave 2019.0.3, I thought I'd post a note here and see if I'm just doing something fundamentally wrong.
I've attached a zipfile containing an example of what I'm trying to do. The scene camera is pointing at a 1-km sphere that is supposed to have its surface displaced by the PNG image file included in the zip, but every time I render the scene I get a smooth, undisplaced sphere.
Thanks...
Displacement not working in OctaneRender 2018.1.3
Moderator: juanjgon
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
- Attachments
-
- displacement.zip
- (869.6 KiB) Downloaded 158 times
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
The conventional render time displacement only works over UV mapped textured objects. The projection nodes are not compatible with it. Octane 2019 has a new vertex displacement node that has more features and supports the projection nodes.
Thanks,
-Juanjo
Thanks,
-Juanjo
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
Ahh, I was afraid that you would say that.
If I upgrade to OR 2019 and find that it breaks something else that I more critically need, is it possible to downgrade back to 2018.1.3?
Thanks!
If I upgrade to OR 2019 and find that it breaks something else that I more critically need, is it possible to downgrade back to 2018.1.3?
Thanks!
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
Well, so far so good. All of my models are rendering exactly the same as before (and perhaps even a little faster!). And best of all, now the displacement is working as I'd hoped:
Thanks Juanjo!Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
Hmmm... OK now I've run into a different problem.
I'm trying to follow this tutorial: https://www.youtube.com/watch?v=dM9HwgitbqQ Although it was created for Cinema 4D, I was hoping that the basic concepts could be ported over to LightWave. The basic idea is that you have two spheres in different layers with slightly different displacements. The inner sphere would be emissive and would look like lava poking out at various points through the planetary crust.
The problem that I'm running into is that no matter what I do I cannot get anything but the outer sphere to render. If I temporarily hide the outer "planetary crust" layer, the inner "lava" layer displaces and renders correctly. It seems as though only one object is allowed to have vertex displacement per scene... is that true? I hope not--that would be a rather severe limitation...
Thanks...
I'm trying to follow this tutorial: https://www.youtube.com/watch?v=dM9HwgitbqQ Although it was created for Cinema 4D, I was hoping that the basic concepts could be ported over to LightWave. The basic idea is that you have two spheres in different layers with slightly different displacements. The inner sphere would be emissive and would look like lava poking out at various points through the planetary crust.
The problem that I'm running into is that no matter what I do I cannot get anything but the outer sphere to render. If I temporarily hide the outer "planetary crust" layer, the inner "lava" layer displaces and renders correctly. It seems as though only one object is allowed to have vertex displacement per scene... is that true? I hope not--that would be a rather severe limitation...
Thanks...
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
ACK! Never mind! Stupid mistake on my part. Getting some funky results but I'm definitely back on the right track. Thanks!
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone