quick edit: as of now, playing is not supported on tygem, wbaduk, some other servers. Observing works. Playing works at least on igs.

I can imagine this to be the most powerful go client ever, if just couple problems were fixed. ..All those servers under one clean client, what else can you wish for?

Guess the right place to post the problems are on the git's issues page, but I'll add here a quite detailed list of what I've encountered

* cant connect to tygem in 2.1.0, in 2.0.0 could.
- solved. Retrying and retrying and eventually it will connect
* wbaduk (and likely tygem too) matchmaking problem. Can't see self making challenges. The rightclick username-> "Match" does nothing.
- no active developer to solve this as of now
* rightclick username->"Talk" did not crash 2.0.0, crashes 2.1.0.
- fixed

details:

First I installed qgo from ubuntu repositories couple days ago. It installed the qgo version 2.0.0 on my Ubuntu 14.04.

A day or two later I installed a newer version 2.1.0 from this github https://github.com/pzorin/qgo

Prior the installation from github, there are following dependancies:



The 2.0.0 version:

I added IGS and Tygem credentials to the client, and managed to connect to both without problems. On both servers, observing games seemed to work as expected. Playing and setting up games on IGS seemed to work normally.

On Tygem, the matchmaking seemed to not work. When I tagged "Open for playing" and "Looking for a game", I didn't get any game challenges, nor my client showed any signs or logs of challenging anyone (unlike in windows tygem client) I did get one eventually, when I was looking at my settings behind the leftside columns "Servers" tab. I actually clicked Accept on the popup, but no new window ever popped up. Also when I right-clicked on a username (username with "stat" field set as "O" on the user list) and chose "Match", nothing happened. When I clicked "talk", I got a new separate tab along the leftside columns "Shouts" and "Messages" tabs. I guess I could have talked to them there. I tried clicking a small goban image below this box, but nothing happened.

The 2.1.0 version:

After having installed 2.1.0, the IGS credentials connected to IGS normally. The tygem credentials did not work anymore. After trying to connect to tygem for a moment, I get Protocol Error "This may also result from wrong username or password".

This is what my linux console says about it, if I run the qgo from console:

I tried removing the tygem credentials and re-entering them, but no change.

Then I added Cyberoro/Wbaduk credentials to the client, and connected there without problems.

On Wbaduk on qgo 2.1.0, I still seem to have a sort of a matchmaking problem. Tagging "Open for playing" and "Looking for a game" does not really do anything. On linux console I keep getting "Found non running game in game registry !!!" spammed every multiples times in a minute. When I right-click someones username on the userlist and choose "Match", the linux console says "room were in 0 room there in 476" The 476 is the number on opponents "Play" field.

Now on qgo 2.1.0 there is also a crash happening, when I right-click a username on IGS or wbaduk, and choose "talk". The linux console outputs this "QSortFilterProxyModel: index from wrong model passed to mapToSource
Segmentation fault (core dumped)"

And to remind, how matchmaking on tygem's native windows client works:

When you tag "Open for playing", you probably get a game request probably once a minute, or once in 5 minutes.

And when you tag "Looking for a game", your client tries to challenge someone of your rank for around 5 seconds, showing their username while challenging, and then switching to a new one and trying to challenge that for 5 seconds. It keeps doing that as long as someone accepts it. On crowdy tygem, you usually have to wait from 5 to 30 seconds to get an even game with an opponent of same strength. This is the best part of Tygem!

I included here my linux console log from connecting to wbaduk, trying to set yourself challenging for match, trying to manually "match" someone, and then crashing it with "talk".


As an extra note. I'm using Lubuntu 14.04 with lxde. It seems that my lxpanel gets messed up too sometimes after having had qgo open for some time. Can't say for sure that it is qgo causing it yet though. Icons appearing in duplicates and in wrong places. I get it fixed with lxpanelctl restart, so this is not a problem for me.

Very nice feedback but it looks like that no one has a solution to these problems. And I can not find a way to play with qgo who looks quiet good and it is a pity.. (I'll use virtual box -_-)

Disclaimer: I am the qgo 2.1 developer. I was attracted to this forum by Malkovich games.

The problem with servers other than IGS is that they use binary protocols apparently without public documentation. Judging from the comments in the source code, the support for them is based on reverse engineering.

Personally, I use qgo only to play on IGS. The crash on "talk" was actually resolved quickly and the updated version packaged in debian, but ubuntu did not pick up the update immediately (the version in 15.04 has this fixed).

Hi pzorin,

Welcome, and thanks so much for qGo.
Does qGo also work on Windows, iOS, or OSX ?

Thanks.

It definitely works on OSX and Windows, but I don't provide precompiled packages because I only use Linux.

It should also be easy to port to Android, iOS, or WinRT, as Qt5 is available on these platforms http://doc.qt.io/qt-5/supported-platforms.html, but I don't have any such devices, so I haven't tried.

I remember a while ago I provided some patches for the windows part of it. There's just less reason to keep windows up to date, since getting the official clients is easy.

The one thing I liked about qgo is you could see all the chat in Korean going on that the English client blocks.

Actually, the new IGS official client, GoPanda2, also works well on Linux. These days I wouldn't have bothered to bring qgo back into usable state. I've heard that some people use it to play on their clubs' NNGS servers, though, so it is still somewhat useful.

Where can you find the credentials for the various go servers? Is there a site or github that hosts that information?

I have looked online and haven't been able to come up with much.

Thank you for any help.