-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ranbow six siege - Anyone having issues. #12
Comments
I happen to have Siege. I'll investigate. |
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):
|
Ok thanks. Seems something else is causing the issue. I take a loot around. |
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.
|
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.) |
Nope they are not running in admin mode No overlays are running at the moment. |
I feel something from an update to steam or uplay messed something up. |
Maybe check the (Edit: For instance, mine has something like this):
|
Following that idea, there should also be a |
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. |
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. |
|
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. |
Thats for a diffrent game. It wont hook at all with any uplay games |
and it works with origin and starwars. |
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. |
Im going to rebuild my steam files and see what it does. |
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. |
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. |
Here is what happens when i use the new update.
|
(Edit: To clarify, |
still no luck i swear its uplay, ive seen some other report the same issue.
|
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 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. |
I'm having the same issue of it not showing the steam overlay. 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. GameOverlayRenderer.log OriginSteamOverlayLauncher_Log.txt GameOverlayUI.exe.log - Didn't change during this session. |
Overlay for Siege won't work right now. Seems that whatever they did with the update messed up non native steam overlay. |
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. |
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) |
I'll investigate and report back. |
OSOL seems to not be handling the UPlay launcher properly when using (Edit: Correction, executable monitoring seems to break when the MainModule is null. Working on a fix right now.) |
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. |
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] [9/2/18 1:00:57 PM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher |
Here are some snippets from the source code.
|
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. |
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): [11/2/18 6:30:15 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher EDIT Perhaps a variable timer for attaching BPM to the game would help? |
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 |
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 :) |
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 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 |
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.) |
[12/2/18 9:50:34 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher I think this is just a steam issue now, unless that tells you anything? |
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? |
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. |
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.) |
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 :/) |
Reporting back after testing on my partners PC - Runs exactly the same, with the process restarts etc, and no overlay. |
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 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. |
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 |
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. |
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: 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? |
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. |
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. |
And even though I know nothing about coding, I'm more than happy to help test anything :) |
I noticed that in the 1.07 change log that you got Siege working? Care to elaborate on what you did? :) |
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. |
Oh, I didn't realise there was a 1.06m lol |
Is the Steam overlay still broken for the Uplay version of Siege? |
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. |
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?
The text was updated successfully, but these errors were encountered: