OctaneRender® for 3ds max® v2025.4 - 16.10

[paride4331]

When denoiser is on (on completion) render times still go up a lot. From 1 min per frame to around 2 min even though the actual denoising times at the end is like 3 seconds

Are 5090s now utilized at full capacity? They used o render as fast as 3080tis

Hi coilbook,
About a month ago (maybe a bit more), NVIDIA told Otoy they’re aware of an issue that’s been affecting some other render engines, where certain kernels take way longer than usual to initialize.
From the user’s side, it can look like Octane is taking forever to start rendering or that render times are unusually long. Right now, it doesn’t really seem like Octane itself is affected, but it could be.
The issue only affects the 50 series GPUs and should be fixed in the latest driver, though it might still show up in some cases. Might be worth trying drivers around 581.29, 580.97, or 577.00 to see if it makes any difference?
Regards
Paride

[coilbook]

When denoiser is on (on completion) render times still go up a lot. From 1 min per frame to around 2 min even though the actual denoising times at the end is like 3 seconds

Are 5090s now utilized at full capacity? They used o render as fast as 3080tis

Hi coilbook,
About a month ago (maybe a bit more), NVIDIA told Otoy they’re aware of an issue that’s been affecting some other render engines, where certain kernels take way longer than usual to initialize.
From the user’s side, it can look like Octane is taking forever to start rendering or that render times are unusually long. Right now, it doesn’t really seem like Octane itself is affected, but it could be.
The issue only affects the 50 series GPUs and should be fixed in the latest driver, though it might still show up in some cases. Might be worth trying drivers around 581.29, 580.97, or 577.00 to see if it makes any difference?
Regards
Paride

Thank you for the info!

[coilbook]

Hello,

1. Any updates when you’ll fix phones fd wet maps rendering very, very slow? With wet maps it renders ten times slower.

2. Also Smp/px in octane view port sometimes don't increase if you look at the scene through an animated camera.

3. Also any solution for phoenix rendering smoke as pure black when sim output is AUR? VDB works

4. If an object has motion blur enabled and added to itoo forest. Itoo will render a stationary object with motion blur. (a stationary object will look blurred out )

Thank you.

[coilbook]

Octane sometimes renders itoo display proxy as actual proxy and not mesh. Point cloud works fine especially when using legacy mode

Hi coilbook,
Are you sure you set the mesh option correctly in the Display > Render panel in iToo?
Regards
Paride

01.jpg

Yes. Octane renders both original mesh and proxies (so one itoo forest gets rendered as a mesh and a proxy ) at the same time when in legacy mode Point cloud is the solution but viewport is slow

[coilbook]

There is a bug with motion blur.

The camera is attached to the moving sphere, but the sphere is getting motion blur as if it were passing by a stationary camera.

The scene is attached.

It should be the opposite — the background should have motion blur because both the camera and the sphere are moving.

Can this be fixed ASAP?

Thanks