That's a new one on me - I've never heard of that problem.
It almost sounds like the GUI isn't receiving move information from an engine. I'd probably check that the engines involved have been properly installed.
Arena Bug : LOOPWATCH-MOVE-ABORTED / Anyone can help?
Sort:
Arena is one of the buggiest chess softwares ever made. It is practicaly useless, but it's free to use.
May 25, 2018
0
#4
igotvishwanothing wrote:
Arena is one of the buggiest chess softwares ever made. It is practicaly useless, but it's free to use.
It has some bugs, but I still use it a lot. Overall, I'm thankful that it exists.
Engines are probably properly installed. Any engine can do this, at any moment, out of dozen engines installed.
May 25, 2018
0
#6
Cylvouplay wrote:
Engines are probably properly installed. Any engine can do this, at any moment, out of dozen engines installed.
That's a mystery to me. I guess the only thing I can suggest is to run it in debug mode until the problem happens again, then maybe send the debug log file to the developers as a bug report.
May 26, 2018
0
#7
Could you mention a few details of your Arena setup? Your operating system, Arena version, the engines used in your tournaments when getting the bug?
One thing you could try is to download the Arena Zip version. Put the Zip file in a new folder that you haven't used before, then unzip the files. Start up Arena, then create a tournament with only the default engines, and see if the bug appears.
I guess we already have the answer, as the bug appeared at some point. It wasn't there when I installed the game. That's why I was expecting a simple configuration problem. Of course I have tried to change config in many ways. And I'm not a fan of reinstalling hundreds of engines, each needing a special configuration etc... Probably two days lost 
Thanks for your suggestions. I let you know if I can try something.
Hardware: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz with 7,9 GB Memory
Operating system: Windows 7 Home Premium Home Edition Service Pack 1 (Build 7601) 64 bit
Engines concerned by the bug : ALL.
Oh forgot to update information in case someone gets the same problem one day.
Just had reinstalled a few days after my complain, saving all (two) config files in the root directory of Arena, to avoid loosing my engine installations, then moved the old config files in the new installation (it was the opportunity to reinstall on SSD - good idea, super fast loading).
Of course I feared the problem was due to configuration and would keep causing problems, but no, problem disappeared completely. No more bug after that, thanks Arena.
In my case this problem appears when i began tournament with loading starting position from pgn file, wich including fen with position, dose not start with the first move.
for example:
[FEN " 3q1k2/p2P2p1/3Q3p/1p6/8/1P3P2/P5K1/8 b - - 0 45"] this will cause an error
and this not
[FEN "3q1k2/p2P2p1/3Q3p/1p6/8/1P3P2/P5K1/8 b - - 0 1"]
Ich hatte das gleiche Problem. Der Fehler lag daran, das ich in der Konfiguration der Oberfäche das Gleiten der Figuren im Turniermodus auf sehr langsam eingestellt hatte. Ich hab mir monatelang die Finger wund gegoogelt und am Ende lag es nur an einem falsch gesetzten Hacken. Nachdem ich den Hacken bei "Geschwindigkeit" auf schnell gesetzt hatte, war das Problem sofort verschwunden. Im CCC Forum hat jemand gemeint, das dass daran liegtGUI im Wettkampf mit diesem langsamen Gleiten zu viel Zeit verschwendet und deshalb das Spiel abbricht.
Tournament games are too frequently aborted like this :
LOOPWATCH-MOVE-ABORTED - after very long movetime
LOOPWATCH currTicks:511.012 AllMovesToEndMilliSeconds:511.000
Game end: * {}
Last game finished without result in 21 moves
Anyone knows how to avoid that? The Loopwatch function may be configured or something? I found nothing of course by Google nor in the files I checked as deeply as I'm able to. The bug has become a real killer to my work on engines ELO and to my fun with engine tournament and observation/study.