Arbitrary range

Newtek Lightwave 3D (exporter developed by holocube, Integrated Plugin developed by juanjgon)

Moderator: juanjgon

Post Reply
spigolo
Licensed Customer
Posts: 292
Joined: Fri Jun 04, 2010 5:16 am
Location: Florence Italy
Contact:

I noticed that Octane on lightwave doesn't support the arbitrary range in the render properties.
I need to render only certain frames of a setup but and I wrote the frames to be rendered like 2-3-7 etc...
but after the first 2 it stops rendering.
Also in the past I noticed that it didn't worked ..is this a known limitation?
3dsign studio
Advanced visual communication
http://www.3dsign.it
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

This sounds like a bug. I'll check it.

Thanks,
-Juanjo
spigolo
Licensed Customer
Posts: 292
Joined: Fri Jun 04, 2010 5:16 am
Location: Florence Italy
Contact:

What I can tell you for sure is that if you assign an arbitrary range like 3,5,7,11 after the last frame Octane restarts rendering
from the first frame...
3dsign studio
Advanced visual communication
http://www.3dsign.it
spigolo
Licensed Customer
Posts: 292
Joined: Fri Jun 04, 2010 5:16 am
Location: Florence Italy
Contact:

Hello Juanjo
have you cheked this bug?
It is very annoyng also as Octane restarts rendering and the only way to stop it is killing the process...
thx
3dsign studio
Advanced visual communication
http://www.3dsign.it
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Sorry for the late reply. I'm trying to find and fix this issue for the next build right now ...

Thanks,
-Juanjo
spigolo
Licensed Customer
Posts: 292
Joined: Fri Jun 04, 2010 5:16 am
Location: Florence Italy
Contact:

Thanks!
3dsign studio
Advanced visual communication
http://www.3dsign.it
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Ok. This problem seems related to a bug in LightWave. The LW team is aware of it, so I hope they could find a solution for the next LW build(s), but meanwhile, I've added a workaround in the plugin code that hopefully could fix this problem. I'll include this fix in the plugin builds.

Thanks,
-Juanjo
pixym
Licensed Customer
Posts: 597
Joined: Thu Jan 21, 2010 4:27 pm
Location: French West Indies

Thanks Juanjo.
Work Station : MB ASUS X299-Pro/SE - Intel i9 7980XE (2,6ghz 18 cores / 36 threads) - Ram 64GB - RTX4090 + RTX3090 - Win10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
User avatar
Lewis
Licensed Customer
Posts: 1100
Joined: Tue Feb 05, 2013 6:30 pm
Location: Croatia
Contact:

In LW 2015 and Octane 4.04 that works fine so it's either LW 2018----> bug or octane 2018.x bug ?
Last edited by Lewis on Fri Jun 21, 2019 11:04 am, edited 1 time in total.
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177

WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

To me, this is a bug introduced in LightWave 2018

Thanks,
-Juanjo
Post Reply

Return to “Lightwave 3D”