OTOY Forums

coilbook wrote: Right after simulation I rendered and it worked.

Then I opened octane viewport. If I open octane viewport while sim is empty nothing works. I have to move time slider to where the sim is and then octane viewport will show smoke.

Rendering second time nothing works. It seems that once you move time slider that is it. Octane wont render phoenix if rendering started during empty frame. I can send you my nightly phoenix build as PM if you need it.
Thank you

Hi coilbook,
Thanks for the description. I could reproduce the problem on max2018 . (seems not happening with max2019..)
That will be fixed in next release.

Hi,
Same problem that occur in 5.14 and 5.15, Forest objects desappear in max viewport when Octane viewport is opened and forest object is selected.

neonZorglub wrote:

coilbook wrote: Hi Could you save it as 2018 version? I am currently using nightly build 3.11.03 Nightly, Build ID: 2018082828466

By the way were you able to find out why volume denoise is not working ?

-ooppss, here is a max2018 version:

smoke60_70_mx18.zip

-It seems the 'Denoise volume' check box doesn't work in the kernel's camera, ! sorry ! It works only in the Octane Camera properties.
You can temporarily enable it by hand, to have a look, from the viewport, open the Octane Node Viewer,
select the Render Target node, see under Tonemap settings / Spectral AI Denoiser..
I'll try to release a fixed version soon..
Thanks

Please add an option in octane camera to match all settings to the main camera kernel Thanks

I have a scene that on V3 is almost maxing out my VRAM but renders fine. In octane 4 with denoiser it seems to either a)crash 3dsmax or b) say render failed. Iv assigned denoiser to one card and rendering to another but I'm still getting hangs.

Anything I can do to combat this? Does using the CPU memory checkbox help? (currently that's unchecked).

EDIT : Just got a BSOD trying to load the scene too. but it's pretty random

Edit 2 : The error log says there's not enough free memory for the denoiser so i unticked 'active' in the devices panel (but left denoise checked) and I have had some instances where it WILL denoise now, but still unstable.

another thing I noticed is that the octane viewport refreshes after 3dsmax performs an autosave. (Max 2014). As Ive set mine to every 10 minutes it can happen in the middle of a render and have to start again,

darkline wrote:I have a scene that on V3 is almost maxing out my VRAM but renders fine. In octane 4 with denoiser it seems to either a)crash 3dsmax or b) say render failed. Iv assigned denoiser to one card and rendering to another but I'm still getting hangs.

Anything I can do to combat this? Does using the CPU memory checkbox help? (currently that's unchecked).

EDIT : Just got a BSOD trying to load the scene too. but it's pretty random

Edit 2 : The error log says there's not enough free memory for the denoiser so i unticked 'active' in the devices panel (but left denoise checked) and I have had some instances where it WILL denoise now, but still unstable.

The issue you see with 4 is likely that caching is failing - in the upcoming RC we have made an improvement that will gracefully handle the situation where this happens, and continue rendering. You can definitely try enabling out of core memory in the mean time using that checkbox.

if exported to standalone version, does not work animation light octane lamps

haze wrote:

darkline wrote:I have a scene that on V3 is almost maxing out my VRAM but renders fine. In octane 4 with denoiser it seems to either a)crash 3dsmax or b) say render failed. Iv assigned denoiser to one card and rendering to another but I'm still getting hangs.

Anything I can do to combat this? Does using the CPU memory checkbox help? (currently that's unchecked).

EDIT : Just got a BSOD trying to load the scene too. but it's pretty random

Edit 2 : The error log says there's not enough free memory for the denoiser so i unticked 'active' in the devices panel (but left denoise checked) and I have had some instances where it WILL denoise now, but still unstable.

The issue you see with 4 is likely that caching is failing - in the upcoming RC we have made an improvement that will gracefully handle the situation where this happens, and continue rendering. You can definitely try enabling out of core memory in the mean time using that checkbox.

Thanks Haze, I'll go back to V3 for this work and wait for next release.
another issue I've noticed is I was rendering a shot here for about 3000 samples. On v3 with 2x 980ti that was taking about 15 mins per frame....
On V4 I have to disable one card for denoising, but now to get to say 350 samples (or 1/10th the quality) 1 980ti is taking 5-6 minutes. Is it right that the v4 kernel is this much slower? or do I have another issue going on?

Elvissuperstar007 wrote:if exported to standalone version, does not work animation light octane lamps

Hi Elvissuperstar007,
thanks for your report.
Regards
Paride

darkline wrote:another thing I noticed is that the octane viewport refreshes after 3dsmax performs an autosave. (Max 2014). As Ive set mine to every 10 minutes it can happen in the middle of a render and have to start again,

Hi darkline,
I tested V4 using 3dsMax 2014, autosave doesn't stop and restarts render.
Any clues to understand?
Regards
Paride