Upcoming feature: move animation

[abik]

An upcoming feature that was on my todo list for a while now (all my other Android games already support it): move animation.


This makes watching engine tournaments hopefully a bit more pleasant.

[pohl4711]

A really cool feature would be: slow down the engines. If we use your great app for playing on the ChessGenius Exclusive against Komodo or Stockfish, it would be great, to slow these engines down (to 1% perhaps?!), otherwise nobody has a chance to win a game (except M.Carlsen...)

Regards - Stefan

[PeterO]

Thank you Aart!

Its so great to see how your app gets better and better! 😀Thank you so much!

Peter

[Nordlandia]

Does move animation use cpu time or compromise performance, like slow down fast time controls?

[hgm]

Of course.

[Nordlandia]

Of course.

Option for turn on off will be useful

[abik]

Does move animation use cpu time or compromise performance, like slow down fast time controls?

Yes, every form of animation claims some CPU time. This will become more apparent for faster games and devices with fewer cores.

Option for turn on off will be useful

Ha! But of course, already there. I learned my lessons over the years. For every 10 people that love a new feature, there always seems to be 20 that hate it....

[abik]

A really cool feature would be: slow down the engines. If we use your great app for playing on the ChessGenius Exclusive against Komodo or Stockfish, it would be great, to slow these engines down (to 1% perhaps?!), otherwise nobody has a chance to win a game (except M.Carlsen...)

There is "Limit ELO" already, for UCI engines that support it.

[PeterO]

Hello Aart,

I love to use the personalities from the engine Rodent III.
Can I use it in your app?

Peter

[Ras]

A really cool feature would be: slow down the engines.

You could either reduce the thinking time for that engine, though that becomes difficult with very short time controls because it overlaps with the move overhead that engines subtract from the available time, and that is different for every engine.

Or set the node rate, but since you can't throttle down the CPU (I guess), the engine has to support that. UCI_Elo is not the same because it usually is also implemented by adding some kind of noise to the eval.