Conversation

Notices

1. M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 12:05:58 JST M.Vorontsov

   • cro

   @cromachina
   okay so i downloaded OTD, it complained about wanting dotnet-runtime which i finally installed after feeling a little sick from having to interact with something microsoft :mado_vomit:
   started otd, it complained about not finding a running daemon (which probably would autostart upon rebooting) had to search the website for quite some time until i found the command to start it mentioned in passing ("otd-daemon") :blobangry:

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 12:05:57 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     (sorry for using you as my tech support)
     after looking at that github page and the vmulti driver i decided to go for it... however, it is a *.bat file that seems to be acting as if it were inside a windows system... and the OTD (more precisely the windows ink plugin) is explicitly asking for that driver... was i perhaps supposed to create a wine(/lutirs) windows environment, install the *windows*-OTD-version inside of it, alongside this driver? i have installed the linux OTD...

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 12:05:57 JST cro

     in reply to

     @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

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 12:49:33 JST cro

     in reply to

     @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.

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 12:49:34 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     MOTHERFUCKER
     i finally figured it out
     i need to install the *linux* OTD on my machine
     i need to run *wine* (not through lutris)
     i need to install the vmutil using *wine* and then and only then does my linux OTD windowsink plugin work....

     fucking hell. all of this could have been much more beginner-friendly if one of those various wiki/faq/help/doc pages mentioned any of this ;_;

     it looks like i have sai2 running on linux *WITH* pen pressure!

     thank you so so much!

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 12:57:42 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     yeah i have yet to wrap my head around all the steps, filter out all the dead-ends and remember the proper procedure for the sake of future reproducability... you cant imagine what a huge deal this is for me. now i dont have to run a windows vm! i can alt+tab in and out of sai! i dont have to use a flash drive pass through + shutdown to move files out of my vm! (i refuse to give win10 network capabilities for file sharing to the host) and now i can draw without lag and stutter!

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 12:57:42 JST cro

     in reply to

     @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

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 12:59:31 JST M.Vorontsov

     in reply to

     • cro

     @cromachina and i dont have to spend money on a gpu! =D

     by the way, could you give me your opinion on the following: i dont feel perfectly comfortable with my drawing setup depending on some obscure, niche github hosted software... should i try and save/backup all the software necessary so i can setup all of this in the future without relying on OTD, its windowsink plugin, and that vmutil driver staying online? or am i being too paranoid? do you feel similarly?

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 12:59:31 JST cro

     in reply to

     @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.

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 13:07:33 JST cro

     in reply to

     @mikhailvorontsov yeaaah, you might want to bring up your issues in the OTD discord lol.

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 13:07:34 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     i have yet to activate this new sai instance with my certificate... after that i want to see if i have this same issue you are talking about... i remember sai ooccasionally spitting out errors on my native windows in the past... right now, sai on linux starts by throwing 3 errors talking about something "history" but nothing more... if i can, i would like to help at least reproducing the issue you are having, since you have helped me out so much

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 13:11:15 JST cro

     in reply to

     @mikhailvorontsov No clue really. Did you reboot? Sometimes udev config only updates on boot.

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 13:11:16 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     first of all ill never use discord 🐴

     second: i am trying various thing right now... i have switched off from "windows ink" mode in OTD and my pressure still works... i have even uninstalled the windowsink plugin and the pressure still works...

     it is like you said, apparently both of these are not needed in my case (a *HUGE* relief for me, i dont have to figure out how to backup niche git projects =D )

     i wonder, why didnt it work in this configuration a couple hours ago lol

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 13:16:57 JST cro

     in reply to

     @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.

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 13:16:58 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     no lol. if i can avoid it, i never turn off my computer ^_^

     my record was about 80 days of continuous up-time

     anyways, could you give me your best guess how to recreate the bug you were having? your bug report is way above my paygrade, i only understood something about memory allocation. should i try and open many large canvases simultaneously and then draw with a scatterbrush?

   • M.Vorontsov (mikhailvorontsov@baraag.net)'s status on Friday, 28-Jun-2024 13:27:29 JST M.Vorontsov

     in reply to

     • cro

     @cromachina
     opening up multiple canvases and using the scatterbrush hasnt done anything yet...
     however, on a canvas of 8000x8000 pixels drawing has no effect, and it gives a couple of errors, which seem to be of no consequence after closing that huge canvas again

     the "file history..." error is one that appears when i draw the first line on a new canvas of any size, and these errors seem to have no consequence either...

   • cro (cromachina@pawoo.net)'s status on Friday, 28-Jun-2024 13:27:29 JST cro

     in reply to

     @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