Unfortunately the screenshots are not complete... have you disabled also the Tonemap option for the Intel GPU?
ciao Beppe
NEW: Octane X - is finally here! [MEGA FAQ THREAD]
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
- Jedi_blade
- Posts: 34
- Joined: Fri Jun 05, 2020 5:26 am
- Location: Iowa/Illinois
I am about to spend another 5k on a PC after shelling out 15k for a mac pro because I cannot GPU render. I do not know if it matters much but this is the error I just got and I had not even touched the scene yet. But that is not the norm, usually I can run Octane X but it is painfully slow on my two Radeon Vega Pro II cards, slower than I have seen it run on the same scene on two 2080tis cards. I have no idea why that would be. But I have realized that for me certain assets seem to crash a lot. Octane X does not update live for me most of the time, if I make any major changes to a scene I have to resend the render to the standalone and that is where most of my crashes come from, although I do get some just doing normal things like adding a floating node or attempting to adjust a UV in the node editor.
If you have Octane X for Catalina do not update to Big Sur, that was when it all changed for me.
If you have Octane X for Catalina do not update to Big Sur, that was when it all changed for me.
Mac Pro (2019)
3.2 GHz 16-Core Intel Xeon W
96 GB 2933 MHz DDR4
Two AMD Radeon Pro Vega II 32 GB
After Burner
3.2 GHz 16-Core Intel Xeon W
96 GB 2933 MHz DDR4
Two AMD Radeon Pro Vega II 32 GB
After Burner
Thing is, for OTOY to make OctaneX work properly it needed certain things in the drivers in Big Sur. I've been lucky; apart from the denoising issue (which seems like it needs another Big Sur update to fix), OctaneX is running pretty well on my Mac Pro (dual 5700XTs). Not sure why your machine isn't performing – it should be great with Radeon Vega Pro IIs.
Jules Urbach stated that this year they should focus on making Octane stable since it's already quite feature-rich. I really hope they live by that because stability is Octane's major Achille's heel. Hopefully, once OctaneX and Octane CUDA are on the same code base and release version, things will get easier/simpler. Feels like we're almost there....
Jules Urbach stated that this year they should focus on making Octane stable since it's already quite feature-rich. I really hope they live by that because stability is Octane's major Achille's heel. Hopefully, once OctaneX and Octane CUDA are on the same code base and release version, things will get easier/simpler. Feels like we're almost there....
- RegSquires
- Posts: 34
- Joined: Mon Jul 20, 2020 11:23 pm
I am using the PR6 C4D Plugin Mac OS Catalina 10.15.7 and without fail when I use PT I get a crash. Been using DL and have had little to no crashes. This is incredibly infuriating. I am also using an EGPU with a Radeon WX 9100. I so want to like Octane but it just doesn't seem to like me. The scene renders fine in the live viewer so its only when I go to render it out as a still that the issue happens.
Hi Jedi_blade,
I need to see some logs.
Please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes.
Then, load the scene in Live View, then in Picture Viewer, or until crash, then reopen c4d, navigate to c4doctane Settings/Other tab, press the Generate log report button, and share the octanelog_report.zip file, thanks.

ciao Beppe
I need to see some logs.
Please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes.
Then, load the scene in Live View, then in Picture Viewer, or until crash, then reopen c4d, navigate to c4doctane Settings/Other tab, press the Generate log report button, and share the octanelog_report.zip file, thanks.

ciao Beppe
- Jedi_blade
- Posts: 34
- Joined: Fri Jun 05, 2020 5:26 am
- Location: Iowa/Illinois
Sorry I have been trying to build a PC and forgot I left this comment, the other day I was seeing crashes even when the viewport was empty and there was nothing there. I have given up trying to use PR7. I often cannot even load C4D scenes and it has been too much trouble. The School of Motion Class I am in is on Week 5 and I am not even starting Week 2 because of how much this is unstable. So I am saving up for a PC.bepeg4d wrote:Hi Jedi_blade,
I need to see some logs.
Please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes.
Then, load the scene in Live View, then in Picture Viewer, or until crash, then reopen c4d, navigate to c4doctane Settings/Other tab, press the Generate log report button, and share the octanelog_report.zip file, thanks.
ciao Beppe
It is going to take me a few weeks or more to get the GPUs for the PC I want, so I am hoping maybe PR8 drops before that so I have something to use if it is stable. But other than that this GPU rendering on the Mac Since July has really just made me see no real way Mac and GPU make sense over PC. At least not yet. I have learned that is because this is new tech and I just made the mistake of buying Mac knowing I want to start 3D rendering.
Mac Pro (2019)
3.2 GHz 16-Core Intel Xeon W
96 GB 2933 MHz DDR4
Two AMD Radeon Pro Vega II 32 GB
After Burner
3.2 GHz 16-Core Intel Xeon W
96 GB 2933 MHz DDR4
Two AMD Radeon Pro Vega II 32 GB
After Burner
They start testing. It's strange that only now. The first beta of macOS 11.2 started two months ago.
MacBook Pro 16" | AMD Radeon Pro 5500M 8 GB | 2,3 GHz Intel Core i9 | 64 GB RAM + eGPU Razer Core X | Asus ROG Strix RX 5700 XT OC