I just installed Krita for the first time today (version 2.7.8.13 x64) . I'm using a Surface Pro running 8.1. I started Krita up immediately after install and had some issues. The stylus was working as an input device for the computer, not quite so well inside Krita - it was rapidly flashing a red no symbol under the stylus point. I thought, "maybe it needed to restart after the install." I restarted the computer and immediately started up Krita again and no more input device. It completely stopped functioning, not just inside Krita, but for the entire computer! I'll probably figure out how to get it back up and working eventually, but it's increadibly frustrating to have a piece of software completely mess up an input device.

As a side note, inside device manager I have one unrecognized device, not sure what that is or if it's related, and wacom under HID is functioning fine. If anybody has any insight into this issue - what caused it and/or how to fix it - I'd greatly appreciate it.

Installing Krita cannot break tablet input system-wide -- that's technically impossible. There is no way Krita can touch system components. Krita also cannot support the Surface Pro, since the Surface Pro uses the used-to-be-deprecated eInk api to communicate with the digitizer, not the more generally used Wintab driver. However, if it's like the Lenovo Helix, and there's a Wacom Wintab driver available as an after-market install, it might work. But on the Helix, I need to reinstall the Wintab driver pretty much every other time I want to use the pen since it's very unstable and after a reboot tends to limit the input area to the top-left 64 pixels square...

On the Helix, you also need one of the new Wintab experimental installers of Krita, because the .13 version isn't compatible with the high-res events the Helix sends out.

Thanks for the quick response.

I restored to a point before the Krita install, then reinstalled, and everything seems ok in regards to my stylus functioning. However, the stylus cursor is still rapidly blinking a no sign, a red circle with a line through it, about 20 times a second. It won't let me start a line most of the time, but if it does start one, I can draw until I lift my stylus without issue (it's super responsive too!). You mentioned hi-res events and and experimental wintab installer. I have no Idea what hi-res events are, where to find that installer, or if that is related to the blinking no sign at all. I'd appreciate it if you would enlighten me on those topics.

Thanks,
Matt

PS
I don't like this forum software. I had a response all typed up and good to go, but my account timed out so it made me log in again but ditched my entire post.

Ahah! I found your topic on the new wintab support here. I ended up going with build 2.7.8.23. Installed it and it works BEAUTIFULLY. You do awesome work!

@mmichalka: The forum will only timeout your user session if you have been inactive for at least an hour - I would suggest checking the "Remember Me" box when logging in to ensure your session remains alive.

Thanks for letting me know about that. Hopefully that will stop me from having forum issues in the future.