@mikhailvorontsov yeah the history one doesn't seem to do anything, i think, but it also means that file recovery does not work. i mention this in my docs
@mikhailvorontsov The bug seems to be non-deterministic, but if I open a lot of files and simply select random scatter brushes, it happens with high frequency. Even opening up the brush texture setting might be enough to trigger it, because it has to load all of the textures to preview them.
@mikhailvorontsov well, like i said, vmulti and windowsink should not be necessary for linux. i didn't need it, but you have to set the tablet into 'artist mode' in OTD if you want pressure to work natively.
@mikhailvorontsov after all this talk i actually went back to the windows VM because working on a doujin was making that many-file issue show up more frequently. in virtualbox you can pretty quickly share a linux folder with your windows machine too. it's possible with qemu too but i find slightly more annoying to configure
@mikhailvorontsov no problem. it seems like your configuration is vastly different from mine, because that doesn't sound like anything i had done. i also built OTD from source since i made modifications to it. i'm also using nixos which comes with a different set of issues.
@mikhailvorontsov vmulti is for windows ink, as you guessed. it's not needed for linux. on linux you have to either run the daemon manually, and then the GUI tool, or if you installed it via your package manager, there may be some configuration that makes it run automatically, like with systemd
@mikhailvorontsov I find they each have their share of pain points, but I switched to linux with the coming of W10's end of lifetime and microsoft's obsession with the "AI OS". They just make it increasing more of a turn off over time.
@mikhailvorontsov ah, i only remember shortcuts if i use something enough, but end up just using the search tool often (F3 with your mouse on the appropriate panel)
@mikhailvorontsov Yeah, I love SAI, been using it for a long time. I think there would be a lot of work getting it to work natively on Linux, because it seems like it depends heavily on Windows GDI to render all of the UI. Not a fan of Krita because of UI/UX issues. Many things that feel like they should be 'close by' are always extra steps away. I feel like Blender has gotten a lot better after getting funding.
@mikhailvorontsov Looking back on this, I had actually gotten SAI working fine with virtualbox with less lag, and trying with qemu again, I ran into issues with SAI being unable to get a system identifier. One other minor annoyance with virtualbox is that the USB redirection stuff was closed source and virtualbox had to be recompiled each update in order to use it.
@mikhailvorontsov I think you'll be able to get it working. It is risky sometimes depending on what you use in SAI because it can freak out badly when wine's internals are not behaving. When I gather enough data about SAI's issues, I'll probably submit a bug report to WineHQ, but I'm not hopeful on it getting fixed anytime soon..
@mikhailvorontsov I think a lot of XP-Pen tablets are already supported, and if yours is not, then you can ask on the OTD Discord for a new config to be made for your tablet, which is probably a simple addition. Are you using virtualbox to run your VM? I had issues getting the GPU to work with that as well, but I think I had more success using virt-manager with qemu.
@mikhailvorontsov Yep, it runs with wine, and pressure works, but you may need to use OpenTabletDriver. I use a very old Cintiq (DTK-2200/K) and I had to add support to OpenTabletDriver myself to get it working. You should be able to run in a VM without performance issues if you have full virtualization enabled for your CPU (AMD-V or VT-X, must be enabled in the BIOS), and give enough processing power to the VM.