OctaneX Studio/Enterprise PR7 for BigSur Tweet

[james_conkle]

Works well on my 2019 16in. MBP. Does this version have the new Tone Mapping that's in the current Cuda release candidate?

[bepeg4d]

@ jamesbat420: please disable AI Denoiser, there is an issue with Big Sur 11.1.
Please also disable the Intel GPU in Octane Settings/Devices panel, if present, and render only with AMD GPUs for now.

@ james_conkle: nope, OctaneX PR7 is basically identical to v2020.1.5 CUDA.

ciao Beppe

[Weezer]

@ jamesbat420: please disable AI Denoiser, there is an issue with Big Sur 11.1.

Er, an issue with Big Sur or an issue with OctaneX? Please don't say we have to wait for yet another macOS update...

[james_conkle]

I've also noticed that when I enable a render region of any size the samples stop at 60 no matter what my target samples are. In CUDA it'll keep going even past the "Spp" I set in Octane Settings (Which isn't perfect but better than caping at 60).

[bepeg4d]

hi james,
no problem here with both render region, that continues after the max samples assigned:

and film region, that stops at the max samples assigned:

ciao beppe

[Weezer]

Hi Beppe – any sign of an OctaneX PR8? Or the full v1 release for that matter?

[bepeg4d]

It is not ready yet.
ciao Beppe

[Weirdpictures]

Hi Aoktar,

thanks for this incredible test release. I can't believe that i am seeing octane running on our 2013 trashcan Mac Pro. I thought it wouldn't be supported, just newer AMD GPU's, but it actually works great on our old machine. Only caveat is that it seems to not like rendering on both integrated AMD GPU's. If we activate both GPU's the live viewer always shows a checker pattern, like both GPU's have a different output. But if we render with just one GPU activated it works perfectly fine (But yes, of course only half the speed

Anyway, unexpected that it works at all, so can't complain. I will try to install R23 today to see if it makes a difference, as well as check it out on our MacBook pro 16 inch from 2020, very exciting times

Thanks for all the hard work over all these years, we love octane on C4D.

Best,

Martin

[cjadams]

I have noticed that the GPU selection settings do NOT persist after a reboot..

If i come back the next day.. and try and use octane.. i get a ton of console errors. till i go in and RE DISABLE the intel graphcs.
is there a reason this does not save?

If I uncheck the intel gpu.. as long as i keep cinema open.. or even if I close and re-open Cinema. Or even logout and login again it seems to stick.. but a computer reboot takes it away again and i get the Gpu errors.
Cinema R23.008 Build RB323902

Confirmed at least for me.. it persists even after restarting C4d or even Logging out and logging in again into Macos - But.. it reverts to having the intel one selected...if i Reboot the whole machine. NOTE that i'm on Macos 11.1 with "automatic Graphics switching" Disabled - Macbookpro 2019 16 inch. AMD Radeon Pro 5300m

[plasmapeppers]

Hi Aoktar,

thanks for this incredible test release. I can't believe that i am seeing octane running on our 2013 trashcan Mac Pro. I thought it wouldn't be supported, just newer AMD GPU's, but it actually works great on our old machine. Only caveat is that it seems to not like rendering on both integrated AMD GPU's. If we activate both GPU's the live viewer always shows a checker pattern, like both GPU's have a different output. But if we render with just one GPU activated it works perfectly fine (But yes, of course only half the speed

Anyway, unexpected that it works at all, so can't complain. I will try to install R23 today to see if it makes a difference, as well as check it out on our MacBook pro 16 inch from 2020, very exciting times

Thanks for all the hard work over all these years, we love octane on C4D.

Best,

Martin

Screen Shot 2021-01-08 at 9.32.22 PM.jpg

If you disable tonemapping on one of them the checker pattern will disappear - you can see the setting for it in cjadams's post right above this one