Winboard Forum

Known Issue in this Eden 0.0.10c (which was released "quietly" because the bug fixed concerned only analyzing in UCI, which few people besides myself will use):

In WB, "force" mode doesn't work properly (Eden just ignores it and thinks it is in non-force mode). That will lead to the following events:

WB: force
...
WB: e2e4 [Eden starts thinking already, when it shouldn't, and immediately returns the book move, e7e5]
Eden: move e7e5
WB: go
Eden: [will start thinking about this new position, and return Nf3 from the book] move g1f3
WB: : move g1f3
Ignoring move out of turn by second, gameMode 5, forwardMost 2
..and it goes downhill from there

This occurs in WB (and not all versions of it? => varying reports whether it works or not) only, not in Arena, as Arena doesn't set force mode.

Workarounds: Use Eden in UCI via Polyglot, or somehow disable force mode in the GUI.

It would be nice if someone could find out exactly when this occurs; it'll get a fix out sooner (because then I won't have to do three things concurrently).

Nicolai Czempin wrote:Known Issue in this Eden 0.0.10c (which was released "quietly" because the bug fixed concerned only analyzing in UCI, which few people besides myself will use):

In WB, "force" mode doesn't work properly (Eden just ignores it and thinks it is in non-force mode). That will lead to the following events:

WB: force
...
WB: e2e4 [Eden starts thinking already, when it shouldn't, and immediately returns the book move, e7e5]
Eden: move e7e5
WB: go
Eden: [will start thinking about this new position, and return Nf3 from the book] move g1f3
WB: : move g1f3
Ignoring move out of turn by second, gameMode 5, forwardMost 2
..and it goes downhill from there

This occurs in WB (and not all versions of it? => varying reports whether it works or not) only, not in Arena, as Arena doesn't set force mode.

Workarounds: Use Eden in UCI via Polyglot, or somehow disable force mode in the GUI.

It would be nice if someone could find out exactly when this occurs; it'll get a fix out sooner (because then I won't have to do three things concurrently).

On the other hand, it may just be a spurious bug report. Please let me know if any of you can reproduce the problem, in version 0.0.10c or 0.0.10b.

Nicolai Czempin wrote:

Nicolai Czempin wrote:Known Issue in this Eden 0.0.10c (which was released "quietly" because the bug fixed concerned only analyzing in UCI, which few people besides myself will use):

In WB, "force" mode doesn't work properly (Eden just ignores it and thinks it is in non-force mode). That will lead to the following events:

WB: force
...
WB: e2e4 [Eden starts thinking already, when it shouldn't, and immediately returns the book move, e7e5]
Eden: move e7e5
WB: go
Eden: [will start thinking about this new position, and return Nf3 from the book] move g1f3
WB: : move g1f3
Ignoring move out of turn by second, gameMode 5, forwardMost 2
..and it goes downhill from there

This occurs in WB (and not all versions of it? => varying reports whether it works or not) only, not in Arena, as Arena doesn't set force mode.

Workarounds: Use Eden in UCI via Polyglot, or somehow disable force mode in the GUI.

It would be nice if someone could find out exactly when this occurs; it'll get a fix out sooner (because then I won't have to do three things concurrently).

On the other hand, it may just be a spurious bug report. Please let me know if any of you can reproduce the problem, in version 0.0.10c or 0.0.10b.

No, it's definitely not spurious. However, it is a "Heisenbug", not always reproducible; depending on timing. Restarting will usually make it go away. It will be fixed in the next release.