https://bugs.kde.org/show_bug.cgi?id=409373
--- Comment #6 from starlightlovestod...@outlook.com --- (In reply to Ahab Greybeard from comment #3) > [I've just realised that you probably have krita settings that give you only > one layer (Background) on startup so that is why you create a new layer to > give you Layer 1. My arrangement is different and I should have thought of > that. > When you make a Blank Frame, you do make a keyframe but many people don't > know what a 'keyframe' is so 'Blank Frame' is easier to understand] > > If you're not animating the Background layer (it's not a good idea to > animate the background layer) then there is no reason to have it in the > Timeline. Are you saying that the presence of the Background layer in the > Timeline is a factor that contributes to the crash? > > I think that onion skins are a distraction in this situation so please turn > them off to simplify the situation. > > When you create a new layer, it should become the active/selected layer, as > indicated by being highlighted in the Layers docker and showing in the > Timeline. The active layer should always be shown in the Timeline so I'm > puzzled as to why you have to manually add Layer 1 to the Timeline. When you > create Layer 1, is is the active/selected layer as shown by being > highlighted in the Layers docker? > > When you draw in a new blank frame on Layer 1, do you use the 'normal' > Freehand Brush tool or some other tool? > > Were you able to create animated layers in krita 4.1.7 and/or krita 4.2.0? > > Can you take a full .png screenshot showing the Layers docker and the > Timeline docker and attach it to a comment? 1. Well, I thought at first that the background layer was the one that caused the crash but later on I tried it with only Layer 1 present in the Timeline, but I got the same crash. 3. Yes, it is highlighted. 4. Freehand brush tool. 5. I didn't animate in the 4.2.0 version. I got 4.2.0v a day before 4.2.1 came out so I'm unsure if it worked then. I had 4.0.1 for about a year and forgot to update it until this year so I'm unsure if this problem occurred in later versions. -- You are receiving this mail because: You are watching all bug changes.
