Myracle GUI

[tttony]

it's fixed now

I dont have wayland, I know X11 is buggy

Keep the good work! it's nice to see chess GUI still in development

[mar]

awesome, thanks for reporting back. I've replaced the official #172 linux zip files with the fixed ones

[mar]

build 173 is up:
- fix (cosmetic): promotion in move list is properly translated in localized SAN/figurine as it should

[Max]

Hi Martin,
there is an issue with Phalanx XXII. I'm on linux and used the Phalanx binary from SCID 5.2.

While installing Phalanx there is a tiny glitch, that Myracle doesn't fill out the engine name tag by itself.
However, the real problem is that Myracle does not recognize Phalanx's moves and therefore "forfeits on time".

Code: Select all

1637393857> xboard
1637393896> new
1637393897> hard
1637393897> easy
1637393898> post
1637393903> new
1637393903> force
1637395666< Phalanx XXII-pg
1637395731< primary book ./pbook.phalanx, 48749 bytes
1637395736< secondary book ./sbook.phalanx, 259074 bytes
1637395736< eco file ./eco.phalanx, 171176 bytes
1637395737< tellics set 1 Phalanx XXII-pg, 820 kB hashtable, 47/253 kB P/S opening book
1637395739< [ white, 1 ]
1637395746< xboard mode on
1637395746< initial position set, machine plays black
1637395747< pondering on
1637395747< pondering off
1637395748< post on
1637395749< initial position set, machine plays black
1637395750< you play both
1637530439> e2e4
1637530473> c7c5
1637530482> g1f3
1637530496> e7e6
1637530504> d2d4
1637530512> c5d4
1637530521> f3d4
1637530523< your move is Pe2-e4  
1637530526< your move is Pc7-c5  
1637530526< your move is Ng1-f3  
1637530526> b8c6
1637530527< your move is Pe7-e6  
1637530527< your move is Pd2-d4  
1637530527< your move is Pc5xd4  
1637530529< your move is Nf3xd4  
1637530533< your move is Nb8-c6  
1637530537> b1c3
1637530545> d8c7
1637530551< your move is Nb1-c3  
1637530552> c1e3
1637530559< your move is Qd8-c7  
1637530559> a7a6
1637530561< your move is Bc1-e3  
1637530564< your move is Pa7-a6  
1637530567> d1d2
1637530574< your move is Qd1-d2  
1637530575> g8f6
1637530581< your move is Ng8-f6  
1637530582> f2f3
1637530591< your move is Pf2-f3  
1637530591> f8e7
1637530598< your move is Bf8-e7  
1637530609> level 0 1 1
1637530610> time 6100
1637530610> otim 6100
1637530612> go
1637530664< level: all moves in 1:00, increment 1 seconds
1638178691<   7     68    65  1503465  Bf1-e2  O-O  O-O  Pb7-b6  Pf3-f4  Bc8-b7  Pe4-e5  Nc6xd4  Be3xd4  
1638418381<   8     59    89  2040705  Bf1-e2  O-O  O-O  Pb7-b6  Pf3-f4  Be7-b4  Pe4-e5  Nf6-e4  
1640039130<   8     59   251  5778267  Bf1-e2  O-O  O-O  Pb7-b6  Pf3-f4  Be7-b4  Pe4-e5  Nf6-e4  
1640039169< tellics whisper depth=8; eval=+0.59; nodes=5778267; nps=2302098
1640039170< my move is Bf1-e2  
1640039171< 9. ... f1e2 
1700524127> result 0-1 {white forfeits on time}
1700524135> easy
1700524285> force
1700524287> quit

[mar]

hi Max,

the problem is that myracle only fills the engine name for xboard protocol version2 and only if the engine reports feature myname

phalanx XXII seems to be old xboard 1, so there is no way for the GUI to get actual engine name (apart from guessing from binary name
or guessing from engine output like tellics) - the user has to help out here

the real problem however is that the GUI misses 9. ... f1e2, because I assume that anything starting with a number is an info line.
I have to say I really don't like the xboard protocol, especially the old one. supporting it means piling up hacks in the GUI

I would really hate to break all other xboard engines by "fixing" xboard mode for phalanx XXII, I have to think and test a lot.
for now your best bet would probably be to use some wb2uci linux alternative, if it exists.

note that not all xboard engines will work in Myracle, like the old xboard EveAnns that have a bug in handling the force command,
while it works in other GUIs because they setup the engine in a different way and I don't plan to hack the GUI to support buggy engines.

for now I'll only say that the xboard protocol support in Myracle is experimental

I'll try to report back here if I figure it out.

[SSTATHIS]

hi Max,

the problem is that myracle only fills the engine name for xboard protocol version2 and only if the engine reports feature myname

phalanx XXII seems to be old xboard 1, so there is no way for the GUI to get actual engine name (apart from guessing from binary name
or guessing from engine output like tellics) - the user has to help out here

the real problem however is that the GUI misses 9. ... f1e2, because I assume that anything starting with a number is an info line.
I have to say I really don't like the xboard protocol, especially the old one. supporting it means piling up hacks in the GUI

I would really hate to break all other xboard engines by "fixing" xboard mode for phalanx XXII, I have to think and test a lot.
for now your best bet would probably be to use some wb2uci linux alternative, if it exists.

note that not all xboard engines will work in Myracle, like the old xboard EveAnns that have a bug in handling the force command,
while it works in other GUIs because they setup the engine in a different way and I don't plan to hack the GUI to support buggy engines.

for now I'll only say that the xboard protocol support in Myracle is experimental

I'll try to report back here if I figure it out.

Hi Max
There is a UCI version for linux by Jim Ablett here:
https://drive.proton.me/urls/9TRAQG8SXC#3J2pemAZ0DpV

[Max]

Hi Max
There is a UCI version for linux by Jim Ablett here:
https://drive.proton.me/urls/9TRAQG8SXC#3J2pemAZ0DpV

Thanks,
but Jim added UCI only to Phalanx XXV & XXIII.

Unfortunately couldn't find a linux version of wb2uci. Testing the wb2uci windows exe with wine and Phalanx XXII now.