Wilhelm wrote: ↑Fri Jun 12, 2026 10:17 am
There are problems with a few engines when more instances a startet at the same time, eg Deep Junior 11.1a. They need 1-3 sec. to initialize and then you can start the next one. Did you eventually have an idea how I can avoid/solve this?
One more question, is it possible to save the window size and position on exit? Thank you!
I see Junior 11 is UCI so it probably does something weird, it should get ucinewgame and isready afterwards,
I don't see what problem it has, it should get a comfortable default 20sec to finish init after isready,
if it requires extra time after go then there's nothing I can do to fix buggy engines, all you can do is increase max time
(if it would help at all)
I don't see why it would have any problems starting multiple instances at the same time, but I have seen some ancient engines write files
and do some crazy things and cannot really run with multiple instances at the same time,
so I guess your only option is to either run with concurrency disabled or alternatively you might try a simple trick
to mark Junior 11 as a GPU engine, in which case it'll only allow a single instance at a time
I don't plan additional hacks to work around buggy programs
as for window size and position: no, not possible and not planned. the reasoning behind this is simple: if monitor setup changes
you may end up with a misplaced window out of bounds, unable to see it or position it using a mouse