I also have a copy of pro motion ng on steam but I couldn't find yet any option to switch the tablet api used, but pro motion ng does detect my pressure. I'm Attaching a screenshot of the tablet api options in krita for reference. Where do I find the dll my tablet uses? If it just replaces /c/Windows/System32/WinTab32.dll, them my md5sum is e8b6ce4f168bf38255a5d3ccbb1e36a3 I was using wintab on krita, wich is the default option, but I was surpised to see that using win8 pointer api (windows ink) also works on krita.
#Aseprite vs pro motion software#
I dont know what other software I can test this. The pressure does not work with the win8 pointer api on aseprite, but it does work at least on krita.
#Aseprite vs pro motion drivers#
I'm using the latest drivers but I'm pretty sure the the driver's quality should be as cheap as the hardware itself (I shouldn't spit in the plate I eat since this tablet has served me well for a very long time). The manufacturer site does not have a product page (at least not today, maybe it had nine years ago), only a support page whithout product info I'm using a "Genius EasyPen i405X" tablet I bought circa 2011, a very cheap (in many ways) chinese tablet which is probably not in production anymore. Sometimes loading via menu do not crash but it crashes while trying to create a new document.
The crash on start happens almost always whereas the crash via menu has a low chance of crashing but it does crash sometimes. In fact while recording the video I could'nt make it crash but later while generating the debug logs I managed to make it crash via the menu. Things like crashing while loading wintab via menu or loading wintab but pressure not working also occurred.". In my first message I mentioned that "When it started happening (.). But I realized that right after a system restart I always had this same behavior, where the normal launch fails but the launch with -disable-wintab + loading wintab via menu succeeds. Things like crashing while loading wintab via menu or loading wintab but pressure not working also occurred. When it started happening the behavior was much less predictable than just "launch with -disable-wintab then enable it on the menu". After this, the crash behavior also started occurring with my steam build even though I haven't touched the steam application directory for aseprite. It did compile successfully but crashed upon start, so I had to run this custom build with the -disable-wintab cli flag.
This started happening after I cloned the master branch and tried for the first time compiling and running from source. Previously my aseprite steam build did not present this behavior on my machine, with the same OS and aseprite versions. The following video illustrates the problem. Describe your bug report or feature request hereĪseprite crash upon launch (probably while loading wintab) but do not crash while loading wintab while the application is running.
0 kommentar(er)
