Page 1 of 1

Arbitrary range

PostPosted: Sat Jun 15, 2019 9:14 am
by spigolo
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?

Re: Arbitrary range

PostPosted: Sat Jun 15, 2019 4:57 pm
by juanjgon
This sounds like a bug. I'll check it.

Thanks,
-Juanjo

Re: Arbitrary range

PostPosted: Sun Jun 16, 2019 6:38 am
by spigolo
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...

Re: Arbitrary range

PostPosted: Tue Jun 18, 2019 5:56 pm
by spigolo
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

Re: Arbitrary range

PostPosted: Wed Jun 19, 2019 5:49 pm
by juanjgon
Sorry for the late reply. I'm trying to find and fix this issue for the next build right now ...

Thanks,
-Juanjo

Re: Arbitrary range

PostPosted: Thu Jun 20, 2019 3:59 am
by spigolo
Thanks!

Re: Arbitrary range

PostPosted: Thu Jun 20, 2019 10:06 pm
by juanjgon
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

Re: Arbitrary range

PostPosted: Fri Jun 21, 2019 4:21 am
by pixym
Thanks Juanjo.

Re: Arbitrary range

PostPosted: Fri Jun 21, 2019 10:55 am
by Lewis
In LW 2015 and Octane 4.04 that works fine so it's either LW 2018----> bug or octane 2018.x bug ?

Re: Arbitrary range

PostPosted: Fri Jun 21, 2019 11:01 am
by juanjgon
To me, this is a bug introduced in LightWave 2018

Thanks,
-Juanjo