Graph Editor: Fcurve extrapolation visibility #76472

New Issue

Closed

opened 2020-05-06 12:15:25 +02:00 by Stanislav Ovcharov · 31 comments

Stanislav Ovcharov commented 2020-05-06 12:15:25 +02:00

Copy Link

Tweak option to toggle off visibility of extrapolated f-curves.
Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View.

The option ‘Show extrapolation” is ON

Graph editor behavior is as usual. The option is ON by default.

The option ‘Show extrapolation” is OFF:

Then:

• Constant extrapolations are hidden.
• Linear extrapolations are shown.
• Cycle modifier present but set to No Cycles: see above.
• Finite cycles are shown. Beyond the cycles: see above.
• Infinite cycles are shown.

If the extrapolation part of the curves are shown they should be drawn a bit different (lower opacity or dotted) whether show_extrapolation option On or Off.
Single keys. They should be shown just as single keyframes in the graph.

  - But first of all we have to implement the simplest variant 
      - The option ‘Show extrapolation” is On:  shows extrapolated curves.

The option ‘Show extrapolation” is Off. doesn't show extrapolated curves at all, whether it is a cycle, a linear extrapolation or a constant.
Examples:

And this are examples for possible improvements on next possible upgrades:
Constant extrapolation:

Linear extrapolation:
--
Cycle extrapolation finite:
--	--
Cycle extrapolation infinite:
--	--

Tweak option to toggle off visibility of extrapolated f-curves. Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View. ### The option ‘Show extrapolation” is ON Graph editor behavior is as usual. The option is ON by default. ### The option ‘Show extrapolation” is OFF: Then: - Constant extrapolations are hidden. - Linear extrapolations are shown. - Cycle modifier present but set to No Cycles: see above. - Finite cycles are shown. Beyond the cycles: see above. - Infinite cycles are shown. If the extrapolation part of the curves are shown they should be drawn a bit different (lower opacity or dotted) whether show_extrapolation option On or Off. Single keys. They should be shown just as single keyframes in the graph. - But first of all we have to implement the simplest variant - The option ‘Show extrapolation” is On: shows extrapolated curves. **The option ‘Show extrapolation” is Off. doesn't show extrapolated curves at all, whether it is a cycle, a linear extrapolation or a constant.** Examples: |  |  | | -- | -- | **And this are examples for possible improvements on next possible upgrades:** Constant extrapolation: |  |  | | -- | -- | Linear extrapolation: |  | | -- | Cycle extrapolation finite: |  |  |  | | -- | -- | -- | Cycle extrapolation infinite: |  |  |  | | -- | -- | -- |

Stanislav Ovcharov commented 2020-05-06 12:15:25 +02:00

Author

Copy Link

Added subscribers: @StanislavOvcharov, @dr.sybren, @LucianoMunoz

Added subscribers: @StanislavOvcharov, @dr.sybren, @LucianoMunoz

Sybren A. Stüvel commented 2020-05-07 12:08:54 +02:00

Member

Copy Link

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

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

Oskar commented 2020-05-12 13:50:03 +02:00

Copy Link

Added subscriber: @Oskar3d

Added subscriber: @Oskar3d

Oskar commented 2020-05-12 13:50:03 +02:00

Copy Link

A small suggestion. I think it would be useful if the extrapolation part of the curves is a drawn a bit different.(lower opacity, dotted, a bit tinner etc.) It gives a bit more information, so you know there are no keyframes prior or following what you see.

A small suggestion. I think it would be useful if the extrapolation part of the curves is a drawn a bit different.(lower opacity, dotted, a bit tinner etc.) It gives a bit more information, so you know there are no keyframes prior or following what you see. 

Luciano Muñoz Sessarego commented 2020-05-12 13:51:53 +02:00

Member

Copy Link

what oscar says would be highly appreciated.

what oscar says would be highly appreciated.

Stanislav Ovcharov commented 2020-05-12 14:59:11 +02:00

Author

Copy Link

In #76472#929792, @Oskar3d wrote:
A small suggestion. I think it would be useful if the extrapolation part of the curves is a drawn a bit different.(lower opacity, dotted, a bit tinner etc.) It gives a bit more information, so you know there are no keyframes prior or following what you see.

Do you mean to use it with Linear and Cycle extrapolation types only when extrapolation is off?

> In #76472#929792, @Oskar3d wrote: > A small suggestion. I think it would be useful if the extrapolation part of the curves is a drawn a bit different.(lower opacity, dotted, a bit tinner etc.) It gives a bit more information, so you know there are no keyframes prior or following what you see. Do you mean to use it with Linear and Cycle extrapolation types only when extrapolation is off?

Luciano Muñoz Sessarego commented 2020-05-12 15:48:24 +02:00

Member

Copy Link

only when the visibility of the extra is on, in anytype, to easily distinguish between the "live curve" and the generated one

only when the visibility of the extra is on, in anytype, to easily distinguish between the "live curve" and the generated one

Stanislav Ovcharov commented 2020-05-12 16:43:13 +02:00

Author

Copy Link

In #76472#929934, @LucianoMunoz wrote:
only when the visibility of the extra is on, in anytype, to easily distinguish between the "live curve" and the generated one

So this thing should be used everywhere/everytime, with this new extrapolation option ON and OFF, shouldn't it? Not to replace new option?

> In #76472#929934, @LucianoMunoz wrote: > only when the visibility of the extra is on, in anytype, to easily distinguish between the "live curve" and the generated one So this thing should be used everywhere/everytime, with this new extrapolation option ON and OFF, shouldn't it? Not to replace new option?

TonyG commented 2020-09-11 19:34:07 +02:00

Copy Link

Added subscriber: @antoine.grasset

Added subscriber: @antoine.grasset

RedMser commented 2020-10-19 17:44:41 +02:00

Contributor

Copy Link

Added subscriber: @RedMser

Added subscriber: @RedMser

Sybren A. Stüvel commented 2020-10-27 11:59:09 +01:00

Member

Copy Link

Also would be useful if the extrapolation part of the curves is a drawn a bit different (lower opacity/dotted,/bit tinner/etc.) whether show_extrapolation option On or Off. It gives a bit more information, so you know there are no keyframes prior or following what you see.

@StanislavOvcharov I agree that this would be nice. To make it possible to just implement it without getting more disucssions, can you pick the one you think is best and update the description & screenshots for this?

Once that's done, I think it's fine to get this implemented. @StanislavOvcharov do you have any idea how long it'll take you? Would Blender 2.92 be a reasonable target (so implemented, reviewed, and merged before 25 November)?

> Also would be useful if the extrapolation part of the curves is a drawn a bit different (lower opacity/dotted,/bit tinner/etc.) whether show_extrapolation option On or Off. It gives a bit more information, so you know there are no keyframes prior or following what you see. @StanislavOvcharov I agree that this would be nice. To make it possible to just implement it without getting more disucssions, can you pick the one you think is best and update the description & screenshots for this? Once that's done, I think it's fine to get this implemented. @StanislavOvcharov do you have any idea how long it'll take you? Would Blender 2.92 be a reasonable target (so implemented, reviewed, and merged before 25 November)?

Luciano Muñoz Sessarego commented 2020-10-29 16:54:40 +01:00

Member

Copy Link

I think this all needs to be much simpler.

On: shows extrapolated curves.
Off. doesnt show extrapolated curves at all, wether it is a cycle, a linear extrapolation or a constant.

The whole idea is to be able to get rid of the extra drawing in the graph editor that makes it harder to view.
Wether we want theeming options for when the extrapolated curves are on I think its secondary (could be a slider for opacity).

I think this all needs to be much simpler. On: shows extrapolated curves. Off. doesnt show extrapolated curves at all, wether it is a cycle, a linear extrapolation or a constant. The whole idea is to be able to get rid of the extra drawing in the graph editor that makes it harder to view. Wether we want theeming options for when the extrapolated curves are on I think its secondary (could be a slider for opacity).

Paul Kotelevets commented 2020-10-30 13:41:59 +01:00

Copy Link

Added subscriber: @1D_Inc

Added subscriber: @1D_Inc

Paul Kotelevets commented 2020-10-30 13:41:59 +01:00

Copy Link

I think that information about surrounding extrapolated animation that allow to distinguish cycled animations types is important for editing.

I think that information about surrounding extrapolated animation that allow to distinguish cycled animations types is important for editing.

Stanislav Ovcharov commented 2020-10-30 13:55:38 +01:00

Author

Copy Link

In #76472#1044375, @LucianoMunoz wrote:
I think this all needs to be much simpler.

On: shows extrapolated curves.
Off. doesnt show extrapolated curves at all, wether it is a cycle, a linear extrapolation or a constant.

The whole idea is to be able to get rid of the extra drawing in the graph editor that makes it harder to view.
Wether we want theeming options for when the extrapolated curves are on I think its secondary (could be a slider for opacity).

I don't mind that about such simplifying if it speeds up implementation but what if you have e.g. cycles for some f-curves? you have to remember that you have got these cycles somewhere on your curves or toggle show_extrapolation on and off back and forth to check it. Described in the task variant allows you to toggle show_extrapolation once and forget about it and do you work in a more calm way

> In #76472#1044375, @LucianoMunoz wrote: > I think this all needs to be much simpler. > > On: shows extrapolated curves. > Off. doesnt show extrapolated curves at all, wether it is a cycle, a linear extrapolation or a constant. > > The whole idea is to be able to get rid of the extra drawing in the graph editor that makes it harder to view. > Wether we want theeming options for when the extrapolated curves are on I think its secondary (could be a slider for opacity). I don't mind that about such simplifying if it speeds up implementation but what if you have e.g. cycles for some f-curves? you have to remember that you have got these cycles somewhere on your curves or toggle show_extrapolation on and off back and forth to check it. Described in the task variant allows you to toggle show_extrapolation once and forget about it and do you work in a more calm way

Stanislav Ovcharov commented 2020-11-12 16:40:24 +01:00

Author

Copy Link

So it was chosen to implement first the simplest way, just on \ off.
On: shows extrapolated curves.
Off. doesn't show extrapolated curves at all, whether it is a cycle, a linear extrapolation or a constant.

So it was chosen to implement first the simplest way, just on \ off. On: shows extrapolated curves. Off. doesn't show extrapolated curves at all, whether it is a cycle, a linear extrapolation or a constant.

Wayde Moss commented 2021-02-13 00:39:35 +01:00

Member

Copy Link

Added subscriber: @wbmoss_dev

Added subscriber: @wbmoss_dev

Wayde Moss self-assigned this 2021-02-13 00:39:35 +01:00

Wayde Moss commented 2021-02-13 00:39:35 +01:00

Member

Copy Link

I'll see if I can finish a patch for the simple approach . The upgrades appear non-trivial as I'm not sure how to properly determine the fcurve extents when multiple fmodifiers exists and how they interact with eachother (cycles modifier, limits modifier, restricted ranges, etc).

I'll see if I can finish a patch for the simple approach . The upgrades appear non-trivial as I'm not sure how to properly determine the fcurve extents when multiple fmodifiers exists and how they interact with eachother (cycles modifier, limits modifier, restricted ranges, etc).

Luciano Muñoz Sessarego commented 2021-02-16 12:04:42 +01:00

Member

Copy Link

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'

Luciano Muñoz Sessarego closed this issue 2021-02-16 12:04:42 +01:00

Luciano Muñoz Sessarego commented 2021-02-16 12:04:42 +01:00

Member

Copy Link

This comment was removed by @LucianoMunoz

*This comment was removed by @LucianoMunoz*

Stanislav Ovcharov commented 2021-02-16 14:05:14 +01:00

Author

Copy Link

Cool! but it's not resolved yet, isn't it?)

Cool! but it's not resolved yet, isn't it?)

Luciano Muñoz Sessarego commented 2021-02-16 14:15:45 +01:00

Member

Copy Link

no he just started :)

no he just started :)

Stanislav Ovcharov commented 2021-02-16 14:39:27 +01:00

Author

Copy Link

In #76472#1113068, @LucianoMunoz wrote:
no he just started :)

but you closed it as resolved)

> In #76472#1113068, @LucianoMunoz wrote: > no he just started :) but you closed it as resolved)

Luciano Muñoz Sessarego commented 2021-02-16 14:42:30 +01:00

Member

Copy Link

interesting, I didnt!, and i tried deleting that and i can only mark as resolved or invalid... can you gimme a hand here @dr.sybren ?

interesting, I didnt!, and i tried deleting that and i can only mark as resolved or invalid... can you gimme a hand here @dr.sybren ?

Philipp Oeser commented 2021-02-16 15:09:25 +01:00

Member

Copy Link

Changed status from 'Resolved' to: 'Confirmed'

Changed status from 'Resolved' to: 'Confirmed'

Philipp Oeser reopened this issue 2021-02-16 15:09:25 +01:00

Sybren A. Stüvel commented 2021-02-23 10:08:47 +01:00

Member

Copy Link

When the design work is finished, and implementation can start, either one of these two should happen:

1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or
2. Re-classify this task as TODO task.

I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it.

The design description has this as 2nd sentence:

Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View.

I don't see a motivation for this, though. Why is this the best spot? What makes this preferred over just having a user preference that sets this?

Is the description of this design task up to date with what's being implemented in {D10442}? If not, please @StanislavOvcharov or @wbmoss_dev update it so that any reviewers know how the code should behave.

When the design work is finished, and implementation can start, either one of these two should happen: 1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or 2. Re-classify this task as TODO task. I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it. The design description has this as 2nd sentence: > Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View. I don't see a motivation for this, though. Why is this the best spot? What makes this preferred over just having a user preference that sets this? Is the description of this design task up to date with what's being implemented in {[D10442](https://archive.blender.org/developer/D10442)}? If not, please @StanislavOvcharov or @wbmoss_dev update it so that any reviewers know how the code should behave.

Stanislav Ovcharov commented 2021-02-23 10:50:44 +01:00

Author

Copy Link

In #76472#1117488, @dr.sybren wrote:

Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View.

I don't see a motivation for this, though. Why is this the best spot? What makes this preferred over just having a user preference that sets this?

Well it looks logical enough for me to place it here..

In #76472#1117488, @dr.sybren wrote:
When the design work is finished, and implementation can start, either one of these two should happen:

1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or
2. Re-classify this task as TODO task.

I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it.

I would choose the option 1 because it is ready for master. And I would leave it even as it is. Looch is right when said that you should know \ remember all your fcurve cycles or linear extrapolation if exist. So there is no big need for further tweaks but I don't mind about it.
So I would edit and close it if you accept.

> In #76472#1117488, @dr.sybren wrote: >> Best place for 'Show extrapolation' command with on/off checkbox in the graph editor menu - View. > I don't see a motivation for this, though. Why is this the best spot? What makes this preferred over just having a user preference that sets this? > Well it looks logical enough for me to place it here..  > In #76472#1117488, @dr.sybren wrote: > When the design work is finished, and implementation can start, either one of these two should happen: > 1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or > 2. Re-classify this task as TODO task. > > I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it. > I would choose the option 1 because it is ready for master. And I would leave it even as it is. Looch is right when said that you should know \ remember all your fcurve cycles or linear extrapolation if exist. So there is no big need for further tweaks but I don't mind about it. So I would edit and close it if you accept.

Sybren A. Stüvel commented 2021-02-26 14:19:02 +01:00

Member

Copy Link

In #76472#1117543, @StanislavOvcharov wrote:
Well it looks logical enough for me to place it here..

Ok, so it's a personal choice. That's fine, but it's better when it's actually been discussed & decided upon by more people in the module. The placement of the option also has implications as to where the option is stored, and how global it is.

An alternative would be to have this as a user preference. That has an impact on how teams of animators look at each others' files.

In #76472#1117488, @dr.sybren wrote:
When the design work is finished, and implementation can start, either one of these two should happen:

1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or
2. Re-classify this task as TODO task.

I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it.

I would choose the option 1 because it is ready for master.

Not if there are still questions about the design.

And I would leave it even as it is.

I don't understand. Option 1 is "close this design task, create a new TODO task for the actual implementation". You can't leave this task as it is AND close it and create a new one.

> In #76472#1117543, @StanislavOvcharov wrote: > Well it looks logical enough for me to place it here.. Ok, so it's a personal choice. That's fine, but it's better when it's actually been discussed & decided upon by more people in the module. The placement of the option also has implications as to where the option is stored, and how global it is. An alternative would be to have this as a user preference. That has an impact on how teams of animators look at each others' files. >> In #76472#1117488, @dr.sybren wrote: >> When the design work is finished, and implementation can start, either one of these two should happen: >> 1. Close the design task as resolved (because the design work is done) and create a new TODO task for keeping track of the implementation, or >> 2. Re-classify this task as TODO task. >> >> I think the 2nd option is the most suitable here, as it's not a huge amount of work that needs a separate task for tracking it. >> > I would choose the option 1 because it is ready for master. Not if there are still questions about the design. > And I would leave it even as it is. I don't understand. Option 1 is "close this design task, create a new TODO task for the actual implementation". You can't leave this task as it is AND close it and create a new one.

Luciano Muñoz Sessarego commented 2021-02-28 08:39:53 +01:00

Member

Copy Link

I believe it should go in the view menu as it is an option that you'd often change, I'd rather it be off by default because just by having it off it improves readability in the graph editor and I'd turn it on just when I "NEED" to see the extrapolation which is how I normally do it in at work all the time, I only turn it on in rare occasions, because i need the graph editor to display as minimal and clear information as it can (its already a spaghetti mess, i don't want more stuff cluttering it)
Also this might mean a bit of a performance improvement by drawing less curves by default, but I dont know how true this las phrase is, i'm just speculating.

I believe it should go in the view menu as it is an option that you'd often change, I'd rather it be off by default because just by having it off it improves readability in the graph editor and I'd turn it on just when I "NEED" to see the extrapolation which is how I normally do it in at work all the time, I only turn it on in rare occasions, because i need the graph editor to display as minimal and clear information as it can (its already a spaghetti mess, i don't want more stuff cluttering it) Also this might mean a bit of a performance improvement by drawing less curves by default, but I dont know how true this las phrase is, i'm just speculating.

blender-admin commented 2021-03-09 21:09:09 +01:00

Copy Link

This issue was referenced by dcd7dacc4f

This issue was referenced by dcd7dacc4fd8d72f3388268959b1324f7aae95e4

Stanislav Ovcharov commented 2021-03-10 04:50:14 +01:00

Author

Copy Link

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'

Stanislav Ovcharov closed this issue 2021-03-10 04:50:14 +01:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

blender-v4.4-release

npr-prototype

blender-v4.2-release

remote-asset-library-monolithic

blender-v3.6-release

blender-v4.3-release

temp-sculpt-dyntopo

blender-v3.3-release

brush-assets-project

pr-extensions-tidy-space

blender-v4.0-release

universal-scene-description

blender-v4.1-release

blender-v3.6-temp_wmoss_animrig_public

gpencil-next

blender-projects-basics

sculpt-blender

asset-browser-frontend-split

asset-shelf

blender-v3.5-release

blender-v2.93-release

sculpt-dev

bevelv2

xr-dev

v4.4.0

v4.2.8

v4.2.7

v3.6.21

v4.2.6

v3.6.20

v4.2.5

v3.6.19

v4.3.2

v4.3.1

v4.3.0

v4.2.4

v3.6.18

v4.2.3

v3.6.17

v4.2.2

v3.6.16

v4.2.1

v3.6.15

v4.2.0

v3.6.14

v3.3.21

v3.6.13

v3.3.20

v3.6.12

v3.3.19

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 System

Asset datablocks, libraries, browser and shelf

Interest

Audio

Interest

Automated Testing

Interest

BlendFile

Interest

Blender Asset Bundle

Interest

Code Documentation

Code comments, Python/RNA API descriptions

Interest

Collada

Interest

Compatibility

Backward and forward compatibility

Interest

Compositing

Interest

Core

Interest

Cycles

Interest

Dependency Graph

Interest

Development Management

Interest

EEVEE

Interest

FBX

FBX I/O related topics

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

USD

Interest

UV Editing

Interest

Undo

Interest

User Interface

Interest

VFX & Video

Interest

Video Sequencer

Interest

Viewport & EEVEE

Interest

Virtual Reality

Interest

Vulkan

Interest

Wayland

Wayland windowing on Unix

Interest

Workbench

Interest

glTF

glTF format I/O topics

Interest: X11

Xorg/X11 windowing

Legacy

Asset Browser Project

Archived

Legacy

Blender 2.8 Project

Archived

Legacy

Milestone 1: Basic, Local Asset Browser

Archived

Legacy

OpenGL Error

Archived

Meta

Good First Issue

Meta

Papercut

Meta

Retrospective

Meta

Security

Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/

Module

Animation & Rigging

Module

Asset System

Module

Core

Module

Development Management

Module

Grease Pencil

Module

Modeling

Module

Nodes & Physics

Module

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

Windows

Platform

macOS

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

Archived

Type

Report

Archived

Type

To Do

No Label

Interest

Animation & Rigging

Module

Animation & Rigging

Severity

Normal

Status

Resolved

Type

Design

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

Hoshinova James-McCarthy-4 Sebastian-Herholz casey-bianco-davis gandalf3 Blendify Aaron Carlisle quantimoney Aditya Y Jeppu Alaska Alaska angavrilov Alexander Gavrilov frogstomp Aleš Jelovčan amelief Amélie Fondevilla elubie Andrea Weikert Andy_Goralczyk Andy Goralczyk ankitm Ankit Meel Anthony-Roberts Anthony Roberts antoniov Antonio Vazquez aras_p Aras Pranckevicius Arnd Arnd Marijnissen bartvdbraak Bart van der Braak mont29 Bastien Montagne blender-bot Blender Bot bnagirniak Bogdan Nagirniak BClark Brad Clark brecht Brecht Van Lommel BrianSavery Brian Savery (AMD) ideasman42 Campbell Barton CharlesWardlaw Charles Wardlaw CharlieJolly Charlie Jolly Chris_Blackbourn Chris Blackbourn lateasusual Chris Clyne (Lateasusual) ChrisLend Christoph Lendenfeld HobbesOS Cian Jinks fclem Clément Foucault cmbasnett Colin Basnett Kdaf Colin Marmond dfelinto Dalai Felinto pioverfour Damien Picard DanielBystedt Daniel Bystedt pepe-school-land Daniel Martinez Lara zanqdo Daniel Salazar Mets Demeter Dzadik erik85 Erik Abrahamsson EAW Evan Wilson filedescriptor Falk David fsiddi Francesco Siddi GaiaClary Gaia Clary DagerD Georgiy Markelov mano-wii Germano Cavalcante zazizizou Habib Gahbiche HooglyBoogly Hans Goudey Harley Harley Acheson weasel Henrik D. Hjalti Hjalti Hjálmarsson howardt Howard Trickey nirved-1 Hristo Gueorguiev mod_moder Iliya Katushenock brita Inês Almeida JacquesLucke Jacques Lucke Jason-Fielder Jason Fielder JasonSchleifer Jason schleifer Jebbly Jeffrey Liu Jeroen-Bakker Jeroen Bakker deadpin Jesse Yurkovich neXyon Joerg Mueller eliphaz John Kiril Swenson guitargeek Johnny Matthews Brainzman Jonas Holzman JoniMercado Jonatan Mercado JorgeBernalMartinez Jorge Bernal JosephEagar Joseph Eagar JoshuaLeung Joshua Leung Bone-Studio Juan Gea jpbouza-4 Juan Pablo Bouza JulianEisel Julian Eisel JulienDuroure Julien Duroure JulienKaspar Julien Kaspar kevindietrich Kévin Dietrich lone_noel Leon Schittek LucianoMunoz Luciano Muñoz Sessarego LukasStockner Lukas Stockner LukasTonne Lukas Tönne LunaRood Luna Rood MaiLavelle Mai Lavelle EosFoxx Marion Stalke Baardaap Martijn Versteegh scorpion81 Martin Felke mendio Matias Mendiola Matt-McLin Matt McLin MetinSeven Metin Seven wave Michael B Johnson Michael-Jones Michael Jones (Apple) makowalski Michael Kowalski pragma37 Miguel Pozo nrupsis Nate Rupsis jesterking Nathan Letwory nathanvegdahl Nathan Vegdahl PrototypeNM1 Nicholas Rishel nickberckley Nika Kutsniashvili Sirgienko Nikita Sirgienko OmarEmaraDev Omar Emara pablovazquez Pablo Vazquez PaoloAcampora Paolo Acampora PascalSchon Pascal Schön pmoursnv Patrick Mours muxed-reality Peter Kim lichtwerk Philipp Oeser P2design Pierrick PICAUT PratikPB2123 Pratik Borhade Limarest Ramil Roosileht farsthary Raul Fernandez Hernandez LazyDodo Ray molenkamp iss Richard Antalik rjg Robert Guetzkow salipour Sahar A. Kashi Sayak-Biswas Sayak Biswas Sean-Kim Sean Kim sherholz Sebastian Herholz sebastian_k Sebastian Koenig ZedDB Sebastian Parborg sebbas Sebastián Barschkis Sergey Sergey Sharybin IRIEShinsuke Shinsuke Irie sidd017 Siddhartha Jejurkar SietseB Sietse Brouwer SimonThommes Simon Thommes SonnyCampbell_Unity Sonny Campbell Stefan_Werner Stefan Werner Lockal Sv. Lockal dr.sybren Sybren A. Stüvel ThomasDinges Thomas Dinges Ton Ton Roosendaal BassamKurdali Ursula kurdali Vasyl-Pidhirskyi Vasyl Pidhirskyi WannesMalfait Wannes Malfait wbmoss_dev Wayde Moss weizhen Weizhen Huang leesonw William Leeson xavierh Xavier Hallade jenkm Yevgeny Makarov ChengduLittleA YimingWu gfxcoder jon denning

No Assignees Wayde Moss

10 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#76472

No description provided.