![[us]](/mwf/v12/flags/us.png "United States")
I've been using 2.2 primarily due to reports that it was stronger in some quad-core instances than 2.3.2a, but have since changed my mind.
However, now that I'm trying to use 2.3.2a.. I find that often the engine just stops working. During infinite analysis mode, when I force a move, normally Rybka 2.2 will continue it's analysis. With 2.3.2a it will sometimes crawl to a 1kn/s halt and wait for me to restart the GUI or cancel the infinite analysis and restart.
Is there a workaround for this? If not I see no reason to use 2.3.2a for casual analysis and would only use it for long overnight analysis of single positions.
However, now that I'm trying to use 2.3.2a.. I find that often the engine just stops working. During infinite analysis mode, when I force a move, normally Rybka 2.2 will continue it's analysis. With 2.3.2a it will sometimes crawl to a 1kn/s halt and wait for me to restart the GUI or cancel the infinite analysis and restart.
Is there a workaround for this? If not I see no reason to use 2.3.2a for casual analysis and would only use it for long overnight analysis of single positions.
Vas addressed this when 2.3 was released. If I remember correctly it has to do with how Rybka uses it's hash information. The GUI may show a major drop in kn/s (like 1kn/s or even 0 kn/s) but that is incorrect. Also notice that the GUI is showing a starting depth when you see the drop in kn/s.
So the engine is still analyzing away at full speed in these cases?
And if Vas addressed it, then why does it still happen in 2.3.2? Or do you just mean he talked about it.
And if Vas addressed it, then why does it still happen in 2.3.2? Or do you just mean he talked about it.
http://rybkaforum.net/cgi-bin/rybkaforum/topic_show.pl?pid=14495;hl=cosmetic
The issue was disccused at the above link - apparently it is not a problem at all - only cosmetic.
The issue was disccused at the above link - apparently it is not a problem at all - only cosmetic.
I've noticed that Deep Shredder 11 x64 also does this.
![[mx]](/mwf/v12/flags/mx.png "Mexico")
> So the engine is still analyzing away at full speed in these cases?
Check the task manager, if Rybka is using some 99% of the CPU then the problem is cosmetic.
Yes but it's not the kn/s or depth display that bothers me. It's that it stops displaying lines in the analysis window. (Sometimes it stops altogether until I force the move)
While not displaying the lines I am aware that it's still chugging away since my cpu fan is on full blast. It's jsut.. I get nothing out of it other than that I can force the move, but I like to study the lines before forcing the move or backtracking etc.
While not displaying the lines I am aware that it's still chugging away since my cpu fan is on full blast. It's jsut.. I get nothing out of it other than that I can force the move, but I like to study the lines before forcing the move or backtracking etc.
> While not displaying the lines I am aware that it's still chugging away since my cpu fan is on full blast. It's jsut.. I get nothing out of it other than that I can force the move, but I like to study the lines before forcing the move or backtracking etc.
Yes, this will happen eventually, when suddenly Rybka will not show anything for the next 24 hours.
But don't worry, Rybka 3 has that solved.
I'd cryogenically freeze myself if there was only a moderate chance of brain damage. I feel like Eric Cartman waiting for the Wii.
Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill