Hi Roland

Thanks for the continued development of Eschecs - it really is an excellent app

@FB_Numpty The bug that you reported is fixed (please download the new files here ). Great, thanks for fixing so quickly - downloaded! Your engine looks great! I downloaded it here and will study it. Thanks, though this is a very old version from FB 0.15 - and the eval is buggy. It isn't the versio...

Hi Roland Many thanks - this is an excellent piece of work - love the gui and it is great to be able to use Velena again. I played a cheeky couple of games with my own console based engine: ****** L I N X 1.0 ****** 1 2 3 4 5 6 7 ------------------------- O O - O X X X ========================== X X...

I've been playing around with the latest Numpty version and played a lot of test games against self and range of opponents. I've found a few bits and bobs: I've fixed the problem with the crashes on piece promotion - think this is due to different handling of promoted piece in different gui (remembe...

Re my earlier post, here are code changes/additions for implementing the draw function: In Sub CommandLoop: sTemp = "feature myname=" + Chr$(34) + "NoMega-14/04/23" + Chr$(34) + " sigint=0 sigterm=0 reuse=0 analyze=0 setboard=1 draw=1 name=0" 'added draw=1 28414 and: EL...

First thing what comes to mind is that the error look's identical to some error's I have found. When the program can not process the info that it receives or it sends info that the other side can not process this can lead to a forfeit on time. I tested the move generator on some positions to depth ...

Well I've given the latest version a good run out at various different time controls against a range of different opponents and average elo gain seems to be around 90 - 110 which is not too far from your results. This would be consistent with the spped gain achieved. I tested this over a few sample ...

Many thanks frisian! - I've got a gauntlet going with x64 compile and will have a look at the latest code. One thing I think might need looking at is some of the move break time parameters - the existing values were the result of a lot of testing, but of course these were based on the typical speeds...

Thanks frisian, results equate to elo difference of between 100 - 130 which is pretty much what I expected and hoped for (perhaps not surprising given the speed difference that performance was relatively better at the bullet time control). Please could you post up the latest development source so I ...

Ok, in looking at the fix_depth issue you raised, I found a problem which probably still exists in your latest development version. If you set fix depth search for anything above 5, Numpty will move instantly and not search to the required depth. To correct this, in addition to the change you mentio...

The tournament has finished and the result was Nomega won 552 times and Numpty_DD won 448 times, 122 games ended in a draw. Numpty_DD had 18 forfeits on time (all with white ???) Well, this looks good for the new version - i am surprised about the number of Numpty_DD losses - I haven't seen this le...

Thanks again frisian, well spotted - some of these things happen so rarely it can be difficult to identify not only the problem but the cause. In hindsight, the issue with root = 0 would explain the odd instance where Numpty would lose on time in the endgame in cases with few moves available - I had...

I don't think that result is that bad, (I assume that they had 60 seconds for 60 moves) the speed difference does not make that great impact if the timing is very small. Since both have the same evaluation routine there not much difference between them. If the time per move gets greater NoMega gets...

Hi frisian I have (hopefully) solved the castling problem, I added code that store and place back the values of w_cas and b_cas. Good work, seems to be case - latest version now solves 'KiwiPete' perft test I posted previously - interesting fix references w_cas & b_cas which are the actual castl...

Just finished another 50 game match under the same conditions - NumptyDD wins by 30:20 - so it seems there still some other things that need to be resolved but at least there were no illegal moves or time losses in these games. 50 games isn't a big enough sample to form a view, and 500 is better th...