Ja, auf Level 4 kann ich das mit 1 sec Pause auch reproduzieren.
Ist schon erstaunlich, was man bei diesen Engines alles beachten muß ...

__________________
Meine Webseite: https://fhub.jimdofree.com/

Irgendwie bin ich nun wieder etwas beruhigt

Edit: Es scheint noch ein Problem mit e.p. zu geben, Sensor Chess mit Weiß:

Hallo Alex,
ja, Enpassant funktioniert ja bei einigen Engines nicht richtig - ist leider auch nicht so leicht zu testen bzw. zu lösen.

Beim Sensor Chess hab ich es jetzt aber doch hinbekommen - neues Plugin ist im Anhang.

Grüße,
Franz

__________________
Meine Webseite: https://fhub.jimdofree.com/

Hi,

jetzt ist auch noch ein Problem im Plugin für die AVE ARB-Module aufgetaucht, daher hänge ich hier nochmal ein komplettes CB-Emu_Update mit allen Änderungen und Bugfixes seit dem letzten offiziellen CB-Emu_Pro an (dieses Update gibt's auch in meinem Download-Folder).

Edit: CB-Emu_Update erneuert (28.5.)!
In MessNew wurden nicht alle GGM-Module angezeigt (Hashfiles arb.xml und ggm.xml korrigiert, ROM-File gms40.zip in gms4.zip umbenannt)

Grüße,
Franz

__________________
Meine Webseite: https://fhub.jimdofree.com/

Krypton Regency ist jetzt emuliert, danke an Berger fur dump usw.

I have a question for you Mess Experts and let me know if I am doing anything wrong.

I wanted to test Mephisto II on Level A3 and thought I would do a shortcut by just entering the FEN to the Start Position and then hit STA to start the calculation and I noticed differences to entering the moves directly into Mephisto II using ENT button and then use STA to start calculating and using Mess Winboard with "Paste FEN" and enter STA on Mephisto II.

This is the Test start position:



These are the results:

Mephisto II (Set1)

1. e4 e5 2. Nf3 Nc6 3. Bc4 Nf6 4. Ng5 d5 5. exd5 Nxd5 6. Nxf7 Kxf7 (START)

MessChess using key entry and STA Key
3.579 Mhz = 15 Seconds 7.e1-g1
6.144 Mhz = 8 Seconds 7.e1-g1

MessChess using Winboard and FEN and STA
r1bq1b1r/ppp2kpp/2n5/3np3/2B5/8/PPPP1PPP/RNBQK2R w KQ - 0 7

3.579 Mhz = 31 Seconds 7.Qf3
6.144 Mhz = 18 Seconds 7.Qf3

Mephisto II (Set2)

1. e4 e5 2. Nf3 Nc6 3. Bc4 Nf6 4. Ng5 d5 5. exd5 Nxd5 6. Nxf7 Kxf7 (START)

MessChess using key entry and STA
3.579 Mhz = 13 Seconds 7.e1-g1
6.144 Mhz = 8 Seconds 7.e1-g1

MessChess & CBEmu using Winboard and FEN and STA
r1bq1b1r/ppp2kpp/2n5/3np3/2B5/8/PPPP1PPP/RNBQK2R w KQ - 0 7

3.579 Mhz = 31 Seconds 7.Qf3
6.144 Mhz = 18 Seconds 7.Qf3

I have tried CBEmu, MessChess, MessExtra and MessNew and they all seem to work correctly when entering the moves directly into Mephisto II (Set 1 & Set 2).

It is only when I try to use CBEmu or MessChess with Winboard that I get the discrepancy.

It may not seem important but in actuality it is, as there can be big difference in strength of the move it plays since more time generally means stronger move as in this example. It's the difference between winning and losing a game:

Let me know if I am doing something wrong or if there is a way to use a FEN where it correctly follows the time as per the original modules.

Also, if this is a Winboard problem can this difference also apply with other ROMs. If yes, then I will have to continue to manually enter the moves to a start position, when using Mess.

Best regards
Nick

Hi Nick,
well, there's an important difference between entering a move sequence or entering the resulting position, and this difference is castling rights!

Among all the hundreds engines in MessChess I only remember 1 or 2 which allow entering castling rights when entering a position, and so this option is not implemented in any plugin (for WinBoard or Arena).
IOW, from your FEN string (in WinBoard) only the following part is used in the plugin (and entered in the engine):
r1bq1b1r/ppp2kpp/2n5/3np3/2B5/8/PPPP1PPP/RNBQK2R w

So it's just the engine's decision, whether it accepts (or makes itself) any castling moves depending on the positions of the king and rooks.

Regards,
Franz

__________________
Meine Webseite: https://fhub.jimdofree.com/

Hi Franz

Thanks, so you think the problem is castling rights, which also adds the extra search time? (13 seconds to 31 seconds). Unfortunately, with FEN's there are loads of positions where castling remains an option. So, I guess I skip FEN's and just do the manual entry if I am testing games.
No complaints Mess ROMs work, it just would have been a time saver with my tests.

Are speed ups reliable will I get the same moves at 300% as I would at 100% or is that also inconclusive? I am looking for ways to shorten time without compromise.

Regards
Nick

Yes, I'm quite sure that castling rights are the reason for this difference.
But it depends on the engine: some engines may always allow castling (after a position setup) when the king and the rook(s) are still in their original positions, others may not.
As long as your computer is powerful enough to run the emulation with the speed value (x%), you will indeed get the same moves.
You can check this with 'Options > Show FPS' (or key F11) in the engine window: if the value in the upper right corner is about the same as your speed value (x%), then the emulation is correctly running with this speed.

__________________
Meine Webseite: https://fhub.jimdofree.com/

Hi Franz,

Thanks, I will try it. Also, I will try a couple of other positions that don't involve castling to have peace of mind of when to use Winboard.

Regards
Nick