Veikk driver download being stopped






















This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Hello IkuzoJosh and welcome. Are you sure that you booted Manjaro in EFI mode? On Manjaro it would be pamac or pacman and the package names can differ. I think you are asking to solve an error, when your original problem is really different.

Safari Chrome Edge Firefox. Support Navigation Support. Close Window. Note Contact your system manufacturer prior to installing software or drivers, or requesting technical support from Intel.

Overall fantastic performance on Mac OS. If you're using Mac, you can go ahead and purchase. The tablet gets 5 out of 5 stars rating from me. Button and touchpad shortcuts work well. Pen is nice to draw with. Overall build quality is solid and design looks good. If you're using Windows, well, I can't recommend it based on my personal experience. I have reviewed many graphic tablets and this is the first time I'm experiencing so many Windows app that do not work with pressure.

I just cannot figure out what's wrong. If you have a Veikk A50, let me know if you have the same problems on Windows. Maybe it's just me. For a 10 by 6 inch tablet, that's a good price. Just for comparison, the 7. I think this pen tablet is a real Wacom killer I got it to work well in Windows after fiddling with the settings in both the driver and software. After this, everything works, including pressure sensitivity. I bought this for my daughter for Christmas and can't get it to work at all on Windows but I have no clue about technology,I will need to get some help.

Lynn Have you installed the driver from their website. Also try reconnecting the USB cable. Sometimes it's the loose connection. Does it work well with windows 10 paint tool sai?

I was wondering because I thought it would work with my photoshop, but the pen pressure was not working at all. I've been using medibang, but so far I'm not comfortable with using since Ive never painted with it. I know how to use paint tool sai and that is why I would to know if I could use it for windows I use the tablet under Windows 7 and cannot find fault with it.

Only minor niggle would be that Windows seems to sometimes lose the driver, which could be an incompatibility issue with other hardware I have installed. It's only happened twice in the last 6 weeks, and only after the machine had been running for considerable time without tablet being connected.

Rebooting solved the problem on each occasion. Gary Webb I'm also not sure what's the problem. Maybe check the Task Manager to see if the driver is still running. If so, force quite and launch the driver again create a shortcut on the desktop and see if the tablet works. Could you update me on your experience with this tablet?

I want to buy one and I have Windows 7 but from what other users have seen the tablet doesn't work very well for Windows. Anyone is welcome and encouraged to comment. Some people who have reached out already: meelash sparshjain RaSTuS The text was updated successfully, but these errors were encountered:. I just received the default keycodes for all of the devices from VEIKK, and I'll try to implement them over the next day or so.

I detailed why I ended up using these long keycodes in the blog post about button mapping, but I'd like any feedback on that as a design decision. In the meantime you can let me know if the pointer events are working properly with v3-alpha, and when I've added the mappings for all of the devices if the buttons are correctly reporting the aforementioned key combinations. Sorry, something went wrong. Now that I've looked at the button codes, the only one that I notice might cause problems is the A15 Pro.

Thanks RaSTuS Almost everything you said is expected, and I might not have been entirely clear. For the buttons, there should be a lot of debugging output right now in dmesg -w whenever you move the mouse or press a button.

You can experiment with this. The only thing that's unexpected is still the GIMP pressure Maybe some debugging with evtest and xinput test will help with that. Cheers jlam, I didn't really expect the buttons to work from reading your notes, but thought I'd try, then report back anyway.

RaSTuS26 Try again with the newest commit. I'm reluctant to implement the A15 and A15Pro buttons before getting more feedback on the Control button, but the A30 was straightforward to implement with the current system.

Same thing, evtest , xinput test , and dmesg outputs will all be helpful. EDIT: I did make sure the old driver was unloaded with 'rmmod veikk' before trying new versions of driver.

RaSTuS26 I believe you've compiled and loaded the version from the master branch -- this is the behavior of the V2 driver and what the V3 driver is intended to fix. It did make a difference, I now had 3 hid-inputs instead of 1, so something did register.

As mentioned I also made sure to unload previous driver with 'rmmod' before activating replugging A RaSTuS26 I understand that it made a difference, but it's not the latest update.

See this line : the format is different from what you're showing. Sorry if this is a stupid question, but how did you download it? Did you make sure to run git checkout v3-alpha after downloading it? Now installed latest v3alpha, will report shortly. RaSTuS26 Cheers! Now go have some fun with xbindkeys. I also realized I made a mistake with the mapping: the fourth button should map to Keypad 3 but I accidentally wrote Keypad 4. Will fix this in the next commit.

In the meantime I'll be waiting on input from sparshjain for the A15 Pro. Will play with that for a bit now. I really wonder if VEIKK performs the key mappings in hardware after sending some command to it since mapping like I'm currently attempting in this driver feels a little too abstruse, but I have no idea about the internals of the driver in Mac or Windows.

Never tried USB sniffing so most likely nothing will come out of this and this will be a spectacular fail, but who knows? Ubuntu I may not have been clear about this, but since I hadn't mapped the keyboard buttons yet for the A15 Pro or the A15, VK Pro, and VK , no events should show up in xinput or evtest yet. But there should be output for the button presses in dmesg , which is what I'm asking you for now. I see that dmesg shows events for pen events, but does it also show button events?

If it does, please annotate the dmesg output like I mentioned here. Hi all!



0コメント

  • 1000 / 1000