New engine releases & news H1 2025

[nocturn9x]

Hello there! Just notifying y'all that I've released version 1.3 of Heimdall

You can find it at the following URL (windows binaries coming soon, I promise): https://git.nocturn9x.space/heimdall-en ... es/tag/1.3

[nocturn9x]

There is a new Thread for first half of 2025...

New engine releases & news H1 2025

Oops, my bad! Moving the post over...

[nocturn9x]

Hello there! Just notifying y'all that I've released version 1.3 of Heimdall

You can find it at the following URL (windows binaries coming soon, I promise): https://git.nocturn9x.space/heimdall-en ... es/tag/1.3

[Damir]

Heimdall is very buggy engine.

If I try and play 5+0 Blitz games, engine will resign on its own with a message Engine caused exception.

If I try and set Engine to use Weirdtime control, engine will run out of time after 8-9 moves.

Not very good in my opinion.

[Gabor Szots]

Heimdall is very buggy engine.

If I try and play 5+0 Blitz games, engine will resign on its own with a message Engine caused exception.

If I try and set Engine to use Weirdtime control, engine will run out of time after 8-9 moves.

Not very good in my opinion.

Make sure you use the default value '<default>' for the eval file.

[Damir]

It does not matter what I use, the engine is not working.

I am using Fritz 19 GUI on playchess server.

[Damir]

I use the engine for online play against other engines and it is simply not working.

[Modern Times]

Heimdall is very buggy engine.

If I try and play 5+0 Blitz games, engine will resign on its own with a message Engine caused exception.

If I try and set Engine to use Weirdtime control, engine will run out of time after 8-9 moves.

Not very good in my opinion.

Would be a good idea to read the webpage for the engine in my opinion !

Heimdall is designed (and tested) to play at the standard time controls of time + increment: since I do not have the hardware nor the time to test others (like sudden death or moves to go), support for outdated/nonstandard time controls has been hidden behind the EnableWeirdTCs option. Unless this option is set, Heimdall will refuse to play either if its own increment is missing/zero or if it is told to play with a moves to go time control (this one is especially important because it is not taken into account at all in time management!): this technically means Heimdall is not fully UCI compliant unless EnableWeirdTCs is enabled, but I believe this trade-off is worth it, as it means that if it does indeed perform worse at untested time controls then the tester will have full knowledge as to why that is. If that upsets you or makes you want to not test Heimdall, that's fine! I'm sorry you feel that way, but this is my engine after all

[nocturn9x]

Heimdall is very buggy engine.

If I try and play 5+0 Blitz games, engine will resign on its own with a message Engine caused exception.

If I try and set Engine to use Weirdtime control, engine will run out of time after 8-9 moves.

Not very good in my opinion.

Would be a good idea to read the webpage for the engine in my opinion !

Heimdall is designed (and tested) to play at the standard time controls of time + increment: since I do not have the hardware nor the time to test others (like sudden death or moves to go), support for outdated/nonstandard time controls has been hidden behind the EnableWeirdTCs option. Unless this option is set, Heimdall will refuse to play either if its own increment is missing/zero or if it is told to play with a moves to go time control (this one is especially important because it is not taken into account at all in time management!): this technically means Heimdall is not fully UCI compliant unless EnableWeirdTCs is enabled, but I believe this trade-off is worth it, as it means that if it does indeed perform worse at untested time controls then the tester will have full knowledge as to why that is. If that upsets you or makes you want to not test Heimdall, that's fine! I'm sorry you feel that way, but this is my engine after all

Thanks for actually bothering with the README

[nocturn9x]

Heimdall is very buggy engine.

If I try and play 5+0 Blitz games, engine will resign on its own with a message Engine caused exception.

If I try and set Engine to use Weirdtime control, engine will run out of time after 8-9 moves.

Not very good in my opinion.

Hello there,

Heimdall is not designed to play at sudden death, so you experiencing this type of behavior is exactly why the weird time control option exists

Heimdall's time management is built around the assumption that increment will be present, and so I test at those conditions only. The fact that the engine is timing out is not surprising to me. Are you experiencing any other issues besides the ones related to timeouts? I do absolutely want to fix any bugs that you may have found!