Steam overlay is busted on Battle.net launched games

[WombatFromHell]

It appears to be a regression in the Battle.net client, but I'm currently investigating.

[WombatFromHell]

I'm having some amount of difficulty reproducing this reported issue. My INI is as follows (for a successful launch):

LauncherPath=C:\Program Files (x86)\Battle.net\Battle.net.exe
LauncherArgs=--exec="launch D3"
LauncherURI=
GamePath=E:\Games\Battle.net\Diablo III\x64\Diablo III64.exe
GameArgs=
MonitorPath=
DetectedCommandline=
[Options]
LauncherMode=Normal
PreLaunchExec=
PreLaunchExecArgs=
PostGameExec=
PostGameExecArgs=
ProxyTimeout=3
PreGameLauncherWaitTime=7
PostGameWaitTime=7
PostGameCommandWaitTime=5
ProcessAcquisitionTimeout=120
InterProcessAcquisitionTimeout=10
ProcessAcquisitionAttempts=5
ReLaunch=True
SkipLauncher=False
DoNotClose=False
ForceLauncher=False
MinimizeLauncher=False
CommandlineProxy=False
ElevateExternals=False
GameProcessAffinity=
GameProcessPriority=
TerminateOSOLUponLaunch=False

[WombatFromHell]

False alarm. There is currently no issue when Battle.net on the current version of OSOL.