build 178 is up:
- fix ECO opening classification (sometimes incorrectly accepting a continuation that would happen later in the game)
- fix (and report) engine GUI info spamming; buggy engines should no longer be able to lock and freeze the GUI
(looks like Little Goliath Evolution 3.16 sometimes went into a crazy-mode infinite loop, sending info to the GUI when mating)
- remove logging "engine writes to stderr"
- limit input lines from engine to 64k bytes (ignore the rest - don't want to take any chances)
- fix: engine output is routed through a local queue instead of global
- in-memory opening moves stored in 16 bits instead of 32 bits
note: some example .bra files had mistakenly weight 1 instead of 0 for chess324 so this has been fixed in the archives as well
Myracle GUI
Moderator: Ras
-
mar
- Posts: 3125
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
-
mar
- Posts: 3125
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: Myracle GUI
build 179 is up:
- perf: process memory usage updates are much less frequent now (8x per second for visible output instead of for every engine output)
- show a messagebox when creating config folder fails (typically due to UAC on Windows when copying to Program Files)
- fix: it could sometimes happen that the output file (pgn/out) would be overwritten when initial write-open would fail; this could happen if some other process would hold the file.
so now such writes are buffered and a flush is attempted when the next game finishes or when tournament is closed;
also when a write fails it's buffered for later. up to 1000 games can be buffered per tournament if this happens
- perf: process memory usage updates are much less frequent now (8x per second for visible output instead of for every engine output)
- show a messagebox when creating config folder fails (typically due to UAC on Windows when copying to Program Files)
- fix: it could sometimes happen that the output file (pgn/out) would be overwritten when initial write-open would fail; this could happen if some other process would hold the file.
so now such writes are buffered and a flush is attempted when the next game finishes or when tournament is closed;
also when a write fails it's buffered for later. up to 1000 games can be buffered per tournament if this happens
Myracle GUI and Cheng