OTOY Forums

bepeg4d wrote:

KeeWe wrote:Since we are in the middle of a project and will get a new workstation with a 5090 soon, will there be a production ready build of 2024? I really don't wanna switch to a beta build with a deadline coming up...

Nope, sorry, it is not possible, at least, not before 2025.1 will be stable.

ciao,
Beppe

Puh, that's a real bummer. Supporting new hardware only in a beta build...

Hi,
supporting a new Nvidia GPUs family is not a joke, especially when you need to use a new cuDNN library.

It happened the same with first RTX Turing support in 2020.1 Alpha.

So this time is better, since we are already at 2025.1-Beta2 version, and the stable 2025.1 version is not too far away.

ciao,
Beppe

Why is the (new) particle size 10 times smaller when I put the geometry into the octane tag?

DinoMuhic wrote:

J.C wrote:Choosing "Enable A/B comparison" from compare menu crashes C4D. Happens on every scene I've tried, even on empty one.
Log attached.

The log says this is Build 0101
Have you tried the same in later builds 0102 or 0103?

Cheers

Looks like this is fixed in latest release. Thanks!

Hi, is it possible to categorise Output AOV's like it is in Standalone or Blender?

btw. in C4D plugin there is missing "Dither for 8bit display" node in Output AOV nodes and also other nodes. There are over 40 nodes in Standalone but in C4D there are 31

Just checking, was animated texture 'start offset' removed or never available in octane? It seems like a small feature and would be greatly useful to have like in Redshift.

Hi,
Is there any known issue with the 'C4D Light Linking' feature in the latest version?
I've been using the latest version for about 2 weeks, and I couldn't use this feature—it wasn't working, or I'm missing something I'm not sure
I installed Octane 2024 R2, and the feature still doesn't work, even though 'C4D Light Linking' is enabled in the Octane settings, of course.

Delizade wrote: Tue Mar 25, 2025 10:59 pm Hi,
Is there any known issue with the 'C4D Light Linking' feature in the latest version?
I've been using the latest version for about 2 weeks, and I couldn't use this feature—it wasn't working, or I'm missing something I'm not sure
I installed Octane 2024 R2, and the feature still doesn't work, even though 'C4D Light Linking' is enabled in the Octane settings, of course.

Please use Octane Light Linking feature instead:
https://docs.otoy.com/cinema4d/Workingw ... nking.html

ciao,
Beppe

J.C wrote: Thu Mar 20, 2025 8:10 pm Hi, is it possible to categorise Output AOV's like it is in Standalone or Blender?

btw. in C4D plugin there is missing "Dither for 8bit display" node in Output AOV nodes and also other nodes. There are over 40 nodes in Standalone but in C4D there are 31
aovs.png

This will be fixed in the next version. The list is only incomplete when you access it from the Add Layer button. If you create the node and go into it's first tab, the list there will have all entries from which you can choose from.

Is there something going on with standard materials ? They're suddenly just not working and rendering as white.

I'm on Driver 572.83. Latest C4D and Octane builds. RTX 4090

Edit1 : tried clean installing the driver. Didn't seem to fix it.
Edit2 : tried multiple different studio driver versions.
Edit3 : Issue is happening on 2025.1.3 and 2024.5.1 but on 26.110, it's rendering fine.
Edit4 : Removed all other plugins just in case, nothing changed
Edit5 : Deleted the prefs folder of C4D. Didn't seem to help.
Edit6 : Clean installing c4d didn't help.
Edit7 : Included a log from C4D 2025. Sphere with a red standard material that's rendering white.
Edit8 : This isn't device-specific. I tried my other machine with the same 2025 build and Octane build. It's running on a 2x4080. Same issue. man, this completely screwed me over as It went unnoticed while I was working and it messed up multiple days worth of rendering.
Edit9 : 2024.1.2-[R3] Build 0102 has the same issue.
Edit10: 2024.1.2-[R2] Build 0101 renders fine.

TLDR: Since 2024.1.2-[R3] Build 0102. Standard material don't render correctly. Same issue appear to be happening on the 2025 version.
This is most definitely related to the support for rendering RS Materials. Seems like it completely broke standard materials. bummer.
I'm reverting back to 2024.1.2-[R2] for now.