lucasart wrote:bestmove e7e6 was returned immediately, and no search seems to have been performed (or perhaps a very very fast one with no display at all). I tried go wtime winc btime binc and same thing happenned.
Octochess brings its own opening book. What you see is a book move. Either start Octochess with the --nobook argument or delete opening_book.db
UCI's OwnBook option isn't understood yet.
go depth 10 returned bestmove g1f3 ? who said that e7e6 should have been played ? the whole point of UCI is to not be path dependant and you specify the position and search conditions and treat each search as a new one.
Interesting. Looks like UCI differs from CECP here. I'll have this fixed in the next version.
quit is irresponsive
Thanks for spotting this. Will be fixed soon.
my task manager is not seeing 1.3 GB of memory consumption, so perhaps there was something wrong allocating the memory perhaps ?
Memory will only be allocated when an actual search starts, which doesn't happen for book moves.
besides, 1314 MB is really not a good choice for a default value. Use something small, like a common like 16 or 32 and think of it as a common denominator for everyone (thing Octochess should be useable on a cell phone).
It's the default for your machine, because your machine has 4GiB of RAM. The default is always a third of total available RAM.
even better is to alloc the TT at the last moment when a setoptin name Hash is issued or a go command is issued and the TT is still not allocated. this would allow it to run on small hardware and not try to alloc big memory before it is told.
Octochess allocates the table at the last moment already.