search

WombatFromHell / OriginSteamOverlayLauncher

An executable wrapper for Steam to make third-party launchers more convenient to use with a Steam Controller
MIT License
413 stars 25 forks source link

Ranbow six siege - Anyone having issues. #12

Open BarterClub opened 6 years ago

BarterClub commented 6 years ago

Its seems to be having a lot of issues now for some reason. I think uplay did an update. Not sure can someone let me know if this is doing the same thing to them?

WombatFromHell commented 6 years ago

I happen to have Siege. I'll investigate.

WombatFromHell commented 6 years ago

I'm not experiencing any issues with Siege + UPlay either with or without OSOL. Double check that you don't have something interfering with the overlays and that you're targeting the "upc.exe" executable instead of "Uplay.exe".

(Edit: I've attached my OSOL v1.05c config below as an example):

[Paths]
LauncherPath=C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\upc.exe
LauncherArgs=
LauncherURI=
GamePath=D:\Games\steamapps2\SteamApps\common\Tom Clancy's Rainbow Six Siege\RainbowSix.exe
GameArgs=
[Options]
PreLaunchExec=
PreLaunchExecArgs=
PostGameExec=
PostGameExecArgs=
PreGameOverlayWaitTime=5
PreGameLauncherWaitTime=12
PostGameWaitTime=7
LauncherMode=Normal
BarterClub commented 6 years ago

Ok thanks. Seems something else is causing the issue. I take a loot around.

BarterClub commented 6 years ago

Well i tried to figure it out. But it seems to be something with uplay. If i have a uplay from steam the overlay works.

I cant get the overlay to even work with uplay it self. So it seems its not hooking to uplay and im at a lot of what to do. I have reinstalled uplay and had no luck. I have made sure steam can hook into different uplay games that are from steam. But it seems that i cant hook into uplay first.

This is what happens since the update to uplay last week.

[11/25/2017 10:15:11 PM] [NOTE] OSOL is running as: originsteamoverlaylauncher
[11/25/2017 10:15:11 PM] [OSOL] Attempting to start the launcher: E:\U Play launcher\Ubisoft Game Launcher\upc.exe
[11/25/2017 10:15:17 PM] [OSOL] Detected the launcher process window at PID [18228] in 6 sec.
[11/25/2017 10:15:22 PM] [OSOL] Launching game, cmd: E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe 
[11/25/2017 10:15:40 PM] [OSOL] Detected the game process at PID [16964] in 18 sec.
[11/25/2017 10:16:14 PM] [OSOL] Game exited, killing launcher instance and cleaning up...

[[Paths]
LauncherPath=E:\U Play launcher\Ubisoft Game Launcher\upc.exe
LauncherArgs=
LauncherURI=
GamePath=E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe
GameArgs=
[Options]
PreLaunchExec=
PreLaunchExecArgs=
PostGameExec=
PostGameExecArgs=
PreGameOverlayWaitTime=5
PreGameLauncherWaitTime=12
PostGameWaitTime=7
ProxyTimeout=5
ProcessAcquisitionTimeout=300
ReLaunch=True
DoNotClose=False
MinimizeLauncher=True
LauncherMode=Normal
WombatFromHell commented 6 years ago

Hmm.. double check that Steam and UPlay are -not- running with Admin privileges.

(Edit: Aside from a privilege conflict you may try temporarily disabling RTSS/Afterburner/DXtory if you use anything like that.)

BarterClub commented 6 years ago

Nope they are not running in admin mode

No overlays are running at the moment.

BarterClub commented 6 years ago

I feel something from an update to steam or uplay messed something up.

WombatFromHell commented 6 years ago

Maybe check the C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\logs\overlay_log.txt file and see what it says near the bottom about what its overlay is doing?

(Edit: For instance, mine has something like this):

[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      Hooks.cpp (38)                                   --- Overlay started --- (D:\Games\steamapps2\steamapps\common\Tom Clancy's Rainbow Six Siege\RainbowSix.exe)
[ 5512]  2017-11-24 19:50:09      [10232]      INFO       Hooks.cpp (56)                                   Create process hooks disabled via command line
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'kernel32.dll' hooked           
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'xinput9_1_0.dll' hooked        
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'dinput8.dll' hooked            
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'dxgi.dll' hooked               
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'd3d9.dll' hooked               
[ 5512]  2017-11-24 19:50:09      [10232]      DEBUG      PlatformHooks.cpp (114)                          'user32.dll' hooked             
[ 5512]  2017-11-24 19:50:10      [10232]      DEBUG      PlatformHooks.cpp (114)                          'kernel32.dll' hooked           
[ 5512]  2017-11-24 19:50:14      [10232]      DEBUG      PlatformHooks.cpp (114)                          'xinput1_4.dll' hooked          
[ 5512]  2017-11-24 19:50:15      [10380]      DEBUG      D3d11Render.cpp (372)                            D3D11 device created            
[ 5512]  2017-11-24 19:50:18      [10380]      DEBUG      Win32InputHooks.cpp (1061)                       RenderWindow 3872508            
[ 5512]  2017-11-24 19:50:18      [10380]      DEBUG      Overlay.cpp (598)                                Sending overlay start request   
[ 5512]  2017-11-24 19:50:18      [10380]      DEBUG      Win32InputHooks.cpp (1061)                       RenderWindow 3872508
WombatFromHell commented 6 years ago

Following that idea, there should also be a C:\Program Files (x86)\Steam\GameOverlayUI.exe.log that tells you what the BPM/Steam overlay is doing when trying to attach to a game. You may look in there and see what's going on that may be causing it to have difficulty hooking the game process.

BarterClub commented 6 years ago

Ok while looking at eh gameoverlayUI for steam it showed that it would not produce a new one until i used a steam game. Not sure if that means that its not even trying to hook into the program or not.

WombatFromHell commented 6 years ago

Interesting, I've never seen a message like that before. Could you paste a snippet like I did above? Just use three tildes (` key above the Tab button) on their own line before and after the text.

BarterClub commented 6 years ago 
Sat Nov 25 22:54:03 2017 UTC - GameOverlay process started: pid: 16276
Sat Nov 25 22:54:03 2017 UTC - GameOverlay process connecting to: pid: 3024
Sat Nov 25 22:54:03 2017 UTC - BuildID: 1509425745
Sat Nov 25 22:54:03 2017 UTC - Steam Path: C:\Program Files (x86)\Steam
Sat Nov 25 22:54:03 2017 UTC - Generating new string page texture 2736: 16x256, total string texture memory is 16.38 KB
Sat Nov 25 22:54:04 2017 UTC - Generating new string page texture 2737: 48x256, total string texture memory is 65.54 KB
Sat Nov 25 22:54:06 2017 UTC - Generating new string page texture 2739: 128x256, total string texture memory is 196.61 KB
Sat Nov 25 22:54:06 2017 UTC - Generating new string page texture 2740: 256x256, total string texture memory is 458.75 KB
Sat Nov 25 22:55:19 2017 UTC - Game Exit Event signaled.
Sat Nov 25 22:55:19 2017 UTC - Shutting down overlay
WombatFromHell commented 6 years ago

Hmm, Steam does seem to be hooking the game process like it should. Does UPlay tell you anything helpful? There could be some other process on your system that's blocking the overlay from displaying itself. Make sure you go through this FAQ article before you give up, if you haven't already.

BarterClub commented 6 years ago

Thats for a diffrent game. It wont hook at all with any uplay games

BarterClub commented 6 years ago

and it works with origin and starwars.

WombatFromHell commented 6 years ago

So the UPlay overlay works, but Steam won't hook Siege. Maybe disable the UPlay overlay and see if that helps Steam hook its overlay to Siege? You could also try doing the opposite of what I said above - force Steam to run as Admin and see if that helps at all in case something is causing privilege interference?

As a side note, I just noticed that the way BattleEye calls RainbowSix.exe via the RainbowSix_BE.exe proxy launcher is causing OSOL to lose track of which executable it needs to be monitoring. I'm investigating why right now.

BarterClub commented 6 years ago

Im going to rebuild my steam files and see what it does.

BarterClub commented 6 years ago

Seems even after that no luck. Not sure what is causing this but its not your program. I do like what you have done to it. Also have you seem https://github.com/BrianLima/UWPHook its something similer to what your doing and they have a very nice clean app.

WombatFromHell commented 6 years ago

I wasn't aware of UWPHook since my application is designed for non-UWP games and I do my best to stay away from the Microsoft Store environment. I do like UWPHook's mediating pre-launcher design though, and I plan to move OSOL toward a similar type of interface very soon.

I'm not interested in supporting and/or building yet another hooking launcher when the existing launchers work fine for the most part - they just lack BPM friendly features. As much as many people love bnetlauncher I found it to be lackluster when it came to said features so I built OSOL.

BarterClub commented 6 years ago

Here is what happens when i use the new update.

[Paths]
LauncherPath=C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\upc.exe
LauncherArgs=
LauncherURI=
GamePath=E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe
GameArgs=
MonitorPath=E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe
[Options]
PreLaunchExec=
PreLaunchExecArgs=
PostGameExec=
PostGameExecArgs=
PreGameOverlayWaitTime=5
PreGameLauncherWaitTime=12
PostGameWaitTime=7
ProxyTimeout=5
ProcessAcquisitionTimeout=300
ReLaunch=True
DoNotClose=False
MinimizeLauncher=False
LauncherMode=Normal

[11/27/2017 9:15:43 PM] [NOTE] OSOL is running as: originsteamoverlaylauncher
[11/27/2017 9:15:43 PM] [OSOL] Attempting to start the launcher: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\upc.exe
[11/27/2017 9:15:47 PM] [OSOL] Detected the launcher process window at PID [6508] in 4 sec.
[11/27/2017 9:15:52 PM] [OSOL] Launching game, cmd: E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe 
[11/27/2017 9:20:56 PM] [FATAL] Timed out while looking for game process, exiting! Internet connection or launcher issue?
WombatFromHell commented 6 years ago

GamePath and MonitorPath are swapped. RainbowSix_BE.exe calls the BattleEye launcher which hooks RainbowSix.exe during the game launch. Those two lines should look like this:

GamePath=E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe
MonitorPath=E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe

(Edit: To clarify, RainbowSix_BE.exe gets terminated by BattleEye upon launch, which will cause OSOL to fail to find it, and you won't (shouldn't?) be able to join BattleEye games without letting RainbowSix_BE.exe call RainbowSix.exe on its own, IIRC.)

BarterClub commented 6 years ago

still no luck i swear its uplay, ive seen some other report the same issue.

[11/28/2017 3:26:57 AM] [NOTE] OSOL is running as: originsteamoverlaylauncher
[11/28/2017 3:26:57 AM] [OSOL] Attempting to start the launcher: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\upc.exe
[11/28/2017 3:27:01 AM] [OSOL] Detected the launcher process window at PID [22956] in 4 sec.
[11/28/2017 3:27:06 AM] [OSOL] Launching game, cmd: E:\U Play launcher\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe 
[11/28/2017 3:27:30 AM] [OSOL] Detected the monitor at PID [15900] in 24 sec.
[11/28/2017 3:27:57 AM] [OSOL] Game exited, killing launcher instance and cleaning up...
WombatFromHell commented 6 years ago

It looks as though OSOL is pointed at the right executables now and appears to be working properly.

No guarantees here, but if you're still having trouble and you believe it's because of OSOL you may try lowering/raising the PreGameOverlayWaitTime and PreGameLauncherWaitTime variables which have to do with how quickly OSOL calls the game to prevent Steam from hooking both the launcher and the game at the same time. If you drop both of those to 1 it comes close to mimicing the standard Steam behavior, and raising them will wait for the launcher to settle down before calling the game.

OSOL as a rule doesn't mess with how processes are hooking each other. Video drivers, the AMD External Events services, antivirus products, and some third party overlays all have a hand in whether or not BPM and those various overlays play nicely with each other.

SubSonix commented 6 years ago

I'm having the same issue of it not showing the steam overlay. First time trying with a uPlay game as I swear they used to work in steam without an extra work. Working fine with all of my Origin games.

I was having issues with either of the overlays working while RTSS was running, but I closed it before these results.

OriginSteamOverlayLauncher.ini - I've tested with variations of Pre-times. [Paths] LauncherPath=C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe LauncherArgs= LauncherURI= GamePath=X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe GameArgs= MonitorPath=X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe [Options] PreLaunchExec= PreLaunchExecArgs= PostGameExec= PostGameExecArgs= PreGameOverlayWaitTime=5 PreGameLauncherWaitTime=5 PostGameWaitTime=15 ProxyTimeout=5 ProcessAcquisitionTimeout=300 ReLaunch=True DoNotClose=False MinimizeLauncher=False LauncherMode=Normal

GameOverlayRenderer.log Fri Dec 22 08:13:23 2017 UTC - Module file name: C:\Programs\Steam\gameoverlayrenderer.dll Fri Dec 22 08:13:23 2017 UTC - GameID = 12522751929262014464 Fri Dec 22 08:13:23 2017 UTC - System page size: 4096 Fri Dec 22 08:13:23 2017 UTC - Hooking SetCursorPos, GetCursorPos, ShowCursor, and SetCursor Fri Dec 22 08:13:23 2017 UTC - Aborting HookFunc because pHookFunctionAddr is null Fri Dec 22 08:13:23 2017 UTC - Failed hooking RegisterDeviceNotificationA() Fri Dec 22 08:13:23 2017 UTC - Aborting HookFunc because pHookFunctionAddr is null Fri Dec 22 08:13:23 2017 UTC - Failed hooking RegisterDeviceNotificationW() Fri Dec 22 08:13:23 2017 UTC - Aborting HookFunc because pHookFunctionAddr is null Fri Dec 22 08:13:23 2017 UTC - Failed hooking UnregisterDeviceNotification() Fri Dec 22 08:13:23 2017 UTC - Game is using dxgi (dx10/dx11), preparing to hook. Fri Dec 22 08:13:23 2017 UTC - Game is using D3D9 or D3D9Ex, preparing to hook. Fri Dec 22 08:13:23 2017 UTC - Modules at GameOverlayRenderer.dll attach Fri Dec 22 08:13:23 2017 UTC - 01: UplayWebCore.exe - (0X00200000 to 0X00372000) Fri Dec 22 08:13:23 2017 UTC - 02: ntdll.dll - (0X77E10000 to 0X77F9D000) Fri Dec 22 08:13:23 2017 UTC - 03: KERNEL32.DLL - (0X77990000 to 0X77A60000) Fri Dec 22 08:13:23 2017 UTC - 04: KERNELBASE.dll - (0X776D0000 to 0X778A7000) Fri Dec 22 08:13:23 2017 UTC - 05: RPCRT4.dll - (0X77AC0000 to 0X77B7E000) Fri Dec 22 08:13:23 2017 UTC - 06: SspiCli.dll - (0X74830000 to 0X74850000) Fri Dec 22 08:13:23 2017 UTC - 07: CRYPTBASE.dll - (0X74820000 to 0X7482A000) Fri Dec 22 08:13:23 2017 UTC - 08: IPHLPAPI.DLL - (0X747D0000 to 0X74800000) Fri Dec 22 08:13:23 2017 UTC - 09: WINHTTP.dll - (0X73380000 to 0X7342D000) Fri Dec 22 08:13:23 2017 UTC - 10: bcryptPrimitives.dll - (0X77A60000 to 0X77AB7000) Fri Dec 22 08:13:23 2017 UTC - 11: ucrtbase.dll - (0X75220000 to 0X75337000) Fri Dec 22 08:13:23 2017 UTC - 12: sechost.dll - (0X755A0000 to 0X755E3000) Fri Dec 22 08:13:23 2017 UTC - 13: USER32.dll - (0X753A0000 to 0X75515000) Fri Dec 22 08:13:23 2017 UTC - 14: win32u.dll - (0X77970000 to 0X77986000) Fri Dec 22 08:13:23 2017 UTC - 15: d3d9.dll - (0X636E0000 to 0X6384C000) Fri Dec 22 08:13:23 2017 UTC - 16: GDI32.dll - (0X75650000 to 0X75672000) Fri Dec 22 08:13:23 2017 UTC - 17: msvcrt.dll - (0X778B0000 to 0X7796D000) Fri Dec 22 08:13:23 2017 UTC - 18: gdi32full.dll - (0X75790000 to 0X758EE000) Fri Dec 22 08:13:23 2017 UTC - 19: msvcp_win.dll - (0X75520000 to 0X7559C000) Fri Dec 22 08:13:23 2017 UTC - 20: dwmapi.dll - (0X71CD0000 to 0X71CF3000) Fri Dec 22 08:13:23 2017 UTC - 21: SHELL32.dll - (0X758F0000 to 0X76C23000) Fri Dec 22 08:13:23 2017 UTC - 22: combase.dll - (0X76C30000 to 0X76E76000) Fri Dec 22 08:13:23 2017 UTC - 23: cfgmgr32.dll - (0X74FE0000 to 0X75018000) Fri Dec 22 08:13:23 2017 UTC - 24: shcore.dll - (0X77640000 to 0X776C8000) Fri Dec 22 08:13:23 2017 UTC - 25: windows.storage.dll - (0X77010000 to 0X775D6000) Fri Dec 22 08:13:23 2017 UTC - 26: advapi32.dll - (0X751A0000 to 0X75218000) Fri Dec 22 08:13:23 2017 UTC - 27: shlwapi.dll - (0X77D70000 to 0X77DB5000) Fri Dec 22 08:13:23 2017 UTC - 28: kernel.appcore.dll - (0X75780000 to 0X7578E000) Fri Dec 22 08:13:23 2017 UTC - 29: powrprof.dll - (0X77DC0000 to 0X77E05000) Fri Dec 22 08:13:23 2017 UTC - 30: profapi.dll - (0X756F0000 to 0X75704000) Fri Dec 22 08:13:23 2017 UTC - 31: ole32.dll - (0X74EE0000 to 0X74FD7000) Fri Dec 22 08:13:23 2017 UTC - 32: libcef.dll - (0X55340000 to 0X595AA000) Fri Dec 22 08:13:23 2017 UTC - 33: OLEAUT32.dll - (0X77B80000 to 0X77C13000) Fri Dec 22 08:13:23 2017 UTC - 34: PSAPI.DLL - (0X75020000 to 0X750Fri Dec 22 08:13:37 2017 UTC - GameOverlayRenderer.dll detaching 0 to 0X75776000) Fri Dec 22 08:13:23 2017 UTC - 36: WINMM.dll - (0X728A0000 to 0X728C4000) Fri Dec 22 08:13:23 2017 UTC - 37: COMDLG32.dll - (0X74990000 to 0X74A64000) Fri Dec 22 08:13:23 2017 UTC - 38: USERENV.dll - (0X73430000 to 0X73452000) Fri Dec 22 08:13:23 2017 UTC - 39: OLEACC.dll - (0X68AC0000 to 0X68B16000) Fri Dec 22 08:13:23 2017 UTC - 40: WINMMBASE.dll - (0X71CA0000 to 0X71CC3000) Fri Dec 22 08:13:23 2017 UTC - 41: CRYPT32.dll - (0X76E80000 to 0X77002000) Fri Dec 22 08:13:23 2017 UTC - 42: MSASN1.dll - (0X775E0000 to 0X775EE000) Fri Dec 22 08:13:23 2017 UTC - 43: chrome_elf.dll - (0X74230000 to 0X742A2000) Fri Dec 22 08:13:23 2017 UTC - 44: HID.DLL - (0X72590000 to 0X7259A000) Fri Dec 22 08:13:23 2017 UTC - 45: COMCTL32.dll - (0X69080000 to 0X6910E000) Fri Dec 22 08:13:23 2017 UTC - 46: WINTRUST.dll - (0X775F0000 to 0X77636000) Fri Dec 22 08:13:23 2017 UTC - 47: IMM32.dll - (0X74EB0000 to 0X74ED5000) Fri Dec 22 08:13:23 2017 UTC - 48: dbghelp.dll - (0X72E00000 to 0X72F81000) Fri Dec 22 08:13:23 2017 UTC - 49: USP10.dll - (0X70BF0000 to 0X70C07000) Fri Dec 22 08:13:23 2017 UTC - 50: VERSION.dll - (0X743E0000 to 0X743E8000) Fri Dec 22 08:13:23 2017 UTC - 51: credui.dll - (0X72360000 to 0X7236D000) Fri Dec 22 08:13:23 2017 UTC - 52: CRYPTUI.dll - (0X5EB80000 to 0X5EC0B000) Fri Dec 22 08:13:23 2017 UTC - 53: NETAPI32.dll - (0X74800000 to 0X74813000) Fri Dec 22 08:13:23 2017 UTC - 54: DWrite.dll - (0X680F0000 to 0X68370000) Fri Dec 22 08:13:23 2017 UTC - 55: Secur32.dll - (0X708B0000 to 0X708BA000) Fri Dec 22 08:13:23 2017 UTC - 56: ncrypt.dll - (0X67E30000 to 0X67E50000) Fri Dec 22 08:13:23 2017 UTC - 57: urlmon.dll - (0X74600000 to 0X7478C000) Fri Dec 22 08:13:23 2017 UTC - 58: WTSAPI32.dll - (0X743F0000 to 0X743FF000) Fri Dec 22 08:13:23 2017 UTC - 59: imagehlp.dll - (0X748E0000 to 0X748F9000) Fri Dec 22 08:13:23 2017 UTC - 60: d3d11.dll - (0X634A0000 to 0X636DE000) Fri Dec 22 08:13:23 2017 UTC - 61: dxva2.dll - (0X71C80000 to 0X71C9E000) Fri Dec 22 08:13:23 2017 UTC - 62: dxgi.dll - (0X73EA0000 to 0X73F33000) Fri Dec 22 08:13:23 2017 UTC - 63: WINSPOOL.DRV - (0X70E60000 to 0X70ECC000) Fri Dec 22 08:13:23 2017 UTC - 64: dhcpcsvc.DLL - (0X71280000 to 0X71294000) Fri Dec 22 08:13:23 2017 UTC - 65: NSI.dll - (0X74A70000 to 0X74A77000) Fri Dec 22 08:13:23 2017 UTC - 66: wevtapi.dll - (0X696C0000 to 0X6970E000) Fri Dec 22 08:13:23 2017 UTC - 67: bcrypt.dll - (0X73630000 to 0X73649000) Fri Dec 22 08:13:23 2017 UTC - 68: NTASN1.dll - (0X67E00000 to 0X67E2C000) Fri Dec 22 08:13:23 2017 UTC - 69: iertutil.dll - (0X72BC0000 to 0X72DD9000) Fri Dec 22 08:13:23 2017 UTC - 70: SAMCLI.DLL - (0X68710000 to 0X68725000) Fri Dec 22 08:13:23 2017 UTC - 71: NETUTILS.DLL - (0X73570000 to 0X7357B000) Fri Dec 22 08:13:23 2017 UTC - 72: gameoverlayrenderer.dll - (0X68F40000 to 0X69075000) Fri Dec 22 08:13:23 2017 UTC - ----------------------------

OriginSteamOverlayLauncher_Log.txt [22/12/17 8:11:42 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher [22/12/17 8:11:42 AM] [OSOL] Attempting to start the launcher: C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe [22/12/17 8:11:45 AM] [OSOL] Detected the launcher process window at PID [2232] in 3 sec. [22/12/17 8:11:50 AM] [OSOL] Launching game, cmd: X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe [22/12/17 8:12:10 AM] [OSOL] Detected the monitor at PID [10324] in 20 sec. [22/12/17 8:13:37 AM] [OSOL] Game exited, killing launcher instance and cleaning up...

GameOverlayUI.exe.log - Didn't change during this session. Thu Dec 21 14:13:10 2017 UTC - GameOverlay process started: pid: 14112 Thu Dec 21 14:13:10 2017 UTC - GameOverlay process connecting to: pid: 9656 Thu Dec 21 14:13:11 2017 UTC - BuildID: 1513371133 Thu Dec 21 14:13:11 2017 UTC - Steam Path: C:\Programs\Steam Thu Dec 21 14:13:15 2017 UTC - Detected possibly crashed/killed game, exiting Thu Dec 21 14:13:15 2017 UTC - Shutting down overlay

BarterClub commented 6 years ago

Overlay for Siege won't work right now. Seems that whatever they did with the update messed up non native steam overlay.

WombatFromHell commented 6 years ago

There's a large thread about this on the Steam Community forum for Siege dating back to around Nov. 20. As of the last update they seem to have broken the Steam overlay.

SubSonix commented 6 years ago

I've been testing this again, and I've noticed that the RainbowSix.exe executable restarts multiple times while the game is launching. (At least 3 times) Could this be related? I could record it for you, but don't know what to use to record the task manager.

WombatFromHell commented 6 years ago

I'll investigate and report back.

WombatFromHell commented 6 years ago

OSOL seems to not be handling the UPlay launcher properly when using MonitorPath to watch the game executable, in this case RainbowSix.exe. Other than that Siege seems to launch and function properly with both the UPlay and Steam overlays as it should.

(Edit: Correction, executable monitoring seems to break when the MainModule is null. Working on a fix right now.)

WombatFromHell commented 6 years ago

The mentioned executable monitoring problem should be fixed in release v1.06k available on the releases page. Let me know if Siege needs any other adjustments.

SubSonix commented 6 years ago

I'm still having no luck with the steam overlay. I did just realise that you seem to have siege on steam, whereas BarterClub (I assume) and I have it solely on uPlay.

Also, unrelated, but I've been meaning to ask, what does this line from the readme mean: "Rename the shortcut in Steam to the name of the game in your launcher so you can retrieve Steam Community profiles."

EDIT* I believe it's just the steam overlay not hooking properly. I'm just guessing though lol This is my GameOverlayRenderer.log after the game and uplay close. (It changes constantly as the game executable's open and close while the game loads.) GameOverlayUI.exe.log does not change.

Wed Feb 07 11:57:03 2018 UTC - Module file name: C:\Programs\Steam\gameoverlayrenderer.dll Wed Feb 07 11:57:03 2018 UTC - GameID = 12522751929262014464 Wed Feb 07 11:57:03 2018 UTC - System page size: 4096 Wed Feb 07 11:57:03 2018 UTC - Hooking SetCursorPos, GetCursorPos, ShowCursor, and SetCursor Wed Feb 07 11:57:03 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Wed Feb 07 11:57:03 2018 UTC - Failed hooking RegisterDeviceNotificationA() Wed Feb 07 11:57:03 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Wed Feb 07 11:57:03 2018 UTC - Failed hooking RegisterDeviceNotificationW() Wed Feb 07 11:57:03 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Wed Feb 07 11:57:03 2018 UTC - Failed hooking UnregisterDeviceNotification() Wed Feb 07 11:57:03 2018 UTC - Game is using dxgi (dx10/dx11), preparing to hook. Wed Feb 07 11:57:03 2018 UTC - Game is using D3D9 or D3D9Ex, preparing to hook. Wed Feb 07 11:57:03 2018 UTC - Modules at GameOverlayRenderer.dll attach Wed Feb 07 11:57:03 2018 UTC - 01: UplayWebCore.exe - (00200000 to 00372000) Wed Feb 07 11:57:03 2018 UTC - 02: ntdll.dll - (77770000 to 778FD000) Wed Feb 07 11:57:03 2018 UTC - 03: KERNEL32.DLL - (74210000 to 742E0000) Wed Feb 07 11:57:03 2018 UTC - 04: KERNELBASE.dll - (76990000 to 76B67000) Wed Feb 07 11:57:03 2018 UTC - 05: atcuf32.dll - (72360000 to 723ED000) Wed Feb 07 11:57:03 2018 UTC - 06: RPCRT4.dll - (75570000 to 7562E000) Wed Feb 07 11:57:03 2018 UTC - 07: SspiCli.dll - (74190000 to 741B0000) Wed Feb 07 11:57:03 2018 UTC - 08: CRYPTBASE.dll - (74180000 to 7418A000) Wed Feb 07 11:57:03 2018 UTC - 09: bcryptPrimitives.dll - (76BF0000 to 76C47000) Wed Feb 07 11:57:03 2018 UTC - 10: sechost.dll - (74AC0000 to 74B03000) Wed Feb 07 11:57:03 2018 UTC - 11: USER32.dll - (748B0000 to 74A25000) Wed Feb 07 11:57:03 2018 UTC - 12: win32u.dll - (77750000 to 77766000) Wed Feb 07 11:57:03 2018 UTC - 13: GDI32.dll - (74B10000 to 74B32000) Wed Feb 07 11:57:03 2018 UTC - 14: gdi32full.dll - (74D80000 to 74EDE000) Wed Feb 07 11:57:03 2018 UTC - 15: msvcp_win.dll - (76B70000 to 76BEC000) Wed Feb 07 11:57:03 2018 UTC - 16: ucrtbase.dll - (74EE0000 to 74FF7000) Wed Feb 07 11:57:03 2018 UTC - 17: SHELL32.dll - (75630000 to 76963000) Wed Feb 07 11:57:03 2018 UTC - 18: msvcrt.dll - (747C0000 to 7487D000) Wed Feb 07 11:57:03 2018 UTC - 19: cfgmgr32.dll - (752E0000 to 75318000) Wed Feb 07 11:57:03 2018 UTC - 20: shcore.dll - (743C0000 to 74448000) Wed Feb 07 11:57:03 2018 UTC - 21: combase.dll - (75320000 to 75566000) Wed Feb 07 11:57:03 2018 UTC - 22: windows.storage.dll - (77080000 to 77646000) Wed Feb 07 11:57:03 2018 UTC - 23: advapi32.dll - (74670000 to 746E8000) Wed Feb 07 11:57:03 2018 UTC - 24: shlwapi.dll - (74450000 to 74495000) Wed Feb 07 11:57:03 2018 UTC - 25: kernel.appcore.dll - (74D70000 to 74D7E000) Wed Feb 07 11:57:03 2018 UTC - 26: powrprof.dll - (74B40000 to 74B85000) Wed Feb 07 11:57:03 2018 UTC - 27: profapi.dll - (74880000 to 74894000) Wed Feb 07 11:57:03 2018 UTC - 28: ole32.dll - (77650000 to 77747000) Wed Feb 07 11:57:03 2018 UTC - 29: IPHLPAPI.DLL - (73F80000 to 73FB0000) Wed Feb 07 11:57:03 2018 UTC - 30: WINHTTP.dll - (73630000 to 736DD000) Wed Feb 07 11:57:03 2018 UTC - 31: d3d9.dll - (669F0000 to 66B5C000) Wed Feb 07 11:57:03 2018 UTC - 32: libcef.dll - (0FC60000 to 13ECA000) Wed Feb 07 11:57:03 2018 UTC - 33: OLEAUT32.dll - (74720000 to 747B3000) Wed Feb 07 11:57:03 2018 UTC - 34: PSAPI.DLL - (76970000 to 76976000) Wed Feb 07 11:57:03 2018 UTC - 35: WS2_32.dll - (744C0000 to 74526000) Wed Feb 07 11:57:03 2018 UTC - 36: COMDLG32.dll Wed Feb 07 11:57:20 2018 UTC - GameOverlayRenderer.dll detaching 32.dll - (75000000 to 75182000) Wed Feb 07 11:57:03 2018 UTC - 38: MSASN1.dll - (748A0000 to 748AE000) Wed Feb 07 11:57:03 2018 UTC - 39: WINTRUST.dll - (74590000 to 745D6000) Wed Feb 07 11:57:03 2018 UTC - 40: IMM32.dll - (746F0000 to 74715000) Wed Feb 07 11:57:03 2018 UTC - 41: dwmapi.dll - (717E0000 to 71803000) Wed Feb 07 11:57:03 2018 UTC - 42: WINMM.dll - (72030000 to 72054000) Wed Feb 07 11:57:03 2018 UTC - 43: USERENV.dll - (73980000 to 739A2000) Wed Feb 07 11:57:03 2018 UTC - 44: OLEACC.dll - (66BF0000 to 66C46000) Wed Feb 07 11:57:03 2018 UTC - 45: COMCTL32.dll - (68A20000 to 68AAE000) Wed Feb 07 11:57:03 2018 UTC - 46: HID.DLL - (66C90000 to 66C9A000) Wed Feb 07 11:57:03 2018 UTC - 47: chrome_elf.dll - (67BD0000 to 67C42000) Wed Feb 07 11:57:03 2018 UTC - 48: dbghelp.dll - (73790000 to 73911000) Wed Feb 07 11:57:03 2018 UTC - 49: USP10.dll - (66BD0000 to 66BE7000) Wed Feb 07 11:57:03 2018 UTC - 50: VERSION.dll - (74110000 to 74118000) Wed Feb 07 11:57:03 2018 UTC - 51: credui.dll - (68060000 to 6806D000) Wed Feb 07 11:57:03 2018 UTC - 52: CRYPTUI.dll - (66300000 to 6638B000) Wed Feb 07 11:57:03 2018 UTC - 53: NETAPI32.dll - (73FB0000 to 73FC3000) Wed Feb 07 11:57:03 2018 UTC - 54: DWrite.dll - (613C0000 to 61640000) Wed Feb 07 11:57:03 2018 UTC - 55: ncrypt.dll - (67290000 to 672B0000) Wed Feb 07 11:57:03 2018 UTC - 56: Secur32.dll - (71900000 to 7190A000) Wed Feb 07 11:57:03 2018 UTC - 57: urlmon.dll - (68D30000 to 68EBC000) Wed Feb 07 11:57:03 2018 UTC - 58: imagehlp.dll - (744A0000 to 744B9000) Wed Feb 07 11:57:03 2018 UTC - 59: WTSAPI32.dll - (73FD0000 to 73FDF000) Wed Feb 07 11:57:03 2018 UTC - 60: d3d11.dll - (65D80000 to 65FBE000) Wed Feb 07 11:57:03 2018 UTC - 61: dxva2.dll - (66BB0000 to 66BCE000) Wed Feb 07 11:57:03 2018 UTC - 62: dxgi.dll - (69FA0000 to 6A033000) Wed Feb 07 11:57:03 2018 UTC - 63: WINSPOOL.DRV - (704A0000 to 7050C000) Wed Feb 07 11:57:03 2018 UTC - 64: dhcpcsvc.DLL - (70990000 to 709A4000) Wed Feb 07 11:57:03 2018 UTC - 65: NSI.dll - (76980000 to 76987000) Wed Feb 07 11:57:03 2018 UTC - 66: wevtapi.dll - (71830000 to 7187E000) Wed Feb 07 11:57:03 2018 UTC - 67: WINMMBASE.dll - (716F0000 to 71713000) Wed Feb 07 11:57:03 2018 UTC - 68: bcrypt.dll - (73080000 to 73099000) Wed Feb 07 11:57:03 2018 UTC - 69: NTASN1.dll - (67260000 to 6728C000) Wed Feb 07 11:57:03 2018 UTC - 70: iertutil.dll - (68B10000 to 68D29000) Wed Feb 07 11:57:03 2018 UTC - 71: SAMCLI.DLL - (712E0000 to 712F5000) Wed Feb 07 11:57:03 2018 UTC - 72: NETUTILS.DLL - (72530000 to 7253B000) Wed Feb 07 11:57:03 2018 UTC - 73: gameoverlayrenderer.dll - (0F1F0000 to 0F332000) Wed Feb 07 11:57:03 2018 UTC - ----------------------------

WombatFromHell commented 6 years ago

That line from the README is referring to a feature of OSOL. You can rename the OSOL executable to whatever you want and the INI will change names to match it. This can help compatibility and INI management in some situations.

I can't do much about hook failures because OSOL doesn't manage process hooking or memory injection at all.

WombatFromHell commented 6 years ago

Just out of curiosity, are you running an AMD GPU or nVidia GPU? Anecdotally, I've noticed from user reports that AMD drivers seem to cause more issues with the BPM overlay and third party overlays in general. I don't have direct evidence to corroborate this however.

SubSonix commented 6 years ago

What are Steam community profiles though?

Do you think it should be hooking correctly, I'll keep testing if so. I didn't know what I was talking about just to reinforce that, maybe attach is a better explanation?

Nvidia

Could you explain these please: PreGameOverlayWaitTime - Seems to be the time between game launcher opening and it launching game? PreGameLauncherWaitTime - Overlay start time after game launches?

Are they backwards? :/

I'm pretty confident I understand them, but keep doubting myself and just need confirmation as that's how my brain works :/

WombatFromHell commented 6 years ago

Community profiles are on the Community page of the BPM Input Configurator. I would refer to the OSOL Project Wiki Troubleshooting section if you haven't already been over the overlay troubleshooting steps.

PreGameOverlayWaitTime controls how long OSOL waits for BPM to finish hooking and animating the detection Toast for LauncherPath, because BPM used to have an issue where if the BPM Toast was still animating when the game process was hooked BPM's overlay would slow to a crawl (it still does this just not as often), this waiting period is a simplistic workaround for that problem - which primarily affects Origin and Battle.net launchers.

PreGameLauncherWaitTime controls how long OSOL waits for the Launcher to start before executing GamePath, which is less important now with the new process detection code which will wait up to ProcessAcquisitionTimeout for a given process name.

(Edit: Essentially I've left those internal waits/timeouts exposed so the user can tweak them to whatever their use case requires. Most of them (except ProcessAcquisitionTimeout) can be reduced to between 1 to 3 seconds pretty safely now unless you have an older machine or very slow internet.)

SubSonix commented 6 years ago

This did not help me :P : "Community profiles are on the Community page of the BPM Input Configurator." Nor did talking about Toast, but I think google helped me with that and you were talking about the UI popups etc?

EDIT Ah big pciture mode. (I've never used it hence the confusion)

Okay, well The PreGame parts are definitely backwards in at least v1.06k, not sure about other versions.

With this Siege launches exactly 15 seconds after upc is "hooked"

[Paths] LauncherPath=C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe LauncherArgs= LauncherURI= GamePath=X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe GameArgs= MonitorPath=X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe DetectedCommandline= [Options] PreLaunchExec= PreLaunchExecArgs= PostGameExec= PostGameExecArgs= PreGameOverlayWaitTime=15 PreGameLauncherWaitTime=60 PostGameWaitTime=15 ProxyTimeout=3 ProcessAcquisitionTimeout=300 ReLaunch=True DoNotClose=False ForceLauncher=False MinimizeLauncher=False CommandlineProxy=False ElevateExternals=False LauncherMode=Normal

[9/2/18 1:00:57 PM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher [9/2/18 1:00:57 PM] [OSOL] Attempting to start the launcher: C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe [9/2/18 1:00:57 PM] [OSOL] Searching for valid process by name: upc [9/2/18 1:01:00 PM] [OSOL] Bound to a valid process at PID: 13172 [upc.exe] in 3 seconds [9/2/18 1:01:15 PM] [OSOL] Launching game, cmd: X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe [9/2/18 1:01:15 PM] [OSOL] Searching for valid process by name: RainbowSix [9/2/18 1:01:39 PM] [OSOL] Bound to a valid process at PID: 644 [RainbowSix.exe] in 24 seconds [9/2/18 1:03:39 PM] [OSOL] The monitor exited, moving on to clean up... [9/2/18 1:03:54 PM] [OSOL] Found launcher still running, cleaning up...

WombatFromHell commented 6 years ago

Here are some snippets from the source code. PreGameOverlayWaitTime executes after LauncherPath because it's intended to help wait for the BPM overlay to finish its Toast animation as mentioned above:

launcherProc = GetProcessTreeHandle(setHnd, launcherName);
launcherPID = launcherProc != null ? launcherProc.Id : 0;

// force the launcher window to activate before the game to avoid BPM hooking issues
Thread.Sleep(setHnd.PreGameOverlayWaitTime * 1000); // wait for the BPM overlay notification
Program.BringToFront(launcherProc.MainWindowHandle);

PreGameLauncherWaitTime currently only runs if LauncherMode=URI. I removed it from the LauncherMode=Normal code path because of the newer process acquisition code. It was originally intended to help with situations where you may need to login to the launcher or in the event of a slow hard drive or internet connection. I'll probably change it for v1.07 to be more useful in the LauncherMode=Normal code path.

WombatFromHell commented 6 years ago

I've made some changes to the behavior of user configurable timeouts and improved logging a bit to make it less confusing. These commits are in test release v1.06l on the releases page.

SubSonix commented 6 years ago

I'm still having issues where the uplay program is closed while the game is still in the loading state (It doesn't always do it, but it does happen): I still believe it's because the game "restarts" multiple times while launching. I'm happy to talk to you via discord or even use teamviewer or something, anything to help. I can't help but think I'm conveying the information in-correcting and confusing myself etc :/

[11/2/18 6:30:15 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher [11/2/18 6:30:15 AM] [OSOL] Attempting to start the launcher: C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe [11/2/18 6:30:16 AM] [OSOL] Searching for valid process by name: upc [11/2/18 6:30:19 AM] [OSOL] Bound to a valid process at PID: 9188 [upc.exe] in 3 seconds [11/2/18 6:30:19 AM] [OSOL] Waiting 12 seconds for potential launcher slowness... [11/2/18 6:30:31 AM] [OSOL] Launching game, cmd: X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe [11/2/18 6:30:31 AM] [OSOL] Searching for valid process by name: RainbowSix [11/2/18 6:31:13 AM] [OSOL] Bound to a valid process at PID: 10156 [RainbowSix.exe] in 42 seconds [11/2/18 6:31:15 AM] [OSOL] The monitor exited, moving on to clean up... [11/2/18 6:31:22 AM] [OSOL] Found launcher still running, cleaning up...

EDIT Perhaps a variable timer for attaching BPM to the game would help?

WombatFromHell commented 6 years ago

I'll investigate some more, but at first glance it looks like the process detection code is deciding to monitor the wrong process for some bizarre reason.

(Edit: In the meantime you could try increasing the value of ProxyTimeout in the OSOL ini. Try 5 or 7 so OSOL is less likely to catch a dead process while the parent is busy churning child processes.)

SubSonix commented 6 years ago

As I said the RainbowSix.exe process seems to restart multiple times while the game is launching, so perhaps it's not monitoring the wrong thing, but only the first instance? (I made a recording of the event if you want to see?)

I'll let you know if it works :)

I'm more than willing to help with this in any way that I can :)

WombatFromHell commented 6 years ago

The basic process I'm using to decide which process to monitor is based on the following facts:

I mention that last step as a potential troublemaker because RainbowSix_BE.exe acts as a caller for RainbowSix.exe (hence the need for MonitorPath), and then the game process behaves as a parent with no children (it has a valid handle and a window title). The game should not be starting a process with both a handle and window title more than once unless there's something wrong with it (my copy purchased through Steam doesn't do that).

Previously, I was simply searching for the game process by name and returning the first PID, but this leads to lots of potential problems like returning dead children. The method I'm currently using is, in theory anyway, more resilient to false positives. As mentioned in my previous post I'm already using ProxyTimeout as a way to prevent OSOL from attaching to a dead process by waiting between ValidateProcTree() loops on top of using - as you put it - a "variable timer" in ProcessAcquisitionTimeout.

WombatFromHell commented 6 years ago

I need more information on how the UPlay version of Siege is behaving at the process level so I'm going to need you to try this executable with debugging turned on and paste what the log says after running it until (or if) the issue is reproduced:

OriginSteamOverlayLauncher-TEST_v1.06m-021118.zip

(Edit: This test version also has some code cleanups that may or may not help matters. It's difficult to say for sure at this point.)

SubSonix commented 6 years ago

[12/2/18 9:50:34 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher [12/2/18 9:50:34 AM] [OSOL] Attempting to start the launcher: C:\Programs\Ubisoft\Ubisoft Game Launcher\upc.exe [12/2/18 9:50:35 AM] [OSOL] Searching for valid process by name: upc [12/2/18 9:50:38 AM] [DEBUG] Trying to bind to detected processes at PIDs: 10880 [12/2/18 9:50:41 AM] [DEBUG] Trying to bind to detected processes at PIDs: 10880 [12/2/18 9:50:41 AM] [OSOL] Bound to a valid process at PID: 10880 [upc.exe] in 6 seconds [12/2/18 9:50:41 AM] [OSOL] Waiting 5 seconds for potential launcher slowness... [12/2/18 9:50:46 AM] [OSOL] Launching game, cmd: X:\Games\Tom Clancy's Rainbow Six Siege\RainbowSix_BE.exe [12/2/18 9:50:46 AM] [OSOL] Searching for valid process by name: RainbowSix [12/2/18 9:50:52 AM] [DEBUG] Trying to bind to detected processes at PIDs: 6764 [12/2/18 9:50:55 AM] [DEBUG] Trying to bind to detected processes at PIDs: 6764 [12/2/18 9:51:01 AM] [DEBUG] Trying to bind to detected processes at PIDs: 6404 [12/2/18 9:51:07 AM] [DEBUG] Trying to bind to detected processes at PIDs: 17000 [12/2/18 9:51:10 AM] [DEBUG] Trying to bind to detected processes at PIDs: 17000 [12/2/18 9:51:10 AM] [OSOL] Bound to a valid process at PID: 17000 [RainbowSix.exe] in 24 seconds [12/2/18 9:54:05 AM] [OSOL] The monitor exited, moving on to clean up... [12/2/18 9:54:10 AM] [OSOL] Found launcher still running, cleaning up...

I think this is just a steam issue now, unless that tells you anything? I'm talking to a Dev on steam about it, hopefully they can shed some light on the subject.

WombatFromHell commented 6 years ago

Was this log gathered when the issue occurred? I ask because the log shows very normal behavior for Siege and UPlay titles in general.

Another question I'm curious about: does this issue occur when launching normally - that is, with just Steam and UPlay?

SubSonix commented 6 years ago

I thought it looked normal.

I just want to make sure we're on the same page: The issue I'm having is that the steam overlay "BPM" Isn't working with Siege.

EDIT And only Siege that I'm aware of. Works fine with other Uplay games I've tested.

WombatFromHell commented 6 years ago

Yes, I follow. It's just that I'm a bit stumped if you've been through the normal troubleshooting steps from the BPM FAQ and you're still having trouble.

Are you able to get the Steam overlay to come up if the UPlay overlay is disabled?

(Edit: At this point I'm thinking it may be BattlEye related wrt non-Steam versions of Siege.)

SubSonix commented 6 years ago

I just wanted to make sure. Yeah, checked the FAQ's and am having no issue with any other game.

Yes, no steam overlay with uplay overlay off.

Thank you for the continuing effort btw :)

(I'm trying to find someone else who has the non steam version to see how theirs loads, but no luck so far :/)

SubSonix commented 6 years ago

As for your thought about battleye, I compared my r6_be.exe filesize with a friend who owns the game on steam and he said it matched, here it is for comparison:

siege

I'm going to download the game onto my partners laptop tonight and see what it does tomorrow and will report back :)

SubSonix commented 6 years ago

Reporting back after testing on my partners PC - Runs exactly the same, with the process restarts etc, and no overlay. So must be an issue/design of the Uplay version.