Jump to content
LaunchBox Community Forums

Recommended Posts

  • 2 weeks later...

Thx for the program, however, it doesn't work for me. When I try to launch a rom through snes9x, Launchbox starts the steamlauncherproxy and after some time of waiting it just kills the process and the game does not start. The debug file says:

2019-05-11 15:36:20 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - 'Donkey Kong Country (Super Nintendo Entertainment System)' ShortcutID resolved to: 13164476238636515328
2019-05-11 15:36:20 [INFO] [ProxyEmulator] [StartProcessWatcher] - Starting ProcessWatcher on 'snes9x-x64.exe'.
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [.ctor] - Instantiated ProcessWatcher for file 'snes9x-x64.exe' (WaitForStartTimeout: 10s).
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [Start] - EventWatcher enabled.
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - Scheduling Process Start Timeout Check.
2019-05-11 15:36:20 [INFO] [SteamShortcutManager] [LaunchShortcut] - Starting Steam shortcut: steam://rungameid/13164476238636515328
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - ProcessWatcher timeout triggered (process did not start in allotted time).
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [OnProcessStatusUpdated] - Invoking 'StatusUpdatedEventHandler' for event type 'WaitForStartTimeout'.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [ProcessWatcherOnStatusUpdated] - Timed out waiting for 'snes9x-x64.exe'.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [ProcWatcher] - Disposing previous ProcessWatcher instance.
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [Stop] - EventWatcher disabled.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [KillProxyProcesses] - Killing SteamLaunchProxy ProcID '10356'...
2019-05-11 15:36:30 [INFO] [GameLaunchingPlugin] [OnGameExited] - GameLaunchingPlugin:OnGameExited()
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
 

 

any ideas?

Link to comment
Share on other sites

16 hours ago, SiriusVI said:

Thx for the program, however, it doesn't work for me. When I try to launch a rom through snes9x, Launchbox starts the steamlauncherproxy and after some time of waiting it just kills the process and the game does not start. The debug file says:

2019-05-11 15:36:20 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - 'Donkey Kong Country (Super Nintendo Entertainment System)' ShortcutID resolved to: 13164476238636515328
2019-05-11 15:36:20 [INFO] [ProxyEmulator] [StartProcessWatcher] - Starting ProcessWatcher on 'snes9x-x64.exe'.
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [.ctor] - Instantiated ProcessWatcher for file 'snes9x-x64.exe' (WaitForStartTimeout: 10s).
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [Start] - EventWatcher enabled.
2019-05-11 15:36:20 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - Scheduling Process Start Timeout Check.
2019-05-11 15:36:20 [INFO] [SteamShortcutManager] [LaunchShortcut] - Starting Steam shortcut: steam://rungameid/13164476238636515328
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - ProcessWatcher timeout triggered (process did not start in allotted time).
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [OnProcessStatusUpdated] - Invoking 'StatusUpdatedEventHandler' for event type 'WaitForStartTimeout'.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [ProcessWatcherOnStatusUpdated] - Timed out waiting for 'snes9x-x64.exe'.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [ProcWatcher] - Disposing previous ProcessWatcher instance.
2019-05-11 15:36:30 [INFO] [ProcessWatcher] [Stop] - EventWatcher disabled.
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [KillProxyProcesses] - Killing SteamLaunchProxy ProcID '10356'...
2019-05-11 15:36:30 [INFO] [GameLaunchingPlugin] [OnGameExited] - GameLaunchingPlugin:OnGameExited()
2019-05-11 15:36:30 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
 

 

any ideas?

Hey @SiriusVI, I just saw/accepted your friend request on Steam. You're offline now, but when you get back on, hit me up, and I'd be happy to help you figure out what the issue is. I'll probably need to see a bit more of your debug.log so we can verify that the Steam initialization stuff is working correctly. It should not be difficult to resolve. If you actually read enough of the plugin description to figure out how to turn on debug logging, you're way ahead of the curve ;) Just hit me up on Steam and we'll get it figured out in a jiffy.

Link to comment
Share on other sites

1 hour ago, alfredolvera said:

Hey @Lahma any new version we can help you test in the meantime? :) Cheers!

Actually, I've been sharing a private alpha of the new update with a few users, and I think I've decided that I'm going to go ahead and promote it to "beta" status and post it on the plugin download page. It has fixed a wide array of problems and despite there always being more to do, and more stuff I would like to cram into every update, I think this release is stable enough to post publicly. Give me a little bit to update the version information on the DLL, post the changelog, and update the download page. I'll go ahead and do it right now. 

By the way, anyone who wants to test pre-release builds of the plugin can msg me on Steam and I would be happy to bring you on board as a tester. The reason I don't share these builds publicly is that they can sometimes have significant bugs or problems, and I don't want general users to confuse them for stable releases. Since I help anyone who is having problems and msgs me, even going so far as using remote control software (TeamViewer) to directly troubleshoot the issue, this could potentially take up a lot more of my time on performing unnecessary support. With that being said, I'm always happy to have more people testing private/pre-release/alpha builds and having more testers could actually be very helpful to me in finding those sneaky, less common bugs that often requires a bigger pool of users with varying configs/setups. 

Edited by Lahma
  • Like 1
Link to comment
Share on other sites

I just finished uploading the new v0.9.2.0 beta update to the plugin download page. For a list of changes and bug fixes, see the Change Log at the bottom of the plugin download page. If you have any problems with the new update or you just have a question, please feel free to contact me via PM, Steam, or via this thread. I would love to hear your any feedback on this new update. Please let me know if it is working well for you, or if you think its a piece of junk that is responsible for blowing up your computer or killing your cat, I would like to know that as well ? Enjoy!

 

  • Like 1
Link to comment
Share on other sites

Just a heads up for anyone interested ( @jwarn010, @SiriusVI ), the next big thing on my to-do list is to see if I can get the plugin working with Steam Big Picture Mode (either LaunchBox/BigBox having been run through BPM or just while BPM is running in the background). I know it is not currently working (or at least a couple of you have reported to me that that is the case) but seeing as I have never tested it, or even thought of doing so, I won't have any idea of the feasibility/difficulty until I look into it a bit further. I will keep y'all updated in this thread.

  • Like 2
Link to comment
Share on other sites

I wanted to let y'all know that @cammelspit notified me that he was having issues with the plugin on the newest Steam beta client that was released a couple of days ago. I have not had time to look into it yet, so I don't know if it was an issue specific to his setup or if indeed Steam changed something in the beta that broke compatibility with the plugin. I'm going to try to look into it soon, but it would be great to hear feedback from anyone else who has used the plugin on the Steam beta and whether or not you had any problems with it.

Link to comment
Share on other sites

  • 4 weeks later...

Hi thanks for this, it's exactly what I need to use my Steam controller with games from GOG and elsewhere directly through LB!

However for the life of me I cannot get it to work. Always crashes when I go to launch a game. On launching a game Steam instantly closes and LB hangs until I kill the process. Am I missing a trick or have Valve borked it with an update do you know?

 

2019-06-16 15:03:36 [INFO] [LaunchViaSteamMenuItem] [.ctor] - SteamLauncher v0.9.2.0 loaded (64-bit mode) from 'T:\LaunchBox\Plugins\SteamLauncher\SteamLauncher.dll'.


2019-06-16 15:03:36 [INFO] [LaunchViaSteamSystemMenuItem] [.ctor] - ISystemMenuItemPlugin loaded - 'UniversalSteamLaunching' is set to True.
2019-06-16 15:03:36 [INFO] [GameLaunchingPlugin] [.ctor] - IGameLaunchingPlugin loaded.
2019-06-16 15:03:50 [INFO] [LaunchViaSteamSystemMenuItem] [OnSelected] - Universal Steam Launching was toggled OFF
2019-06-16 15:04:13 [INFO] [GameLaunchingPlugin] [OnBeforeGameLaunching] - GameLaunchingPlugin:OnBeforeGameLaunching() - Game: The Witcher 3: Wild Hunt - Game of the Year Edition 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64\witcher3.exe'
2019-06-16 15:04:14 [INFO] [GameLaunchingPlugin] [OnAfterGameLaunched] - GameLaunchingPlugin:OnAfterGameLaunched() - Game: The Witcher 3: Wild Hunt - Game of the Year Edition 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64\witcher3.exe'
2019-06-16 15:05:02 [INFO] [GameLaunchingPlugin] [OnGameExited] - GameLaunchingPlugin:OnGameExited()
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamInstallPath] - Setting Steam installation path to: 'c:\program files (x86)\steam'
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamClientDllPath] - Setting Steam Client DLL path to: 'c:\program files (x86)\steam\steamclient64.dll'
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamExePath] - Setting Steam EXE path to: 'c:\program files (x86)\steam\Steam.exe'
2019-06-16 15:05:49 [INFO] [GameShortcut] [.ctor] - Creating Game Shortcut - Platform: 'Windows'; Title: 'Witcher 3: Wild Hunt - Game of the Year Edition'
2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - Generating Steam shortcut...
    2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - LaunchBox directory located at: 'T:\LaunchBox'
    2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - Exe Path: 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64\witcher3.exe'
    2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - Arguments: ''
    2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - Start Directory: 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64'
    2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GenerateShortcut] - Original Platform Name: Windows; Custom Platform Name: [EMPTY]; (Changed: True)
2019-06-16 15:05:49 [INFO] [SteamContext] [.ctor] - Instantiating SteamContext singleton...
2019-06-16 15:05:49 [INFO] [SteamContext] [ClientShortcuts] - Initializing ClientShortcuts...
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamPid] - Attempting to retrieve Steam PID from registry value named 'pid' inside the key 'HKEY_CURRENT_USER\Software\Valve\Steam\ActiveProcess'.
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '11572'.
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [SteamProcess] - Steam is already running.
2019-06-16 15:05:49 [INFO] [SteamContext] [InitSteam] - Beginning initialization of Steam...
    2019-06-16 15:05:49 [INFO] [SteamContext] [InitSteam] - Steam initialization succeeded!
2019-06-16 15:05:49 [INFO] [SteamContext] [InitClientEngineInterface] - Beginning initialization of the ClientEngine interface...
    2019-06-16 15:05:49 [INFO] [SteamContext] [InitClientEngineInterface] - ClientEngine initialization succeded! (CLIENTENGINE_INTERFACE_VERSION005)
2019-06-16 15:05:49 [INFO] [SteamContext] [InitClientShortcutsInterface] - Beginning initialization of the ClientShortcuts interface...
    2019-06-16 15:05:49 [INFO] [SteamContext] [InitClientShortcutsInterface] - ClientShortcuts initialization succeeded!
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamPid] - Attempting to retrieve Steam PID from registry value named 'pid' inside the key 'HKEY_CURRENT_USER\Software\Valve\Steam\ActiveProcess'.
2019-06-16 15:05:49 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '11572'.
2019-06-16 15:05:49 [INFO] [SteamContext] [ClientShortcuts] - Setting LastKnownSteamPid: 11572
2019-06-16 15:05:49 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - Searching 1706174176 shortcuts to find all SteamLauncher shortcuts.
2019-06-16 15:11:00 [INFO] [LaunchViaSteamMenuItem] [.ctor] - SteamLauncher v0.9.2.0 loaded (64-bit mode) from 'T:\LaunchBox\Plugins\SteamLauncher\SteamLauncher.dll'.
2019-06-16 15:11:00 [INFO] [LaunchViaSteamSystemMenuItem] [.ctor] - ISystemMenuItemPlugin loaded - 'UniversalSteamLaunching' is set to True.
2019-06-16 15:11:00 [INFO] [GameLaunchingPlugin] [.ctor] - IGameLaunchingPlugin loaded.
2019-06-16 15:11:24 [INFO] [LaunchViaSteamSystemMenuItem] [OnSelected] - Universal Steam Launching was toggled OFF
2019-06-16 15:12:44 [INFO] [Config] [Save] - Saving config file.
2019-06-16 15:12:44 [INFO] [Config] [Save] - Config file saved.
2019-06-16 15:13:01 [INFO] [LaunchViaSteamMenuItem] [.ctor] - SteamLauncher v0.9.2.0 loaded (64-bit mode) from 'T:\LaunchBox\Plugins\SteamLauncher\SteamLauncher.dll'.
2019-06-16 15:13:01 [INFO] [LaunchViaSteamSystemMenuItem] [.ctor] - ISystemMenuItemPlugin loaded - 'UniversalSteamLaunching' is set to False.
2019-06-16 15:13:01 [INFO] [GameLaunchingPlugin] [.ctor] - IGameLaunchingPlugin loaded.
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamInstallPath] - Setting Steam installation path to: 'c:\program files (x86)\steam'
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamClientDllPath] - Setting Steam Client DLL path to: 'c:\program files (x86)\steam\steamclient64.dll'
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamExePath] - Setting Steam EXE path to: 'c:\program files (x86)\steam\Steam.exe'
2019-06-16 15:15:32 [INFO] [GameShortcut] [.ctor] - Creating Game Shortcut - Platform: 'Windows'; Title: 'Witcher 3: Wild Hunt - Game of the Year Edition'
2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - Generating Steam shortcut...
    2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - LaunchBox directory located at: 'T:\LaunchBox'
    2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - Exe Path: 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64\witcher3.exe'
    2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - Arguments: ''
    2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - Start Directory: 'D:\GOG Galaxy\Games\The Witcher 3 Wild Hunt GOTY\bin\x64'
    2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GenerateShortcut] - Original Platform Name: Windows; Custom Platform Name: [EMPTY]; (Changed: True)
2019-06-16 15:15:32 [INFO] [SteamContext] [.ctor] - Instantiating SteamContext singleton...
2019-06-16 15:15:32 [INFO] [SteamContext] [ClientShortcuts] - Initializing ClientShortcuts...
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamPid] - Attempting to retrieve Steam PID from registry value named 'pid' inside the key 'HKEY_CURRENT_USER\Software\Valve\Steam\ActiveProcess'.
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '3836'.
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [SteamProcess] - Steam is already running.
2019-06-16 15:15:32 [INFO] [SteamContext] [InitSteam] - Beginning initialization of Steam...
    2019-06-16 15:15:32 [INFO] [SteamContext] [InitSteam] - Steam initialization succeeded!
2019-06-16 15:15:32 [INFO] [SteamContext] [InitClientEngineInterface] - Beginning initialization of the ClientEngine interface...
    2019-06-16 15:15:32 [INFO] [SteamContext] [InitClientEngineInterface] - ClientEngine initialization succeded! (CLIENTENGINE_INTERFACE_VERSION005)
2019-06-16 15:15:32 [INFO] [SteamContext] [InitClientShortcutsInterface] - Beginning initialization of the ClientShortcuts interface...
    2019-06-16 15:15:32 [INFO] [SteamContext] [InitClientShortcutsInterface] - ClientShortcuts initialization succeeded!
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamPid] - Attempting to retrieve Steam PID from registry value named 'pid' inside the key 'HKEY_CURRENT_USER\Software\Valve\Steam\ActiveProcess'.
2019-06-16 15:15:32 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '3836'.
2019-06-16 15:15:32 [INFO] [SteamContext] [ClientShortcuts] - Setting LastKnownSteamPid: 3836
2019-06-16 15:15:32 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - Searching 3922208480 shortcuts to find all SteamLauncher shortcuts.

Edited by JedExodus
  • Thanks 1
Link to comment
Share on other sites

Hey guys, sorry for the delay. I've been out of the state, but I'm on my way home now. Prior to leaving town, I FINALLY figured out a resilient method of finding the correct vtable offsets that my plug-in uses (when it interfaces with the Steam client dll) such that Steam updates will no longer break compatibility with my plug-in. Unfortunately I didn't have enough time to post the update before I left, but thankfully this means I already have a working version of the plug-in to post that will fix the problem. I will try to post it first thing tomorrow when I get home. This should be the last time anyone has to worry about a Steam update breaking compatibility with my plug-in (I can nearly guarantee it.) I appreciate y'all being patient!

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

1 minute ago, Lahma said:

Hey guys, sorry for the delay. I've been out of the state, but I'm on my way home now. Prior to leaving town, I FINALLY figured out a resilient method of finding the correct vtable offsets that my plug-in uses (when it interfaces with the Steam client dll) such that Steam updates will no longer break compatibility with my plug-in. Unfortunately I didn't have enough time to post the update before I left, but thankfully this means I already have a working version of the plug-in to post that will fix the problem. I will try to post it first thing tomorrow when I get home. This should be the last time anyone has to worry about a Steam update breaking compatibility with my plug-in (I can nearly guarantee it.) I appreciate y'all being patient!

Sounds awesome! No worries on the delay. Also no rush at least for me :D

  • Like 1
Link to comment
Share on other sites

Thank you lahma. Absolutely no apology required, the community is very fortunate to have contributors such as yourself. 

I'm relatively new to LB and haven't used your tool as of yet but it's going to be of great use to me and no doubt others. 

Thank you again for all your hard work, by reading through the thread I can see you've been very attentive and helpful, you're a hero!

  • Thanks 1
Link to comment
Share on other sites

14 hours ago, JedExodus said:

Thank you lahma. Absolutely no apology required, the community is very fortunate to have contributors such as yourself. 

I'm relatively new to LB and haven't used your tool as of yet but it's going to be of great use to me and no doubt others. 

Thank you again for all your hard work, by reading through the thread I can see you've been very attentive and helpful, you're a hero!

I appreciate the kind words! I hope you find the plugin useful. Once you're able to give it a try, please share your experience.

  • Like 1
Link to comment
Share on other sites

The new update is available for download (Beta v0.9.3.0). The only change in this update is the addition of a resilient//reliable means of finding the needed Steam client DLL vtable offsets. This one has been a long time coming... It was VERY tricky trying to figure out how to do this in a reliable way that would make it resistant to future Steam updates. I am confident that this should finally fix the problem of any Steam update potentially breaking compatibility with the plugin. You can download the new update here:

As always, BE ABSOLUTELY SURE that you do not have 2 copies of the plugin ANYWHERE within the LaunchBox directory structure at the same time. This means, if you want to backup the old version of your plugin prior to updating, you must cut/copy and paste the SteamLauncher directory somewhere completely outside of the the LaunchBox directory (such as your desktop). Being that the previous version of the plugin does not work at all anymore (with the latest Steam version), I would suggest just extracting the new SteamLauncher.dll and overwriting the old one... that should make things simple. You shouldn't have to delete your config.xml file or anything. There should not be any compatibility issues in that regard.

Edited by Lahma
  • Thanks 1
Link to comment
Share on other sites

IMPORTANT:

I very briefly uploaded the wrong version of the plugin when I updated the plugin download page. The wrong rar was only posted for about 10 min (at around 5:20 AM CST time). It appears that 1 or 2 people might have downloaded it though.. so if you did, please be sure to go to the download page again and download the correct version. Sorry about the confusion.

Link to comment
Share on other sites

Oh, and one more thing... While I didn't include the feature with this last update, mostly because it needs a bit more testing, I have come up with a round-about way of making the plugin compatible with the new LaunchBox pause screen feature. It relies on some fairly hackish behavior, but it does seem to be working well. For those who care, I will explain a bit further.

Since the plugin relies on using a "proxy" process that it uses as a substitute process (for the emulator/game process) within LaunchBox, without any additional code, LaunchBox is attempting to interface with the proxy process instead of the game/emulator process. The result of this is that when you use the LB pause screen, instead of it suspending the game/emulator process, it is instead suspending the proxy process. This obviously isn't the desired behavior since the game/emulator won't be suspended (although for games/emulators that automatically pause when focus is lost, it may appear to do so) and any hotkeys sent by the LB pause screen will be sent to the proxy instead of the game/emulator.

The workaround relies on using methods outside of the LB plugin API (I guess this is fairly obvious)... By using dynamic objects, and maybe a little bit of reflection, I can essentially gain access to LB's internal "Currently Running Process" reference. I can then reassign this reference to a new Process object (a Process object pointing to the actual game/emulator process), forcibly unsubscribing from the old Process event handler, creating a new Process event handler, and then having that Process event handler call the internal LB Process event handler. Doing this essentially makes LB see the Steam-launched game/emulator as the process that it would have normally handled the launch of itself. 

It is definitely going to need some more testing before a public release, but I just thought I'd let y'all know that I am working on it. If anyone find the new LB pause screens really useful and would like to help with testing an alpha of this new functionality, hit me up on Steam. Having a few people helping with testing would probably be very useful. Thanks!

  • Thanks 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...