OTOY Forums

Found a small error which appears from time to time random.

Although the denoiser is checked in settings: I don't have the dropdown for denoised beauty. I need to click the checkbox off and on again to make it work.

Hi NZ.
Here is the problem I have with alpha.
In octane viewport I have the alpha, in render I have the alpha channel, and in denoised render I have no alpha.
I I use render alpha for denoised render, a fringe appear at the alpha limit.
If I check "use denoised beauty instead of beauty" I have two denoised renders one with alpha and the other without alpha, but I have lost my undenoised render...
grrrr !!
I join my file if it can help

Hi.
Ray epsilon values in Octane Preferences and in Render Setup are different.
I know that Re values are internally converted for a unit precision problem but my brain would like to see same values everywhere
Thanks

HHbomb wrote:Hi NZ.
Here is the problem I have with alpha.
In octane viewport I have the alpha, in render I have the alpha channel, and in denoised render I have no alpha.
I I use render alpha for denoised render, a fringe appear at the alpha limit.
If I check "use denoised beauty instead of beauty" I have two denoised renders one with alpha and the other without alpha, but I have lost my undenoised render...
grrrr !!
I join my file if it can help

Hi HHbomb,
Thanks for the sample scene ! I could reproduce the issue.
There seems to be a bug in the way the render elements are saved in the scene.
A simple solution is to Delete the 'Denoised Beauty' render element, and to re-Add it.
I also noted that when saving as png from your scene, (with alpha enabled), It saves a corrupted black and white image ..
This is also fixed by deleting and re-adding the render element..
I'll keep investigating to fix this issue.
Thanks!

And thanks for reporting the ray epsilon in Preferences.. this will be fixed in the next release.

[EDIT]:
The reason of no alpha was the tga settings. In your Render element, is was set to 24 bits per pixel.
You just need to change it to 32.
Unfortunately, the Octane plugin can't check those settings, all the supported formats and settings are managed by 3dsMax.

As for my test with a corrupted png, it was somehow set to Monochrome 1 bit / pixel..

So those settings should be the first thing to check if an output seems wrong.. Thanks

mbetke wrote:Found a small error which appears from time to time random.

Although the denoiser is checked in settings: I don't have the dropdown for denoised beauty. I need to click the checkbox off and on again to make it work.

Hi mbetke,
Thanks for reporting this issue.
I couldn't reproduce it.
Do you have some Octane camera in one 3dsmax viewport ?
do you have a sample scene ?
Thanks

Please check and fix VDB preview and render speed.

v2022.1 - 13.12 VS 2021.1.6_-_12.24

v2022.1 - 13.12:
Evaluation time - slow (18sec VS 3sec)
viewport FPS - (0 fps VS 24 fps)

Standalone 2022.1 is fast with VDB.

Already pointed out the problem here
viewtopic.php?f=80&t=80238

Hi mbetke,
Thanks for reporting this issue.
I couldn't reproduce it.
Do you have some Octane camera in one 3dsmax viewport ?
do you have a sample scene ?
Thanks

I use the default 3dsmax camera all the time.

I don't have a sample scene because it happens totally random and is not dependent on the scene.

I'm encountering a Stack Overflow when attempting to render a scene with "AOV Output".

I've recently updated to Max 2023.3

When attempting to open the Render Settings of a saved file (that used to render properly) it crashes.

I've also started a new scene, and merged the content of the "defected" scene. resetting it all back will yield that Stack overflow when attempting to add the AOV Output on the render elements.

any idea?

ofirgardy wrote:I'm encountering a Stack Overflow when attempting to render a scene with "AOV Output".

I've recently updated to Max 2023.3

When attempting to open the Render Settings of a saved file (that used to render properly) it crashes.

I've also started a new scene, and merged the content of the "defected" scene. resetting it all back will yield that Stack overflow when attempting to add the AOV Output on the render elements.

any idea?

Hi ofirgardy,
Thank you for reporting this issue.
There seems to be a bug when some AOV output are added in the Render elements.
You might also be able to recover your scene this way:
-open the scene
-open Octane viewport (using the context menu in a 3dsmax viewport)
-click the last button (multi-pass selection) and choose 'Export passes selection to Render Elements'
This should cleanup the render elements (this doesn't include the AOV elements)

It seems you can add 1 AOV render element for now, but it might crash again if you add a second one..
Sorry about that.
This will be fixed in the next release, in the coming days.
Thanks

ramone163 wrote:Please check and fix VDB preview and render speed.

v2022.1 - 13.12 VS 2021.1.6_-_12.24

v2022.1 - 13.12:
Evaluation time - slow (18sec VS 3sec)
viewport FPS - (0 fps VS 24 fps)

Standalone 2022.1 is fast with VDB.

Already pointed out the problem here
viewtopic.php?f=80&t=80238

Hi ramone163,
Thank you for the details and the video.
This will be fixed in the next release.
Thanks