It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
As the topic says, on Witcher 3:Wild hunt the gametime played isn't showing, it keeps on showing 0m.

My current GoG Galaxy version is 1.0.2.970

Running it on Windows 7.
Probably a stupid question, but you are starting it through the client right?
avatar
SirPrimalform: Probably a stupid question, but you are starting it through the client right?
Yes and I don't exit the Galaxy client while in game either.
Post edited May 25, 2015 by Petelete
avatar
Petelete: As the topic says, on Witcher 3:Wild hunt the gametime played isn't showing, it keeps on showing 0m.

My current GoG Galaxy version is 1.0.2.970

Running it on Windows 7.
Could you create a ticket on Mantis regarding this issue and attach GalaxyClient.log to it? This will help us determine why it's not working for you.
avatar
SirPrimalform: Probably a stupid question, but you are starting it through the client right?
So you have to start the game THROUGH the client ? I was wondering why Darksiders was stuck at 43 mins, even tho I played a lot more than that . Aw well, shit happens :P
I noticed this too. But in my case it is still tracking my playing time; it just takes a while to refresh.
avatar
Petelete: As the topic says, on Witcher 3:Wild hunt the gametime played isn't showing, it keeps on showing 0m.

My current GoG Galaxy version is 1.0.2.970

Running it on Windows 7.
avatar
Fallen_Zen: Could you create a ticket on Mantis regarding this issue and attach GalaxyClient.log to it? This will help us determine why it's not working for you.
I have no idea what or where Mantis is.
avatar
Fallen_Zen: Could you create a ticket on Mantis regarding this issue and attach GalaxyClient.log to it? This will help us determine why it's not working for you.
avatar
Petelete: I have no idea what or where Mantis is.
http://mantis.gog.com/
[GalaxyCommunicationService] Caught stop serving exception: StopServingException: Timeout was reached after 30 s

Thats the error in log. Apparently can't start service, I tried starting that service manually and it gives error : ...started and then stopped...

Already tried reinstalling Galaxy client. (Had to manually remove two of those galaxy services before could reinstall)

Achievements sync work and sync fine.
Post edited May 25, 2015 by Petelete
avatar
Petelete: [GalaxyCommunicationService] Caught stop serving exception: StopServingException: Timeout was reached after 30 s

Thats the error in log. Apparently can't start service, I tried starting that service manually and it gives error : ...started and then stopped...

Already tried reinstalling Galaxy client. (Had to manually remove two of those galaxy services before could reinstall)

Achievements sync work and sync fine.
I've had this same issue and it's preventing login to GOG Galaxy. Anyone else encountered this or found a way to bypass? The client has been allowed through the firewall already.
This is still a problem in Galaxy 1.1.23, none of my games track playtime for me, though my friend doesn't seem to have a problem so I have no idea where the problem Really is.
avatar
Enmoku: This is still a problem in Galaxy 1.1.23, none of my games track playtime for me, though my friend doesn't seem to have a problem so I have no idea where the problem Really is.
I have the same problem for months, thought it was with everyone until a friend pointed out to me that apparently I'm the exception. All my GOG games have been installed and played through Galaxy. Currently running version 1.1.24. on Windows 10.
Hey,

Not sure if it will help but I had the same issue before and I noticed that, in my case, it was linked to the firewall built in my antivirus (Bitdefender). I set it in "parano" mode which means that every time a port action is happening (even if it concerns the local loop), an authorisation is requested.

If I say no (or don't do anything because the pop up request is displayed in the background) then the time is not registered.

Once again, I'm not sure of the exact reason why and not sure that it'll help but it could be a direction...

Edit: fixed typo.
Post edited December 14, 2016 by cal74
I have only Windows Firewall in use and everything's pretty much allowed. Also running Windows 7 so this is not Windows 10 specific.
Random thought. Does this occur only if you have "too many" games installed and listed in Galaxy? Somewhere around the time I had over 40 games installed it stopped working, but before that it seemed to work fine. I guess I'll test by uninstalling a few games and see if it resumes operation.

Edit: Nope, that's not it. But I noticed GalaxyCommunication service is not starting up. And I recall there being crashes related to it months ago, roughly back when it last worked in fact. Not sure why it now refuses to start.

Edit 2: Reading the GalaxyClient.log, I noticed that Galaxy is somehow detecting each game being closed few seconds after they've been launched even though this is not true.

Edit 3: For those interested in this problem, look over to: http://mantis.gog.com/view.php?id=4234
Post edited January 01, 2017 by Enmoku