Hi,
one of the best feature in lw 2019 is the smoothing groups and I'm using it a lot because I avoid to divide my object only to stop the smoothing.
I thought in Octane the smoothing groups work great because in IPR the render is perfect, as I see in native and in openGL.
The problem is the final render (F9, or F10, or screamernet). The smoothing groups don't exist.
There is a way to resolve this issue?
I attach a couple of images to show what happens in the final render, you can see a simple object with some sm.gr. assigned. IPR is ok, F9 is a disaster.
Thank you for the help.
Bye
Gianluca
Trouble with Smoothing Groups
Moderator: juanjgon
-
Rainbow-3D
- Posts: 64
- Joined: Tue Dec 11, 2018 7:27 pm
- Attachments
-
-
-
-
Win 7 x64 | Asus P8P67-M - i72600K | 16 GB RAM | 1 x nVidia RTX 2800
Win 11 | i7 13700K | 64 GB RAM | 1 x nVidia RTX 4090
Win 11 | i7 13700K | 64 GB RAM | 1 x nVidia RTX 4090
Hi,
This sounds like some kind of bug or limitation on the LightWave side. Somehow the smoothing groups normals are not computed in the final F9/F10 rendering stage. I'll investigate it to be sure and report this issue to the LightWave dev. team if finally it is a LW limitation.
Thanks,
-Juanjo
This sounds like some kind of bug or limitation on the LightWave side. Somehow the smoothing groups normals are not computed in the final F9/F10 rendering stage. I'll investigate it to be sure and report this issue to the LightWave dev. team if finally it is a LW limitation.
Thanks,
-Juanjo
-
Rainbow-3D
- Posts: 64
- Joined: Tue Dec 11, 2018 7:27 pm
Hi,
I tested it with native engine: VPR and final F9 render both right, the problem is in Octane final F9. If the bug is in lightwave side and we wait the LW dev. team to resolve it, I afraid we lose the hope to see it fixed...
In any case thank you for the help.
Have a good day
Bye
Gianluca
I tested it with native engine: VPR and final F9 render both right, the problem is in Octane final F9. If the bug is in lightwave side and we wait the LW dev. team to resolve it, I afraid we lose the hope to see it fixed...
In any case thank you for the help.
Have a good day
Bye
Gianluca
Win 7 x64 | Asus P8P67-M - i72600K | 16 GB RAM | 1 x nVidia RTX 2800
Win 11 | i7 13700K | 64 GB RAM | 1 x nVidia RTX 4090
Win 11 | i7 13700K | 64 GB RAM | 1 x nVidia RTX 4090
Hi, just wondering if there were any updates on this? Having the exact same problem, and although workaround exist, none of them are ideal. One could for instance use IPR for final render, but what if you want to render a sequence?
I'm on Octane 4 and LW 2019.1.4.
Many thanks
Johan
I'm on Octane 4 and LW 2019.1.4.
Many thanks
Johan
-
tomas.base
- Posts: 9
- Joined: Tue Jun 02, 2020 1:51 pm
- Location: Czech Republic
Try exporting the scene from IPR to ORBX and rendering it in Standalone.
I still use LW 2015, so I can't try it, but I know that sometimes, for example, triangulation of polygons is different when exporting from IPR than via F9 / F10. I've seen it, for example, in the leaves of flowers that are thick. It also rarely happened to me that exports via F9 did not show up in standalone at all, but exports from IPR always did. (rather exceptional cases).
It seems that the IPR after export to ORBX is always the same in Standalone.
Tomas
I still use LW 2015, so I can't try it, but I know that sometimes, for example, triangulation of polygons is different when exporting from IPR than via F9 / F10. I've seen it, for example, in the leaves of flowers that are thick. It also rarely happened to me that exports via F9 did not show up in standalone at all, but exports from IPR always did. (rather exceptional cases).
It seems that the IPR after export to ORBX is always the same in Standalone.
Tomas