Page MenuHome

GP: Time offset and Armature modifier causes glitches
Confirmed, NormalPublic

Description

System Information
Operating system:WINDOWS10
Graphics card:GTX1060

Blender Version
Broken: 2.93LTS

Exact steps for others to reproduce the error

  1. Open file
  2. 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.

Event Timeline

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 (ISS) changed the task status from Needs Triage to Needs Information from User.Jun 25 2021, 4:02 PM

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.

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.

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 (raylee2233) added a comment.EditedJun 25 2021, 7:54 PM

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

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 (ISS) changed the task status from Needs Information from User to Needs Triage.Wed, Jul 7, 8:06 AM

@Richard Antalik (ISS) I think we can close the report. It looks the problem was how the drived was done.

@Richard Antalik (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

Richard Antalik (ISS) renamed this task from Greasenpencil Modifiers Unknown to GP: Time offset and Armature modifier causes glitches.Thu, Jul 8, 5:33 AM
Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.
Richard Antalik (ISS) updated the task description. (Show Details)