Metal: Resolve runtime issues with texture views #107167

Merged
Jeroen Bakker merged 1 commits from Jason-Fielder/blender:MetalEEVEENext_TextureViewCompatibility into main 2023-05-01 09:14:06 +02:00
Member

When creating a texture view, Metal may require that the original
GPUTexture state is modified in some way. This may be a result
of deferred creation, or, to cache the texture view against the
source.

As a result, GPUTexture passed into GPU_texture_create_view
cannot be const.

Small fixes have also been made in the Metal texture
implementation to ensure correct function of texture views.

Authored by Apple: Michael Parkin-White

Ref #96261

When creating a texture view, Metal may require that the original GPUTexture state is modified in some way. This may be a result of deferred creation, or, to cache the texture view against the source. As a result, GPUTexture passed into GPU_texture_create_view cannot be const. Small fixes have also been made in the Metal texture implementation to ensure correct function of texture views. Authored by Apple: Michael Parkin-White Ref #96261
Jason Fielder added 1 commit 2023-04-20 12:42:50 +02:00
When creating a texture view, Metal may require that the original
GPUTexture state is modified in some way. This may be a result
of deferred creation, or, to cache the texture view against the
source.

As a result, GPUTexture passed into GPU_texture_create_view
cannot be const.

Small fixes have also been made in the Metal texture
implementation to ensure correct function of texture views.

Authored by Apple: Michael Parkin-White

Ref #96261
Jason Fielder requested review from Jeroen Bakker 2023-04-20 12:43:19 +02:00
Jeroen Bakker requested changes 2023-04-24 08:49:11 +02:00
@ -1820,3 +1821,4 @@
/* Assign usage. */
gpu_image_usage_flags_ = GPU_texture_usage(src);
BLI_assert_msg(
Member

How bad is it to have incorrect usage flags. This might also fail for devs/users not familiar with the Metal backend and they are then not able to continue their work. Would rather see an CLog error/warning depending on the actual priority to fix the issue. Or guarded by --debug-gpu.

How bad is it to have incorrect usage flags. This might also fail for devs/users not familiar with the Metal backend and they are then not able to continue their work. Would rather see an CLog error/warning depending on the actual priority to fix the issue. Or guarded by --debug-gpu.
First-time contributor

Yeah, its likely not important for non-metal platforms right now, but there was a discussion about moving the checks outside of the GPU backend, as this may also help the Vulkan bring-up.

However, we can guard it behind debug-gpu for now perhaps?
The purpose of this was mostly for aiding bring-up, to ensure certain features were using required flags up front, though hopefully the debug-gpu flag can still be used for this.

Yeah, its likely not important for non-metal platforms right now, but there was a discussion about moving the checks outside of the GPU backend, as this may also help the Vulkan bring-up. However, we can guard it behind debug-gpu for now perhaps? The purpose of this was mostly for aiding bring-up, to ensure certain features were using required flags up front, though hopefully the debug-gpu flag can still be used for this.
Member

I think for now it is better to assert all the time. This way it is easier for users/developers to detect any issue so we can fix it. Hiding it behind the --debug-gpu flag has some other cons:

  • might crash when we ask users to provide more information about a different issue.
I think for now it is better to assert all the time. This way it is easier for users/developers to detect any issue so we can fix it. Hiding it behind the --debug-gpu flag has some other cons: - might crash when we ask users to provide more information about a different issue.
Jeroen Bakker approved these changes 2023-05-01 09:12:52 +02:00
Jeroen Bakker added the
Interest
Metal
label 2023-05-01 09:13:05 +02:00
Jeroen Bakker added this to the 3.6 LTS milestone 2023-05-01 09:13:09 +02:00
Jeroen Bakker added this to the Viewport & EEVEE project 2023-05-01 09:13:13 +02:00
Jeroen Bakker merged commit 36e1ebc78d into main 2023-05-01 09:14:06 +02:00
Howard Trickey referenced this issue from a commit 2023-05-29 02:51:43 +02:00
Sign in to join this conversation.
No reviewers
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, 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 Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#107167
No description provided.