Windows: Disable shader draw parameter support on certain Qualcomm GPUs #127148
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
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
Core
Module
Development Management
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
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#127148
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Anthony-Roberts/blender:x-elite-shader-draw-parameters"
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?
This works around an issue where eevee was rendering a pure black cube in certain shader configurations in the default scene (#122837).
This only affects X Elite devices (8cx Gen3 is unaffected).
@blender-bot package windows-arm64
Package build started. Download here when ready.
@ -456,0 +466,4 @@
/* X Elite devices have GPU driver version 31, and currently no known release version of the
* GPU driver renders the cube correctly. This will be changed when a working driver version
* is released to commercial devices to only enable these flags on older drivers. */
if (ver0 == 31) {
are there older versions we need to worry about?
No, version 30.x.x.x, which is the current release on 8cx Gen3, doesn't have the issue.
Only public builds of 31.x.x.x (the current release on X Elite devices, the new generation) exhibit the issue. In the future, when we get a fixed version of the driver, I'll expand the check to only enable these flags below that sub-version
There is a similar check in that file (line 153) where I disable older drivers due to a bug, also, which by extension disables older devices.
Allright, fair enough, if driver 32 comes out and it doesn't fix the issue, people are back to black cubes for blender versions that may not get any more maintenance releases,
if (ver0 >= 31) {
be better here, You can always come in back later and add a&& vers < N
to whitelist the newer drivers and disable the workaround on those.I'd rather see people on the workaround longer than needed, than potentially going back to black cubes.
Driver 32 would be with the next generation of chips that aren't due for a few years yet :) the new release for this gen would be a sub-version release, which I was intending on adding later - can swap it to a
>
though, no problemNah, all good then!