investigating more further:
when single eve and single sanderling = no errors at all
when two eves and single sanderling = no errors at all
when two eves and two sanderlings = propmod and/or drone windows is ignored after some time
this got me thinking that issue might be related to sanderling which is kind of not able to separate processes correctly after some time.
interestingly, when am starting fresh sanderling identify each eve proces with ease automaticaly. (different logged users)
when its broken or looks like broken and i restart sanderling its not able to identify correct process anymore, its green but selected process belong to another user, i have to select correct one manualy, then it switch and measuring correct one - but usually after a short while its behave incorrectly again.
how is even possible that instance on one user is able to see process on another one?
(maybe running not as administrator will prevent sanderling to be able to see other processes?)
thinking out loud, sorry
edit: running now three clients + three sanderlings not as administrator and seems to be ok for now. Will be observing it for a while.
note: is running sanderling not as admin still safe? cannot eve detect running non-admin processes to sent them to ccp?
ok so problem is there even not running as admin, it’s definitely better than running it as admin, but after a while modules are not read correctly, but rest of the bot is working like normally.
So definitely there is a problem with modules part.
so kind of confirmed, logged different ships with different number of modules, and sanderling which supposed to read 5modules is (even with selected correct process) switching to process which contains 3modules -> and therefor it’s not reading modules correctly then.
Still strange, but definitely happening.