Gimp 2.8.22 tablet drawing issue5/7/2023 ![]() ![]() In addition, the keyboard and mouse driven movement controls (pan, scroll, zoom) don't work until I have physically clicked on the scroll bar. TL DR: I have set up the drawing tablet to work in GIMP, but it only places dots and cannot make strokes. I feel like both of these issues are being caused by some weird active window shenanigans, but that's about as much as I can think of. ![]() Because middle clicking is the only way I would move around when using the pen tablet, this is a must-have feature that needs to work reliably. Am I missing something?Īs for the movement issues, it seems that nearly every movement command that is issued by not directly clicking on the scroll bar (Middle click to pan, scroll wheel, and zooming with ctrl) do not work until some amount of time has passed with the drawing window being active (about 5 seconds?) or until one of the scroll bars has been clicked. I tried GIMP 2.6.8, and it just worked right after installation I didn't need to change anything. The pen works in the other software I use, but not in GIMP. I have already gone into the input configuration windows and set the tablet to use the "screen" and all of the features of the pen are configured in the driver. Moving the pen around still moves around the cursor, but it doesn't actually draw. If I drag the cursor to one of the toolbox areas of the screen while holding the tablet down (like drawing), it draws a straight line from where I started to where the cursor ended on the toolbox section (I use single window mode). It seems to pick up on the pressure with which I jab the tablet with (I can place light or dark dots), but obviously I want to do more than just place dots. I can draw with the mouse, but when I put the pen on the tablet, I can only place a dot. The primary issue is with drawing I cannot draw in GIMP with the pen tablet. I'm currently using GIMP 2.8.22 on a windows 8.1 64-bit installation on my laptop with a Turcom 8" x 6" tablet connected. I've got problems with how 2.10 actually works aside from its performance, but that's best saved for a different post.There are quite a few details as to how GIMP is behaving on my computer, so skip to the TL:DR if you want a summary. However come to find out, XCF files made in 2.10 are not compatible with older versions, so I basically locked myself out of my own files unless I re-upgraded to 2.10 :/ I tried to downgrade to 2.8, and after experiencing some unexpected loading errors, finally got the older version to work. I've been using a drawing tablet to mess around on it, so I dunno if that's the problem. ![]() I could do it, but I'd spend all day doing one stupid thing, and that kind of process is completely inefficient.Ģ.10 will unexpectedly crash, and it's spiked in frequency as of typing this post. It's so slow that my main method of making new "infrastructure" to graphics is pretty much impossible in the timeframe I allow myself to work in. I've been using files upwards of 10GBs in size, so I got a feeling I'm doing something wrong I have no idea about that's not really Gimp's fault. It doesn't even have to be that large: the main file I've been using as of late is around 1000x1000px, and everything's chugging.īeyond 50-100mbs the time it takes to save is more than 7 seconds. The larger an image, the slower the program gets at doing pretty much anything. I appreciate the work the Gimp guys have done, and their contributions have allowed me to make my dreams a reality.Īnyway, this is what I've been experiencing: Also, I get the feeling some of these things have been drug into the ground, so sorry for egging the problem on if it's already been talked about. It seems like these problems are solely tied to the 2.10 version itself, but then again I'm not an expert. Also, while I had some minor grievances with 2.8, it ran pretty smoothly, and I've got a pretty good rig at my disposal. To preface this, I've gotta say that I've been using Gimp for years now, but am still a relative newbie, and I don't like getting into things associated with the subsystems. I didn't know it at the time, but that was a big mistake. ![]() So I'm on Windows 10, and upgraded from 2.8 to 2.10, and then to 2.10.2. ![]()
0 Comments
Leave a Reply. |