Mark Ingram

Thanks @Stevel05. This is the same as the other reports we've received, and we'll have a fix soon.

In July 2020, only 0.86% (and declining) of Steam gamers were on Linux.

Sounds like you're trying to save as a raster image, but you have non-pixel (vector) data in the image. You'd need to give us further details on what you're trying to do before we can really address these issues.

Do you have RightMouse configured to do something different?

@KynaMH are you using an XP Pen?

We changed the input mechanism for tablets in 1.8.4, but you can revert back to the previous logic by using the --legacy-wintab command line option.

We have no way of knowing that you have Windows Ink enabled in the driver, unfortunately. If you want to use Windows Ink, you will have to disable the WinTab driver at startup by using the --disable-wintab command line option. We have Huion devices here for testing, and we don't have issues with pressure data not being received - though admittedly we don't have your particular model. Do you definitely have a brush with pressure configured on one of the dynamics? Have you tried the Force Pressure option? A follow-up question @MrDoodlezz, what do you use the right click for? As we've changed shortcuts in 1.8.4 to no longer use right click as a modifier.

"Legacy" in the --legacy-wintab command line flag context refers to our legacy implementation (the low precision input data), not the hardware itself, though I appreciate that may be ambiguous. In the future we're going to add a preference item that will allow you to choose between: High precision input (the current default, not compatible with mouse mode, and some tablet devices such as XP Pen). Low precision input (how we previously received data, in 1.8.3 and before). Windows Ink input (for users who prefer this mode). Hope that clears things up.

They shortcut has changed in 1.8.4 to be Ctrl+Alt to make it easier to use for pen users.

Are you using Mouse Mode on the tablet? If so, this is no longer supported without using the --legacy-wintab command line option. More details here:

Hi @smallyellowbox, I think we will add an option in Preferences because adding command line options isn't great for users. In 1.8.4 we no longer support Mouse Mode without using the --legacy-wintab command line option (the reason is, we now get high precision data from the tablet, whereas previously we only used low precision data from the cursor position).

Ideally it would be off - though that would change how your son interacts with the pen. Disabling "Mouse Mode" will fix the problem as well as allowing us to receive higher precision data. The --legacy-wintab option is to allow people to revert back to the 1.8.3 way of receiving input (low precision data).

I'm not sure on an Ugee. With a Wacom you just launch Wacom Properties from the Start menu and the option will be on there.

That's how my computer is currently behaving (as expected). But, I have seen this before on a colleague's computer, so I'll see whether we can remember what steps we took to resolve this for them...

You shouldn't need to change any DPI settings on the app, we are per-monitor DPI aware (so we support DPI changes even when moving the application window between monitors). By changing the DPI compatibility level, you're effectively overriding what we have configured the application to do. Have you ever configured a custom scaling level in Windows Settings?

Hi @prof_b, has your son got "Mouse Mode" enabled?

Do you have Mouse Mode enabled?

That's exactly why I'm asking you these questions. I'm just trying to work out what the problem is, so we can fix it or suggest a solution. We no longer support "Mouse Mode" by default, so you will need to supply the --legacy-wintab command line option to prevent your tablet from supplying high precision data to the application. By doing this, your pen will act like a mouse, but with the addition of pressure data. More information is available in the FAQ here:

Hi @voom, it looks like you have some custom extensions installed (the blue glow, the buttons on all window title bars etc). The File | Open dialog is provided by Windows, but it looks like the rest of the UI is scaling properly. Have you changed any DPI settings specifically for this application?

What size brush are you using? Does it still stutter if you use a small brush?

Hi, is that "Yes" to all 3 questions?

Can you try launching the application with the --legacy-wintab option and see if that solves the problem for you? Instructions here

Hi, thanks for the report. I have 3 4K monitors here, they're set to 150%, 200%, and 250%. I don't see any scaling issues, but have heard reports of this before, so we're going to need a bit more info. Are you on Windows 10? Can you provide a couple of screenshots of the issues you're seeing?

(Until we work out a fix for this)

Hi, thanks for your feedback. A couple of points if I can: 1) We do respond to pressure input, we always have done, and we continue to do so. Normally when customers are experiencing "no pressure" on their brushes, it's because they're using a brush with no pressure controller configured, and don't have "Force Pressure" enabled. 2) The NVIDIA driver is for your GPU, not your pen, so shouldn't make a difference here. 3) We do beta test, the first 1.8.4 beta patch was available on May 4th, that's 3 months of beta testing, and we haven't had a single report of pressure not working. We always welcome more beta testers, so if you'd like to help test future versions out, keep an eye on the beta forum - https://forum.affinity.serif.com/index.php?/forum/34-photo-beta-on-windows/.