User defined default color for images #107016

New Issue

Open

opened 2023-04-17 00:11:22 +02:00 by Daniel Salazar · 20 comments

Daniel Salazar commented 2023-04-17 00:11:22 +02:00

Member

Copy Link

The Default Color

If you map a texture in such a way that the image doesn't cover the entire model, the default color should show up.

Interestingly Blender does have a default color and as far as I know the only way to see it is to set an image texture extension mode to Clip. In that case, any UVs mapped outside of the image space get the color black (0.0, 0.0, 0.0). However this default color can not be currently defined by the user.

The Panic Color

The panic color for images AKA the bright magenta (1.0, 0.0, 1.0) appears when an image file has not been loaded correctly. It's meant as a visible warning for missing images.

The Problem With UDIMs

External texturing tools are able to skip UDIM tiles that do not contain any valuable information apart from the base color value.

Blender doesn't correctly support variable size UDIM sets and expects all UDIM sets to be of equal size.

The panic color currently shows up when dealing with variable size UDIM sets (color, normal, roughness, etc).

As a way of an extremely simplified example I've created the following file featuring a material with 2 UDIM sets, one for the Color and one for the Normal.

The problem appears because the 2 UDIMs are not conformed by the same number of tiles (images).

The Color UDIM with 3 tiles:

The Normal UDIM with 2 tiles:

The Normal UDIM delivers the panic color (magenta) in the non existing 1003 UDIM tile.

This is incorrect behavior since no image is really missing (there can not be a missing image if the tile does not exist in the first place).

The proposal

Allow for the default color to be user definable.

In the case of single image textures with extend mode set to clip, this color is applied to any UVs that exist outside of the (0.0, 0.0) - (1.0, 1.0) space.

Default color set to (0.28, 0.25, 0.2):

In the case of UDIMs this color is applied to any UVs that exist outside any tile.

Default color set to (0.5, 0.5, 1.0) AKA the bluish normal base color:

For existing tiles that have failed to load their image (missing images). The pink panic color is still expected.

Panic color to be expected since the tile exists but it's image was not found.

**The Default Color** _**If you map a texture in such a way that the image doesn't cover the entire model, the default color should show up.**_ Interestingly Blender does have a default color and as far as I know the only way to see it is to set an image texture extension mode to _Clip_. In that case, any UVs mapped outside of the image space get the color black (0.0, 0.0, 0.0). However this default color can not be currently defined by the user.  **The Panic Color** The panic color for images AKA the bright magenta (1.0, 0.0, 1.0) appears when an image file has not been loaded correctly. It's meant as a visible warning for **missing images**.  **The Problem With UDIMs** External texturing tools are able to _skip_ UDIM tiles that do not contain any valuable information apart from the base color value. Blender doesn't correctly support variable size UDIM sets and expects all UDIM sets to be of equal size. The panic color currently shows up when dealing with **variable size UDIM sets** (color, normal, roughness, etc). As a way of an extremely simplified example I've created the following file featuring a material with 2 UDIM sets, one for the Color and one for the Normal.  The problem appears because the 2 UDIMs are not conformed by the same number of tiles (images). The Color UDIM with 3 tiles:  The Normal UDIM with 2 tiles:  The Normal UDIM delivers the panic color (magenta) in the non existing 1003 UDIM tile. This is incorrect behavior since no image is really missing (there can not be a missing image if the tile does not exist in the first place).  **The proposal** Allow for the default color to be user definable. In the case of single image textures with extend mode set to clip, this color is applied to any UVs that exist outside of the (0.0, 0.0) - (1.0, 1.0) space. Default color set to (0.28, 0.25, 0.2):  In the case of UDIMs this color is applied to any UVs that exist outside any tile.  Default color set to (0.5, 0.5, 1.0) AKA the bluish normal base color:  For existing tiles that have failed to load their image (missing images). The pink panic color is **still expected**.  Panic color to be expected since the tile **exists** but it's image was not found. 

image.png

110 KiB

image.png

412 KiB

image.png

120 KiB

image.png

99 KiB

image.png

98 KiB

image.png

89 KiB

image.png

148 KiB

image.png

98 KiB

image.png

62 KiB

image.png

559 KiB

👍 1

Daniel Salazar added the

Type

Design

label 2023-04-17 00:11:22 +02:00

Daniel Salazar changed title from User defined default color for images to WIP: User defined default color for images 2023-04-17 00:11:35 +02:00

Jeroen Bakker added this to the Sculpt, Paint & Texture project 2023-04-24 15:55:13 +02:00

Jeroen Bakker commented 2023-04-24 16:01:26 +02:00

Member

Copy Link

Think is a good startingpoint.
Just for clarity I think that the 'default color' is stored inside the Image data-block not in the node itself. The node will read it from the Image data-block. Not sure if it is important to show this property at all inside the shading node as it might confuse some users.

Perhaps we should only use this color for missing udim textures. What should the default color be? Pink, Black, ...
We already have a default color for generated images. So we need to check if we want to use the same property or use a different. I think it is better to have a new property to store this color as it will have a different description.

what do you think?

Think is a good startingpoint. Just for clarity I think that the 'default color' is stored inside the Image data-block not in the node itself. The node will read it from the Image data-block. Not sure if it is important to show this property at all inside the shading node as it might confuse some users. Perhaps we should only use this color for missing udim textures. What should the default color be? Pink, Black, ... We already have a default color for generated images. So we need to check if we want to use the same property or use a different. I think it is better to have a new property to store this color as it will have a different description. what do you think?

🚀 1

Daniel Salazar commented 2023-04-24 20:33:45 +02:00

Author

Member

Copy Link

Perhaps we should only use this color for missing udim textures. What should the default color be? Pink, Black, ...

Can't think of any default color that makes sense for all cases. I'd say pink is a good default color since it is easy to spot that there are "missing" tiles. Also it's what happens right now anyway so it would introduce no change to existing scenes.

Other than that, Node Wrangler could be updated to auto-load PBR textures with better default colors based on the texture type (roughness, normal, etc).

> Perhaps we should only use this color for missing udim textures. What should the default color be? Pink, Black, ... Can't think of any default color that makes sense for all cases. I'd say pink is a good default color since it is easy to spot that there are "missing" tiles. Also it's what happens right now anyway so it would introduce no change to existing scenes. Other than that, Node Wrangler could be updated to auto-load PBR textures with better default colors based on the texture type (roughness, normal, etc).

Paul Kotelevets commented 2023-05-02 16:48:13 +02:00

Copy Link

I think saturated magenta has been chosen for error detection because it is nice alerting color which is quite rare in the real word.
For example, if you render with missing textures, it is easy to detect the resulting cyberpunk vibes because of a missing textures.

Can you please clarify - why it should deliver bluish color, while it does it direct job - showing that something is missing for a proper error handling (a missing udim in this case)?

I think saturated magenta has been chosen for error detection because it is nice alerting color which is quite rare in the real word. For example, if you render with missing textures, it is easy to detect the resulting cyberpunk vibes because of a missing textures. Can you please clarify - why it should deliver bluish color, while it does it direct job - showing that something is missing for a proper error handling (a missing udim in this case)?

Daniel Salazar commented 2023-05-02 22:30:24 +02:00

Author

Member

Copy Link

I think saturated magenta has been chosen for error detection because it is nice alerting color which is quite rare in the real word.
For example, if you render with missing textures, it is easy to detect the resulting cyberpunk vibes because of a missing textures.

Can you please clarify - why it should deliver bluish color, while it does it direct job - showing that something is missing for a proper error handling (a missing udim in this case)?

The key to understand the problem is those UDIM tiles are missing on purpose. Certain production texturing tools can export variable size UDIM sets. Blender doesn't allow this and expects all UDIM sets to be of equal size, creating magenta errors :)

> I think saturated magenta has been chosen for error detection because it is nice alerting color which is quite rare in the real word. > For example, if you render with missing textures, it is easy to detect the resulting cyberpunk vibes because of a missing textures. > > Can you please clarify - why it should deliver bluish color, while it does it direct job - showing that something is missing for a proper error handling (a missing udim in this case)? The key to understand the problem is those UDIM tiles are missing on purpose. Certain production texturing tools can export variable size UDIM sets. Blender doesn't allow this and expects all UDIM sets to be of equal size, creating magenta errors :)

Daniel Salazar commented 2023-05-03 06:16:28 +02:00

Author

Member

Copy Link

Updated the proposal to cover some concerns by @1D_Inc as well as my own findings.

Updated the proposal to cover some concerns by @1D_Inc as well as my own findings.

Daniel Salazar changed title from WIP: User defined default color for images to WIP: User defined background color for images 2023-05-03 06:29:53 +02:00

Daniel Salazar changed title from WIP: User defined background color for images to WIP: User defined base color for images 2023-05-03 06:51:37 +02:00

Jesse Yurkovich commented 2023-05-03 07:10:54 +02:00

Member

Copy Link

I find the UDIM example rather strange. A few questions / comments:

• There's geometry in tile 1003, why is the texturing tool not producing a texture for it?
• The texture shows as missing because Blender is looking up the UV coords of that geometry and finding no texture at that location; it's not really because different sized UDIM sets are not supported. If you feed a different set of coordinates into your Normal Map then the 2-UDIM case will be fine for example.
• Is there another Renderer out there that allows such a missing value to be set and used for Rendering?
• This will require quite a bit of plumbing internally. Is that worth it? Why not do the following: For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. Or said another way, this is almost like the generated texture case.

I find the UDIM example rather strange. A few questions / comments: - There's geometry in tile 1003, why is the texturing tool not producing a texture for it? - The texture shows as missing because Blender is looking up the UV coords of that geometry and finding no texture at that location; it's not really because different sized UDIM sets are not supported. If you feed a different set of coordinates into your Normal Map then the 2-UDIM case will be fine for example. - Is there another Renderer out there that allows such a missing value to be set and used for Rendering? - This will require quite a bit of plumbing internally. Is that worth it? Why not do the following: For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. Or said another way, this is almost like the generated texture case.

Daniel Salazar commented 2023-05-03 07:35:24 +02:00

Author

Member

Copy Link

I find the UDIM example rather strange. A few questions / comments:

• There's geometry in tile 1003, why is the texturing tool not producing a texture for it?
• The texture shows as missing because Blender is looking up the UV coords of that geometry and finding no texture at that location; it's not really because different sized UDIM sets are not supported. If you feed a different set of coordinates into your Normal Map then the 2-UDIM case will be fine for example.
• Is there another Renderer out there that allows such a missing value to be set and used for Rendering?
• This will require quite a bit of plumbing internally. Is that worth it? Why not do the following: For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. Or said another way, this is almost like the generated texture case.

Unfortunately real world production models do come like this. And in some cases it's not about 2 or 3 tiles but hundreds of tiles per set with random ones missing on each set (deemed unneeded). So this is more about being able to load and render files exported from other software correctly.

What you mentioned about generated textures is interesting and yet another way of looking at this.

> I find the UDIM example rather strange. A few questions / comments: > - There's geometry in tile 1003, why is the texturing tool not producing a texture for it? > - The texture shows as missing because Blender is looking up the UV coords of that geometry and finding no texture at that location; it's not really because different sized UDIM sets are not supported. If you feed a different set of coordinates into your Normal Map then the 2-UDIM case will be fine for example. > - Is there another Renderer out there that allows such a missing value to be set and used for Rendering? > - This will require quite a bit of plumbing internally. Is that worth it? Why not do the following: For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. Or said another way, this is almost like the generated texture case. > Unfortunately real world production models do come like this. And in some cases it's not about 2 or 3 tiles but hundreds of tiles per set with random ones missing on each set (deemed unneeded). So this is more about being able to load and render files exported from other software correctly. What you mentioned about generated textures is interesting and yet another way of looking at this.

Jesse Yurkovich commented 2023-05-03 07:40:23 +02:00

Member

Copy Link

But again, if there's geometry in those "missing" tiles, you providing a default value is still going to result in a "wrong" render won't it? How are these models expected to be used? Do they expect the users to guess that they need to use Black instead of White for their missing "mask" textures? And they expect people to use a default normal color for the missing normal maps?

But again, if there's geometry in those "missing" tiles, you providing a default value is still going to result in a "wrong" render won't it? How are these models expected to be used? Do they expect the users to guess that they need to use Black instead of White for their missing "mask" textures? And they expect people to use a default normal color for the missing normal maps?

Daniel Salazar commented 2023-05-03 09:15:43 +02:00

Author

Member

Copy Link

But again, if there's geometry in those "missing" tiles, you providing a default value is still going to result in a "wrong" render won't it? How are these models expected to be used? Do they expect the users to guess that they need to use Black instead of White for their missing "mask" textures? And they expect people to use a default normal color for the missing normal maps?

I've renamed the proposal to user defined base color. Based on your comments I think the word default is confusing.

And yes, that's exactly how it works! The mask is probably the greatest example of all. Imagine a model with 300 UDIM tiles and now you want to add a logo decal somewhere. Probably only one or 2 of the UDIM tiles is going to be used for the white mask. The rest will be "missing" and rely on the user defined default color of black.

> But again, if there's geometry in those "missing" tiles, you providing a default value is still going to result in a "wrong" render won't it? How are these models expected to be used? Do they expect the users to guess that they need to use Black instead of White for their missing "mask" textures? And they expect people to use a default normal color for the missing normal maps? I've renamed the proposal to _user defined base color_. Based on your comments I think the word default is confusing. And yes, that's exactly how it works! The mask is probably the greatest example of all. Imagine a model with 300 UDIM tiles and now you want to add a logo decal somewhere. Probably only one or 2 of the UDIM tiles is going to be used for the white mask. The rest will be "missing" and rely on the user defined default color of black.

Paul Kotelevets commented 2023-05-03 09:31:21 +02:00

Copy Link

For tile 1003, click new tile and create a small 4x4 Generated Solid color texture.

Technically, UDIM tiles has fill tile option, but such empty tiles are lost after syncronization with texture folder.

> For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. Technically, UDIM tiles has fill tile option, but such empty tiles are lost after syncronization with texture folder.

Iliya Katushenock commented 2023-05-03 12:56:26 +02:00

Member

Copy Link

Why this is WIP, this isn't pull request i guess?

Why this is WIP, this isn't pull request i guess?

Daniel Salazar changed title from WIP: User defined base color for images to WIP: User defined default color for images 2023-05-04 00:38:49 +02:00

Daniel Salazar commented 2023-05-04 00:47:11 +02:00

Author

Member

Copy Link

I've rolled back the naming to Default Color since I've confirmed this is what artists with industry experience expect.

I've rolled back the naming to Default Color since I've confirmed this is what artists with industry experience expect.

Daniel Salazar changed title from WIP: User defined default color for images to User defined default color for images 2023-05-04 00:48:10 +02:00

Daniel Salazar commented 2023-05-04 06:02:11 +02:00

Author

Member

Copy Link

Edited the proposal to show the use case of Default Color for single images.

Edited the proposal to show the use case of Default Color for single images.

Jeroen Bakker commented 2023-05-04 08:17:06 +02:00

Member

Copy Link

For tile 1003, click new tile and create a small 4x4 Generated Solid color texture.

Technically, UDIM tiles has fill tile option, but such empty tiles are lost after syncronization with texture folder.

There is a benefit that this proposal adds that unused tiles don't occupy space. the fill tile option would create a new tile and adds some overhead, even when the tile is 1x1 Eevee would still need to go over this tile to match the UV coordinates. When the tile doesn't exist it adds less overhead. IIRC Cycles does something similar.

Note that the more complex a model gets the more likely it will become to have missing UDIM tiles. For example when using multi material models where a feature is only needed for a specific material/part of the model. These models could be optimized to use less memory.

Looking at example base human meshes that are being used by VFX movies. They already use 50-100 UDIM tiles. Now when the model has some cybernetic body parts, that for some reasons is added to the base mesh, which uses a metallic UDIM texture, you only want to specify the tiles that only covers those parts.

> > For tile 1003, click new tile and create a small 4x4 Generated Solid color texture. > > Technically, UDIM tiles has fill tile option, but such empty tiles are lost after syncronization with texture folder. There is a benefit that this proposal adds that unused tiles don't occupy space. the fill tile option would create a new tile and adds some overhead, even when the tile is 1x1 Eevee would still need to go over this tile to match the UV coordinates. When the tile doesn't exist it adds less overhead. IIRC Cycles does something similar. Note that the more complex a model gets the more likely it will become to have missing UDIM tiles. For example when using multi material models where a feature is only needed for a specific material/part of the model. These models could be optimized to use less memory. Looking at example base human meshes that are being used by VFX movies. They already use 50-100 UDIM tiles. Now when the model has some cybernetic body parts, that for some reasons is added to the base mesh, which uses a metallic UDIM texture, you only want to specify the tiles that only covers those parts.

❤️ 2

Paul Kotelevets commented 2023-05-05 13:11:26 +02:00

Copy Link

you only want to specify the tiles that only covers those parts.

Yes, the point behind the idea if a having missing tiles support is clear, the examples are good.
Just want to mention that having the ability to quickly detect missing tiles from model's visual appearance is important for model's debugging, for example, before export for using in other applications or UV packing/repacking process.

Something like a checkbox that globally but temporarily enables magenta for missing tiles so you can quickly analyse the model (for example, to distinguish which part of it is solved by texture and which part by image background color - to make sure you provided all the necessary textures) could work well.

> you only want to specify the tiles that only covers those parts. Yes, the point behind the idea if a having missing tiles support is clear, the examples are good. Just want to mention that having the ability to quickly detect missing tiles from model's visual appearance is important for model's debugging, for example, before export for using in other applications or UV packing/repacking process. Something like a checkbox that globally but temporarily enables magenta for missing tiles so you can quickly analyse the model (for example, to distinguish which part of it is solved by texture and which part by image background color - to make sure you provided all the necessary textures) could work well.

Daniel Salazar commented 2023-05-05 22:41:57 +02:00

Author

Member

Copy Link

you only want to specify the tiles that only covers those parts.

Yes, the point behind the idea if a having missing tiles support is clear, the examples are good.
Just want to mention that having the ability to quickly detect missing tiles from model's visual appearance is important for model's debugging, for example, before export for using in other applications or UV packing/repacking process.

Something like a checkbox that globally but temporarily enables magenta for missing tiles so you can quickly analyse the model (for example, to distinguish which part of it is solved by texture and which part by image background color - to make sure you provided all the necessary textures) could work well.

The images are not missing. Also you can change the default color to magenta if you want to check for that.

> > you only want to specify the tiles that only covers those parts. > > Yes, the point behind the idea if a having missing tiles support is clear, the examples are good. > Just want to mention that having the ability to quickly detect missing tiles from model's visual appearance is important for model's debugging, for example, before export for using in other applications or UV packing/repacking process. > > Something like a checkbox that globally but temporarily enables magenta for missing tiles so you can quickly analyse the model (for example, to distinguish which part of it is solved by texture and which part by image background color - to make sure you provided all the necessary textures) could work well. > The images **are not missing**. Also you can change the default color to magenta if you want to check for that.

Jesse Yurkovich commented 2023-05-05 23:11:10 +02:00

Member

Copy Link

You only know they're missing because you have a native format (like the .blend file) which actively remembers how many tiles there should be.

When you receive assets by other means -- either as a random .zip or USD archive or as a MaterialX material -- those formats don't tell you how many tiles should be there. All you are given is that virtual path.

e.g. A USD asset will only have color.<UDIM>.png. There's nothing in the format or specification about how many files that path represents and should be found on disk.

You only know they're missing because you have a native format (like the .blend file) which actively remembers how many tiles there should be. When you receive assets by other means -- either as a random .zip or USD archive or as a MaterialX material -- those formats don't tell you how many tiles _should_ be there. All you are given is that virtual path. e.g. A USD asset will only have `color.<UDIM>.png`. There's nothing in the format or specification about how many files that path represents and should be found on disk.

Daniel Salazar commented 2023-05-05 23:31:25 +02:00

Author

Member

Copy Link

You only know they're missing because you have a native format (like the .blend file) which actively remembers how many tiles there should be.

When you receive assets by other means -- either as a random .zip or USD archive or as a MaterialX material -- those formats don't tell you how many tiles should be there. All you are given is that virtual path.

e.g. A USD asset will only have color.<UDIM>.png. There's nothing in the format or specification about how many files that path represents and should be found on disk.

The pink color is meant for textures that have gone missing. Blender can not possible know if a texture was missing from the start. Same for regular (non UDIM) textures. What pink needs to help detect is when a model that is already loaded has broken an existing path. If a texture has loaded once, it will be detected when missing.This is already covered in the proposal.

To help detect an irregular number of UDIMs we need a tile counter visible. I will add that to the proposal or create a PR myself.

> You only know they're missing because you have a native format (like the .blend file) which actively remembers how many tiles there should be. > > When you receive assets by other means -- either as a random .zip or USD archive or as a MaterialX material -- those formats don't tell you how many tiles _should_ be there. All you are given is that virtual path. > > e.g. A USD asset will only have `color.<UDIM>.png`. There's nothing in the format or specification about how many files that path represents and should be found on disk. The pink color is meant for textures that have **gone missing**. Blender can not possible know if a texture was missing from the start. Same for regular (non UDIM) textures. What pink needs to help detect is when a model that is already loaded has broken an existing path. If a texture has **loaded once**, it will be detected when missing.This is already covered in the proposal. To help detect an irregular number of UDIMs we need a tile counter visible. I will add that to the proposal or create a PR myself.

Paul Kotelevets commented 2023-05-06 18:08:47 +02:00

Copy Link

To help detect an irregular number of UDIMs we need a tile counter visible. I will add that to the proposal or create a PR myself.

That would be awesome. Thanks)

> To help detect an irregular number of UDIMs we need a tile counter visible. I will add that to the proposal or create a PR myself. That would be awesome. Thanks)

Julien Kaspar commented 2023-05-10 11:10:59 +02:00

Member

Copy Link

@Sergey Pointed out that this could be implemented by the Render & Cycles, Eevee & Viewport or even Core modules. This is not really a Sculpt, Paint & Texture task.
I'll tag them here for this issue.

@Sergey Pointed out that this could be implemented by the Render & Cycles, Eevee & Viewport or even Core modules. This is not really a Sculpt, Paint & Texture task. I'll tag them here for this issue.

Julien Kaspar added the

Module

Render & Cycles

Interest

Core

Interest

EEVEE & Viewport

Interest

Sculpt, Paint & Texture

labels 2023-05-10 11:11:29 +02:00

Julien Kaspar removed this from the Sculpt, Paint & Texture project 2023-05-10 11:11:34 +02:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

brush-assets-project

blender-v4.1-release

blender-v3.3-release

blender-v3.6-release

universal-scene-description

blender-v3.6-temp_wmoss_animrig_public

temp-sculpt-dyntopo

gpencil-next

anim/animation-id-113594

blender-v4.0-release

blender-projects-basics

bridge-curves

sculpt-blender

asset-browser-frontend-split

asset-shelf

tmp-usd-python-mtl

tmp-usd-3.6

blender-v3.5-release

blender-v2.93-release

realtime-clock

sculpt-dev

bevelv2

xr-dev

v4.1.1

v3.6.11

v3.3.18

v4.1.0

v3.3.17

v3.6.10

v3.6.9

v3.3.16

v3.6.8

v3.6.7

v3.3.14

v4.0.2

v4.0.1

v4.0.0

v3.6.5

v3.3.12

v3.6.4

v3.6.3

v3.3.11

v3.6.2

v3.3.10

v3.6.1

v3.3.9

v3.6.0

v3.3.8

v3.3.7

v2.93.18

v3.5.1

v3.3.6

v2.93.17

v3.5.0

v2.93.16

v3.3.5

v3.3.4

v2.93.15

v2.93.14

v3.3.3

v2.93.13

v2.93.12

v3.4.1

v3.3.2

v3.4.0

v3.3.1

v2.93.11

v3.3.0

v3.2.2

v2.93.10

v3.2.1

v3.2.0

v2.83.20

v2.93.9

v3.1.2

v3.1.1

v3.1.0

v2.83.19

v2.93.8

v3.0.1

v2.93.7

v3.0.0

v2.93.6

v2.93.5

v2.83.18

v2.93.4

v2.93.3

v2.83.17

v2.93.2

v2.93.1

v2.83.16

v2.93.0

v2.83.15

v2.83.14

v2.83.13

v2.92.0

v2.83.12

v2.91.2

v2.83.10

v2.91.0

v2.83.9

v2.83.8

v2.83.7

v2.90.1

v2.83.6.1

v2.83.6

v2.90.0

v2.83.5

v2.83.4

v2.83.3

v2.83.2

v2.83.1

v2.83

v2.82a

v2.82

v2.81a

v2.81

v2.80

v2.80-rc3

v2.80-rc2

v2.80-rc1

v2.79b

v2.79a

v2.79

v2.79-rc2

v2.79-rc1

v2.78c

v2.78b

v2.78a

v2.78

v2.78-rc2

v2.78-rc1

v2.77a

v2.77

v2.77-rc2

v2.77-rc1

v2.76b

v2.76a

v2.76

v2.76-rc3

v2.76-rc2

v2.76-rc1

v2.75a

v2.75

v2.75-rc2

v2.75-rc1

v2.74

v2.74-rc4

v2.74-rc3

v2.74-rc2

v2.74-rc1

v2.73a

v2.73

v2.73-rc1

v2.72b

2.72b

v2.72a

v2.72

v2.72-rc1

v2.71

v2.71-rc2

v2.71-rc1

v2.70a

v2.70

v2.70-rc2

v2.70-rc

v2.69

v2.68a

v2.68

v2.67b

v2.67a

v2.67

v2.66a

v2.66

v2.65a

v2.65

v2.64a

v2.64

v2.63a

v2.63

v2.61

v2.60a

v2.60

v2.59

v2.58a

v2.58

v2.57b

v2.57a

v2.57

v2.56a

v2.56

v2.55

v2.54

v2.53

v2.52

v2.51

v2.50

v2.49b

v2.49a

v2.49

v2.48a

v2.48

v2.47

v2.46

v2.45

v2.44

v2.43

v2.42a

v2.42

v2.41

v2.40

v2.37a

v2.37

v2.36

v2.35a

v2.35

v2.34

v2.33a

v2.33

v2.32

v2.31a

v2.31

v2.30

v2.28c

v2.28a

v2.28

v2.27

v2.26

v2.25

Labels

Clear labels   

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

This issue affects/is about backward or forward 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

Issues relating to Wayland windowing support.

  

Interest

Workbench

  

Interest: X11

Issues relating to Xorg/X11 support.

  

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

Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  

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 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

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

6 Participants

Notifications

Subscribe

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#107016

No description provided.