OctaneRender® 2026.1 [current 2026]

[akvahouse]

Hi guys, Gaussian splats is broken in this release?

Screenshot_2.jpg

Same file works fine in houdini

Screenshot_3.jpg

[mojave]

Hi guys, Gaussian splats is broken in this release?
Screenshot_2.jpg
Same file works fine in houdini
Screenshot_3.jpg

Looks like the file path has a ":" at the end? If this is not the issue, could you share a link to the file itself?

[akvahouse]

Hi guys, Gaussian splats is broken in this release?
Screenshot_2.jpg
Same file works fine in houdini
Screenshot_3.jpg

Looks like the file path has a ":" at the end? If this is not the issue, could you share a link to the file itself?

All three files I found online do not work in Octane. Perhaps there are some special settings that need to be enabled for them to work properly.

TROUBLE_2.gif

Link to splats:
https://fex.net/s/tldnb6d

[jobigoud]

All three files I found online do not work in Octane. Perhaps there are some special settings that need to be enabled for them to work properly.

These appear to be regular point cloud PLY files, not gaussian splats.
Some viewers might detect that and load them as regular point clouds like Houdini but Octane gaussian splat node currently doesn't handle that. Many other GS viewers will fail in the same way.
The error message we show when this happens could be improved. The colon at the end of the path is unrelated.

[nuno1980]

Happy holidays!

VRAM size used at PT@32-parallel and @128-tile:
--at 7680x4320
2026.1 - 10.3GB
2025.x - 2.6GB

--at 1920x1080
2026.1 - 2.8GB
2025.x - 2.6GB

Why does new 2026.1 need to use VRAM size for resolution screen? But 2026.1 seems to be "not" faster than 2025.x.

[mojave]

Happy holidays!

VRAM size used at PT@32-parallel and @128-tile:
--at 7680x4320
2026.1 - 10.3GB
2025.x - 2.6GB

--at 1920x1080
2026.1 - 2.8GB
2025.x - 2.6GB

Why does new 2026.1 need to use VRAM size for resolution screen? But 2026.1 seems to be "not" faster than 2025.x.

Thank you for the report, we will look into this.

[tombyrom]

Hello guys,
The new displacement is completely broken when used in conjunction with a normal or bump map. Please see attached. It completely breaks the UV's

Please can this be looked at?

For landscapes, using mix material this will be super important, and means we will need to use the old displacement

It is also pretty much broken on any mesh with a high poly count

Thanks

[Tugpsx]

Having an issue alembic import whereas the batch render does not match the viewport. I understand that I can adjust the images in post, but something may be off with the batch render, or I have something incorrectly set. Here is my batch setting.

Screenshot 2025-12-08 224351.png

[J.C]

Hello guys,
The new displacement is completely broken when used in conjunction with a normal or bump map. Please see attached. It completely breaks the UV's

Please can this be looked at?

For landscapes, using mix material this will be super important, and means we will need to use the old displacement

It is also pretty much broken on any mesh with a high poly count

Thanks

The triangles (number depend on mesh triangles count) appear on any mesh. Looks like a bug to fix.

[coilbook]

So is neural rendering a replacement for Brigade?