Steam Overlay and World of Warcraft

[Cheetah Blades]

OK, so what is going on here? I have used the Steam Overlay in WoW for a little over a year now. I know that in order for it to work, you must add the game.exe file to the Steam library, not the launcher or in some cases the 64-bit file. For a while, though - I would say since the end of 5.2 until now - I hadn't launched the game through Steam. So today I decide to do it to chat with a friend of mine, and every time I launch the game and pressed the hotkeys for the overlay, nothing would come up. I have tried using the 64 bit file and even the WoW launcher, and I still have not had any luck here. In another forum (dated in August of this year), someone said to try ticking in the WoW launcher the option to only open the 32-Bit client for WoW. The OP of that thread also said that he got his overlay to work by restarting Steam.

I have done all of these things and still no cigar. I have done some more research on this matter and I've only gotten a strange jumble of uncertainty across the web. Some have said that there have been issues ever since a Battle.net Desktop Client was released, which has caused huge amounts of trouble for Hearthstone players. People have said that Blizzard has "done something" that has pretty much disabled the Steam Overlay from working in all Blizzard games. However, some from posts as recent as October have said that their overlay works fine, and I think I even came across a Diablo 3 thread posted yesterday or a couple of days ago where the OP was concerned about being banned for his using of the Steam Overlay.

I have no idea what's going on here. All I know is that it used to be as simple as clicking Add Non-Steam Game, browsing to the World of Warcraft folder, adding the .exe file, and launching the game. Now not only does my Steam Overlay not work, but Steam also does not indicate when I'm in the game (which isn't really a big deal to me if I can still get the overlay to work).

[Cheetah Blades]

Never mind! Got the overlay to work, just had to add -noautolaunch64bit after the directory in the target box (from the Properties window).

[Pandaemonio]

ok i really need a solution. Can you report step by step?

[Cheetah Blades]

Originally posted by Nefasto:

ok i really need a solution. Can you report step by step?

I don't know if this will work for you, as it seems that problem has a differnet solution for various people, but when you have WoW listed as a non-steam game in your Steam library, right click on the game, click on Properties, and in the box headed as Target, add a space and

-noautolaunch64bit

to the end of the file's location. So for example, it looks like this in my window:

"F:\World of Warcraft\Wow.exe" -noautolaunch64bit

Sorry if you haven't found a solution while waiting for this response. I've been out of commission on Steam for a while.

[Veetus]

Originally posted by Cheetah Blades:

Originally posted by Nefasto:

ok i really need a solution. Can you report step by step?

I don't know if this will work for you, as it seems that problem has a differnet solution for various people, but when you have WoW listed as a non-steam game in your Steam library, right click on the game, click on Properties, and in the box headed as Target, add a space and

-noautolaunch64bit

to the end of the file's location. So for example, it looks like this in my window:

"F:\World of Warcraft\Wow.exe" -noautolaunch64bit

Sorry if you haven't found a solution while waiting for this response. I've been out of commission on Steam for a while.

Not working for me :(

[CumHummer]

yes its cool

[Veetus]

Originally posted by Дед синяк:

yes its cool

?