Testers Wanted – 5.2.3-Beta1 – Issues and Feedback Thread

Develop Artists Feedback & Testing
43

If you click DEV BUILD button on the welcome screen it leads to 404

44

Thank you, I will try that.
I hope it will run up smoothly when it is officially released.

45

That’s fixed now: Welcome Page: Fix "DEV BUILD" button going to a 404 (!2171) · Merge requests · Graphics / Krita · GitLab

2 Likes
46

Hi, all!

Thank you for testing! I have fixed the openGL 16-bit issue, the fix is already available in nigtlies. Are there any other critical issues that should block the release of 5.2.3?

2 Likes
47

Hi, @Feldiarts!

Could you make a video of a problem, and, possibly, share a testing file you use? I cannot reproduce the issue here locally :frowning:

Are you using Windows or Linux, btw?

I have an idea of what could be wrong in this canse, but I need to be able to reproduce the issue to be able to actually fix it.

48

There are problems with color coded selection when using the magic wand tool on a flats layer.
It will select the entire piece, instead of the specific areas.
I have checked and this is 5.2.3beta specific, as it functions as it should in 5.2.2

5.2.3 beta behaviour

5.2.2 expected behaviour

49

Win11, line tool doesn’t activate if I switch keyboard language from English to another language (default shortcuts)

50

Sounds like bug 434228 – Can't invoke shortcuts which require holding a key while using non US layouts

51

@Konstrukto as I said here Testers Wanted – 5.2.3-Beta1 – Issues and Feedback Thread - #18 by Deif_Lou i fixed that in master but forgot to backport it. I already pushed the fix to 5.2.3 so it should be ok in the release. Thanks for the report anyway.

4 Likes
52

I’m not sure if this is a bug or not, but the popup palette doesn’t show up consistently like the previous versions when the shortcut is set to the “A” key in the Krita 5.2.3 beta. I had no problems using the popup palette in Krita 5.2.2 but had issues when trying to use the popup palette with the “A” key. However, the popup palette works fine in the Krita 5.2.3 beta if I use the right mouse button. I have since reverted back to Krita 5.2.2. I’m on windows 10.

1 Like
53

I think it would have been better to report it where the issues belonging to the 5.2.3 BETA are collected:
Testers Wanted – 5.2.3-Beta1 – Issues and Feedback Thread

@AhabGreybeard, @raghukamath, @Sooz: If you think the same, would you be so kind to move this report into the Issues and Feedback topic for the 5.2.3?

Michelist

54

I wasn’t aware of this thread. This post can be moved to the appropriate thread if needed.

2 Likes
55

With the 5.2.3-beta1 portable .zip package on Windows 10, I have no problems using the ‘A’ key for Show Popup Widget in the Canvas Input Settings.
Are you sure that the ‘A’ key is not used in the Keyboard Shortcuts?

1 Like
56

Yes, I just checked the 5.2.3-beta1 portable and the ‘A’ key is not used in the keyboard shortcuts or canvas input settings besides ‘Show Popup Widget’. I’ve noticed that using other keys besides ‘A’ works fine (like ‘F’ or right click), but ‘A’ specifically is messing up for my setup. I’ve also noticed that the ‘A’ key will temporary work once you open up ‘Configure Krita’ but will stop working once Krita is restarted.

Also, the ‘A’ key works when bringing up the selection pop up menu when a selection tool is active.

57

Hi, all!

Could you please help with testing the final release packages before we actually publish them?

The things that need extra attention:

  1. 16-bit-integer images on Windows on ANGLE backend (I have fixed the issue, so it should work correctly now)

  2. Animation playback with audio. I have rewritten a small part of it, so it needs extra attention. Here are the test cases that would be nice to test before the release:

    • try adding audio that is shorter than the playback range

      • play it
      • pause/restart in the end of the range, where there is no audio
      • scrub at the area with no sound
      • start again
      • change the speed and repeat the steps with the area without sound: the audio should play at the correct speed and should be in sync (not so in 5.2.3-beta1)

    • remove existing audio from the image [0]

      • play it
      • try to change speed to 25%, then scrub and play/pause randomly; it should keep the speed consistent and not crash

[0] - it is not the same as opening an image without sound, since adding sound changes the playback engine inside Krita

Packages can be found in this CI pipeline:

8 Likes
58

I reported this as a bug but just FYI tiling two canvases in subwindows mods in android (each selected a different tool like transform on one canvas and brush on the other) bugs out the canvas behaviours in unexpected ways. It’s a problem in 5.2.3(beta1) as well as in this nightly build.

60

Hi @sooz I edited the first post to put message from dmitry. @dkazakov asked me to highlight this topic a bit more so I have pinned it globally too.

3 Likes
61

Perfect!

62

Hi @dkazakov , I tried it on Windows 11.

  1. 16-bit + ANGLE is fixed
  2. I couldn’t get a crash with either added audio or fresh opening a file with existing audio, removing it, scrubbing etc.

However, I believe I found a new (?) bug related to the audio playback. The audio is cut off sooner than expected. Here’s how I can repro it:

  1. Start Krita
  2. Create a new document, open the animation timeline
  3. Modify the animation settings:
    start frame 0
    end frame 1000 (just sufficiently large)
    FPS 10
  4. Add an audio file. In my case it was a WAV file with 27 seconds length.
  5. Play back the animation. It will play normally and the audio will end at around 270’th frame.
    (everything works as expected until this point)
  6. Modify the animation settings again, and change the FPS to 20
  7. Play back the animation. The audio will stop at the same frame, but now due to the FPS being twice as large as before, it will be cut off in half before finishing (i.e. only 13.5 seconds of 27 seconds clip will play).
  8. (BONUS) Remove the audio clip. Add back the same audio clip. Now it play in full at 20 FPS.

Scrubbing, stopping, resuming, adding keyframes, and changing the playback speed percentage doesn’t affect this.

I hope this helps!