Page 2 of 2

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Mon Aug 11, 2025 10:42 am
by paride4331
Hi tombyrom,
The new displacement feature is still not functioning. This was essentially due to a communication oversight. An unexpected issue arose between releases during development, which required us to postpone the fix to an upcoming release.
Regards
Paride

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Tue Sep 02, 2025 12:47 pm
by samsue
Hallo,

The Guardian / Freezing issue was solved in this version? We are getting a lot of problem even so we are not using Octane, the Max Windows freezes

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Wed Sep 03, 2025 3:23 pm
by coilbook
Hi,
For some reason when using a quick mesh and point cloud with octane we cannot render flowers and leaves. Is it a bug? (We are using itoo 9 Forest IVY)

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Thu Sep 04, 2025 5:02 pm
by tombyrom
Last time I used forest ivy I am pretty sure I had to output full mesh, I dont think quick mesh is supported yet by Octane. Does selecting mesh work?

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Fri Sep 05, 2025 8:07 am
by mbetke
Yes you can only render full geometry for ForestIvy. I had a project with a huge wall and had to switch back to a common 3D model.

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Fri Sep 05, 2025 4:22 pm
by coilbook
material editor is still very slow to load.
Missing textures was never fixed/implemented like you promised.



Thank you

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Sun Sep 07, 2025 2:42 pm
by coilbook
coilbook wrote: Wed Sep 03, 2025 3:23 pm Hi,
For some reason when using a quick mesh and point cloud with octane we cannot render flowers and leaves. Is it a bug? (We are using itoo 9 Forest IVY)
this is from itoo people. Can you please add support for forest ivy?

"It appears that Octane Render is currently unable to process the ForestIvy structure. Therefore, the Mesh Viewport mode must be used to render the object accurately. I’m afraid that we can't do much more in this case. For developers of render engines that don't have an SDK (like the mentioned Octane), we provide an internal API written in C++ for the 3ds Max SDK. They use this data to generate the instances directly in their render engine, and the final implementation of ForestPack's features depends on the way it's done for that specific render engine."

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Thu Sep 11, 2025 3:08 am
by neonZorglub
coilbook wrote: Sun Sep 07, 2025 2:42 pm
coilbook wrote: Wed Sep 03, 2025 3:23 pm Hi,
For some reason when using a quick mesh and point cloud with octane we cannot render flowers and leaves. Is it a bug? (We are using itoo 9 Forest IVY)
this is from itoo people. Can you please add support for forest ivy?

"It appears that Octane Render is currently unable to process the ForestIvy structure. Therefore, the Mesh Viewport mode must be used to render the object accurately. I’m afraid that we can't do much more in this case. For developers of render engines that don't have an SDK (like the mentioned Octane), we provide an internal API written in C++ for the 3ds Max SDK. They use this data to generate the instances directly in their render engine, and the final implementation of ForestPack's features depends on the way it's done for that specific render engine."
Hi coilbook,
That's right, the ForestPack IVY objects are not natively supported in current versions.
We are adding support for the next versions (16.09 and 26.02)
Thanks

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Thu Sep 11, 2025 1:29 pm
by tombyrom
neonZorglub, just letting you know that I was getting OSL update issues in the slate editor with this 2026 version. Clicking between different OSL textures in the Slate editor would result in a visual merging of parameters, caching previous OSL texture params and displaying them in the next one - making it almost impossible to update correct ones, even re-opening max did not work, looked like some weird caching issue.

I just switched back to your latest 2025 build (todays) and it its stable. However, there is a seperate issue where changing a value in a float range for example looks to refresh other params whilst you are moving the float up and down.

Edit:
Actually, I think I've pinpointed the root cause, as the same issue is now happening in 2025 version. Seems that when you have one OSL texture going into an input of another OSL texture it starts to get really buggy in the slate editor. This does not happen in standalone. I will get a simplifed version so you can debug.

Edit two:
It seems that actually, there is some sort of caching issue as now my 2025 install has the exact same issues as 2026, even after decoupling the OSL textures, they exhibit weird behavior when changing params within it. Video - https://drive.google.com/file/d/1G2iMdtCLwecDJccY60RPgNFd9OnUcN45/view?usp=sharing

Re: OctaneRender® for 3ds max® v2026.1 Alpha3 - 26.01

Posted: Wed Sep 17, 2025 4:44 am
by coilbook
we need better volumetric lights and fog like other renderers have