GP: Time offset and Armature modifier causes glitches #89433

New Issue

raylee · 2021-06-25T15:44:41+02:00

raylee commented

2021-06-25 15:44:41 +02:00

System Information
Operating system:WINDOWS10
Graphics card:GTX1060

Blender Version
Broken: 2.93LTS

Exact steps for others to reproduce the error

#89433.blend

Open file
Move selected bone to left until it hits constraint, and then a bit randomly

GP object will keep rotating in one direction and can be reset only by changing frame.
Same happens when scrubbing in negative frame range.

**System Information** Operating system:WINDOWS10 Graphics card:GTX1060 **Blender Version** Broken: 2.93LTS **Exact steps for others to reproduce the error** [#89433.blend](https://archive.blender.org/developer/F10216738/T89433.blend) - Open file - Move selected bone to left until it hits constraint, and then a bit randomly GP object will keep rotating in one direction and can be reset only by changing frame. Same happens when scrubbing in negative frame range.

raylee commented

2021-06-25 15:44:41 +02:00

Added subscriber: @RayLee

raylee commented

2021-06-25 15:48:53 +02:00

I Can’t upload files to the website.

Please download it on the Google Disk
https://drive.google.com/file/d/1nKEJfYfWzF9yrh0kSh_lbErkSXKq4hNi/view?usp=sharing

I Can’t upload files to the website. Please download it on the Google Disk https://drive.google.com/file/d/1nKEJfYfWzF9yrh0kSh_lbErkSXKq4hNi/view?usp=sharing

Richard Antalik commented

2021-06-25 16:02:55 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-06-25 16:02:55 +02:00

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

Richard Antalik commented

2021-06-25 16:02:55 +02:00

I can reproduce the issue, but we require sample files to be simplified as much as possible. Please remove all objects that are not required to reproduce the bug.

raylee commented

2021-06-25 16:15:29 +02:00

In #89433#1182721, @iss wrote:
I can reproduce the issue, but we require sample files to be simplified as much as possible. Please remove all objects that are not required to reproduce the bug.

In the file I uploaded, I deleted most of the stuff and kept it as simple as possible.

> In #89433#1182721, @iss wrote: > I can reproduce the issue, but we require sample files to be simplified as much as possible. Please remove all objects that are not required to reproduce the bug. In the file I uploaded, I deleted most of the stuff and kept it as simple as possible.

Antonio Vazquez commented

2021-06-25 18:58:01 +02:00

Added subscriber: @antoniov

Antonio Vazquez commented

2021-06-25 18:58:01 +02:00

I did not looked at your file, but the Time modifier is a special one and not sure it's designed to work as expected with Drivers. I will take a look anyway.

Edit: Testing your file with the Time modifier only, it works. First, I would advice you to put always Time modifier the first on the stack. Also, I have seen your driver moves from 0 to 100, but the frames are from 1 to 50.

Review your file and look at the armature setup because it looks the problem is not in the TimeOffset.

I did not looked at your file, but the Time modifier is a special one and not sure it's designed to work as expected with Drivers. I will take a look anyway. Edit: Testing your file with the Time modifier only, it works. First, I would advice you to put always Time modifier the first on the stack. Also, I have seen your driver moves from 0 to 100, but the frames are from 1 to 50. Review your file and look at the armature setup because it looks the problem is not in the TimeOffset.

raylee commented

2021-06-25 19:54:45 +02:00

In #89433#1182819, @antoniov wrote:
I did not looked at your file, but the Time modifier is a special one and not sure it's designed to work as expected with Drivers. I will take a look anyway.

Edit: Testing your file with the Time modifier only, it works. First, I would advice you to put always Time modifier the first on the stack. Also, I have seen your driver moves from 0 to 100, but the frames are from 1 to 50.

Review your file and look at the armature setup because it looks the problem is not in the TimeOffset.

I found the problem in your prompt, when the crayon frame 0 has no keyframe, and the drive manager Time modifier.Then GP has this strange phenomenon

Doesn’t seem to have anything to do with the modifier order

> In #89433#1182819, @antoniov wrote: > I did not looked at your file, but the Time modifier is a special one and not sure it's designed to work as expected with Drivers. I will take a look anyway. > > Edit: Testing your file with the Time modifier only, it works. First, I would advice you to put always Time modifier the first on the stack. Also, I have seen your driver moves from 0 to 100, but the frames are from 1 to 50. > > Review your file and look at the armature setup because it looks the problem is not in the TimeOffset. I found the problem in your prompt, when the crayon frame 0 has no keyframe, and the drive manager Time modifier.Then GP has this strange phenomenon Doesn’t seem to have anything to do with the modifier order

Antonio Vazquez commented

2021-06-26 11:47:09 +02:00

If you move to frame 0, it stands to reason that nothing is displayed. About order in the stack, really Time modifier is always evaluated first, but for better understanding of whats going on, it's better to put the first one in the stack, but it's not mandatory.

If you move to frame `0`, it stands to reason that nothing is displayed. About order in the stack, really Time modifier is always evaluated first, but for better understanding of whats going on, it's better to put the first one in the stack, but it's not mandatory.

Richard Antalik commented

2021-07-07 08:06:13 +02:00

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

Antonio Vazquez commented

2021-07-07 10:45:16 +02:00

@iss I think we can close the report. It looks the problem was how the drived was done.

Richard Antalik commented

2021-07-08 04:50:09 +02:00

In #89433#1187943, @antoniov wrote:
@iss I think we can close the report. It looke dthe problem was how the drived was done.

I did not understand your comments, so I wanted to recheck. I understand now, that property range was incorrect, which is causing problems, but there is still issue, that such setup won't recover from such state.

I have simplified the file and will update this report

> In #89433#1187943, @antoniov wrote: > @iss I think we can close the report. It looke dthe problem was how the drived was done. I did not understand your comments, so I wanted to recheck. I understand now, that property range was incorrect, which is causing problems, but there is still issue, that such setup won't recover from such state. ![untitled.png](https://archive.blender.org/developer/F10216712/untitled.png) I have simplified the file and will update this report

Richard Antalik changed title from ~~Greasenpencil Modifiers Unknown~~ to GP: Time offset and Armature modifier causes glitches

2021-07-08 05:33:15 +02:00

Richard Antalik commented

2021-07-08 05:33:15 +02:00

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

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

GP: Time offset and Armature modifier causes glitches #89433