Page 10 of 10

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Mon Nov 09, 2015 12:56 pm
by FrankPooleFloating
Nope. Didn't help. You can test what I am talking about by toggling the Matte button on/off with IPR open. Just have any object (as layer 1) and a plane (layer 2) as shadow catcher with diffuse/matte.

Now, this is not every day that I would want/need to mask a shadow layer, so that is why I prolly didn't hit this until now... this is not critical, by any stretch, so no biggie if you can't get this working. ;)

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Tue Nov 10, 2015 7:57 pm
by FrankPooleFloating
Okay J.. something else to maybe take a look at: GPUs sit at roughly 50° after closing IPR (and would stay there for eternity), but after F9s they go back to normal idle temp of 35°... Any way you can dump whatever is still cooking in GPUs when closing IPR?.. I think we may have touched on this way back... did you already look into this?

Just trying to, er, be green and shit... and maybe save a couple bucks on electric. ;)

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Wed Nov 25, 2015 12:37 pm
by MrFurious
Im having the same issue as Frank above (except more around 60deg warm now in Melbourne), has been like that since I can remember dare I say it may have been responsible for driver/gpu crashes (lost a few now, getting expensive!) Except after F9 render the IPR is closed and the gpu's are still cooking. Only when I close Lightwave do the gpu's slow down

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Wed Nov 25, 2015 1:07 pm
by MrFurious
Actually I've noticed something similar in Octane Standalone, where my temps are hovering around the 60deg mark when IPR is paused. Stop IPR and the temps drop. One would think that if the IPR is paused there's negligible gpu activity yes?

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Wed Nov 25, 2015 1:18 pm
by FrankPooleFloating
I'm sure Juanjo is deep, deep in the salt mines, with Marcus & Co and other plug devs... Maybe 3.0 will fix this anyway...

I have actually been keeping both GPUs at Low Priority for both IPR and F9s, until I am up with new 780Ti(s) and full water blocks.. which really isn't all that bad. I think they are still cookin' at 80% or something, and I can be working in Substance Painter, ZBrush, AE, PS etc during renders.

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Wed Nov 25, 2015 1:22 pm
by BorisGoreta
I have this heat problem too but I use it to my advantage to heat up the room especially now when the winter is coming, you can easily tell when all my household occupants gather in my room rather then somewhere else, because it is so cozy and warm, no need for a true fireplace at all.

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Wed Nov 25, 2015 1:30 pm
by FrankPooleFloating
I hope household occupants = flat-mates... If I called my wife a household occupant, I'd probably get a kick in the nuts... :shock:

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Sun Nov 29, 2015 2:08 pm
by FrankPooleFloating
I did some further testing, and I can say with complete confidence, something is still cooking in GPUs after IPR is closed... and even Clear Scene (which disables Octane plug, and presumably does a Switch to LW) keeps GPUs running at 50­­°, forever. Only a F9/F10 or closing LW empties GPUs and temps go back to 32°.

Juanjo, I see you boppin' around forums today (hopefully that means imminent release)... do you have any info about this IPR business?

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Sun Nov 29, 2015 2:21 pm
by juanjgon
I will check this issue for Octane 3. I remember a problem closing the Octane render threads in the IPR, but I will check again what was the problem.

-Juanjo

Re: OctaneRender™ 2.2 for LightWave™ - Daily builds

Posted: Sun Nov 29, 2015 2:35 pm
by FrankPooleFloating
I just remembered that way back, you originally had IPR rendering forever (or maybe 64,000 samples or something), and when me and couple other dudes asked for it, you added IPR stop using kernel samples... could it have something to do with the original/default IPR setup, of rendering forever?