Support Huge Image Sizes in image/uv editor #80113

Closed
opened 2020-08-25 21:01:39 +02:00 by Jeroen Bakker · 8 comments
Member

D8234: Use DrawManager for Image/UV Editor uses a new drawing method for the image/uv editor. It has a limitation that huge images are resized to fit on the GPU. These max size depends on the used hardware typically the limitation is between 12k and 16k and the GL Texture limit setting in the user preference.

In case the user uses a huge texture it is more likely that not all pixels are shown on the screen. We could create a sub-buffer with visible areas of the image and render those. This only needs to do in case the provided GPUTexture isn't sufficient.

NOTE: This makes an assumption that viewport size does not exceed the max gpu texture size. eg every pixel in the image is actually shown in a single image editor.

Technical test cases

  • Zoomed in (seeing individual pixels) with and without repeat
  • Zoomed out (skipping some pixels) with and without repeat
[D8234: Use DrawManager for Image/UV Editor](https://archive.blender.org/developer/D8234) uses a new drawing method for the image/uv editor. It has a limitation that huge images are resized to fit on the GPU. These max size depends on the used hardware typically the limitation is between 12k and 16k and the GL Texture limit setting in the user preference. In case the user uses a huge texture it is more likely that not all pixels are shown on the screen. We could create a sub-buffer with visible areas of the image and render those. This only needs to do in case the provided `GPUTexture` isn't sufficient. NOTE: This makes an assumption that viewport size does not exceed the max gpu texture size. eg every pixel in the image is actually shown in a single image editor. ## Technical test cases * Zoomed in (seeing individual pixels) with and without repeat * Zoomed out (skipping some pixels) with and without repeat
Jeroen Bakker self-assigned this 2020-08-25 21:01:39 +02:00
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Added subscriber: @slumber

Added subscriber: @slumber

Added subscriber: @brecht

Added subscriber: @brecht

If the subimages are created to fit the viewport, they need to be updated when panning and can't be shared between multiple image editors.

I think tiling the image would be a better solution, since it avoids those problems and doesn't require any special invalidation logic. Only visible tiles can be loaded. Possibly such a system could use ARB_sparse_texture, though I'm not sure that actually supports sizes bigger than 16k in practice.

In general, I think tiling and mipmaps are the right way to handle very high res images.

If the subimages are created to fit the viewport, they need to be updated when panning and can't be shared between multiple image editors. I think tiling the image would be a better solution, since it avoids those problems and doesn't require any special invalidation logic. Only visible tiles can be loaded. Possibly such a system could use `ARB_sparse_texture`, though I'm not sure that actually supports sizes bigger than 16k in practice. In general, I think tiling and mipmaps are the right way to handle very high res images.

Overall, I think efficient display of images > 16K is quite low priority, not something that we should spend much time on now or consider a blocker for committing the image editor / draw manager changes.

Overall, I think efficient display of images > 16K is quite low priority, not something that we should spend much time on now or consider a blocker for committing the image editor / draw manager changes.
Jeroen Bakker changed title from Support Huge Image Sizes. to Support Huge Image Sizes in image/uv editor 2020-08-27 14:34:22 +02:00
Jeroen Bakker removed their assignment 2020-09-15 15:28:55 +02:00
Author
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Jeroen Bakker self-assigned this 2022-02-14 15:35:26 +01:00
Author
Member

Fixed by bdd74e1e93

Fixed by bdd74e1e93
Sign in to join this conversation.
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
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#80113
No description provided.