Wacom tablet behavior #133
Comments
|
From AaronBPaden on July 11, 2012 22:43:03 Tested on my Linux machine, and it works fine. Must be a Windows specific issue. |
|
From davidcapello on July 12, 2012 04:55:42 Hi! I've a Wacom pen, but it will be really hard to get a tablet to test this. If I prepare several special version (to log messages/events/behavior), would you like to be the beta tester? Owner: davidcapello |
|
From AaronBPaden on July 12, 2012 11:06:24 Sure I'd be happy to, but I don't have a Windows machine at home (my "main machine" is Linux, first post was a typo). I wont have a chance to look at it for a couple of weeks, I think. |
|
From AaronBPaden on July 19, 2012 00:06:04 An update: I'll be able to test a build next week if you want me to. |
|
From grizzlys...@gmail.com on August 09, 2012 02:57:28 I would be happy to help as well. I have a Windows machine + Wacom tablet at home. |
|
From bebert55...@gmail.com on February 21, 2013 10:34:12 I'm really interesting to test this feature, any builds are downloadable ? |
|
From davidcapello on April 17, 2014 13:19:33 Issue #218 has been merged into this issue. |
|
From davidcapello on April 17, 2014 13:20:25 Issue #281 has been merged into this issue. |
|
From davidcapello on April 17, 2014 13:20:56 Issue #332 has been merged into this issue. |
|
From davidcapello on April 17, 2014 13:21:09 Issue #383 has been merged into this issue. |
|
From davidcapello on April 17, 2014 13:23:47 Status: Accepted |
|
From davidcapello on April 17, 2014 18:27:21 Someone want to test a possible fix for this issue? I've a new beta available, please send me an email if you are interested. |
|
From davidcapello on April 17, 2014 18:33:18 Related commit: dd2ce20 |
|
From davidcapello on April 28, 2014 21:43:26 Fixed. Status: Fixed |
|
Has this bug reappeared, because I'm running into something very similar on 1.13 and beta7. |
|
@sam-baker what operating system are you running? windows? macos? what specific OS version? I don't have other reports about this on 1.1.13 or beta7 |
|
Windows 10 with Wacom Bamboo tablet. There is a momentary pause when the stylus touches the tablet. The length of the pause seems to be related to the distance the stylus travels, rather than the time spent pressed down. It appears to act the same at close magnification as far, except that it's more noticeable when zoomed out because that pause covers more real estate on the screen. I'm including a gif of the behavior http://i.imgur.com/fM21zcC.gif I tried to keep the motion fluid so you could see when it freezes. |
|
I've had this problem with Bamboo and Cintiq tablets before with other graphics programs, and found it to be a problem with Wacom's settings. At the time, I found a solution with the same instructions as this issue report, although this is not the exact solution I used (it was a long while ago, so..). Anyway, you might give this a try if you haven't done something like it already. Hope that helps! |
|
@oceanhahn Thanks. Those settings were already set, though. I've also check the behavior in few other graphics programs like photoshop, and it only happens in aseprite. |
|
@sam-baker some time ago people had issues with Wacom tablets, but they were related to the "old backend", some possible solutions are in the FAQ: https://www.aseprite.org/faq/#i-have-a-lag-using-my-pen-is-there-any-solution Anyway, are you using the regular |
|
@dacap That was it. Thanks. Option in the Wacom properties called Use Windows Ink in the mapping properties. |
From AaronBPaden on July 10, 2012 05:35:29
ASEPRITE behaves strangely when using a Wacom tablet. UI buttons require a "double-tap" be activated. Drawing tools are the same way. You have to press down twice to get the pixel to change. If you press down and drag (say with the pencil or line tools), it will eventually register, but not for a pixel or several depending on what scale you're working at.
This is testing the Windows version. I'm with my main machine right now, but I'll be able to try it out on Linux later in the week to see if this is platform specific.
Original issue: http://code.google.com/p/aseprite/issues/detail?id=133
The text was updated successfully, but these errors were encountered: