GPencil: Massive slowdown when stroke number scales #97240

New Issue

David Elahee · 2022-04-11T09:41:59+02:00

David Elahee commented

2022-04-11 09:41:59 +02:00

System Information
Operating system: Win10
Graphics card: NV GTX960 / NV RTX 2080

Blender Version
Broken: e03d78417a77
Worked: never

Short description of error

Our artist want to make "gris" quality characters with a lot of inner shades, and created a huge character with lot of strokes and did not break it down in sub objects.
Alas when using "Edit mode" to animate the keys blender gets extremely choppy.
If we remove strokes situation gets better which leads us to believe that stroke/key storage is too linear or computed during motion

Exact steps for others to reproduce the error
download : https://drive.google.com/file/d/1Wfj7fs2JmG5sZnR_S9SfxJ0iBXOvj_fX/view
go to "strokes"
go to edit mode
select hairs
move hairs around
observe any movement or undo is very choppy and slow

note :
As a dodge, we will try to split the character strokes in sub objects but we thought it would be important for this use case to be fixed because going back and forth in sub objects can be a time consuming and be counter intuitive for less technical artists.
Thank you so much for reading and creating GPencil.

**System Information** Operating system: Win10 Graphics card: NV GTX960 / NV RTX 2080 **Blender Version** Broken: e03d78417a77 Worked: never **Short description of error** Our artist want to make "gris" quality characters with a lot of inner shades, and created a huge character with lot of strokes and did not break it down in sub objects. Alas when using "Edit mode" to animate the keys blender gets extremely choppy. If we remove strokes situation gets better which leads us to believe that stroke/key storage is too linear or computed during motion **Exact steps for others to reproduce the error** download : https://drive.google.com/file/d/1Wfj7fs2JmG5sZnR_S9SfxJ0iBXOvj_fX/view go to "strokes" go to edit mode select hairs move hairs around observe any movement or undo is very choppy and slow note : As a dodge, we will try to split the character strokes in sub objects but we thought it would be important for this use case to be fixed because going back and forth in sub objects can be a time consuming and be counter intuitive for less technical artists. Thank you so much for reading and creating GPencil.

David Elahee commented

2022-04-11 09:41:59 +02:00

Added subscriber: @delahee

Antonio Vazquez commented

2022-04-11 10:09:32 +02:00

Added subscribers: @filedescriptor, @antoniov

Antonio Vazquez commented

2022-04-11 10:09:32 +02:00

What Blender version are you using it? There was a change in this area.

@filedescriptor could you test with your code if this is faster now?

What Blender version are you using it? There was a change in this area. @filedescriptor could you test with your code if this is faster now?

Antonio Vazquez changed title from ~~GPencil // Massive slowdown when storke number scales~~ to GPencil: Massive slowdown when stroke number scales

2022-04-11 10:10:08 +02:00

David Elahee commented

2022-04-11 10:13:16 +02:00

As mentionned we tested with a few "branch" builds and notably e03d78417a77
thx

As mentionned we tested with a few "branch" builds and notably e03d78417a77 thx

Pratik Borhade commented

2022-04-20 07:19:10 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-04-20 07:19:10 +02:00

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

Pratik Borhade commented

2022-04-20 07:19:10 +02:00

Hi @delahee , please upload simple test file.
Larges files are not that handy for developers for further investigation.

Hi @delahee , please upload simple test file. Larges files are not that handy for developers for further investigation.

Antonio Vazquez commented

2022-04-20 08:01:07 +02:00

@PratikPB2123 IMHO we would move this as Know Issuebecause we already know where are the bottlenecks and we are thinking in a redesign of the data structure, but with the actual design is almost impossible to solve.

@PratikPB2123 IMHO we would move this as `Know Issue`because we already know where are the bottlenecks and we are thinking in a redesign of the data structure, but with the actual design is almost impossible to solve.

Pratik Borhade commented

2022-04-20 08:09:56 +02:00

@antoniov , feel free to move this report to "known issues" category :)

Antonio Vazquez commented

2022-04-20 09:08:05 +02:00

As we know that the problem is the legacy data structure design, we move it as Know Issue.

Antonio Vazquez commented

2022-04-20 09:08:13 +02:00

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

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

GPencil: Massive slowdown when stroke number scales #97240