Lahma
-
Posts
404 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Lahma
-
Huh.. Never would have thought to suggest that one. Would be very interesting if that did indeed fix the issues for @Corgana and @fromlostdays.
-
Ya, I'm 100% sure the problem isn't related to my plugin. I was just trying to offer some helpful troubleshooting advice. Hopefully either you or @fromlostdays can figure out what is specifically causing the issue. Despite the problem not being related to SteamLauncher, if 2 of you are experiencing the issue already, I suspect there will be others asking for help with the same problem. It would be nice to be able to point them towards a solution, even if it isn't my responsibility.
-
@Corgana, I would definitely try a selective startup before you go messing with DDU. You're not at risk of messing anything up doing that.
-
Huh... that is an interesting outcome... I am an indeed using Vulkan in Cemu and the overlay is working just fine. It seems pretty clear to me that there is common component shared by both you and @Corgana which is causing the issue. Again, I'm pretty sure the Cemu version has nothing to do with the problem @Corgana. My guess would be that there is some conflicting software or driver that is causing the problem, specifically in relation to the Vulkan renderer. I will be interested to hear from @Corgana if the overlay starts working for him as well whenever he switches to the OpenGL renderer in Cemu. If so, I would guess that you are both likely running the same problematic software/driver. If not, it may be a more generalized issue related to an OS setting or shared component used in many different software packages. My recommendation for both of you would be to try to do a 'Diagnostic Startup' or a 'Selective Startup' (with both 'Load system services' and 'Load startup items' unchecked) and then try to launch Cemu via Steam (without starting any other software or services) and see what the result is. You can find this option by opening your start menu and typing 'msconfig'. On the 'General' tab, you will see the options I mentioned: Are both of you using Nvidia GPU's? If not, what is your GPU vendor? If the issue is related to the GPU driver, it is unlikely that a 'Selective Startup' will remedy the problem. If the 'Selective Startup' doesn't help narrow down the issue, as a last resort, I would attempt to use DDU (along with exactly following its instructions for how to use it) to uninstall your GPU driver. Following that, you can then load the latest version of your GPU driver and try again. Hopefully we can figure out how to resolve the issue, and identify exactly what the problematic component is, because I suspect there will be others encountering the same issue if there are already 2 of you having the same problem in our relatively small group of users. Remind me again, are both of you using Windows 10 or Windows 11?
-
Hey @fromlostdays, just to be sure, I checked all my software versions and it looks like the issue likely has nothing to do with that. I too am using the lastest Cemu 1.26.2 (product version 1.26.2f), the latest LaunchBox 12.11, and the latest version of Steam. The overlay is working fine for me. Remind me again.. You said that when you manually add Cemu as a non-Steam shortcut to Steam that the overlay still doesn't work (even after you load a game in Cemu), right? Do me a favor and check these Steam settings and tell me if you have them set the same as me: Let me ask you a few more questions to see if we can't figure out this issue of yours. Are you using Vulkan or OpenGL in Cemu? Do you have any other software installed/running which might be trying to inject its own overlay (MSI Afterburner/Riva Tuner, Xbox Game Bar, Nvidia GeForce Experience, Discord, SpecialK, etc)? ***BIG ONE*** Are you trying to run Cemu as administrator ('Run this program as administrator' checked in the 'Compatibility' tab in the cemu.exe file properties dialog) when Steam and/or LaunchBox are NOT running as administrator? (This will absolutely cause the overlay not to work as Steam can't inject its overlay into a process running with higher privileges than itself.) When you respond back with this info (and if none of this fixed your issue), I will see what else I can suggest that might be helpful in troubleshooting the issue. If worst comes to worst, I'd be happy to remote into your machine for a few min to see if I can resolve the issue (Teamviewer, Windows Remote Desktop, or whatever). Just let me know!
-
Hey @Qbertzelious! While the vast majority of games work without any issues, there are always a plethora of exceptions that can be caused by a variety of issues. In almost every single case, this is not going to be a result of any limitation with the plugin or its capabilities but instead, it is likely going to be an issue with Steam being able to hook the game properly and inject its overlay. One way you can test any game exe to be sure that there isn't a problem with SteamLauncher itself is by opening Steam and manually adding that game EXE to Steam's library via the "Add non-Steam game" feature. If you add the game exe to Steam that way and try to manually launch the game through Steam and the overlay doesn't work, then you know that the problem is related to Steam not being able to hook the game and injects its overlay. With that being said, there are often many ways you can work around the issue of Steam not being able to inject its overlay. Without knowing the exact issue you're facing though, its hard for me to suggest any workarounds to try. From what little info I could find online, it sounds like Prodeus is a Unity game. If you'd like me to try to help you troubleshoot the issue, do a few things for me: Tell me what the path is to the game exe Tell me what other executables you see in that same path (I'm trying to figure out if the game has a launcher exe or not).. Might be easier to just post a screenshot of the game's folder in file explorer Create a non-Steam shortcut pointing to the game exe in Steam and then open up that non-Steam game's properties window and copy paste the following into the "Launch Options" field without the quotes: "-show-screen-selector" Now try to launch that non-Steam shortcut.. because of the "-show-screen-selector" command line argument, you will likely see a pop-up window prior to the game launching that allows you to change some graphics options and such.. just choose whatever (or change nothing) and run the game and check if the Steam overlay works (press SHIFT+TAB or the menu button if you're using a controller) Once I've got that info from you, hopefully we can figure out what the issue is. I assume you've got the plugin working with other games/emulators/roms within LaunchBox, right? It is just this game that you are having an issue with, correct?
-
I'm glad everything is working out well for you @JedExodus! Please let me know if you come across any issues or have any ideas for improvements or new features. Sorry @Cheslin, somehow I missed your message. Was the recommendation from @fromlostdays able to fix your issue? If not, could you please provide a bit more detail as to what you are trying to accomplish or what issue you are having?
-
Hey @Qbertzelious! If you used the LaunchBox importer tool to import your GOG games and you open up the properties of those titles and they point to a custom URL (such as gog://launch/XXXXX or something similar), then they cannot work with SteamLauncher simply because it is impossible to intercept and redirect the game launch process. If the game properties however point to the game EXE or a shortcut file (.lnk) that points to the game exe, then it should work fine with SteamLauncher. If the game does use a custom URL, you can simply modify it to point the game executable instead and it should work fine then. If you find that your GOG imported games are pointing to the game exe or a shortcut that points to the game exe and they still aren't working, let me know, and I can look into the issue further and figure out what is going on. I hope that was a sufficient explanation. If not, let me know, and I will try to articulate further. Thanks!
-
Ya, I did notice that actually. The problem is related to the dark WPF theme I'm using for the UI. I messed with it briefly but the theme consists of a PILE of XAML code I have to sort through to fix the issue, so I ultimately decided it wasn't big enough of an issue compared to getting the update out as quickly as possible. I will definitely fix it though and release another minor update as quickly as possible. I appreciate the report @Corgana.
-
Just posted the new update. Thanks to everyone who reported bugs and thanks to @JedExodus for requesting the addition of the 'Status' filter type to the 'Selective Use' feature. v0.9.8.1 (May 24, 2022) Fixed a bug which crashed the plugin if the user did not already have 'config.xml' and 'vtables.xml' files in their SteamLauncher directory. Added a 'Status' filter type to the 'Selective Use' feature which should help filter based on where games were imported from (Xbox Game Pass, GOG, etc).
-
Appreciate the feedback @Corgana! FYI, I'm fixing to post another update which fixes a couple of bugs (crashes related to not having 'config.xml' and 'vtables.xml' files already in your SteamLauncher directory from previous releases) and also adds an additional 'Filter Type' to the 'Selective Use' feature.
-
As I said, I didn't do a lot of testing prior to releasing the update 🤔 I appreciate the reports @CookiePLMonster , @Razor112, and @Nokiaman. I'm working on fixing the bug(s) and I will release a new update shortly.
-
Its gotta be something with your setup @Razor112 because yours is the 1st report I've gotten of this issue. There are many other people having absolutely no issue with the new update. If you msg me on Steam, I would be happy to help you troubleshoot the issue.
-
No problem! Sorry it took so long to get the update out. Hopefully all the time I spent rewriting a large portion of the code ends up making future updates much quicker and easier to perform. Manual updates of the actual plugin DLL should now only need to be done for actual feature updates and bug fixes and such. Any breaking changes made to the Steam client library should now be fixable with a quick and easy update to the online definitions database. I look forward to hearing about your (or anyone else's) experience with the 'Selective Use' feature (if that is something you are even interested in). I need to look back through the support thread and see specifically who it was that was requesting that feature (I know there was at least a few of you).
-
The new update, v0.9.8.0, has been posted to the plugin download page. Please note, I have not done extensive testing on this prior to release. If you have any issues or find any bugs, please report them here in the support thread and I will attempt to fix them as quickly as possible. Also, please let me know how the new 'Selective Use' (or 'Filtering') feature works for all of you. I'm curious to know if many of you find it helpful or not. Thanks! v0.9.8.0 (May 23, 2022) Overhauled a large portion of the codebase, changing nearly all functionality related to Steam internals into dynamic code that can be updated from an online database. Now, regardless of whether vtable offsets are modified or the number/order/type of parameters are changed, I can fix any broken functionality by simply updating an online definitions database. This should make future updates much quicker and more seamless. Added a much requested feature: the ability to selectively use the plugin based on a list of filters. This new feature can be found in the settings menu under the tab labeled 'Selective Use'. I won't go into a lot of detail here as I believe it is pretty self-explanatory but I will describe one thing that might not be totally clear by the description in the settings menu. In LaunchBox, if you open any game's properties window and navigate to the 'Custom Fields' tab, you can add a new entry and set the key to 'SLEnabled' (without the quotes). If you then set the value to '0', this game will ALWAYS be ignored by SteamLauncher, regardless of any user-supplied filters. Alternatively, you can set the value to '1' and this game will ALWAYS have its launch intercepted (and run via Steam) by SteamLauncher, regardless of any user-supplied filters. If you have any additional questions, just leave a message on the support thread and I would be happy to explain things further.
-
FINALLY, got the new update compiled and working. Doing a bit of testing and bug fixing before I push out the update.
-
Just wanted to let y'all know I'm very close to having things finished up. Obviously it has taken a bit longer than expected (what's new, right?) but considering I've completely rewritten about 30% of the code base from scratch and have spent about 25 hours coding in just the last few days, the update has been delayed for lack of trying. Give me just 1 or 2 more days and I'll have the update ready. The update will also include the new filtering or "conditional usage" functionality many of you have been requesting. You can view the link below for more info on how it will work:
- 851 replies
-
- 10
-
-
-
-
Just wanted to let y'all know that I'm aware that the latest Steam update broke the plugin. I'm coding away as quickly as possible to get the fix pushed out. I'm trying to get the fix pushed out in the next day if I can. The release might prove to be a bit buggy since it will include month's of other major changes I've made to the code base but I can fix any bugs that are found quickly. I'll post back here when I push out the update.
-
There is no problem with the plugin on Windows 11. I develop and run the plugin on Windows 11. The only current issue is if you're running the Steam beta which I will push out an update for soon. You won't have to actually manually update the plugin though. As long as you have internet access, the plugin will automatically update its vtable offset list online which should fix the issue with the Steam beta. I'm trying to push out the update as quickly as possible but as usual, I'm just a bit swamped with work stuff at the moment. Hopefully I should be able to get the updated offset list pushed out in the next few days though. Sorry about the delay. If you want to msg me on Steam @The_Keeper86, I can remotely connect to your machine over TeamViewer and see what the problem is. I can assure you that the problem isn't directly related to Windows 11 though. Regardless, I would be happy to help you out. Just let me know.
-
Oh joy... Appears Valve has likely made some major changes to the Steam Client Shortcuts interface again... Likely some of the vtable offsets have changed. I will look into this as quickly as possible so that those of you who wish to use the beta version of Steam may continue to do so. Note: I have not actually verified that the beta version of Steam is broken with the plugin.. I am only assuming so based on several of your posts concerning issues while using the beta version of Steam.
-
Just leaving a note here that I talked with @The_Keeper86 directly on Steam about the issues he was having.
-
I just specifically tested the setup that I suggested (run Steam as admin, run LB as admin, launch Genshin from LB with SteamLauncher enabled) and everything works fine including the Steam overlay. Just to be sure, in LB, your Genshin Impact game entry is pointed to "GenshinImpact.exe", right (as opposed to trying to launch a Steam URL or the Genshin Impact Launcher or something else)? While you can certainly open up the file properties and configure an exe to run as admin if you want to, when I'm saying to run something as admin, I'm simply referring to right clicking the exe (or a shortcut to it) and clicking "Run as administrator". Btw, you don't need to set "SteamOverlayUI" to run as admin... It is launched by Steam so it will run with whatever permissions Steam is run with. Let me expound on that a bit more actually... The only reason Steam would have to be run as admin for its overlay to work is if a particular game has a flag set that requires it to be run as admin (which unfortunately is common these days because of lazy devs and terrible programming practices.. in 99% of cases you can actually force these games to run without admin permissions by using a special command). The reason this is so is because if a game is running as admin and Steam is not, Steam won't have the appropriate permissions to inject its overlay into the game process (because low/medium privilege processes can't inject code into high privilege processes). Furthermore, if you're seeing a UAC ("Do you want to allow this app to make changes to your device?") dialog when you run a game from a launcher (whether that be LB, Steam, or whatever), then that means that the launcher is NOT running as admin. Any process that is running as admin will NOT show a UAC dialog whenever it launches another process with admin privileges (by default, a process launches other processes with the same privileges it has.. so if it is running as admin, it will launch other processes as admin and won't show a UAC dialog)... so if you're seeing a UAC dialog when you try to launch Genshin from LB/Steam/etc, then you can be sure that for whatever reason your launcher is not actually running as admin. I guess I'm unfamiliar with the windows nag notification you're talking about... Unless you're talking about UAC? If you're referring to UAC, then you absolutely should NOT turn it off. You're making a huge sacrifice in security doing so. You're welcome to take my advice or leave it but being that my occupation is in reverse code engineering (computer security), I can confidently tell you from an educated perspective that disabling UAC is a terrible idea unless you have a good reason for doing so and know what you're doing. You really should not run anything as admin that you don't have to... If there is a bug in a piece of software that can be exploited by an attacker and that software is running as admin, the attacker will have complete, unmitigated access on your system and can do anything they please. You're of course always going to be playing a balancing game between convenience and security and only you can decide how much security you're willing to trade for convenience. My suggestion would be to only run Steam/LB as admin whenever absolutely necessary (such as when playing Genshin). In an ideal world, for normal, every-day tasks, users wouldn't even log into Windows with an administrator account.. However, due to a wide variety of issues, this isn't realistic for most people and that is exactly the reason that UAC exists. It helps to keep certain processes from running with unlimited, admin-level rights and warns you whenever a process tries to obtain admin privileges.
-
Just wanted to followup with you and see if you were able to get the overlay working with my previous advice. Let me know if it works out for you. Edit: Just thought I would also note that if you put the text '-show-screen-selector' (without the quotes) under 'Launch Options' in your non-Steam shortcut (or as a launch argument in LB), this will force the Unity screen selector dialog to be shown prior to Genshin launching which will allow you to set custom resolution and graphics options prior to the game launching (including being able to force windowed mode).
-
Steam has to be running as admin and if you want to launch it through LB using SteamLauncher, you'll have to run LaunchBox as admin too. The reason for this is Genshin's stupid anti-cheat driver which is implemented very poorly. It requires Genshin to be running as admin in order for it to communicate with the kernel driver.
-
I'm working on it. Got it mostly implemented already actually. Just need to do a bit more testing and then implement a tab in the GUI for managing the feature. You can refer to this previous post of mine to see the concept for how the feature will function:
