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 ...

PR 7 is out with a plugin and standalone version if you upgrade to Big Sur 11.1 - it might have fixed the bugs you are talking about, so Id recommend trying that first.

I can verify something is up with universal and metallic maps, I set Metalness to 1.0 float and it just ... stopped rendering. It won't start back up, won't restart. The app isn't frozen, I can still adjust the nodes, change settings etc. Even deleting the offending Universal material does nothing ...

Actually it looks like I had managed to install it in two different C4D plugin folders. Oops! They should streamline that :lol:

Having it in Cinema's bundle /Applications/Maxon Cinema 4D R2X/plugins and in Cinema's other plugins folder ~/Library/Preferences/Maxon/Maxon Cinema 4D R2X/plugins.

Not ...

Ok with the PR 7 Standalone it works as expected - and its definitely faster! I suspect the crashing might have something to do with code signing as the PR7 DMG + the App bundle were not signed properly - had to override, and so it might be that the Cinema 4D version isn't giving me the chance to ...

It also doesn't work for me, says there is a heap allocation error.

Application Specific Information:
/Applications/Maxon Cinema 4D R22/plugins/OctaneX_Enterprise_PR7_BigSur/liboctane.dylib
abort() called
Cinema 4D(7455,0x10d451e00) malloc: Incorrect checksum for freed object 0x7fd9bee4ee40 ...

I strongly suggest that you all get on the Octane Discord server - 11.1 breaks PR5 and everything before it, you will have to wait for PR7 (which is apparently coming very soon) and will have support for M1.

I haven't tried VDBs, but going out of core and rendering image sequences work fine for me. I think the key difference between us is either that I am only using 1 GPU or what I think is more likely is that I am using a VII eGPU, which is based on the Vega 2 architecture and you're using 5700XTs ...

I believe what is happening is your scene is going out of core - check to see if your VRAM exceeds the 11GB of your 2080Tis (or the 22 if NVLinked). If this is the case data has to be moved from main CPU Memory during render and as a result your GPUs might have a series of spikes instead of one ...

This is indeed the case: the AMD 5900x has only 24 PCIe lanes, your existing Intel has 40. Depending on the motherboard, these lanes can be split up differently, but the lower the amount of lanes the GPU gets, the slower cpu-memory-dependent things will be (like gaming or scene loading times). GPUs ...