So the question for me is there a way to disable it? I have never needed that particular feature to the Color selectors and could just do without.
Well the bug i know is you boot krita then press ctrl+lmb on the dockers before clicking anything else and the square appears. Then you click around and it goes away feels like bad default values on startup. And this looks like an extension of that somehow. When i get qt6 to work i will try it out.
hello, i m testing 5.3 and iâve noticed a lag in the cursor display when switching to previous brush. The cursor seems to be âstuckâ waiting for a refresh of the canva⌠but you can paint with the new brush, just the cursor and outline are not update instantly (in the previous version, it is instant)
someone notice that too?
some changes have been made in this area?
should i report a bug?
Hello! Iâve just downloaded Krita 6 but I havenât been able to open Krita since I did
I use a dell laptop to run the program and installed the 64bits windows version.
I use plugins for Krita as well
Have no idea, maybe hidden in kritarc config, or hard-coded?
Disable all external plugins in 5.2 and run 6.0 again to tryout.
Problem is, Krita automatically uninstalled 5.2 when I installed 6. And when I tried to go back to 5.2 it said that I had to manually uninstall 6
Update on this:
I downloaded the portable version of 5.3 and that works fine. The new stabilize settings took some time getting used to but they work okay now
5.3.0 Android
Are we still able to reposition the toolbars?
In previous versions, there was a tiny area on the left ege that you could press and drag. In 5.3 Android there doesnât seem to be any way to move the toolbars.
I put everything I need in Custom Toolbar1 and want to move it to the bottom of the screen, if possible.
Itâs a new toggle in the Settings menu, Lock Toolbars (on by default). You should be able to move them after unlocking them.
Oh my gosh!!! Thatâs genius. Thanks for telling me, I totally missed that.
Congrats on the Beta releases! Iâve been playing with the Krita 6.0 Beta AppImage for a bit on Arch Linux with KDE Plasma for a little bit and it seems to work real well.
One thing Iâve noticed so far is that the the Specific Color Selector docker doesnât seem to register any changes to Saturation or Lightness/Value that are made either through picking a color with the Wide Gamut Color Selector, or entering in a hex code while itâs set to HSL or HSV Modes. RGB, HSI and HSY modes seem to work as expected.
Also, if I run the AppImage with QT_QPA_PLATFORM=wayland, when I use my tablet stylus, Krita uses the Crosshair cursor from my Plasma theme, as someone else mentioned before in this thread. If i use my mouse, then it uses the cursor settings defined within Krita, as expected.
Hi! Iâm trying the new 5.3 beta (on Windows 10), and I came across what seems to be a bug with camera panning.
Itâs a problem with panning while dragging a tool beyond the view limit. It seems that the panning starts not when you cross the view limit, but a little bit before it on the right and bottom sides. The problem is that this distance is fixed regardless of how zoomed in you are. It looks to be about 40 pixels.
This is problematic when working with pixel art, as any attempt to make a selection will drag the camera.
I canât attach a video since Iâm a new user, but itâs simple to recreate. Just make a small canvas of 100px by 100px and zoom in. If you try to make a selection near the bottom right corner, youâll see that the view moves.
A fix for this is in progress here: Fix zoom being too fast when zoomed in (!2632) ¡ Merge requests ¡ Graphics / Krita ¡ GitLab
Hello ! It so nice to see our wonderfull software evolving ![]()
I just installed it (iâm on Linux-Solus and it seems to work fine) and, as i was testing the new text-tool, i was wondering how to change the spacing between lines and paragraph above the others, and also spacing between letters ? i just find how to change width of each letters or tilt of italic. Thank you for your answers ![]()
quick report, im having a crash on 6.0 specifically a little bit after the time i create a second project, seems to be a ticking bomb after i resize the image (part of the workflow)
heres what i believe is to be the most relevant part of the log:
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:39: TypeError: Cannot read property âmodelWrapperâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:33: TypeError: Cannot read property âhighlightedIndexâ of null
qrc:/qt/qml/org/krita/components/ResourceDelegateBase.qml:41: TypeError: Cannot read property âpaletteâ of null
qrc:/FontResourceDropdown.qml:17:9: Unable to assign ResourceView_QMLTYPE_0 to ResourceView_QMLTYPE_0
QWidgetRepaintManager: skipped frames: 0 %
qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 37 qtcode 16777249
qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 54 qtcode 67
qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 37 qtcode 16777249
qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 54 qtcode 67
QWidgetRepaintManager: skipped frames: 0 %
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
QDomDocument called with unopened QIODevice. This will not be supported in future Qt versions.
The imageRectInWidgetPixels topLeft() does not match the documentOffsetF!
imageRectInWidgetPixels: QRectF(-0.6,-0.6 0x0)
documentOffsetF: QPointF(1,1)
qrc:/SvgTextToolOptions.qml:249: TypeError: Cannot read property âtextTypeâ of null
qrc:/SvgTextToolOptions.qml:42: TypeError: Cannot read property âoptionsModelâ of null
qrc:/SvgTextToolOptions.qml:337: TypeError: Cannot read property âshowLineDebugâ of null
qrc:/SvgTextToolOptions.qml:342: TypeError: Cannot read property âshowDebugâ of null
qrc:/SvgTextToolOptions.qml:327: TypeError: Cannot read property âshowCharacterDebugâ of null
qrc:/SvgTextToolOptions.qml:332: TypeError: Cannot read property âshowDebugâ of null
qrc:/SvgTextToolOptions.qml:321: TypeError: Cannot read property âshowDebugâ of null
qrc:/SvgTextToolOptions.qml:317: TypeError: Cannot read property âshowDebugâ of null
qrc:/SvgTextToolOptions.qml:124: TypeError: Cannot read property âshowTextPropertyButtonâ of null
qrc:/SvgTextToolOptions.qml:74: TypeError: Cannot read property âoptionsModelâ of null
qt.core.qobject.connect: QObject::connect: No such signal WdgImageSize::okClicked()
krita.ui: WARNING: thumbnail generation for âBackgroundâ took longer than expected: 283 (timeout: 40 )
krita.ui: This layerâs thumbnail will be rendered in imprecise mode from now on
WARNING: idle task consumed more than 200 ms, it can cause visible distractions to the user
WARNING: time consumed in âlayer-thumbnails-strokeâ is 285 ms
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
QWidgetRepaintManager: skipped frames: 0 %
Segmentation fault (core dumped) /home/lucas/AppImages/krita.appimage
note: currently running fedora kde 43, with a gtx 1050 ti
Idk why but 6.0 or Qt6 ver of krita is buggy on Linux. But 5.3.0 works great.
The 6.0 versions has so much latency when i draw. The cursor lags behind alot. Krita 5.4 dosent have those latency
I made a 120 fps recording, hopefully it will be clear to see, but on 5.3 the cursor outline (big circle) stucks for a moment after I release the stylus, then teleports back to the cursor.
On 5.2.15 there is no such problem with the same settings:
@raghukamath / @sooz / @Takiro / @tiar: Can you please close this topic and move the initial post to the Krita 5.3/6.0 beta 1 released topic, where it belongs?
Thank you!
Michelist
Adding vblank_mode=0 environment variable to force disable vsync seems to fix the latency issue for me with AMD integrated GPU.
