Cinema4D version 2020.1.5-R4 (Obsolete stable) 17.10.2020

[VVG]

Ahmet,should we expect improved XP support in 2020.2?
(SDK XP made available OTOY)

Tell us what improvements can you expect now?


Thanks

[aoktar]

Ahmet,should we expect improved XP support in 2020.2?
(SDK XP made available OTOY)

Tell us what improvements can you expect now?


Thanks

I'm not on yet, working on core revisions/addons for 2020.2. You have to wait all finish then I'll take a look. Thanks

[thodosplay998]

We are working to wrap up 2020.2 this month. We are on RC2 about to come out now, RC3 by end of week, and typically there are four RC builds before stable.

That would be great! Thanks for the info!

[hellagain]

Two months can't fix a denoise! Facking shit!

[jianle]

Two months can't fix a denoise! Facking shit!

[bepeg4d]

The issue is more complex, and it is caused by Nvidia CUDA.
The core devs have prepared 2020.1 SDK based on CUDA 11 with A100 Ampere GPUs, and everything was working perfectly.
Then Nvidia has presented Ampere RTX 30X0, but based on new CUDA 11.1, and the core devs had to rewritten everything with new 2020.2 SDK to perfectly support the new architecture.
So the issue is already fixed in latest Standalone 2020.2 Release Candidate.
But now, all plugins have to be rewritten with the new SDK, and this is taking time, but we are almost there, and 2020.2 has so many new cool features, that it worths to wait a little bit more, trust me!

Happy GPU Rendering,
ciao Beppe

[Antoncromas]

The issue is more complex, and it is caused by Nvidia CUDA.
The core devs have prepared 2020.1 SDK based on CUDA 11 with A100 Ampere GPUs, and everything was working perfectly.
Then Nvidia has presented Ampere RTX 30X0, but based on new CUDA 11.1, and the core devs had to rewritten everything with new 2020.2 SDK to perfectly support the new architecture.
So the issue is already fixed in latest Standalone 2020.2 Release Candidate.
But now, all plugins have to be rewritten with the new SDK, and this is taking time, but we are almost there, and 2020.2 has so many new cool features, that it worths to wait a little bit more, trust me!

Happy GPU Rendering,
ciao Beppe

Your competitor's engine had denoise support for 3000 cards on day one. Just saying. . .

[tomsvfx]

The issue is more complex, and it is caused by Nvidia CUDA.
The core devs have prepared 2020.1 SDK based on CUDA 11 with A100 Ampere GPUs, and everything was working perfectly.
Then Nvidia has presented Ampere RTX 30X0, but based on new CUDA 11.1, and the core devs had to rewritten everything with new 2020.2 SDK to perfectly support the new architecture.
So the issue is already fixed in latest Standalone 2020.2 Release Candidate.
But now, all plugins have to be rewritten with the new SDK, and this is taking time, but we are almost there, and 2020.2 has so many new cool features, that it worths to wait a little bit more, trust me!

Happy GPU Rendering,
ciao Beppe

Your competitor's engine had denoise support for 3000 cards on day one. Just saying. . .

Thats because Redshift uses Optix wich is made by Nvidia, so it makes sense that by default upgrading CUDA, Optix gets upgraded automaticly, probably without doing much.
Octane on the other hand has custom made Denoiser, wich also works way better than Optix (plus Optix has a big dedicated team working on it)

[thodosplay998]

The issue is more complex, and it is caused by Nvidia CUDA.
The core devs have prepared 2020.1 SDK based on CUDA 11 with A100 Ampere GPUs, and everything was working perfectly.
Then Nvidia has presented Ampere RTX 30X0, but based on new CUDA 11.1, and the core devs had to rewritten everything with new 2020.2 SDK to perfectly support the new architecture.
So the issue is already fixed in latest Standalone 2020.2 Release Candidate.
But now, all plugins have to be rewritten with the new SDK, and this is taking time, but we are almost there, and 2020.2 has so many new cool features, that it worths to wait a little bit more, trust me!

Happy GPU Rendering,
ciao Beppe

Your competitor's engine had denoise support for 3000 cards on day one. Just saying. . .

Thats because Redshift uses Optix wich is made by Nvidia, so it makes sense that by default upgrading CUDA, Optix gets upgraded automaticly, probably without doing much.
Octane on the other hand has custom made Denoiser, wich also works way better than Optix (plus Optix has a big dedicated team working on it)

I'm 90% sure that Octane has the same OptiX denoiser. And no, OptiX is not updating automaticly. Nvidia gives you CUDA SDK and OptiX SDK. And to implement it takes time. And i think you are right an OTOY team took some time when working on denoiser to make it custom. Because Redshift is bad at denoising. like alot.

[Goldorak]

Your competitor's engine had denoise support for 3000 cards on day one. Just saying. . .

Thats because Redshift uses Optix wich is made by Nvidia, so it makes sense that by default upgrading CUDA, Optix gets upgraded automaticly, probably without doing much.
Octane on the other hand has custom made Denoiser, wich also works way better than Optix (plus Optix has a big dedicated team working on it)

I'm 90% sure that Octane has the same OptiX denoiser. And no, OptiX is not updating automaticly. Nvidia gives you CUDA SDK and OptiX SDK. And to implement it takes time. And i think you are right an OTOY team took some time when working on denoiser to make it custom. Because Redshift is bad at denoising. like alot.

To confirm - we don't use the Optix denoiser in any way - our Spectral AI denoiser is completely custom built by us for Octane (for much higher quality), and depends on NVIDIA CuDNN (which NVIDIA initially broke with Ampere, but didn't fix until month later which is why we are only now able to get ampere support working with 2020.2).on MacOS we have the AI Denoiser working with Metal/AVX2 on Intel/AMD/Apple hardware.