Viewport Render (and Render Animation) color looks completely off from the Viewport #73956

New Issue

Open

opened 2020-02-18 01:59:28 +01:00 by Gabriel Moro · 29 comments

Gabriel Moro commented 2020-02-18 01:59:28 +01:00

Copy Link

System Information
Operating system: Darwin-19.0.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.2.24

Blender Version
Broken: version: 2.82 (sub 6), branch: master, commit date: 2020-02-11 14:45, hash: c939b4df18

Short description of error
Rendering the viewport animation gives a very different result from the actual viewport.
(Also: Viewport Anti-Aliasing isn't taken into consideration on the Viewport Render).

The problem is more noticeable when the Viewport Shading is set to "Flat", even though it also shows in "Studio". It delivers very dull colors with less contrast and a blue-ish tone.
Changing between Cycles and Eevee doesn't affect the Viewport Render (from my tests).

flat:
--	--

Exact steps for others to reproduce the error

• Open attached file.
• Go to View -> Viewport Render Image
  Viewport Colors.blend

**System Information** Operating system: Darwin-19.0.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.2.24 **Blender Version** Broken: version: 2.82 (sub 6), branch: master, commit date: 2020-02-11 14:45, hash: `c939b4df18` **Short description of error** Rendering the viewport animation gives a very different result from the actual viewport. (Also: Viewport Anti-Aliasing isn't taken into consideration on the Viewport Render). || | -- | -- | The problem is more noticeable when the Viewport Shading is set to "Flat", even though it also shows in "Studio". It delivers very dull colors with less contrast and a blue-ish tone. Changing between Cycles and Eevee doesn't affect the Viewport Render (from my tests). || | -- | -- | flat: || | -- | -- | **Exact steps for others to reproduce the error** - Open attached file. - Go to View -> Viewport Render Image [Viewport Colors.blend](https://archive.blender.org/developer/F8348132/Viewport_Colors.blend)

Gabriel Moro commented 2020-02-18 01:59:28 +01:00

Author

Copy Link

Added subscriber: @GabrielMoro

Added subscriber: @GabrielMoro

blender-admin commented 2020-02-18 01:59:28 +01:00

Copy Link

#77291 was marked as duplicate of this issue

#77291 was marked as duplicate of this issue

blender-admin commented 2020-02-18 01:59:28 +01:00

Copy Link

#75544 was marked as duplicate of this issue

#75544 was marked as duplicate of this issue

Ankit Meel commented 2020-02-18 05:56:41 +01:00

Member

Copy Link

Added subscriber: @ankitm

Added subscriber: @ankitm

Ankit Meel commented 2020-02-18 05:56:41 +01:00

Member

Copy Link

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Ankit Meel commented 2020-02-18 05:56:41 +01:00

Member

Copy Link

if you're rendering by Eevee, it would be different from what cycles would render. I am not aware of what viewport uses, but try changing render engine. Also, is possible add a blender file to help debug the issue.

if you're rendering by Eevee, it would be different from what cycles would render. I am not aware of what viewport uses, but try changing render engine. Also, is possible add a blender file to help debug the issue.

Gabriel Moro commented 2020-02-18 17:57:12 +01:00

Author

Copy Link

I see now that the problem is more noticeable when the Viewport Shading is set to "Flat", even though it also shows in "Studio". It delivers very dull colors with less contrast and a blue-ish tone.
Changing between Cycles and Eevee doesn't affect the Viewport Render (from my tests).

Viewport Colors.blend

I see now that the problem is more noticeable when the Viewport Shading is set to "Flat", even though it also shows in "Studio". It delivers very dull colors with less contrast and a blue-ish tone. Changing between Cycles and Eevee doesn't affect the Viewport Render (from my tests).     [Viewport Colors.blend](https://archive.blender.org/developer/F8348132/Viewport_Colors.blend)

Alex commented 2020-02-18 18:59:45 +01:00

Copy Link

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

Alex commented 2020-02-18 18:59:45 +01:00

Copy Link

It looks like Viewport Render Image uses the same Color Management as Eevee and Cycles while viewport itself in Workbench mode seems to always work in Standard View Transform. Try setting Color Management – View Transform to Standard instead of Filmic in Render Properties, it should even work after you hit Viewport Render Image.

It looks like Viewport Render Image uses the same Color Management as Eevee and Cycles while viewport itself in Workbench mode seems to always work in Standard View Transform. Try setting Color Management – View Transform to Standard instead of Filmic in Render Properties, it should even work after you hit Viewport Render Image.

Ankit Meel commented 2020-02-18 19:06:13 +01:00

Member

Copy Link

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'

Gabriel Moro commented 2020-02-19 19:45:29 +01:00

Author

Copy Link

Changing it to View Transform Standard fixes the color problem! Perhaps a small tweak to set it automatically when rendering the Viewport would fix it for everyone else?
Could the fact that the viewport anti-aliasing is ignored when rendering this way also be fixed? In this case, for example, I'm rendering my walk cycle by using the viewport, but the hair looks bad because anti-aliasing isn't been taken into consideration.

Thanks again for the info on the color!

Changing it to View Transform Standard fixes the color problem! Perhaps a small tweak to set it automatically when rendering the Viewport would fix it for everyone else? Could the fact that the viewport anti-aliasing is ignored when rendering this way also be fixed? In this case, for example, I'm rendering my walk cycle by using the viewport, but the hair looks bad because anti-aliasing isn't been taken into consideration. Thanks again for the info on the color!

Germano Cavalcante commented 2020-02-20 14:13:37 +01:00

Member

Copy Link

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

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

Jeroen Bakker commented 2020-03-13 16:23:01 +01:00

Member

Copy Link

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented 2020-03-13 16:23:01 +01:00

Member

Copy Link

In solid mode we don't use the view transform as that is setup for rendering. When rendering an image from the viewport the image editor uses the view transform. This works as designed.
The work around described in this ticket is not correct as it changes the scene setting, and that is not what you want when you are rendering.

Best option would be that the render result known if it needs to display the view transform or not. Currently it does not have this ability. I will file it as a known issue.

In solid mode we don't use the view transform as that is setup for rendering. When rendering an image from the viewport the image editor uses the view transform. This works as designed. The work around described in this ticket is not correct as it changes the scene setting, and that is not what you want when you are rendering. Best option would be that the render result known if it needs to display the view transform or not. Currently it does not have this ability. I will file it as a known issue.

Ankit Meel commented 2020-04-09 07:22:57 +02:00

Member

Copy Link

Added subscriber: @ThamQiLun

Added subscriber: @ThamQiLun

Richard Antalik commented 2020-06-04 11:18:25 +02:00

Member

Copy Link

Added subscriber: @istoltoto

Added subscriber: @istoltoto

pistol ioan commented 2020-06-04 12:19:39 +02:00

Copy Link

workaround solution

Hey, thank you for adding me here.

One of our team member did a script to workaround this problem.

Instead of using Viewport Render Animation, the script will use Viewport Render Image and move to render the next frame automaticly.
The script have no stop button and is not working with Esc either, so you either leave it to finish till the end of timeline, or you shoutdown the Blender.

Credit to: Jefferson Rausseo

render_viewport_alternative.py

**workaround solution** Hey, thank you for adding me here. One of our team member did a script to workaround this problem. Instead of using Viewport Render Animation, the script will use Viewport Render Image and move to render the next frame automaticly. The script have no stop button and is not working with Esc either, so you either leave it to finish till the end of timeline, or you shoutdown the Blender. Credit to: Jefferson Rausseo  [render_viewport_alternative.py](https://archive.blender.org/developer/F8576264/render_viewport_alternative.py)

Daniel Calderón commented 2020-06-25 20:34:43 +02:00

Copy Link

Added subscriber: @xdanic

Added subscriber: @xdanic

Jaro commented 2020-09-28 18:39:26 +02:00

Copy Link

Added subscriber: @JustRed

Added subscriber: @JustRed

Jaro commented 2020-09-28 18:39:26 +02:00

Copy Link

oh, almost reported same issue.
This is rather painful as people do be using filmic

oh, almost reported same issue. This is rather painful as people do be using filmic

Philipp Oeser removed the

Interest

EEVEE & Viewport

label 2023-02-09 15:15:09 +01:00

Richard Antalik referenced this issue 2023-09-27 03:52:21 +02:00

Blender taking wrong background color for View - > Viewport Render Image #112928

ManBlender commented 2023-09-27 09:35:03 +02:00

Copy Link

It's looks like alpha transparency layer on whole output from tool setting bar, where is this upp screen on viewport and transparent. Then on whole image it's look darker, but not soo similar..

It's looks like alpha transparency layer on whole output from *tool setting* bar, where is this upp screen on viewport and transparent. Then on whole image it's look darker, but not soo similar..

ManBlender commented 2023-09-27 09:51:39 +02:00

Copy Link

@istoltoto the render_viewport_alternative.py not changing for me the background, this same problem when white converted do gray.
The script working really hard btw.. why?

The problem can be related with Hue parameter. When white is, then any changes not saving this parameter for color pickup, but default is from gray viewport. Then when B taking to viewport can have this same issue.. soo maybe not alpha, but hue..

@istoltoto the render_viewport_alternative.py not changing for me the background, this same problem when white converted do gray. The script working really hard btw.. why? The problem can be related with Hue parameter. When white is, then any changes not saving this parameter for color pickup, but default is from gray viewport. Then when B taking to viewport can have this same issue.. soo maybe not alpha, but hue..

ManBlender commented 2023-11-06 20:15:43 +01:00

Copy Link

@iss @mano-wii Is possible to change priority for this issue? It's more like normal.. it's touching important area of work of this software to save result of work. I'm still combining some crazy way as print screen to paint, then cropping area, etc.. then of course broken resolution sizes, etc. around some interoperability with process, etc.

@iss @mano-wii Is possible to change priority for this issue? It's more like normal.. it's touching important area of work of this software to save result of work. I'm still combining some crazy way as print screen to paint, then cropping area, etc.. then of course broken resolution sizes, etc. around some interoperability with process, etc.

Richard Antalik commented 2023-11-07 05:51:14 +01:00

Member

Copy Link

@ManBlender This is up to viewport developers. I can't tell whether it can be prioritized.

@ManBlender This is up to viewport developers. I can't tell whether it can be prioritized.

😕 1

ManBlender commented 2024-04-22 17:23:29 +02:00

Copy Link

Can be related due class in blender around operating internal objects to save.
#120929 (comment)

Can be related due class in blender around operating internal objects to save. https://projects.blender.org/blender/blender/issues/120929#issuecomment-1173000

ManBlender commented 2024-04-22 23:06:37 +02:00

Copy Link

Ok, I think I found solution:

import bpy

bpy.context.scene.view_settings.view_transform = 'Standard'
bpy.context.scene.view_settings.look = 'None'
bpy.context.scene.display_settings.display_device = 'sRGB'

After this state in Blender is changed correctly.

Soo.. the problem is 'sRGB' and upper setting must be saved in default in required files.
Is this regression due changes in options?

Ok, I think I found solution: ``` import bpy bpy.context.scene.view_settings.view_transform = 'Standard' bpy.context.scene.view_settings.look = 'None' bpy.context.scene.display_settings.display_device = 'sRGB' ``` After this state in Blender is changed correctly. Soo.. the problem is 'sRGB' and upper setting must be saved in default in required files. Is this regression due changes in options?

ManBlender commented 2024-04-22 23:08:15 +02:00

Copy Link

@mano-wii Can You check RGBA ?
https://projects.blender.org/blender/blender/src/branch/main/source/blender/nodes/composite/nodes/node_composite_rgb.cc

@mano-wii Can You check RGBA ? https://projects.blender.org/blender/blender/src/branch/main/source/blender/nodes/composite/nodes/node_composite_rgb.cc

Jeroen Bakker commented 2024-04-23 06:49:38 +02:00

Member

Copy Link

When setting the color management to srgb/standard you match the color management profile of the overlay and therefore you don't see the issue, but in this case you're not able to use the color management you want to use.

Priority of this issue and classification is correct for this kind of issue.

It isn't a regression as this is part of the color management pipeline (https://developer.blender.org/docs/features/gpu/viewports/color_management/#known-issues). Viewport can have 2 color management profiles active. One for the render engine (which is controlled by the color management panel) and one for the overlays (overlay engine is fixed to sRGB/Standard).

There is no known solution how to solve this without introducing other issues. One trick I remember we added was to hide the overlays before exporting.

Not sure why you're referring to the source code of the compositor as that is done in a linear space and uses a fixed conversion matrix.

When setting the color management to srgb/standard you match the color management profile of the overlay and therefore you don't see the issue, but in this case you're not able to use the color management you want to use. Priority of this issue and classification is correct for this kind of issue. It isn't a regression as this is part of the color management pipeline (https://developer.blender.org/docs/features/gpu/viewports/color_management/#known-issues). Viewport can have 2 color management profiles active. One for the render engine (which is controlled by the color management panel) and one for the overlays (overlay engine is fixed to sRGB/Standard). There is no known solution how to solve this without introducing other issues. One trick I remember we added was to hide the overlays before exporting. Not sure why you're referring to the source code of the compositor as that is done in a linear space and uses a fixed conversion matrix.

ManBlender commented 2024-04-23 12:19:44 +02:00

Copy Link

It was time ago a option "display_device" ? Coz this is the case to have option which variant to set.
Also regarding pipeline..
https://blender.community/c/rightclickselect/JP8l/?sorting=hot

And know-issues:
Currently there isn't a python API to render to the color buffer. This results that add-ons that will use BGL rely on the display space. The consequence is that add-ons aren't able use the full potential of the drawing color pipeline.

• but I changed type, soo it's not actual or limited?

Finally I can do this as proposed by script or impacting by this for other things as I not understanding well due code?

Compositor or other should operate a display_device variable not static I think. Time ago I meet other issue regarding conversion movie clip/gif then blender not work adequately around but I recognized the problem now as relation around color systems.

It was time ago a option "display_device" ? Coz this is the case to have option which variant to set. Also regarding pipeline.. https://blender.community/c/rightclickselect/JP8l/?sorting=hot And know-issues: `Currently there isn't a python API to render to the color buffer. This results that add-ons that will use BGL rely on the display space. The consequence is that add-ons aren't able use the full potential of the drawing color pipeline.` - but I changed type, soo it's not actual or limited? Finally I can do this as proposed by script or impacting by this for other things as I not understanding well due code? Compositor or other should operate a display_device variable not static I think. Time ago I meet other issue regarding conversion movie clip/gif then blender not work adequately around but I recognized the problem now as relation around color systems.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

blender-v3.3-release

partial-write-refactor

brush-assets-project

universal-scene-description

fix-121021

blender-v4.1-release

blender-v3.6-release

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

11 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#73956

No description provided.