https://bugs.kde.org/show_bug.cgi?id=436524
--- Comment #2 from Benjamin Round <benalbe...@gmail.com> --- Hi Eoin, I tried it with Krita 5 pre-alpha and the issue still persists. Find attached my Krita info where the bug happened. - I am running Windows 10 Home 64bit - b350 gaming 3 - motherboard - r9 380x 4GB - GPU - Ryzen 1700 8c, 16thread - CPU - 2666MHz 16 GB Corsair Vengence - RAM - 1TB 970 evo NVME m.2 - SSD I think that is all that is relevant, let me know otherwise. The bug is a bit random as it worked once when I had "frame rendering clone limit" set at 8. However, it hasn't ever worked when I push the limit to 16 (the max). Thanks, Benjamin On Wed, May 5, 2021 at 9:21 AM Eoin O'Neill <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436524 > > Eoin O'Neill <eoinoneill1...@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |eoinoneill1...@gmail.com > Resolution|--- |WORKSFORME > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Eoin O'Neill <eoinoneill1...@gmail.com> --- > Hi Benjamin, > > There have been a lot of changes on the upcoming version of Krita 5 > regarding > animation rendering and caching. As a result, I seem to be unable to > reproduce > this bug on the master branch. > > Could you try the latest nightly Krita build (Krita Next) available from > our > website and see if it works for you? If it doesn't work, could you please > give > me details on your operating system and hardware specs? > > Sorry for the inconvenience, > Eoin. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
