Eevee ambient occlusion is incorrect on M1 macMini #87801
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#87801
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: macOS-11.2.3-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Apple 4.1 Metal - 71.0.7
Blender Version
Broken version: 2.93.0 Beta, branch: master (modified), commit date: 2021-04-19 10:12, hash:
6dffdb02faNote: Earlier versions I tested (running with Rosetta 2) all have this bug.
Short description of error
Eevee ambient occlusion is incorrect on M1 macMini.
Exact steps for others to reproduce the error
From default scene:
Note: Every file, every combination of settings produce this issue to some extent.
Added subscriber: @Andari
#91176 was marked as duplicate of this issue
#90086 was marked as duplicate of this issue
#87650 was marked as duplicate of this issue
Added subscriber: @Lucas-Bleackley-Petter
I can confirm this issue is happening on Apple Silicon Macs. I'm noticing it on my 2020 Mac mini
M1and it affects both the 2.92.0 release and the latest arm64 2.93.0 Beta (c75b2019e1).Here's a .blend file I created following the steps above to reproduce the error:
Ambient Occlusion Test.blend
On a 2018 MacBook Pro Intel, running the 2.92.0 release on macOS 10.15.7, this is what the viewport and renders of the above .blend file look like, as expected:
{F10102598}
On the Mac mini
M1, running the arm64 2.93.0 Beta (c75b2019e1) on macOS 11.3.1, this is what the viewport and renders look like. The glitching is very noticeable.{F10102579}
On the Mac mini
M1, running the 2.92.0 release via Rosetta 2 on macOS 11.3.1, this is what the viewport and renders look like. The glitching is noticeable in the viewport, but the render less so, although the render is still incorrect compared to the render from the Intel MacBook Pro above.{F10102587}
Added subscriber: @PratikPB2123
Adding MacOS as a tag here since you are facing the problem on Mac.
Btw I am not able to reproduce it on Windows.
Added subscriber: @ankitm
Changed status from 'Needs Triage' to: 'Confirmed'
There's no M1 in triaging team, but confirming due to easy steps, and active reporters.
Added subscriber: @JacobMerrill-1
it would be neat to have 'teamviewer' or something like that be used to confirm issues / even test builds etc on willing users machines
Added subscribers: @ColbyKlein, @mano-wii
Added subscriber: @jon_b
I'd donate an account of this M1 cloud server if it would get used to fix Blender M1 bugs:
https://www.scaleway.com/en/hello-m1/
Any way we can move this forward? (not complaining, but I'm just ignorant of the process)
This is a critical bug for any M1 users who are planning on EEVEE as a final render option.
I was able to build Blender from source on my M1 MacMini without any issues. I started experimenting with the Eevee AO shader without success on figuring out what this issue is. I do not have enough time to properly look into it though. If anyone has the faintest idea what this is caused by, let me know, and I will try to squeeze in the time to check it. My idea was that it might have something to do with what the depth component of the framebuffer samples outside its borders.
Added subscribers: @CorradoPiscitelli, @fclem, @Jeroen-Bakker, @icappiello
Confirmed on M1 iMacs and Blender 2.93.1
System Information
Operating system: macOS-11.4-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Apple 4.1 Metal - 71.6.4
Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash:
1b8d33b18cWorked: (newest version of Blender that worked as expected)
Short description of error
Different AO results between apple M1 and Intel machines.
Opening the same file in rendered on EEVEE on an M1 machine gives different results from an Intel one.
See attached image for visual reference
Please note that both Rosetta and native ARM are consistent in this result.
Exact steps for others to reproduce the error
Set view in rendered. The effect becomes move visible changing ambient occlusion distance and factor values.
Based on attached .blend file Apple_M1_AO_bug.blend
Added subscriber: @SensArice
Added subscriber: @Khameir
I would like to emphasise how this is currently a 100% pipeline breaker in our production as we heavily rely on EEVEE. Is there any chance to get an update on this? Thanks for all your hard work!
Yes, this has been an issue for about 6 months and has had no progress unfortunately. Could use some direction on how the community could help diagnose at least. This stops me from using EEVEE at all as a rendering engine.
This will be tackled next week.
Thanks a lot Clément! Let me know if there is anything i could test for you!
This issue was referenced by
f2e96c2473This issue was referenced by
84f98e28e3Changed status from 'Confirmed' to: 'Resolved'
Hi!
I tested this with the latest build from builder.blender.org on my M1 iMac, and I have found no problems!
Thanks for the Fix!
Thank you, @fclem!! Your fix works great. On 2.93.5RC, renders on Intel and Apple Silicon match each other. It has also resolved #88241 (macOS: Eevee Screen Space Reflections are broken on arm64), which can now be closed too!