Bug 399468 - Onion Skin Bug
Summary: Onion Skin Bug
Status: RESOLVED DUPLICATE of bug 367524
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.1.3
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-07 01:57 UTC by Heather
Modified: 2018-10-07 14:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Here are some screenshots of the issue. (600.86 KB, image/png)
2018-10-07 01:57 UTC, Heather
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Heather 2018-10-07 01:57:26 UTC
Created attachment 115457 [details]
Here are some screenshots of the issue.

SUMMARY
I'm trying to use the animation set up you have, but there is an issue with the onion skin I am having. When I draw something, and then go to the next frame, it brings the previous frame along with it. It's supposed to reset the frame, and drop the opacity of the previous, giving it a red coloration, AKA making an "onion skin." What I found out is that when you erase the drawing brought along with it in that frame, then you see the red onion skin, but it should not of brought the entirety of the previous frame in the first place. I'm not sure how you would recreate this, since I asked someone and they said that they've never seen this bug before. I hope that you will be able to resolve this issue quickly. 


I added an attachment of some screenshots of the problem.
Comment 1 joupent 2018-10-07 14:00:58 UTC
If I understand your explanation correctly, you are not encountering a technical bug, but a perhaps unintuitive design choice.

It looks like your later frames have been drawn on top of (copies of) the previous ones. This happens if you create frames either by using the duplicate frame action or by drawing on a frame when auto-keying is enabled. There are differing opinions on what this behavior should be. 

I am marking this as duplicate to the report where this is already discussed.

*** This bug has been marked as a duplicate of bug 367524 ***