Project attached. The hair object has a material already applied and is working correctly. If you render, you should see some red hair, this is as expected.

hair a.jpg

However if you move the white QSG material from Null A to Null B, then relaunch the render, all hair now render black.

hair ...

Just to add, Ive had near identical problems with 3090 and 4090 cards, though with msi afterburner rather than hwinfo. This is with it simply installed and not actively adjusting the cards.

muchos gracias

Add an octane tag to any particle system and set the mode to Voxel. The attributes window layout is incorrectly spaced out.

octane 2025.2.0
c4d 2025.2.1

I don't.

But I have.

And now it doesn't work.

I spent 2 hours trying to work out why my sims were all rendering in the wrong place, but screw it, lets not fix bugs, lets make all the other c4d octane users waste their day working around basic octane shortcoming too.

Does anyone have any insight on how to inject the c4d pyro colours into octane's rendering? Im trying to render some rainbow dust but cant work it out. I can using images and gradients piped into the density colour mapped on from the outside but im trying to use the color of the volume itself so the ...

Open the attached project and play through to frame 10. Note that there are 3 emissions coming out of the cube. If you render to the live view, these emissions will all be in the wrong location.

The bug is that octane is ignoring the fact that the Pyro Output object is not at 0, 0, 0. Once the Pyro ...

Open the attached project
Render to live view, I get this which is correct:

render1.jpg

I then click on the denoised version and see this which is incorrect:

render2.jpg

Clicking back on the standard main render is now also incorrect.

render_3.jpg

Re sending the data to the gpu will fix ...

I loaded a native redshift project into c4d 2025.2 with octane 2025.1 (just one of the c4d content library trees)
I converted the RS materials to Octane materials with the octane convert command
I have saved the project, everything is good.

However since updating octane to 2025.2, c4d/octane now ...

Problem seems fixed in 2025.2, will update if it happens again