I have been bug reporting for the past few Krita updates since the pen is now has a huge offset from the tablet. I am concerned that Krira not taking this point seriously with no actions in the past few updates. Though the responses are even stranger.

"NTrig's wintab drivers actually have a bug."
That is not true. None of my other graphic programs have this issue.
Manga Studio, Anime Studio, Sketchbook Pro 7, Corel Draw X7, Corel Pantshop Pro, ACDsee, and Inscape to name a few all track correctly.

"desktop scaling somehow messes up Krita's tablet pen calculations."
Again since all other software works correctly this has to be a flaw with Krita. (See below for evidence)

The big concern that I have is Krita keeps saying that is a problem with the surface Pro 3, when Krita 4.01.0 tracks perfectly (as reported) So 3 alpha's later the problem still exists? Seems strange that they are avoiding fixing such a premium drawing device.

The problem is that we can not figure out why this is happening, because we do not have a test-device. N-trig is quite rare as a tablet-base compared to wacom or UC-logic.(Both of which had companies deliver test-devices to the Krita foundation)

Furthermore, the maintainer, Boudewijn, has told you on several occasions he's personally going to look for this bug once he has the money to buy it.

Krita is not abandoning the surface pro 3(which is to say, fixing n-trig support is not going off the agenda), there's just no resources. It's an opensource project, and comprises of volunteers or people working for minimum wage, paid by donations and Krita on steam.
Boudewijn's comments on your bug where not meant to be dismissals, but rather he was trying to make an educated guess as to why this happened, to communicate he was not ignoring you, till the moment he can actually obtain one of these devices and start debugging.

Check if the display scaling it set to something else than 100% and if so set it to 100% and restart. Currently no Krita developer has a Surface 3 as far as I know to test.

So what changed from Krita 4.01.0?
I was tying to beta, but if nothing will be done till someone get a device then there is no point to continue.

Rob Frydyrck wrote:So what changed from Krita 4.01.0?
I was tying to beta, but if nothing will be done till someone get a device then there is no point to continue.

The problem is that I don't really know what you mean with Krita 4.01.0... The next release will be Krita 2.9, and the beta's for that are named 2.8.79.xx.
What happened, and this boudewijn tried to explain, is that we fixed a bug showing up with in uc-logic based tablets in our wintab communication, and he suspect that something went wrong there. However, until we are sure that this is what caused the problem(it could be something else entirely), and until we know how to have Krita identify the n-trig driver specifically, we can not tell Krita to do one thing for uc-logic and the other for n-trig.

If you have subscribed to this bug: https://bugs.kde.org/show_bug.cgi?id=339349 (You know the one, you commented on it, in the right column of all the bug-statistics there's an option to subscribe), you get all updates to this bug in the bugtracker e-mailed to you, including when it's possibly fixed. That's likely a whole lot less stressful for you.

At one point we fixed a scaling bug when using dual monitor setups with yiynova tablet monitors by using the 'officially' correct way of getting the desktop size from the wintab api.

If an older development build works for you, please continue using those. Note here on the forum or in bugzilla which was the exact filename of the last download that worked for you, as well as the git string from the about box. Keep in mind that these are _development_ builds, for testing. They are expected to have issues.

Besides, currently I am working on:

* PSD layer styles
* PSD transparency masks
* Resource bundles
* Multi-image, multi-window interface
* Animation plugin design

Dmitry, who did most of the the tablet support code, is working on transform masks, as part of the kickstarter feature list... And after that, there are a number of other things that need to be done before the 2.9 feature freeze.

We don't have _time_ to fix every bug right away, or even within a month! Install the last version that worked for you and then download the zipfile with the portable version of Krita if you want to try a newer version. When we fix the desktop scaling bug, it'll be in the announcement.

@TheraHedwig: The version that woks is 2.8.3 (git c49997b) (x64)
That should give you a clue what to fix.

The 4.12.0 was me mistakenly reporting the platform number, as I misread the menu.


My concern is way you keep adding new features to broken code? It makes SP uses feel like that are left behind and not want to test. I am here to test SP3 updates now. If this keeps getting put off there is little reason for me to continue at this time. Or may be come back in the spring to check in.

Rob Frydyrck wrote:My concern is way you keep adding new features to broken code? It makes SP uses feel like that are left behind and not want to test. I am here to test SP3 updates now. If this keeps getting put off there is little reason for me to continue at this time. Or may be come back in the spring to check in.

Software development is always a balancing act between adding the new features promised for the next release and fixing bugs. We do both. The desktop scaling bug on the surface pro 3 is something very specific. I can stop working on new features, but I _cannot_ fix that bug without access to the hardware, not without regressing to bugs we fixed earlier. If we go back to the tablet handling code in 2.8, we'll break Huion, Yiynova and multi-monitor Wacom setups.

I just tried to see if it was reproducible by enabling desktop scaling to 150% on my Windows 7 development system with my Wacom Cintiq tablet. It is not.

Therefore, it is not the case that Krita cannot handle Windows desktop scaling. The case is that Krita currently uses the Wintab API in a way that the NTrig drivers screw up. It is very likely a bug in the NTrig Wintab drivers that we'll have to work around.

If you or other Surface Pro 3 users, or Microsoft sends the Krita Foundation the cheapest SP3, without type cover or anything, or send the Krita Foundation the price of an SP3, I'll have the bug fixed in a day... If that doesn't happen, it'll have to wait until I've got a spare 819 euros myself to invest in this hardware. I already tried my connections to find a way to approach Microsoft for a development unit, but no luck.

boudewijn wrote:If you or other Surface Pro 3 users, or Microsoft sends the Krita Foundation the cheapest SP3, without type cover or anything, or send the Krita Foundation the price of an SP3, I'll have the bug fixed in a day... If that doesn't happen, it'll have to wait until I've got a spare 819 euros myself to invest in this hardware. I already tried my connections to find a way to approach Microsoft for a development unit, but no luck.

Uhm, maybe it's a silly question but did you try contacting microsoft directly explaining the situation to them?
The Surface branch has been particularly caring in giving sample machines to whoever needed them for review and development and listening to users suggestions, they seems to really want the surface to be a machine that works for artists...

I really am not upset that Krita is broke for Surface pro users, as I have other drawing programs. I was just helping to beta test. Still no use since there is no time for fixes to be done. I can check back next in the spring see....
I just find it odd that none of my other program have this issue, even other little programs.

Azzart wrote:

boudewijn wrote:If you or other Surface Pro 3 users, or Microsoft sends the Krita Foundation the cheapest SP3, without type cover or anything, or send the Krita Foundation the price of an SP3, I'll have the bug fixed in a day... If that doesn't happen, it'll have to wait until I've got a spare 819 euros myself to invest in this hardware. I already tried my connections to find a way to approach Microsoft for a development unit, but no luck.

Uhm, maybe it's a silly question but did you try contacting microsoft directly explaining the situation to them?
The Surface branch has been particularly caring in giving sample machines to whoever needed them for review and development and listening to users suggestions, they seems to really want the surface to be a machine that works for artists...

I wanted to, but I don't know anyone I could approach directly at Microsoft. If you have a suggestion, please contact me privately.

Rob Frydyrck wrote:I really am not upset that Krita is broke for Surface pro users, as I have other drawing programs. I was just helping to beta test. Still no use since there is no time for fixes to be done. I can check back next in the spring see....
I just find it odd that none of my other program have this issue, even other little programs.

The wintab API is big and labyrinthine, there's probably parts that are 'recommended' to use that nobody uses.

boudewijn wrote:The wintab API is big and labyrinthine, there's probably parts that are 'recommended' to use that nobody uses.

Well you certainly know much more about programming that I do. Best of luck with figuring it all out.

Rob Frydyrck wrote:

boudewijn wrote:The wintab API is big and labyrinthine, there's probably parts that are 'recommended' to use that nobody uses.

Well you certainly know much more about programming that I do. Best of luck with figuring it all out.

Thanks . I've re-pinged my contacts, and Azzart has also helped me. If we get dev hardware, I'm pretty sure we'll have a build for you with a bug fix really soon...

Hah! I still haven't got an Surface Pro 3, but I did get an Intel SDP today (a development platform), which includes an n-trig pen, and with that setup, I can reproduce the offset! Also crashes, problems with the OpenGL display, all the while 2.8 seems to work flawlessly. I'll need to setup a dev env on the device and then I can start figuring out the issues.