Page 1 of 1
Fuego and SmartGo
Posted: Sun Nov 20, 2011 2:20 pm
by judicata
For some reason, I can't get Feugo 1.1 working on SmartGo (latest version), although I can get other GTP engines working (e.g. Gnugo). Fuego works without any parameters in GoGui and in Many Faces of Go. Any suggestions from anyone? (in Windows 7 64 bit).
Re: Fuego and SmartGo
Posted: Sun Nov 20, 2011 3:25 pm
by emeraldemon
I don't have smartgo, is there a way you can get the GTP text? E.G. In GoGui I get something like:
Code: Select all
name
= Fuego
protocol_version
= 2
version
= 1.1
etc. Or does it not even get that far?
Re: Fuego and SmartGo
Posted: Sun Nov 20, 2011 3:38 pm
by judicata
Sure - I don't have any problems in GoGui. I'm going to try some older versions and see when it quit playing nice with SmartGo.
Re: Fuego and SmartGo
Posted: Sun Nov 20, 2011 4:05 pm
by emeraldemon
I mean can you get smartgo to give you similar output, showing the gtp responses fuego gives it?
Re: Fuego and SmartGo
Posted: Sun Nov 20, 2011 7:44 pm
by judicata
emeraldemon wrote:I mean can you get smartgo to give you similar output, showing the gtp responses fuego gives it?
Oh-sorry, I misunderstood. I'm not sure how to get SmartGo to display that info, but it wouldn't get that far anyway--I just get an error message (similar to when I leave out parameters on GnuGo).
Re: Fuego and SmartGo
Posted: Mon Nov 21, 2011 9:52 am
by smartgo
Try passing the --quiet option to Fuego.
Also, in SmartGo, you can choose Tools > Special > More Options, and set the GTPDebug setting to 1. That will show you the responses of the GTP engine, and may help you track down what is going on.
Re: Fuego and SmartGo
Posted: Mon Nov 21, 2011 4:31 pm
by judicata
smartgo wrote:Try passing the --quiet option to Fuego.
Also, in SmartGo, you can choose Tools > Special > More Options, and set the GTPDebug setting to 1. That will show you the responses of the GTP engine, and may help you track down what is going on.
Ah ha! The --quiet option worked. Thanks.