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

×
Hi,

I´m using the galaxy 2.0 client now since a few months and also the Battle.net integration and it worked fine for me when i wanted to start Call of Duty or World of Warcraft.
Since two or three weeks I have the problem that my galaxy 2.0 wont work anymore with my battle.net client.
When I want to play Call of Duty and I click on the play button in the 2.0 launcher it wont open the Battle.net client and of couse not the game.
So i have to manualy start the Battle.net client and start the games my self.

I tried to reinstall 2.0 and Battle.net client too...but nothing works.
And yes I also deleted the plugin folders to be sure everything is fresh installed.

I searched in the forum but could not find a solution so maybe I´m not alone or someone knows what to do now.
Bump
So seems like I´m the only one with this problem :(
avatar
falkthewolf: Hi,

I´m using the galaxy 2.0 client now since a few months and also the Battle.net integration and it worked fine for me when i wanted to start Call of Duty or World of Warcraft.
Since two or three weeks I have the problem that my galaxy 2.0 wont work anymore with my battle.net client.
When I want to play Call of Duty and I click on the play button in the 2.0 launcher it wont open the Battle.net client and of couse not the game.
So i have to manualy start the Battle.net client and start the games my self.

I tried to reinstall 2.0 and Battle.net client too...but nothing works.
And yes I also deleted the plugin folders to be sure everything is fresh installed.

I searched in the forum but could not find a solution so maybe I´m not alone or someone knows what to do now.
Go to the cog wheel > settings > integrations, and check if your integrations are all still connected. One of the main issues that I have with 2.0 is that your connections time out and you have to go through the process of reconnecting them.

EDIT: I am personally thinking about going back to Steam for my launcher again. You do have to add games manually, but it seems to work better overall. There are too many issues, like the one that you are bringing up here for me to stick with it.
Post edited February 18, 2020 by STOPchris1
avatar
falkthewolf: Hi,

I´m using the galaxy 2.0 client now since a few months and also the Battle.net integration and it worked fine for me when i wanted to start Call of Duty or World of Warcraft.
Since two or three weeks I have the problem that my galaxy 2.0 wont work anymore with my battle.net client.
When I want to play Call of Duty and I click on the play button in the 2.0 launcher it wont open the Battle.net client and of couse not the game.
So i have to manualy start the Battle.net client and start the games my self.

I tried to reinstall 2.0 and Battle.net client too...but nothing works.
And yes I also deleted the plugin folders to be sure everything is fresh installed.

I searched in the forum but could not find a solution so maybe I´m not alone or someone knows what to do now.
avatar
STOPchris1: Go to the cog wheel > settings > integrations, and check if your integrations are all still connected. One of the main issues that I have with 2.0 is that your connections time out and you have to go through the process of reconnecting them.

EDIT: I am personally thinking about going back to Steam for my launcher again. You do have to add games manually, but it seems to work better overall. There are too many issues, like the one that you are bringing up here for me to stick with it.
It has nothing to do with this integretions settings.
I still have Bnet in my gog 2.0 launcher.
It´s just the problem that it won´t launch the games.

Beside of that i have non problems with other games or platforms and I have 12 connected.
It all works like a charm even non platform games.
As i said i had no problems with Bnet till my post day and used it for like a few months
avatar
STOPchris1: Go to the cog wheel > settings > integrations, and check if your integrations are all still connected. One of the main issues that I have with 2.0 is that your connections time out and you have to go through the process of reconnecting them.

EDIT: I am personally thinking about going back to Steam for my launcher again. You do have to add games manually, but it seems to work better overall. There are too many issues, like the one that you are bringing up here for me to stick with it.
avatar
falkthewolf: It has nothing to do with this integretions settings.
I still have Bnet in my gog 2.0 launcher.
It´s just the problem that it won´t launch the games.

Beside of that i have non problems with other games or platforms and I have 12 connected.
It all works like a charm even non platform games.
As i said i had no problems with Bnet till my post day and used it for like a few months
Well, since a lot of other people have this working fine, I would check your Battle.net settings? Anything that could be causing the difference between you (not working) and the rest of us (working)? Settings would be the first place I would start, since your connection is fine (integration still connected).
avatar
falkthewolf: It has nothing to do with this integretions settings.
I still have Bnet in my gog 2.0 launcher.
It´s just the problem that it won´t launch the games.

Beside of that i have non problems with other games or platforms and I have 12 connected.
It all works like a charm even non platform games.
As i said i had no problems with Bnet till my post day and used it for like a few months
avatar
STOPchris1: Well, since a lot of other people have this working fine, I would check your Battle.net settings? Anything that could be causing the difference between you (not working) and the rest of us (working)? Settings would be the first place I would start, since your connection is fine (integration still connected).
Sorry but I´m feeling like you think I´m dumb.
Of course i checked all of that otherwise i would not write that i reinstalled both clients and did resets of those stuff.
Ok it seems like it fixed it self by a battle.net update.
Somehow it works now.