Im using os 10.15.1 with blender 2.83 and the latest version of prorender. I normally kept the device on both my cpu and graphics card and when I tried to switch to only one of them blender slowed down and I had to force quit it.
I am having the same issue with a 2019 iMac, with an i9-9900 processor, 64GB ram and the Radeon Vega 48.
When in MacOS (the latest version) i can render single images but when i render an animation (as frames) it does one frame and then while initialising for the next, blender crashes consistently from blender 2.83 - 2.82a, i tried it with 2.81 but i got artefacts on the left side of the image with the right hand side totally fine (weirdly, wondered if this will help troubleshoot the source of the problem for developers)
I have run the same file on macOS using Evvee and it worked perfectly, and using bootcamp i am using Prorender in blender 2.83 on windows 10 and is working fine with no crashes while rendering.
Hope this can be fixed as the frames are actually rendering slower in windows 10 so would like to get back on macOS.
Hi, I got this week a complete new MacPro with the 16core processor and one W5700 videocard. I installed the newest 2.83 Blender version and the most recent version of AMD Prorender. Different attempts to render a single image or a animation have the same result: the system crashes. What is going wrong?
Not sure if I should make another thread but I've found that RPR crashes pretty regularly when working on a standard scene like Blender's Barcelona Pavilion.
It is after I've switched the renderer to RPR and start changing the settings. Specifically — and I'm not sure if this feature uses RPR or Cycles — it happens most often when switching back and forth between a render preview in the main viewport. If I don't ever attempt to use the viewport preview render than the crashing is less frequent. But otherwise I can expect it to happen 3-4x a day. The steps looks something like:
1. Launch Blender open the blend file, set the scene switch to RPR
2. Change RPR samples, quality, add sun-sky, set those.
3. In the viewport switch to render preview mode to see where the shadows are falling, if light it too bright etc
4. Switch back to non-preview mode, then render.... result doesn't look right, cancel
5. Go back to render preview in viewport change more settings, then switch off the preview again
7. iterate 3-6 until crash occurs
What I'm not sure of is whether if using RPR, and choosing a render preview, that preview is being generated by RPR engineor by Eevee or something else. Maybe this is not RPR but an Eevee bug.
macOS 10.15.6, latest Blender LTS build, current RPR and material library versions (downloaded a couple weeks ago). MBP14,3 with AMD 560 dGPU. Later plan to test with eGPU.
So, just on a higher level, your workflow seems a bit strange. Can't you stay in the viewport preview mode and iterate on lighting until it looks correct? Why not?
Otherwise it's a bit hard to diagnose