6/22/2023 0 Comments Artrage 4.5 windows 10 glitch![]() Looking at Lenovo's site there is a Wintab driver specifically for the device you are using: There may still be a problem with the RTS input however even in this case. Restart ArtRage and see if that helps (apologies if you have already done this). The first thing to do is make sure that you have tried turning off Realtime Stylus and making sure Wintab is turned on in the Preferences panel's Input section. In cases where apps only support Wintab (which is fairly common, as not many apps have implemented the current RTS standard) those apps may work fine, but if the Wacom Feel driver is causing collisions between Wintab and RTS, which has been known to happen, it may cause problems for apps that support both. The Wacom Feel driver is generally used where a device does not do Wintab natively (being an older standard and not the MS suggested standard for screen input devices) and as a generic driver it may not work properly with some devices. Please let me know if this clarifies something or if I should really move this discussion into an email to support. This makes it hard to put little quick details and breaks my confidence in my stroke. SAI responded flawlessly while ArtRage hesitated for a moment every time, resulting in a significant gap. In both cases I tried to start my vertical lines at exactly the horizontal line. To illustrate here are two drawings, one in SAI and one in ArtRage, done on the same tablet, same driver and everything else, within few minutes between the drawings. It's a delay between pen touching the screen and line starting to appear, in that order. Now the main issue why I even started experimenting with disabling Tap-and-hold. Buttons in tool windows (like Don't Save in exit confirmation) cannot be tapped when tap-and-hold is disabled. ![]() Moving tool windows slows to a crawl in few seconds when tap-and-hold is enabled, and cannot be moved at all when tap-and-hold is disabled. I've just upgraded to the latest driver version 7.3.2-12 which made no difference at all. These are equipped with limited Wacom hardware controlled by Wacom Feel driver, us./en/feeldriver/. I'm using ArtRage 4.5.10-64 on a Lenovo ThinkPad 10 running Windows 10. Has anyone else reported this behavior? Is there anything that I can do to fix it, or is it out of my hands and a bug in the program?įirst I want to make sure that you know what my system is. I've tried uninstalling and then reinstalling it but it made no difference. I don't experience this behavior anywhere else within Windows, so I think it is a bug with ArtRage. ![]() If I recall correctly, it only started up sometime within the past few versions. This is a relatively recent behavior, I believe. The only things I can do with the stylus without the program hanging up is, as I said, selecting a tool or color, or drawing on the canvas. What I did for this screenshot was open the tool settings dialog and then use my stylus to attempt to drag it somewhere else on the screen. In it you can see the program using 29% CPU time and Windows indicates it is "Not responding". I took a screenshot during one of these occurrences. Eventually it will settle back to normal, but the action I made with the stylus may or may not be registered (not sure what criteria makes it register or not). What happens is if I open a window like the preferences dialog, or tool settings, or even click "Check now" when asking whether to check for updates, if I use the stylus to do this, the application's CPU utilization will spike to close to 30% and the whole program will hang for several seconds. Everything works relatively perfectly except when I try to use the stylus to interact with the UI in any fashion, except in cases of picking a tool or color. I'm using ArtRage 4.0.6 on Windows 8.1 with my Surface Pro 2.
0 Comments
Leave a Reply. |