Paintstorm won't read Wacom AES
-
moonlitdude
- Posts:6
- Joined:Tue Jan 01, 2019 6:50 pm
I have noticed that Painstorm won't read my wacom bamboo ink pen..is there something i am doing wrong or there isn't driver support for AES? I don't have any pen pressure.
Re: Paintstorm won't read Wacom AES
last windows update do something and I've lost pen pressure on my Wacom Intuos until delete all my settings and update Wacom drivers, it's strange that stable drivers stop to works.
-
moonlitdude
- Posts:6
- Joined:Tue Jan 01, 2019 6:50 pm
Re: Paintstorm won't read Wacom AES
Thank you for telling me, Yes windows has screwed my laptop recently with their updates. I tried uninstalling and reinstalling but its not working. what drivers you specifically removed?
-
moonlitdude
- Posts:6
- Joined:Tue Jan 01, 2019 6:50 pm
Re: Paintstorm won't read Wacom AES
i want to address the issue that wacom AES for lenovo and other supported tocuh tablets that use wacom bamboo ink is not supported by paintstorm. wacom aes is not the same driver as other wacom tablets, i do not have pen pressure and it needs to be solved
Re: Paintstorm won't read Wacom AES
Older/cheaper Wacom tablets seem to be degrading in support on pretty much all OS. I use Huion and XP Pen and issues happen less quickly, but still occur.
I think the issue is because conflicting support in the standard drivers trying not to clash with all the different tablets now.
More expensive / newer tablets seem to get priority. It's one aspect of tablets that is quite annoying. Professionals usually have to keep updating to the most supported tablets. Although less supported, I've never had an issue on tablets with BSD, with or without disabling updates. but BSD is also hard to find support for, if you can even find a driver/tablet that supports it, but if all else fails and you can't afford newer devices, it may be worth looking into. I tried Linux, but disabling updates caused issues and strange bugs with the drivers and enabling updates broke my drivers. I have no tried Mac but I heard they have issues too.
I don't think this is a Paintstorm problem, it seems to happen with different programs. Windows and Linux in particularly seem to offload hooks with the drivers depending on how much your tablet freezes the system/program. Programs without the problem I think just get lucky in that they don't cause certain hard/memory faults that break the hooks. Since there can be so many different errors, the experience is going to be different for everyone's system and hard to debug if a program's developer can't produce it. I consider these issues as being in the domain of delay/throughput rather than logical errors. A program that is optimised to be fast may struggle with compensating such OS/driver delays, a program that is optimised to support driver call delays may struggle with keeping efficient/fast.
As others don't experience this, I'd consider it a system issue, not really the responsible of devs, though devs can try to optimise throughput... It may harm optimisations for users of other tablets. If PSS' devs aren't even supporting delay performance due to using more faster computers, then I'd say to keep in mind, PSS being in its early stages, is really optimised for future PCs, not slower older ones.
For example, my old PC can't support input to Chrome for some reason, then I found that using a passive USB interface fixed it. So how can I say just because it didn't work for Chrome that it was Chrome's fault for not compensating unbridged/unstable USB interfaces?
I think it's a good idea for Paintstorm to express tested device compatibility per tablet in my personal opinion, but of course PSS is still in a phase of early development and it's important for the developers to actually create the software first. But perhaps a tested support list with CPU/specs tested twinned to the tablet, least people can see if it's adequate, then later PSS can implement a compatibility scanner. Adobe Photoshop does this, though the non-auto spec is in the UX manual, and they determine what's working through heavy intense telemetry collecting versus brush response checks e.g. detecting if pressure was working. But if PSS did do this, then users can be sure that it's a problem with PSS rather than a throughput issue with their system. Even Adobe Photoshop, CSP, Corel Painter's teams fail to support many hardware issues.
In my opinion, Paintstorm is not at all at fault here or being incompetent. I am a developer myself (not for Paintstorm but more general graphic haptics) and know such levels of hardware support is not easy. The PSS team does a great job, they're not quite as staffed I imagine as some more performance-stable developers who have a lot more professional testers and many different computers to test on themselves.
Hardware support logs are a great idea, but for later versions.
But for now, when the developers do have the time, I'd like them to make a chart on their website of tablets they have tested and know work, as here clearly PSS support here has had the same issues with OP's tablet "Wacom Bamboo".
As a side note, PSS supporting the WinTab / Windows Ink better via a switch toggle would enable people to at least use bridges that allowed say Wacom based devices to input via the Windows driver, which has it's own consistent support that would take the pressure off of PSS' developers.
And non-Wacom tablets at Bamboo quality now exist for a very small amount of money, from other manufacturers such as Huion, XP Pen, as I know of, there's many others companies. I've seen people pick up tablets similar to the Bamboo for just 5 american dollars, though many go for 15-70 dollars.
Amazon enlists:
Wacom
HUION
Trust
Ugee
Genius
XP-Pen
GAOMON
Parblo
Though if the issue is your system / motherboard / power, etc, another branded tablet might not help you.
Just I find Wacom to have the worst support and not to mention overpriced (albeit the high priced Cintiqs do have 4k screens unlike many brands - though I'd argue Microsoft managed it cheaper and with lower parallax in their Surface series which is a whole computer and not just a tablet), most other brands have their own unique driver without juggling all the support like Wacom do.
I think the issue is because conflicting support in the standard drivers trying not to clash with all the different tablets now.
More expensive / newer tablets seem to get priority. It's one aspect of tablets that is quite annoying. Professionals usually have to keep updating to the most supported tablets. Although less supported, I've never had an issue on tablets with BSD, with or without disabling updates. but BSD is also hard to find support for, if you can even find a driver/tablet that supports it, but if all else fails and you can't afford newer devices, it may be worth looking into. I tried Linux, but disabling updates caused issues and strange bugs with the drivers and enabling updates broke my drivers. I have no tried Mac but I heard they have issues too.
I don't think this is a Paintstorm problem, it seems to happen with different programs. Windows and Linux in particularly seem to offload hooks with the drivers depending on how much your tablet freezes the system/program. Programs without the problem I think just get lucky in that they don't cause certain hard/memory faults that break the hooks. Since there can be so many different errors, the experience is going to be different for everyone's system and hard to debug if a program's developer can't produce it. I consider these issues as being in the domain of delay/throughput rather than logical errors. A program that is optimised to be fast may struggle with compensating such OS/driver delays, a program that is optimised to support driver call delays may struggle with keeping efficient/fast.
As others don't experience this, I'd consider it a system issue, not really the responsible of devs, though devs can try to optimise throughput... It may harm optimisations for users of other tablets. If PSS' devs aren't even supporting delay performance due to using more faster computers, then I'd say to keep in mind, PSS being in its early stages, is really optimised for future PCs, not slower older ones.
For example, my old PC can't support input to Chrome for some reason, then I found that using a passive USB interface fixed it. So how can I say just because it didn't work for Chrome that it was Chrome's fault for not compensating unbridged/unstable USB interfaces?
I think it's a good idea for Paintstorm to express tested device compatibility per tablet in my personal opinion, but of course PSS is still in a phase of early development and it's important for the developers to actually create the software first. But perhaps a tested support list with CPU/specs tested twinned to the tablet, least people can see if it's adequate, then later PSS can implement a compatibility scanner. Adobe Photoshop does this, though the non-auto spec is in the UX manual, and they determine what's working through heavy intense telemetry collecting versus brush response checks e.g. detecting if pressure was working. But if PSS did do this, then users can be sure that it's a problem with PSS rather than a throughput issue with their system. Even Adobe Photoshop, CSP, Corel Painter's teams fail to support many hardware issues.
In my opinion, Paintstorm is not at all at fault here or being incompetent. I am a developer myself (not for Paintstorm but more general graphic haptics) and know such levels of hardware support is not easy. The PSS team does a great job, they're not quite as staffed I imagine as some more performance-stable developers who have a lot more professional testers and many different computers to test on themselves.
Hardware support logs are a great idea, but for later versions.
But for now, when the developers do have the time, I'd like them to make a chart on their website of tablets they have tested and know work, as here clearly PSS support here has had the same issues with OP's tablet "Wacom Bamboo".
As a side note, PSS supporting the WinTab / Windows Ink better via a switch toggle would enable people to at least use bridges that allowed say Wacom based devices to input via the Windows driver, which has it's own consistent support that would take the pressure off of PSS' developers.
And non-Wacom tablets at Bamboo quality now exist for a very small amount of money, from other manufacturers such as Huion, XP Pen, as I know of, there's many others companies. I've seen people pick up tablets similar to the Bamboo for just 5 american dollars, though many go for 15-70 dollars.
Amazon enlists:
Wacom
HUION
Trust
Ugee
Genius
XP-Pen
GAOMON
Parblo
Though if the issue is your system / motherboard / power, etc, another branded tablet might not help you.
Just I find Wacom to have the worst support and not to mention overpriced (albeit the high priced Cintiqs do have 4k screens unlike many brands - though I'd argue Microsoft managed it cheaper and with lower parallax in their Surface series which is a whole computer and not just a tablet), most other brands have their own unique driver without juggling all the support like Wacom do.
-
moonlitdude
- Posts:6
- Joined:Tue Jan 01, 2019 6:50 pm
Re: Paintstorm won't read Wacom AES
max08 wrote:Older/cheaper Wacom tablets seem to be degrading in support on pretty much all OS. I use Huion and XP Pen and issues happen less quickly, but still occur.
I think the issue is because conflicting support in the standard drivers trying not to clash with all the different tablets now.
More expensive / newer tablets seem to get priority. It's one aspect of tablets that is quite annoying. Professionals usually have to keep updating to the most supported tablets. Although less supported, I've never had an issue on tablets with BSD, with or without disabling updates. but BSD is also hard to find support for, if you can even find a driver/tablet that supports it, but if all else fails and you can't afford newer devices, it may be worth looking into. I tried Linux, but disabling updates caused issues and strange bugs with the drivers and enabling updates broke my drivers. I have no tried Mac but I heard they have issues too.
I don't think this is a Paintstorm problem, it seems to happen with different programs. Windows and Linux in particularly seem to offload hooks with the drivers depending on how much your tablet freezes the system/program. Programs without the problem I think just get lucky in that they don't cause certain hard/memory faults that break the hooks. Since there can be so many different errors, the experience is going to be different for everyone's system and hard to debug if a program's developer can't produce it. I consider these issues as being in the domain of delay/throughput rather than logical errors. A program that is optimised to be fast may struggle with compensating such OS/driver delays, a program that is optimised to support driver call delays may struggle with keeping efficient/fast.
As others don't experience this, I'd consider it a system issue, not really the responsible of devs, though devs can try to optimise throughput... It may harm optimisations for users of other tablets. If PSS' devs aren't even supporting delay performance due to using more faster computers, then I'd say to keep in mind, PSS being in its early stages, is really optimised for future PCs, not slower older ones.
For example, my old PC can't support input to Chrome for some reason, then I found that using a passive USB interface fixed it. So how can I say just because it didn't work for Chrome that it was Chrome's fault for not compensating unbridged/unstable USB interfaces?
I think it's a good idea for Paintstorm to express tested device compatibility per tablet in my personal opinion, but of course PSS is still in a phase of early development and it's important for the developers to actually create the software first. But perhaps a tested support list with CPU/specs tested twinned to the tablet, least people can see if it's adequate, then later PSS can implement a compatibility scanner. Adobe Photoshop does this, though the non-auto spec is in the UX manual, and they determine what's working through heavy intense telemetry collecting versus brush response checks e.g. detecting if pressure was working. But if PSS did do this, then users can be sure that it's a problem with PSS rather than a throughput issue with their system. Even Adobe Photoshop, CSP, Corel Painter's teams fail to support many hardware issues.
In my opinion, Paintstorm is not at all at fault here or being incompetent. I am a developer myself (not for Paintstorm but more general graphic haptics) and know such levels of hardware support is not easy. The PSS team does a great job, they're not quite as staffed I imagine as some more performance-stable developers who have a lot more professional testers and many different computers to test on themselves.
Hardware support logs are a great idea, but for later versions.
But for now, when the developers do have the time, I'd like them to make a chart on their website of tablets they have tested and know work, as here clearly PSS support here has had the same issues with OP's tablet "Wacom Bamboo".
As a side note, PSS supporting the WinTab / Windows Ink better via a switch toggle would enable people to at least use bridges that allowed say Wacom based devices to input via the Windows driver, which has it's own consistent support that would take the pressure off of PSS' developers.
And non-Wacom tablets at Bamboo quality now exist for a very small amount of money, from other manufacturers such as Huion, XP Pen, as I know of, there's many others companies. I've seen people pick up tablets similar to the Bamboo for just 5 american dollars, though many go for 15-70 dollars.
Amazon enlists:
Wacom
HUION
Trust
Ugee
Genius
XP-Pen
GAOMON
Parblo
Though if the issue is your system / motherboard / power, etc, another branded tablet might not help you.
Just I find Wacom to have the worst support and not to mention overpriced (albeit the high priced Cintiqs do have 4k screens unlike many brands - though I'd argue Microsoft managed it cheaper and with lower parallax in their Surface series which is a whole computer and not just a tablet), most other brands have their own unique driver without juggling all the support like Wacom do.
Thank you very very much for the reply, and informing me (and anyone else reading) the complexity of solving pen driver issues. I am confident that PSS doesn't support Wacom AES (which is windows ink driver) and i am not surprised, but rather disappointing because i am a serious user of Paint storm and drawing without pen pressure is really tricky. But i guess it is alright becuase most softwares were slow to adapt wacom aes. I have a UGEE tablet but it is one of the earlier ones,the G5 and like you said, the old drivers might not be compatible. I am getting my laptop ready to be formatted. i also have tested it on another AES device so i know it isn't supported yet. But i am giving UGEE one more go.
thank you so much again for the information! i always will continue to support PSS as much as i can.
-
moonlitdude
- Posts:6
- Joined:Tue Jan 01, 2019 6:50 pm
Re: Paintstorm won't read Wacom AES
Just a current update on this subject. I HAVE NO IDEA how this happened. every 2 days i would use Painstorm. It always doesn't have pen pressure.
But today out of nowhere it started to have pen pressure. I checked the 2 other laptops and only mine still has it. which was very strange and surprising. Didn't make any changes to my laptop. but i am very happy it works now.
But today out of nowhere it started to have pen pressure. I checked the 2 other laptops and only mine still has it. which was very strange and surprising. Didn't make any changes to my laptop. but i am very happy it works now.