Regression: Image Editor Texture Draw Stops Updating #96952

Open
opened 2022-04-01 15:55:45 +02:00 by Charzard4261 · 16 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79

Blender Version
Broken: version: 3.1.0 (probably introduced by {f663a1dc09}?)
Worked: 3.0

this was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues -- @lichtwerk)

Short description of error
Image on Image Editor -> Paint does not update when being drawn on at certain close view levels until the viewport is moved Blender Draw Bug.gif

Exact steps for others to reproduce the error
Load default scene
Switch to Texture Paint tab
Create new image
Zoom in 7 or 8 times (for reference I am using a scroll wheel that has steps)
Draw on the image
It will sometimes update fine, sometimes stop updating when it passes over a what looks like a UV boundry, that extends off the screen

See gif where I added a material to it
Sorry if this has already been reported, haven't been able to find a public bug tracker
image_paint_bug.blend

This is the file I (-- @lichtwerk) used on linux to bisect/reproduce on a 1920x1080 display (since this seems to depend on monitor/zoom etc):
image_paint_bug_repro.blend

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 **Blender Version** Broken: version: 3.1.0 (probably introduced by {f663a1dc09}?) Worked: 3.0 this was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues -- @lichtwerk) **Short description of error** Image on Image Editor -> Paint does not update when being drawn on at certain close view levels until the viewport is moved ![Blender Draw Bug.gif](https://archive.blender.org/developer/F12961907/Blender_Draw_Bug.gif) **Exact steps for others to reproduce the error** Load default scene Switch to Texture Paint tab Create new image Zoom in 7 or 8 times (for reference I am using a scroll wheel that has steps) Draw on the image It will sometimes update fine, sometimes stop updating when it passes over a what looks like a UV boundry, that extends off the screen See gif where I added a material to it Sorry if this has already been reported, haven't been able to find a public bug tracker [image_paint_bug.blend](https://archive.blender.org/developer/F12962159/image_paint_bug.blend) This is the file I (-- @lichtwerk) used on linux to bisect/reproduce on a 1920x1080 display (since this seems to depend on monitor/zoom etc): [image_paint_bug_repro.blend](https://archive.blender.org/developer/F13051310/image_paint_bug_repro.blend)
Author

Added subscriber: @Charzard4261

Added subscriber: @Charzard4261

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

I can confirm,
It depends a lot on zoom and position.
It's a regression.
Investigating...

I can confirm, It depends a lot on zoom and position. It's a regression. Investigating...

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Caused by f663a1dc09

Caused by f663a1dc09
Philipp Oeser changed title from Image Editor Texture Draw Stops Updating to Regression: Image Editor Texture Draw Stops Updating 2022-04-05 15:51:27 +02:00
Jeroen Bakker self-assigned this 2022-05-03 20:49:29 +02:00
Member

I suspect the EPSILON... Will test with equal.

I suspect the EPSILON... Will test with equal.
Member

This comment was removed by @Jeroen-Bakker

*This comment was removed by @Jeroen-Bakker*
Jeroen Bakker removed their assignment 2022-05-04 14:42:17 +02:00
Member

Although I am able to reproduce on mac mini, I am not on linux...
I have been narrowing this one down but feels like it is a driver issue.
The correct data is send to the driver, but it doesn't seem to be uploaded to the GPU....
Not sure what the solution might be. I will be looking at other bugs and might come back...

Although I am able to reproduce on mac mini, I am not on linux... I have been narrowing this one down but feels like it is a driver issue. The correct data is send to the driver, but it doesn't seem to be uploaded to the GPU.... Not sure what the solution might be. I will be looking at other bugs and might come back...
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Just noting that I have seen this in linux, too (was very hard to reproduce though)

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44
version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `rBc77597cd0e15`
Just noting that I have seen this in linux, too (was very hard to reproduce though) ``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `rBc77597cd0e15` ```
Member

If it is not caused by f663a1dc09, does it happen in 3.0? 2.93? Can this still be bisected? (would do it myself, but afraid my bisects would be very fragile, because it was so hard to repro on linux)

If it is not caused by f663a1dc09, does it happen in 3.0? 2.93? Can this still be bisected? (would do it myself, but afraid my bisects would be very fragile, because it was so hard to repro on linux)

It was also a little difficult to replicate on Windows.
I think it depends on the resolution of the monitor.
Once you find the position and scale, just save the file so it will be easy to repro again.

It was also a little difficult to replicate on Windows. I think it depends on the resolution of the monitor. Once you find the position and scale, just save the file so it will be easy to repro again.
Member

OK, so for me, this was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues)

This is the file I used on linux to bisect/reproduce on a 1920x1080 display:
image_paint_bug_repro.blend

OK, so for me, this was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues) This is the file I used on linux to bisect/reproduce on a 1920x1080 display: [image_paint_bug_repro.blend](https://archive.blender.org/developer/F13051310/image_paint_bug_repro.blend)
Member

Strange was retry-ing this issue and it seems to be resolution aware. I wasn't able to reproduce at all on 1440p, but did on 1080p.
Looking at the numbers I still didn't see any incorrect numbers.

1440p

&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.28068918, xmax 0.48047072, ymin 0.50000000, ymax 0.62912399 (0.199781537056x0.129123985767)
 *** START
&gpu_texture_region_to_update: xmin 0, xmax 1031, ymin 528, ymax 1194 (1031x666)
&tile_region_to_extract: xmin 287, xmax 492, ymin 512, ymax 645 (205x133)
 *** END
&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.50000000 (0.199781537056x0.102242797613)
 *** START
&gpu_texture_region_to_update: xmin 0, xmax 1031, ymin 0, ymax 528 (1031x528)
&tile_region_to_extract: xmin 287, xmax 492, ymin 408, ymax 512 (205x104)
 *** END
&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)

1080p

&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.30568603, xmax 0.45547372, ymin 0.50000000, ymax 0.59424454 (0.149787694216x0.094244539738)
 *** START
&gpu_texture_region_to_update: xmin 0, xmax 773, ymin 348, ymax 835 (773x487)
&tile_region_to_extract: xmin 313, xmax 466, ymin 512, ymax 609 (153x97)
 *** END
&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.50000000 (0.149787694216x0.067363411188)
 *** START
&gpu_texture_region_to_update: xmin 0, xmax 773, ymin 0, ymax 348 (773x348)
&tile_region_to_extract: xmin 313, xmax 466, ymin 444, ymax 512 (153x68)
 *** END
&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)
&info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926)
&changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000)
&changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000)

What could be a difference is that the height of the subtexture is an odd number.
Can anyone test if this makes a difference?
NOTE: this isn't the fix, just a test to suppress odd numbers.

diff --git a/source/blender/draw/engines/image/image_drawing_mode.hh b/source/blender/draw/engines/image/image_drawing_mode.hh
index 58abc02eb7c..b1bb451f32e 100644
--- a/source/blender/draw/engines/image/image_drawing_mode.hh
+++ b/source/blender/draw/engines/image/image_drawing_mode.hh
@@ -304,6 +304,8 @@ template<typename TextureMethod> class ScreenSpaceDrawingMode : public AbstractD
                  texture_height / BLI_rctf_size_y(&info.clipping_uv_bounds)),
             ceil((changed_overlapping_region_in_uv_space.ymax - info.clipping_uv_bounds.ymin) *
                  texture_height / BLI_rctf_size_y(&info.clipping_uv_bounds)));
+        gpu_texture_region_to_update.ymax &= ~1;
+        gpu_texture_region_to_update.ymin &= ~1;
         print_rcti_id(&gpu_texture_region_to_update);
         rcti tile_region_to_extract;
         BLI_rcti_init(
Strange was retry-ing this issue and it seems to be resolution aware. I wasn't able to reproduce at all on 1440p, but did on 1080p. Looking at the numbers I still didn't see any incorrect numbers. 1440p ``` &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.28068918, xmax 0.48047072, ymin 0.50000000, ymax 0.62912399 (0.199781537056x0.129123985767) *** START &gpu_texture_region_to_update: xmin 0, xmax 1031, ymin 528, ymax 1194 (1031x666) &tile_region_to_extract: xmin 287, xmax 492, ymin 512, ymax 645 (205x133) *** END &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.50000000 (0.199781537056x0.102242797613) *** START &gpu_texture_region_to_update: xmin 0, xmax 1031, ymin 0, ymax 528 (1031x528) &tile_region_to_extract: xmin 287, xmax 492, ymin 408, ymax 512 (205x104) *** END &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.28068918, xmax 0.48047072, ymin 0.39775720, ymax 0.62912399 (0.199781537056x0.231366783381) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) ``` 1080p ``` &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.30568603, xmax 0.45547372, ymin 0.50000000, ymax 0.59424454 (0.149787694216x0.094244539738) *** START &gpu_texture_region_to_update: xmin 0, xmax 773, ymin 348, ymax 835 (773x487) &tile_region_to_extract: xmin 313, xmax 466, ymin 512, ymax 609 (153x97) *** END &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.50000000, ymax 0.75000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.50000000 (0.149787694216x0.067363411188) *** START &gpu_texture_region_to_update: xmin 0, xmax 773, ymin 0, ymax 348 (773x348) &tile_region_to_extract: xmin 313, xmax 466, ymin 444, ymax 512 (153x68) *** END &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.25000000, ymax 0.50000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.25000000, xmax 0.50000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) &info.clipping_uv_bounds: xmin 0.30568603, xmax 0.45547372, ymin 0.43263659, ymax 0.59424454 (0.149787694216x0.161607950926) &changed_region_in_uv_space: xmin 0.00000000, xmax 0.25000000, ymin 0.00000000, ymax 0.25000000 (0.250000000000x0.250000000000) &changed_overlapping_region_in_uv_space: xmin 0.00000000, xmax 0.00000000, ymin 0.00000000, ymax 0.00000000 (0.000000000000x0.000000000000) ``` What could be a difference is that the height of the subtexture is an odd number. Can anyone test if this makes a difference? NOTE: this isn't the fix, just a test to suppress odd numbers. ``` diff --git a/source/blender/draw/engines/image/image_drawing_mode.hh b/source/blender/draw/engines/image/image_drawing_mode.hh index 58abc02eb7c..b1bb451f32e 100644 --- a/source/blender/draw/engines/image/image_drawing_mode.hh +++ b/source/blender/draw/engines/image/image_drawing_mode.hh @@ -304,6 +304,8 @@ template<typename TextureMethod> class ScreenSpaceDrawingMode : public AbstractD texture_height / BLI_rctf_size_y(&info.clipping_uv_bounds)), ceil((changed_overlapping_region_in_uv_space.ymax - info.clipping_uv_bounds.ymin) * texture_height / BLI_rctf_size_y(&info.clipping_uv_bounds))); + gpu_texture_region_to_update.ymax &= ~1; + gpu_texture_region_to_update.ymin &= ~1; print_rcti_id(&gpu_texture_region_to_update); rcti tile_region_to_extract; BLI_rcti_init( ```
Member

@Jeroen-Bakker : what difference should I see? I think I dont see any difference with those two lines....

@Jeroen-Bakker : what difference should I see? I *think* I dont see any difference with those two lines....
Philipp Oeser removed the
Interest
Sculpt, Paint & Texture
label 2023-02-10 09:11:31 +01:00
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
4 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#96952
No description provided.