I thought the same...
not gonna say anything...
Memory reduction looks like a great improvement.
OctaneRender® 2024.1 Alpha 1
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
not gonna say anything...
Memory reduction looks like a great improvement.
C4D 2025.1.1 Octane 2025.2.1 v1.5.1, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
Hey there, really promising update!
Any estimations on when the MacOS version will be available?
Thanks in advance
Any estimations on when the MacOS version will be available?
Thanks in advance
http://www.jopfe.com - freelancing motion designer and 3d artist
I have the same question...its so long announced, but seems to be a dead end.
PURE3D Visualisierungen
Sys: Intel Core i9-12900K, 128GB RAM, 2x 5090 RTX, Windows 11 Pro x64, 3ds Max 2024.2
Sys: Intel Core i9-12900K, 128GB RAM, 2x 5090 RTX, Windows 11 Pro x64, 3ds Max 2024.2
We are really sorry about the delay. We found some serious regressions very last minute and decided that it doesn't make sense to release the macOS version as it is. We are currently working through these and with some luck we might get an update out end of this week.lacilaci wrote:Hi,
OctaneRender 2024.1 Alpha 1 Standalone for MacOS (not ready yet, will be provided as soon as possible)
So, I can't waitis there some ETA? Want to see finally why I bought M3 MacBook
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yes you are correct. Let me fix this in the release notes. This list is for 2024.KeeWe wrote:Does this mean we can expect these changes THIS year or 2024? Since theres only 1 month left in 2023, I assume you meant in the production cycle of 2024.What's on the 2024.x Roadmap for this Year?
Headless rendering with multi-render and multi-engine live linking (Blender, UE, C4D and standalone)
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Since 2023.1 took so long to get finalized we decided to roll the 2023.2 changes into 2024.1. We are aiming to get 2024.1 finalized way sooner than 2023.1, so the changes can be used in a production environment as soon as possible.renderingz wrote:This 2024.1 alpha is identical to what was stated would be part of 2023.2. What happens to 2023 going forward? Does this mean the geometry updates won't come to 2023?
Also... what happened to all these features you listed as coming in future versions of 2023? Are they coming as part of v2023, are they pushed to v2024?
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
The denoiser itself probably won't get significantly faster and that rendering itself slows down significantly if you use the AI denoiser is due to the additional data it requires to do the denoising, but this is very scene dependent. The new Open Image Denoise mode should improve the situation though as it is only calculating 2 additional AOVs and thus the additional overhead during rendering is reduced a lot compared to the AI denoiser. At least it should be. If you have a scene where this is not the case, please let us know.coilbook wrote:Can we get a faster denoiser? Rendering times increase by a factor of 2
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Exciting release!
Please, push the Rest Position to the release of 2024.1! It's essential for a lot of use-cases. And also we are hoping that the features exposed to plugins, like Brigade denoiser, will arrive to Houdini plugin too! Is the Brigade denoiser planned at all for 2024.1 or it's still unknown?
Please, push the Rest Position to the release of 2024.1! It's essential for a lot of use-cases. And also we are hoping that the features exposed to plugins, like Brigade denoiser, will arrive to Houdini plugin too! Is the Brigade denoiser planned at all for 2024.1 or it's still unknown?
Hi, thanks for the great update.
I don't want to ask a thousands times repeated question, and without any malice, what is causing the last part of Brigade (the RT denoiser) to be delayed so long? - I saw Jules respond to this on FB some time ago that they were trying to get it working in C4D with Maxon, and already have it working in UE5. But really, if it's at a stage of plugin implementation, why can't we have a peek on how it runs in standalone?
- Is it an octane core level issue, where some fundamental core changes still need to take place, or is it more a case of let's wait until we're sure DCC's would have been able to implement the piping necessary to have the RT feedback in the DCCs.
And now that we're at DCCs, I'm primarily a 3Ds Max user, so I suppose my primary question is - is this something that requires host DCCs' own dev team to implement (like in the case of C4D), or can we expect plugin devs to handle this? - I am asking as the 'lighting bolt' icon has been available to octane standalone for quite some time, but I haven't yet seen a DCC other than UE have this feature implemented.
A kind thank you in advance for answering these questions.
Kind regards,
Jani
I don't want to ask a thousands times repeated question, and without any malice, what is causing the last part of Brigade (the RT denoiser) to be delayed so long? - I saw Jules respond to this on FB some time ago that they were trying to get it working in C4D with Maxon, and already have it working in UE5. But really, if it's at a stage of plugin implementation, why can't we have a peek on how it runs in standalone?
- Is it an octane core level issue, where some fundamental core changes still need to take place, or is it more a case of let's wait until we're sure DCC's would have been able to implement the piping necessary to have the RT feedback in the DCCs.
And now that we're at DCCs, I'm primarily a 3Ds Max user, so I suppose my primary question is - is this something that requires host DCCs' own dev team to implement (like in the case of C4D), or can we expect plugin devs to handle this? - I am asking as the 'lighting bolt' icon has been available to octane standalone for quite some time, but I haven't yet seen a DCC other than UE have this feature implemented.
A kind thank you in advance for answering these questions.
Kind regards,
Jani
i9 9920X, 64GB, RTX 2080Ti
Ryzen 1800x, 64GB, 2x RTX 3090
Ryzen 1800x, 64GB, 2x RTX 3090