Page 28 of 32
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 2:03 am
by geo_n
juanjgon wrote:I want to release a beta version of the 2.10 plugin ASAP, with the new render passes feature.
-Juanjo
Please asap
Render with the infochannel kernel embedded in exr would be great.
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:09 am
by atnreg
Juanjo, I did some more testing and one scene stopped/crashed at 99%. I enabled the log and finally noticed that there were one object that had polygons with area 0.0 which Octane does not support.
I fixed the object and now the scene renders fine
But could you please add some check to this plugin so that when the render or IPR starts, it would immediately warn about objects that has errors (so instead or in addition to writing the error messages to log, it would show popup warning). Now I worked on this scene in IPR without any problems and even F9 rendered it correctly in some cases (depends on max samples). So it is very difficult if not impossible to know something is wrong as everything works and looks fine until you notice the render has stopped and Layout is not responding.
The log of course tells that but it is very hard to find those errors from 500KB text file and I don't want to keep log on all the time
Anyway, 2.6.1 behaves exactly the same as 2.6.4 in this so the latest update has no special problem.
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:13 am
by juanjgon
In theory the null polygons are filtered before init the rendering.
Can you please send to me the object with this problem to test it here?
What is the error that you have seen in the log file?
-Juanjo
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:16 am
by BorisGoreta
Yes, but if at init state they are OK they could be animated to reach 0 scale at some point and if only transformations are updated this does not get filtered. Am I right ?
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:26 am
by juanjgon
BorisGoreta wrote:Yes, but if at init state they are OK they could be animated to reach 0 scale at some point and if only transformations are updated this does not get filtered. Am I right ?
Yes, this could be possible, geometry can only be filtered for the first frame. Perhaps I could replace this filtering that remove the polygons with null are with a new one that could make the are of those polygons a little > 0.0
Let me think about it.
-Juanjo
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:52 am
by atnreg
juanjgon wrote:In theory the null polygons are filtered before init the rendering.
Can you please send to me the object with this problem to test it here?
What is the error that you have seen in the log file?
-Juanjo
Yes of course, I sent it in private message, the rar contains both fixed and faulty versions
The warning I found in log was:
WARNING: this object has a degenerated polygon with 3 vertex but with area 0.0, not supported by Octane
that exactly same error repeated literally thousands of times even though that object (layer 2, other layers are fine) only has 194 polygons

The fixed version has 170 polygons. All polygons are CC patches.
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 10:58 am
by juanjgon
atnreg wrote:
The warning I found in log was:
WARNING: this object has a degenerated polygon with 3 vertex but with area 0.0, not supported by Octane
that exactly same error repeated literally thousands of times even though that object (layer 2, other layers are fine) only has 194 polygons

The fixed version has 170 polygons. All polygons are CC patches.
Yes, but this is a warning from the plugin that means that this polygon has been filtered (removed) from the scene, so all should work fine.
I am going to make more tests about this issue with your objects ... currently it is even possible that Octane doesn't crash with this polygons in the last versions. I need to test it.
-Juanjo
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 11:08 am
by atnreg
juanjgon wrote:
Yes, but this is a warning from the plugin that means that this polygon has been filtered (removed) from the scene, so all should work fine.
I am going to make more tests about this issue with your objects ... currently it is even possible that Octane doesn't crash with this polygons in the last versions. I need to test it.
-Juanjo
Ok, thank you, hopefully you will find the problem cause

Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 12:37 pm
by Godstrike
atnreg wrote:BTW, what temperatures are you people getting?
My GTX690 gets 85 C and GTX Titan Black 83 C, are those too high?
If so, how can I force the fans to increase RPM?
Have you tried MSI Afterburner? Works a treat on my 2 x GTX 590's and 2 x GTX 580 3GB's. When I set my rig up for a big render I dial the fans to 85% and also turn up my PCI fan controller to maximise air-flow through the case. I get about 80 - 85 degrees on average.
Re: OctaneRender™ for LightWave™ 2.0 DAILY BUILD
Posted: Fri Sep 26, 2014 3:35 pm
by atnreg
Godstrike wrote:
Have you tried MSI Afterburner? Works a treat on my 2 x GTX 590's and 2 x GTX 580 3GB's. When I set my rig up for a big render I dial the fans to 85% and also turn up my PCI fan controller to maximise air-flow through the case. I get about 80 - 85 degrees on average.
No I haven't but it seems to be for certain MSI cards only. Mine is Gigabyte

I also downloaded EVGA PrecisionX which has similar features. Thanks for the tip anyway
