This is quite understandable. I just wanted to mention the problem as a feedback.
This would be great indeed! ProRender is already a powerful renderer, so it will be good to be enriched with such features.
This is quite understandable. I just wanted to mention the problem as a feedback.
This would be great indeed! ProRender is already a powerful renderer, so it will be good to be enriched with such features.
@bsavery hey whatās the plan with blender rpr and macOS on their SoC since it only supports metal api.
The current macs donāt have an ams gpu - while it looks that the m2 or higher SoC might get back some eGPU or even connection inside a pc box like the rumored MacPro.
So RPR is using the Metal API. As far as I know the blender plugin should work with the official build of blender with the latest M1 Apple computers. (which would run via rosetta)
However I imagine the plugin we publish would not work with @skw 's experimental ARM build. If / when that becomes blender official we would look at supporting it.
Get the build from https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.0.1
https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.0.13 this development build includes cryptomatte aovs.
More info https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/pull/165
When will be available working Apple M1 version (GPU)?
Do you have a M1 chip to test this on? Have you tried it? But it SHOULD work if you have an x86 build of blender.
If youāre seeing something different, please report a bug on github.
Doesnāt surprise me on the apple build. An ARM executable canāt load dylibs compiled for x86. Which is basically what that error is saying.
The artifacts in the other version are strange, but again we havenāt tested it (you know since itās not our GPU). But Iāll see if we can do something.
Great. Thanks.
Some good updates since we last talked!
Get the latest beta build here: https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.0.23
What is the definition of Backscatter as used in the uber shader?
SO I have a āfunā case.
Blender 2.92 or 2.83 - Prorender latest 3.0ā¦
CPU 1950x, 64GBs, Windows 10
GPUs - RX 6900x + Vega 56 + Vega 56. - 20.12.1 offical drivers
6900 renders great, no issues
Any vega (or combination of setups) starts causing corruption. red/white checker pattern.
For the first 1/2 of the render, all GPUās render perfectly. then corruption starts.
Tried OCCT GPU and GPU memory testing, no issues. Gamining, no issues.
Iāll try the latest beta drivers from AMD, but do wonder why there are no certified drivers since December 2020ā¦
I can test any config if needed,
Iāll give the latest beta builds in a short bit, but Iām getting same wierd effect as yfile in windows10 on the official build. This only happens when i mix GPUās together (Vega + Navi2) If I just render on Navi2, no issues, render on Vega, not as many issues.
Will report if latest beta 3.0.31 fixed the wierd ātileā spiral issue.
Generally (so far and more testing to do) all 3 GPUās are rendering together.
However there is a āinstance/scaleā issue.
First image is the cycles render whiel the second in ProRender. One of the modules (square block of the ship that is instanced from another file) is rotated in Pro, but not Cycles, and one module is scaled up 10 fold though not visible in viewport or Cycles render.
And interesting that it seems to be just the two modules, all others modules or other instanced files are OK.
Hi all! We just released some new builds for your pleasure including the following enhancements:
And a lot more fixes as well as these. Check them out at https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.1.0