Clip Studio / Manga Studio -- Pausing Problems?
10 years ago
I'm having some odd issues with Clip Studio on my desktop here.
Every now and then, while I'm in the middle of drawing something, everything will just... stop... for a couple seconds. And then start moving again. It's just enough to completely throw me off my flow. The frequency it happens at can be anywhere from about once every half hour to ALL THE FUCKING TIME. It's so frustrating.
This doesn't happen in other paint programs (Sai, Photoshop, etc), so it's not a system-wide problem.
This can happen weather I'm using the pen or the mouse, so it's not a Wacom problem.
This doesn't happen on my much lower-spec laptop, so it's not a resource problem.
Anybody have an idea what could be going on here? I'm flummoxed. :T
Every now and then, while I'm in the middle of drawing something, everything will just... stop... for a couple seconds. And then start moving again. It's just enough to completely throw me off my flow. The frequency it happens at can be anywhere from about once every half hour to ALL THE FUCKING TIME. It's so frustrating.
This doesn't happen in other paint programs (Sai, Photoshop, etc), so it's not a system-wide problem.
This can happen weather I'm using the pen or the mouse, so it's not a Wacom problem.
This doesn't happen on my much lower-spec laptop, so it's not a resource problem.
Anybody have an idea what could be going on here? I'm flummoxed. :T
FA+

Try killing off everything you don't need to see if it's a confliction. Exit dropbox, web browsers, bluetooth, etc etc down to the bare bones if you have to.
Also if you have regular wired gear your mouse may have an issue where it thinks the user is making motion when it's just sitting there which can screw with wacom input, see if having just one device attached helps.
Eh, maybe I screwed up the config somehow? I guess I should reinstall Clip Studio and see what happens.
You may have bad memory. What can happen is most programs use a tiny amount of system memory that is found in newer computers and everything works just fine until a program tries to use more memory then what you use normally and the errors start showing when it tries to use memory it thinks is available but isn't.
I did just uninstall and reinstall Clip Studio completely and then did some sketching, and it happened twice during that.
http://nanimoose.furryhome.com/stuff/spike.png
I'm gonna dig down into the Resource Monitor and see if I can narrow it down more.
My first reaction would be to use Process Monitor (from Mircosoft's web site) to capture the specific network addresses the application is trying to reach. I'd then add those addresses to my hosts file and test to make sure the application still runs. Many companies use different servers for telemtery and license checks, so by blocking only the addresses that are causing pauses, usually the application will still work normally and can still download updates. It's a better option than completely blocking the application in the Windows firewall.
Wireshark is great for packet inspection to see what is transferred, but I haven't figured out how to use it properly, yet.
I wish I could investigate this, but my Intuos 1 tablet is way too old and doesn't work with the latest drivers. The newest driver I can use is 6.1.5-3, though that one causes massive lag due to constant disk access, so I'm currently using 6.1.2-5. I've known for a while that Wacom drivers are logging your every move and constantly writing to disk, and this is why people have so many lagging issues with Wacom products.
Did you try some of the 3d functionality? It seems to happen more if I make use of it.
SOLUTION:
This turned out to be some sort of loose or short circuit in my motherboard's network card. This problem actually got worse over time, and eventually started having more obvious effects (like the network cutting out and reconnecting randomly, several times over the course of a day). I eventually disabled the LAN functions on my motherboard and instead started using an external USB-to-RJ45 network input, and this seems to have fixed this issue. I don't know why this affected Clip Studio so much more intensely than any other software I run, but boy howdy it did.