[BUG maybe?] Pressing on "value changing slider" for Flexibility on Warp transform does nothing

Not sure how the flexibility field intended to be used.
However when I try to press little triangles to change the values nothing changes.

warp-flexibility-bug

System Information

Krita

Version: 4.4.8
Languages: en_US, en
Hidpi: true

Qt

Version (compiled): 5.12.11
Version (loaded): 5.12.11

OS Information

Build ABI: x86_64-little_endian-llp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: winnt
Kernel Version: 10.0.19043
Pretty Productname: Windows 10 (10.0)
Product Type: windows
Product Version: 10

OpenGL Info

Vendor: “Google Inc.”
Renderer: “ANGLE (NVIDIA GeForce GTX 1080 Ti Direct3D11 vs_5_0 ps_5_0)”
Version: “OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)”
Shading language: “OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)”
Requested format: QSurfaceFormat(version 3.0, options QFlagsQSurfaceFormat::FormatOption(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile)
Current format: QSurfaceFormat(version 3.0, options QFlagsQSurfaceFormat::FormatOption(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)
Version: 3.0
Supports deprecated functions false
is OpenGL ES: true

QPA OpenGL Detection Info
supportsDesktopGL: true
supportsAngleD3D11: true
isQtPreferAngle: true

P.S. Did not know where to put, so post it here.

Checked it on Version: 5.0.0-beta1 (git 2e95dd5)
The behavior is as expected. So it is fixed in later versions.

Sorry for making a fuzz.

No problem, that is what the forum is for. To verify and discuss the problem before reporting actual bug

Hm. Found how to make Krita crash with this tool though.
Steps to reproduce.

  1. Create new image 1024x1024
  2. Draw some lines on the empty layer
  3. Ctr+T
  4. Warp Mode
  5. Set flexibility to 10
  6. Start clicking subdivide (on the value around 15+ the crash is happening)

On 4.4.8 subdivision does not cause a crash.

Sys Info

Krita

Version: 5.0.0-beta1 (git 2e95dd5)
Languages: en_US, en
Hidpi: true

Qt

Version (compiled): 5.12.11
Version (loaded): 5.12.11

OS Information

Build ABI: x86_64-little_endian-llp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: winnt
Kernel Version: 10.0.19043
Pretty Productname: Windows 10 (10.0)
Product Type: windows
Product Version: 10

OpenGL Info

Vendor: “Google Inc.”
Renderer: “ANGLE (NVIDIA GeForce GTX 1080 Ti Direct3D11 vs_5_0 ps_5_0)”
Version: “OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)”
Shading language: “OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)”
Requested format: QSurfaceFormat(version 3.0, options QFlagsQSurfaceFormat::FormatOption(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile)
Current format: QSurfaceFormat(version 3.0, options QFlagsQSurfaceFormat::FormatOption(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)
Version: 3.0
Supports deprecated functions false
is OpenGL ES: true

QPA OpenGL Detection Info
supportsDesktopGL: true
supportsAngleD3D11: true
isQtPreferAngle: true

Hardware Information

GPU Acceleration: auto
Memory: 65470 Mb
Number of Cores: 6
Swap Location: C:/Users/rapid/AppData/Local/Temp

Current Settings

Current Swap Location: C:/Users/rapid/AppData/Local/Temp
Current Swap Location writable: true
Undo Enabled: true
Undo Stack Limit: 30
Use OpenGL: true
Use OpenGL Texture Buffer: true
Disable Vector Optimizations: false
Disable AVX Optimizations: false
Canvas State: OPENGL_SUCCESS
Autosave Interval: 900
Use Backup Files: true
Number of Backups Kept: 1
Backup File Suffix: ~
Backup Location: Same Folder as the File
Backup Location writable: false
Use Win8 Pointer Input: false
Use RightMiddleTabletButton Workaround: false
Levels of Detail Enabled: false
Use Zip64: false

Display Information
Number of screens: 2
Screen: 0
Name: \.\DISPLAY1
Depth: 32
Scale: 1
Resolution in pixels: 2560x1440
Manufacturer:
Model:
Refresh Rate: 59
Screen: 1
Name: \.\DISPLAY2
Depth: 32
Scale: 1
Resolution in pixels: 2560x1440
Manufacturer:
Model:
Refresh Rate: 59

Yes this is reproducible with Krita 5.0 please report this bug to bugs.krita.org with the steps that you mentioned.

1 Like

With Windows 10 and Krita 5 BETA 1 I can go to the maximum of 30 possible subdivisions without crashing it. In any of the 3 possible modes.

Michelist

With the Aug 29 5.1.0-prealpha appimage, I can only get a crash with the Anchor Strength set to Strong(Rigid), at 12 subdivisions.

Done

https://bugs.kde.org/show_bug.cgi?id=441826

2 Likes

I think that the slider issue may be related to the redesign I made of the widget. Maybe the single step (the amount that the value changes when the arrows are clicked) is set to a big value (the default) there and being bigger than the range nothing happens. I’ll check it tomorrow.
I also think that this options panel needs some improvements (alignment, bigger flexibility slider).
@yetanotherpainter and others: what do you think would be a good increment for that slider? 1?

Do you mean the step size of the flexibility slider? It already has 0.1 steps. But a slightly larger slider would be good, then you can also see your arithmetic tasks in it :wink:
Or did your question concern the subdivide steps? If you want an even finer division there, I would not go beyond 0.1 steps. At least for me, that would be completely sufficient.
But I am not sure if I have properly grasped your question.

################

And in case anyone else is interested:
Have now tested 5.0.0 beta 1 e5fda5c on Windows 10 several times out of curiosity and I have not been able to crash this version either.
Then I got even more curious, and on attempts with the 4.4.8 Krita froze the first time, in the 24th run, however I had not freshly restarted Krita then, as I had edited another image before, but it was no longer loaded in Krita when it froze. In five further attempts with 4.4.8, for which I restarted Krita each time and also always created a new test file, I could no longer get it to freeze or even crash.

Michelist

I think 0.1 is pretty good setting (version 5.0).
So if I set flexibility to 5 and I want to fine tune it (meaning to do slight adjustments) I can click one or two times and get slight offset. I would leave 0.1 as it is right now.

In terms of input fields improvements I would look further. There are some input fields that I can use sliding and there are some is not. What would be great if all input fields were unified and had same behavior.

I like input fields in Blender there you can slide and if you hold Shift the slider will move much slower what gives the ability to finer control. :slight_smile:

In terms of steps for subdivision I think it makes more sense to live steps as 1. It makes more sense to have grid 3x4 than grid 3.3x5.4 - never seen this kind of thing really. At least in user interface (for calculations maybe - but user does not have know about it)

Ok forget that I said that input fields are not unified. They are pretty much unified. Though in “Select a Color” there are different type of input fields.

Would be nice to have sliding there too. :slight_smile:
Basically revision of all input fields and making them all the same. That is my point. As an opinion :slight_smile:

Ok, sorry for the confusion. I see that the slider works right on 5.0, which for some reason I thought you were using in the little video.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.