macOS 10.11 and NVIDIA user interface display broken #61551
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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, Assets & 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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61551
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
{F6612545}System Information
Operating system:
OS X El Capitan Version 10.11.6
iMac (24-inch, Early 2009)
Graphics card: NVIDIA GeForce GT 130 512 MB (standard built-in)
Blender Version
Broken:
blender-2.80.0-git20190214.a9da750aee08-x86_64 (from app file name - splash screen unreadable)
Short description of error
See screenshot. Interface is very colorful, but obviously unusable.
Granted, this is a 10 year old computer, but Blender 2.79b works like a charm.
Exact steps for others to reproduce the error
Interface appears as seen here upon launch.
Added subscriber: @Gregor1
#63374 was marked as duplicate of this issue
#62949 was marked as duplicate of this issue
blender/blender-addons#62848 was marked as duplicate of this issue
#59697 was marked as duplicate of this issue
#59955 was marked as duplicate of this issue
#61844 was marked as duplicate of this issue
Added subscriber: @oprinds
I have the same issue and can add some extra info
System Information
Operating system:
OS X El Capitan Version 10.11.6
Macbook pro mid 2009
Blender version : blender-2.80.0-git20190214.a9da750aee08-x86_64
Extra info:
This only happens when using the 'Higher performance' graphics setting (NVIDIA GeForce 9600M GT). Setting the power settings to 'Better battery life' (NVIDIA GeForce 9400M) works. It seems to me blender mixes up the two gpu's and perhaps the textures are initialized on the wrong gpu or something like that..
Side notes
The Eevee renderer doesn't work even while using the 'Better battery life' setting. It renders either completely white or black. OpenGL core profile 3.3 should be 100% supported though on the system using both gpu's according to OpenGL Extension Viewer. The OpenGL Compatibility mode is only 2.1 on both gpu's
Here is the output from opening blender while using 'Higher performance' setting..
blender-output.txt
Do you think the eevee render issue is related, or should I start a second thread for that?
Thanks for any help...
Added subscribers: @fclem, @ZedDB
The issue here is that apple has very buggy opengl drivers. Additionally they have dropped opengl support so they will not fix their buggy drivers either.
@fclem anything we can do here?
Added subscribers: @goofx, @DotBow
Added subscriber: @Grivius
Scrambled, extremely colorful User Interfaceto macOS 10.11 and NVIDIA user interface display brokenAdded subscriber: @tarikboucherba
I have downloaded the source code and setup the project to compile on my mid 2009 macbook pro (running 10.11.6).
If anyone has some ideas or tips on what to try out, or patches to test I can do and test it right away.
Added subscriber: @willardj
I don't know what to say at this point. Even the basic shaders are not behaving correctly.
@oprinds you can try starting with a single area with only text and icons and try to see what does not work from here. Seems the biggest problem is texture drawing, not a single textured quad displays correctly.
Added subscriber: @earlevel
I got some warnings from AppKit and CoreGraphics. I am not sure what they mean, but they are related to the GL context, so I am posting them here. Maybe some of you can make out what it means and if it's is perhaps related to the texture drawing issues.
I just realized, it was my breakpoints, that triggered the warnings..
Sorry for the noise..
Added subscribers: @JWS, @mib2berlin
Added subscriber: @brecht
Changed status from 'Open' to: 'Archived'
Closing since we only officially support macOS 10.12 and higher for Blender 2.80 now.
More information on that decision is here:
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/
We keep this bug listed in #61936 (EOL GPU problems tracking report) in case anyone is interested in fixing it.