Ranbow six siege - Anyone having issues.

[BarterClub]

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]

Hmm, sounds like it could very well be because of BattlEye. The Steam version must have some workarounds that don't exist in the UPlay version.

Have you tried launching RainbowSix.exe directly (without the BattlEye launcher, RainbowSix_BE.exe) to confirm whether or not the overlay comes up?

The only other way to workaround the overlay not coming up would be to use GloSC if you want to use a hybrid gamepad config. OSOL can still be used to manage the UPlay launcher in that situation, just set it as the target in your GloSC config.

[SubSonix]

Yeah, tried every combination that I can think of and no go. They might patch it eventually.

I might even buy year 2 gold on steam if it's on sale on the free weekend/next steam sale :P

[WombatFromHell]

Given that this issue has turned out to be related to a specific interaction with a 3rd party program that is outside the scope of the OSOL project (UPlay specific BattlEye support) I'm going to go ahead and close it. If anything new comes up feel free to open a fresh issue ticket with pertinent information.

Hopefully Valve or the Siege devs will eventually get around to adding some compatibility workarounds for BPM support wrt BattlEye for Siege.

[lahma0]

I think I might have a piece of information relevant to this riddle. I am also running the non-Steam version of Rainbow Six Siege, and I also am having all of the same problems mentioned in this thread (I've tried v1.06k and v1.06l, I've tried adjusting the timeout variables, monitoring all of the log files, and even wrote a script to monitor the uplay/game processes loading/closing/order/etc). Looking through the code for OriginSteamOverlayLauncher and reading some of WombatFromHell's comments in this thread, I'm wondering if the issue could be process-detection related. Once the game is loaded and running, "RainbowSix.exe" appears to be a very strange process. I don't know if it is being virtualized, or what the deal is, but it has virtually no metadata attached to it. Looking at it in Process Explorer, it is has no valid "image" associated with it, meaning it points to no file path, it has no environment, and Process Explorer seems to be a bit confused by the exe in general. It is however definitely the "main" game executable as it consuming nearly 8GB of ram and uses 30%-90% of my CPU. Let me provide some screenshots to better illustrate what I'm talking about, and perhaps this may help you get a better idea of why this may or may not be related to the way OriginSteamOverlayLauncher is doing process detection.

Here is a link to all of the photos listed below in case there is any problem viewing them inside of this post: https://photos.app.goo.gl/umwhDvW4jt0VSJPq1

Let me know if there is any other data I can collect or anything else I can do to help resolve this issue, or if you've decided you're done messing with this issue for now, I totally understand.

Oh, and one more thing, is 'UbisoftGameLauncher.exe' relevant in any way to OriginSteamOverlayLauncher or this process in general? Is this EXE even present in the Steam version of the game?

[WombatFromHell]

I've noticed much the same behavior when I was initially developing a workaround for UPlay launcher behavior.

This is just conjecture on my part, but this executable behavior is extremely likely to be related to the BattlEye proxy which provides client/server anti-cheat capabilities to Siege. Making it harder to find the process to attach to makes it slightly more difficult to inject code into the process in addition to all the other things BattlEye does. A side effect of this is that it can also break overlays, which is likely why the Steam version behaves differently to the UPlay version.

Unfortunately, I'm not able to do much more to diagnose or solve this issue at this time, because I don't have any code built into OSOL to track memory or d3d hooks (nor do I plan to implement any). This "bad behavior" is primarily an issue left to the Steam Input devs to solve by communicating with the Siege devs. If anyone out there is willing to take a crack at it and submit a pull-request I'll gladly cooperate on a solution, to which I'll reopen this and mark it as a 'help wanted'.

To answer your final question (since my version of the game is the Steam version): no, I don't see "UbisoftGameLauncher.exe" in my game directory or any of its subdirectories at all.

[lahma0]

Thanks for the reply WombatFromHell. If I get some free time, I may look into things further. I actually have a lot of recent experience with hooking/code-injection/disassembly of Steam DLLs, so if I figure anything out, I'll definitely try to submit a pull request.

[SubSonix]

And even though I know nothing about coding, I'm more than happy to help test anything :)

[SubSonix]

I noticed that in the 1.07 change log that you got Siege working? Care to elaborate on what you did? :)

[WombatFromHell]

You might be mistaken. I simply compressed the change log from v1.06m into the changes for the v1.07. I didn't really have a chance to test against Siege though.

[SubSonix]

Oh, I didn't realise there was a 1.06m lol

[WombatFromHell]

Is the Steam overlay still broken for the Uplay version of Siege?

[SubSonix]

i wish I could help test this for you, but I ended up buying the game on Steam while it was on sale.

Hopefully someone can help you out :)

I'll ask around my friends for those who don't have the Steam version and reply again to this asap.