Lahma

June 24, 2019

On 6/22/2019 at 4:22 PM, JedExodus said:

I am definitely a novice when it comes to MAME, but it certainly seems to work with (nay require) zipped files. I have tried forcing the video mode to OpenGL inside MAME just to make sure the Steam overlay worked with it. When I launch with desktop steam overlay successfully and map controls to my Steam Controller it opens this up in a second window, with all the big picture mode . However it is binding to desktop mode only. So it doesn't seem to be picking up this instance of the game I think? Unchecking the option to use Big Picture mode and then launching with Steam controller the game still fails to boot as well funnily.

As far as the cheeky features go I was thinking of being to enable or disable on a per game or per platform basis. I run my ScummVM games through a launcher (there's probably a far more sensible way to do this) and that isn't compatible for me. Not sure if it's possible but would be very nice for the fringe case games/platforms so it's smoother when launching BigBox on the main telly.

Thanks again!

PS. Oh and the launch arguments look normal to me, just a mirror of LB's

Hey @JedExodus, like I said previously, I am a total Mame noob, but @cammelspit has been looking into this issue for like 2 days now (seriously.. he has spent a ridiculous amount of time trying to figure out whats going on), and its become very clear that there has been some recent changes (Windows? Steam? Mame?) that have broken Mame with Steam. Unfortunately (or fortunately depending on your perspective) this is completely unrelated to my plugin and therefore is not something I can fix. You can verify this by adding Mame as a non-Steam shortcut to Steam and trying to run it with any controller turned on/plugged in. If you have your Mame video mode set to "auto", you will get a "MAME has stopped working" msg box. If you have your Mame video mode set to "opengl", the Mame process will silently crash/close. Hopefully someone in the Mame/Steam community will figure out what is going on with this soon, but until then, there is unfortunately not a lot I can do. If I have an over abundance of time one day, and the problem still isn't resolved, I can possibly try to debug the crash to try to narrow down the cause, but I would prefer to leave that up to others since it is obviously outside of the scope of the plugin. One thing I can say is that it does not appear to be related to a recent Windows 10 update... @cammelspit is running the latest Windows 10 update but I am running a much older Windows 10 version (1709), and we are seeing the same exact issue.

Now, onto something I can offer you some help with... I can definitely help you to get your ScummVM launcher working with the plugin. It will probably only require a couple of simple steps. First, can you tell me specifically what launcher you're using and what format it is? Is it a .bat file or an .exe file? If it is a .bat file, you will likely need to use "Bat to Exe Converter" to convert the batch file to an exe. If the batch file stays open for the duration of the game/emulator, you should be able to just convert it to an exe and that should be all that is needed. If however the batch file just launches another exe and immediately closes, you will likely need to either modify that batch file so that it does stay open or you will need to add a "LauncherToExe" entry in my plugin's config.xml file (both still require you to convert the bat to an exe). It should only take about 5-10 min to setup. If you want, shoot me a msg on Steam and I will walk you through the process.

Adding a way to enable/disable SteamLauncher on a per-game or per-platform basis is actually not a bad idea... Should be simple enough to implement. I'm thinking some entries in the SteamLauncher config.xml such as the following might work:

Would something like that work for you?

June 22, 2019

6 hours ago, JedExodus said:

Heya, having trouble loading up Mame for some reason. The oddest part is that it'll work if I have my Steam controller off and click the game with my mouse so the overlay is in desktop mode, but if the Steam overlay is on big picture mode for any reason it there's nothing doing

Reveal hidden contents

2019-06-22 09:23:12 [INFO] [LaunchViaSteamMenuItem] [.ctor] - SteamLauncher v0.9.3.0 loaded (64-bit mode) from 'T:\LaunchBox\Plugins\SteamLauncher\SteamLauncher.dll'.

2019-06-22 09:23:12 [INFO] [LaunchViaSteamSystemMenuItem] [.ctor] - ISystemMenuItemPlugin loaded - 'UniversalSteamLaunching' is set to True.
2019-06-22 09:23:12 [INFO] [GameLaunchingPlugin] [.ctor] - IGameLaunchingPlugin loaded.
2019-06-22 09:24:08 [INFO] [GameLaunchingPlugin] [OnBeforeGameLaunching] - GameLaunchingPlugin:OnBeforeGameLaunching() - Game: Smash T.V. '..\arcade\smashtv.zip' - Emulator: MAME 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:24:08 [INFO] [ProxyEmulator] [SetLauncherExeToProxy] - Adding a RepairPath to the config - Id: 93f68371-9926-4245-919d-98fb1f24ef4c - Path: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:24:08 [INFO] [Config] [Save] - Saving config file.
2019-06-22 09:24:08 [INFO] [Config] [Save] - Config file saved.
2019-06-22 09:24:08 [INFO] [ProxyEmulator] [SetLauncherExeToProxy] - Set 'MAME' application path to the proxy executable.
2019-06-22 09:24:10 [INFO] [GameLaunchingPlugin] [OnAfterGameLaunched] - GameLaunchingPlugin:OnAfterGameLaunched() - Game: Smash T.V. '..\arcade\smashtv.zip' - Emulator: MAME 'Plugins\SteamLauncher\SteamLauncherProxy.exe'
2019-06-22 09:24:10 [INFO] [ProxyEmulator] [RestoreAppPaths] - Repairing application paths...
2019-06-22 09:24:10 [INFO] [ProxyEmulator] [RestoreAppPaths] - Successfully repaired path! Title: 'MAME' - Path before repair: 'Plugins\SteamLauncher\SteamLauncherProxy.exe' - Path after repair: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:24:10 [INFO] [Config] [Save] - Saving config file.
2019-06-22 09:24:10 [INFO] [Config] [Save] - Config file saved.
2019-06-22 09:24:10 [INFO] [GameShortcut] [.ctor] - Creating Game Shortcut - Platform: 'Arcade'; Title: 'Smash T.V.'
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - Generating Steam shortcut...
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - LaunchBox directory located at: 'T:\LaunchBox'
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - Exe Path: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - Arguments: '-keyboardprovider dinput "T:\arcade\smashtv.zip"'
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - Start Directory: 'D:\emulators\MAME'
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GenerateShortcut] - Original Platform Name: Arcade; Custom Platform Name: Arcade; (Changed: False)
2019-06-22 09:24:11 [INFO] [SteamContext] [.ctor] - Instantiating SteamContext singleton...
2019-06-22 09:24:11 [INFO] [SteamContext] [ClientShortcuts] - Initializing ClientShortcuts...
2019-06-22 09:24:11 [INFO] [SteamProcessInfo] [GetSteamInstallPath] - Setting Steam installation path to: 'C:\Program Files (x86)\Steam'
2019-06-22 09:24:11 [INFO] [SteamProcessInfo] [GetSteamClientDllPath] - Setting Steam Client DLL path to: 'C:\Program Files (x86)\Steam\steamclient64.dll'
2019-06-22 09:24:11 [INFO] [SteamProcessInfo] [GetSteamExePath] - Setting Steam EXE path to: 'C:\Program Files (x86)\Steam\Steam.exe'
2019-06-22 09:24:11 [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-22 09:24:11 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '5160'.
2019-06-22 09:24:11 [INFO] [SteamProcessInfo] [SteamProcess] - Steam is already running.
2019-06-22 09:24:11 [INFO] [SteamContext] [InitSteam] - Beginning initialization of Steam...
2019-06-22 09:24:11 [INFO] [SteamContext] [InitSteam] - Steam initialization succeeded!
2019-06-22 09:24:11 [INFO] [SteamContext] [InitClientEngineInterface] - Beginning initialization of the ClientEngine interface...
2019-06-22 09:24:11 [INFO] [SteamContext] [InitClientEngineInterface] - ClientEngine initialization succeded! (CLIENTENGINE_INTERFACE_VERSION005)
2019-06-22 09:24:11 [INFO] [SteamContext] [InitClientShortcutsInterface] - Beginning initialization of the ClientShortcuts interface...
2019-06-22 09:24:11 [INFO] [SteamContext] [GetShortcutsInterfacePtr] - 'GetIClientShortcuts' vtable entry located at index '54' (IClientEngine+0x1B0).
2019-06-22 09:24:11 [INFO] [SteamContext] [InitClientShortcutsInterface] - ClientShortcuts initialization succeeded!
2019-06-22 09:24:11 [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-22 09:24:11 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '5160'.
2019-06-22 09:24:11 [INFO] [SteamContext] [ClientShortcuts] - Setting LastKnownSteamPid: 5160
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - Searching 2 shortcuts to find all SteamLauncher shortcuts.
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - SteamLauncher shortcut found: [2147483650] Smash T.V. (Arcade)
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [RecycleShortcut] - Recycling shortcut with AppID: 2147483650
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - Assigning properties to existing Steam shortcut: [2147483650] 'Smash T.V. (Arcade)' | "D:\emulators\MAME\mame64.exe" | "D:\emulators\MAME" | -keyboardprovider dinput "T:\arcade\smashtv.zip"
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [ResolveShortcutId] - Attempting to resolve ShortcutID for Smash T.V. (Arcade)...
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - 'Smash T.V. (Arcade)' ShortcutID resolved to: 18376342700698894336
2019-06-22 09:24:11 [INFO] [LauncherToExe] [ResolveRelationship] - No Launcher-to-Exe relationship found for file 'D:\emulators\MAME\mame64.exe'.
2019-06-22 09:24:11 [INFO] [ProxyEmulator] [StartProcessWatcher] - Starting ProcessWatcher on 'mame64.exe'.
2019-06-22 09:24:11 [INFO] [ProcessWatcher] [.ctor] - Instantiated ProcessWatcher for file 'mame64.exe' (WaitForStartTimeout: 10s).
2019-06-22 09:24:11 [INFO] [ProcessWatcher] [Start] - EventWatcher enabled.
2019-06-22 09:24:11 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - Scheduling Process Start Timeout Check.
2019-06-22 09:24:11 [INFO] [SteamShortcutManager] [LaunchShortcut] - Starting Steam shortcut: steam://rungameid/18376342700698894336
2019-06-22 09:24:15 [INFO] [ProcessWatcher] [OnEventArrived] - ProcessWatcher:OnEventArrived contains class name InstanceCreationEvent
2019-06-22 09:24:15 [INFO] [ProcessWatcher] [OnProcessStatusUpdated] - Invoking 'StatusUpdatedEventHandler' for event type 'Started'.
2019-06-22 09:24:15 [INFO] [ProxyEmulator] [ProcessWatcherOnStatusUpdated] - Process 'mame64.exe' started.
2019-06-22 09:24:15 [INFO] [ProxyEmulator] [EnableActiveWindowHook] - Enabling proxy active window hook.
2019-06-22 09:24:15 [INFO] [ActiveWindow] [ActiveWindowChanged] - Adding new subscriber to ActiveWindowChanged.
2019-06-22 09:24:15 [INFO] [ActiveWindow] [EnableHook] - Window event hook enabled.
2019-06-22 09:24:16 [INFO] [ActiveWindow] [WinEventProc] - WinEventProc - Window Title: 'LaunchBox Game Startup' - Handle: '524330'.
2019-06-22 09:24:16 [INFO] [ProxyEmulator] [ProxyOnActiveWindowChanged] - ProxyOnActiveWindowChanged Event - Window Title: 'LaunchBox Game Startup' - Handle: '524330'
2019-06-22 09:24:17 [INFO] [ActiveWindow] [WinEventProc] - WinEventProc - Window Title: 'D:\emulators\MAME\mame64.exe' - Handle: '196770'.
2019-06-22 09:24:17 [INFO] [ProxyEmulator] [ProxyOnActiveWindowChanged] - ProxyOnActiveWindowChanged Event - Window Title: 'D:\emulators\MAME\mame64.exe' - Handle: '196770'
2019-06-22 09:24:17 [INFO] [ActiveWindow] [WinEventProc] - WinEventProc - Window Title: 'MAME: Smash T.V. (rev 8.00) [smashtv]' - Handle: '262556'.
2019-06-22 09:24:17 [INFO] [ProxyEmulator] [ProxyOnActiveWindowChanged] - ProxyOnActiveWindowChanged Event - Window Title: 'MAME: Smash T.V. (rev 8.00) [smashtv]' - Handle: '262556'
2019-06-22 09:24:19 [INFO] [ActiveWindow] [WinEventProc] - WinEventProc - Window Title: 'D:\emulators\MAME\mame64.exe' - Handle: '196770'.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [ProxyOnActiveWindowChanged] - ProxyOnActiveWindowChanged Event - Window Title: 'D:\emulators\MAME\mame64.exe' - Handle: '196770'
2019-06-22 09:24:19 [INFO] [ActiveWindow] [WinEventProc] - WinEventProc - Window Title: 'LaunchBox Big Box' - Handle: '131574'.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [ProxyOnActiveWindowChanged] - ProxyOnActiveWindowChanged Event - Window Title: 'LaunchBox Big Box' - Handle: '131574'
2019-06-22 09:24:19 [INFO] [ProcessWatcher] [OnEventArrived] - ProcessWatcher:OnEventArrived contains class name InstanceDeletionEvent
2019-06-22 09:24:19 [INFO] [ProcessWatcher] [OnProcessStatusUpdated] - Invoking 'StatusUpdatedEventHandler' for event type 'Stopped'.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [ProcessWatcherOnStatusUpdated] - Process 'mame64.exe' stopped.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [ProcWatcher] - Disposing previous ProcessWatcher instance.
2019-06-22 09:24:19 [INFO] [ProcessWatcher] [Stop] - EventWatcher disabled.
2019-06-22 09:24:19 [INFO] [ProxyEmulator] [DisableActiveWindowHook] - Disabling proxy active window hook.
2019-06-22 09:24:19 [INFO] [ActiveWindow] [ActiveWindowChanged] - Removing subscriber from ActiveWindowChanged.
2019-06-22 09:24:19 [INFO] [ActiveWindow] [ActiveWindowChanged] - Last subscriber unsubscribed from ActiveWindowChanged.
2019-06-22 09:24:19 [INFO] [ActiveWindow] [DisableHook] - Window event hook disabled.
2019-06-22 09:24:20 [INFO] [GameLaunchingPlugin] [OnGameExited] - GameLaunchingPlugin:OnGameExited()
2019-06-22 09:24:20 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
2019-06-22 09:24:35 [INFO] [Config] [Save] - Saving config file.
2019-06-22 09:24:35 [INFO] [Config] [Save] - Config file saved.
2019-06-22 09:24:44 [INFO] [LaunchViaSteamMenuItem] [.ctor] - SteamLauncher v0.9.3.0 loaded (64-bit mode) from 'T:\LaunchBox\Plugins\SteamLauncher\SteamLauncher.dll'.
2019-06-22 09:24:44 [INFO] [LaunchViaSteamSystemMenuItem] [.ctor] - ISystemMenuItemPlugin loaded - 'UniversalSteamLaunching' is set to True.
2019-06-22 09:24:44 [INFO] [GameLaunchingPlugin] [.ctor] - IGameLaunchingPlugin loaded.
2019-06-22 09:29:14 [INFO] [GameLaunchingPlugin] [OnBeforeGameLaunching] - GameLaunchingPlugin:OnBeforeGameLaunching() - Game: Smash T.V. '..\arcade\smashtv.zip' - Emulator: MAME 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:29:14 [INFO] [ProxyEmulator] [SetLauncherExeToProxy] - Adding a RepairPath to the config - Id: 93f68371-9926-4245-919d-98fb1f24ef4c - Path: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:29:14 [INFO] [Config] [Save] - Saving config file.
2019-06-22 09:29:14 [INFO] [Config] [Save] - Config file saved.
2019-06-22 09:29:14 [INFO] [ProxyEmulator] [SetLauncherExeToProxy] - Set 'MAME' application path to the proxy executable.
2019-06-22 09:29:14 [INFO] [GameLaunchingPlugin] [OnAfterGameLaunched] - GameLaunchingPlugin:OnAfterGameLaunched() - Game: Smash T.V. '..\arcade\smashtv.zip' - Emulator: MAME 'Plugins\SteamLauncher\SteamLauncherProxy.exe'
2019-06-22 09:29:14 [INFO] [ProxyEmulator] [RestoreAppPaths] - Repairing application paths...
2019-06-22 09:29:14 [INFO] [ProxyEmulator] [RestoreAppPaths] - Successfully repaired path! Title: 'MAME' - Path before repair: 'Plugins\SteamLauncher\SteamLauncherProxy.exe' - Path after repair: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:29:14 [INFO] [Config] [Save] - Saving config file.
2019-06-22 09:29:14 [INFO] [Config] [Save] - Config file saved.
2019-06-22 09:29:14 [INFO] [GameShortcut] [.ctor] - Creating Game Shortcut - Platform: 'Arcade'; Title: 'Smash T.V.'
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - Generating Steam shortcut...
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - LaunchBox directory located at: 'T:\LaunchBox'
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - Exe Path: 'D:\emulators\MAME\mame64.exe'
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - Arguments: '-keyboardprovider dinput "T:\arcade\smashtv.zip"'
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - Start Directory: 'D:\emulators\MAME'
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GenerateShortcut] - Original Platform Name: Arcade; Custom Platform Name: Arcade; (Changed: False)
2019-06-22 09:29:15 [INFO] [SteamContext] [.ctor] - Instantiating SteamContext singleton...
2019-06-22 09:29:15 [INFO] [SteamContext] [ClientShortcuts] - Initializing ClientShortcuts...
2019-06-22 09:29:15 [INFO] [SteamProcessInfo] [GetSteamInstallPath] - Setting Steam installation path to: 'C:\Program Files (x86)\Steam'
2019-06-22 09:29:15 [INFO] [SteamProcessInfo] [GetSteamClientDllPath] - Setting Steam Client DLL path to: 'C:\Program Files (x86)\Steam\steamclient64.dll'
2019-06-22 09:29:15 [INFO] [SteamProcessInfo] [GetSteamExePath] - Setting Steam EXE path to: 'C:\Program Files (x86)\Steam\Steam.exe'
2019-06-22 09:29:15 [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-22 09:29:15 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '5160'.
2019-06-22 09:29:15 [INFO] [SteamProcessInfo] [SteamProcess] - Steam is already running.
2019-06-22 09:29:15 [INFO] [SteamContext] [InitSteam] - Beginning initialization of Steam...
2019-06-22 09:29:15 [INFO] [SteamContext] [InitSteam] - Steam initialization succeeded!
2019-06-22 09:29:15 [INFO] [SteamContext] [InitClientEngineInterface] - Beginning initialization of the ClientEngine interface...
2019-06-22 09:29:15 [INFO] [SteamContext] [InitClientEngineInterface] - ClientEngine initialization succeded! (CLIENTENGINE_INTERFACE_VERSION005)
2019-06-22 09:29:15 [INFO] [SteamContext] [InitClientShortcutsInterface] - Beginning initialization of the ClientShortcuts interface...
2019-06-22 09:29:15 [INFO] [SteamContext] [GetShortcutsInterfacePtr] - 'GetIClientShortcuts' vtable entry located at index '54' (IClientEngine+0x1B0).
2019-06-22 09:29:15 [INFO] [SteamContext] [InitClientShortcutsInterface] - ClientShortcuts initialization succeeded!
2019-06-22 09:29:15 [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-22 09:29:15 [INFO] [SteamProcessInfo] [GetSteamPid] - The Steam PID value retrieved from the registry is '5160'.
2019-06-22 09:29:15 [INFO] [SteamContext] [ClientShortcuts] - Setting LastKnownSteamPid: 5160
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - Searching 2 shortcuts to find all SteamLauncher shortcuts.
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [GetSteamLauncherShortcuts] - SteamLauncher shortcut found: [2147483650] Smash T.V. (Arcade)
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [RecycleShortcut] - Recycling shortcut with AppID: 2147483650
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - Assigning properties to existing Steam shortcut: [2147483650] 'Smash T.V. (Arcade)' | "D:\emulators\MAME\mame64.exe" | "D:\emulators\MAME" | -keyboardprovider dinput "T:\arcade\smashtv.zip"
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [ResolveShortcutId] - Attempting to resolve ShortcutID for Smash T.V. (Arcade)...
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [AssignShortcutProperties] - 'Smash T.V. (Arcade)' ShortcutID resolved to: 18376342700698894336
2019-06-22 09:29:15 [INFO] [LauncherToExe] [ResolveRelationship] - No Launcher-to-Exe relationship found for file 'D:\emulators\MAME\mame64.exe'.
2019-06-22 09:29:15 [INFO] [ProxyEmulator] [StartProcessWatcher] - Starting ProcessWatcher on 'mame64.exe'.
2019-06-22 09:29:15 [INFO] [ProcessWatcher] [.ctor] - Instantiated ProcessWatcher for file 'mame64.exe' (WaitForStartTimeout: 10s).
2019-06-22 09:29:15 [INFO] [ProcessWatcher] [Start] - EventWatcher enabled.
2019-06-22 09:29:15 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - Scheduling Process Start Timeout Check.
2019-06-22 09:29:15 [INFO] [SteamShortcutManager] [LaunchShortcut] - Starting Steam shortcut: steam://rungameid/18376342700698894336
2019-06-22 09:29:25 [INFO] [ProcessWatcher] [ScheduleProcessStartTimeoutCheck] - ProcessWatcher timeout triggered (process did not start in allotted time).
2019-06-22 09:29:25 [INFO] [ProcessWatcher] [OnProcessStatusUpdated] - Invoking 'StatusUpdatedEventHandler' for event type 'WaitForStartTimeout'.
2019-06-22 09:29:25 [INFO] [ProxyEmulator] [ProcessWatcherOnStatusUpdated] - Timed out waiting for 'mame64.exe'.
2019-06-22 09:29:25 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.
2019-06-22 09:29:25 [INFO] [ProxyEmulator] [ProcWatcher] - Disposing previous ProcessWatcher instance.
2019-06-22 09:29:25 [INFO] [ProcessWatcher] [Stop] - EventWatcher disabled.
2019-06-22 09:29:26 [INFO] [GameLaunchingPlugin] [OnGameExited] - GameLaunchingPlugin:OnGameExited()
2019-06-22 09:29:26 [INFO] [ProxyEmulator] [DisposeProxyEmulator] - Disposing ProxyEmulator.

Have a few feature requests but don't want to be too cheeky about it. You work hard enough fella!

Hey @JedExodus, there is a known compatibility issue with using the plugin while Steam Big Picture Mode is running. This is actually the next uncompleted item on my to-do list for the plugin, so hopefully I will be able to investigate/fix this issue for the next release. It will be interesting to see what the issue is as there really should not be any big difference between launching a game via Steam while BPM is on/off. As far as the plugin not working while your Steam controller is on, all you need to do is change the setting so that BPM is not launched when you turn on your controller (or turn you controller on and then exit BPM). Believe it or not, I don't actually use Mame, but there are certainly a lot of other people that do with the plugin. @cammelspit has a lot of experience with Mame actually. Looking at your log (at least the 1st launch attempt), it appears that everything worked correctly and that Mame started successfully. Being that I have no experience with Mame, I don't really know if the launch arguments and stuff look correct... Does Mame support compressed roms (I see that your rom is zipped and I don't see that your have LB set to decompress the rom prior to launching)? One thing you can do is open up Steam, click "Library" and click the last option "Hidden". You should then see the hidden shortcut that the plugin created. You can check the properties of that shortcut to make sure everything looks correct and you can also try launching the shortcut manually to see if it works. I might ask @cammelspit to look at your log to see if your Mame launch args look the same as his. Report back here with your results and we will go from there.

I'm always happy to take feature requests so don't be shy! ? I appreciate the sentiments however.

June 21, 2019

10 hours ago, JunkRunner said:

After a lot of digging, and moving to another machine I found a few things.

It would appear that you check that the path contaings "*LaunchBox\Plugins\SteamLauncher\*" I had mine as "eXoDOS\…." this caused it to produce a warning message.

I've noticed that I get slightly different results when using LaunchBox vs BigBox. Also if I turn global steam launch off and use the context menu, it will actually launch, but not via the proxy. Another gotcha appears to stem from the fact that you're renaming the original exe and replacing it with the proxy. There's quite a lot of brittleness in this process, but without having tried my hand at it myself I cannot comment on a better alternative (or if one even exists). I now realise that the proxy will never work for exodos as it's a bunch of batch files, since you're renaming it wont execute, it also appears that steam doesn't support batch files only exe's.

I've tried the DOSBox that ships with LB and that only works without the proxy. Steam thinks I'm playing LB not doom.

It also seems that once the proxy fails, that's it... you have to restart the whole lot before anything will work again. Something seems to be holding onto some corrupted object that keeps getting reused.

I've cracked your binaries open to have a look inside, haven't had much time to spend on it yet. But so far it seems like a lot of what I've deducted is correct.

I'm still not sure why it doesn't work for me, but it works for others. I'm guessing that it has to do with the fact that I'm trying to run batch files which screws the pipeline up and then nothing else will work.

@cammelspit what kind of witchery do you employ to make eXoDOS work?

I'm not trying to argumentative here or anything but most of your assumptions are wrong. The only time any exe file is being renamed is in the case of LB's internal DosBox implementation. For everything else, the only type of "renaming" that is being done is with LB's internal references. For this whole process to work, the LB's game/emulator path is swapped for a few ms and then swapped back. Furthermore, if you use "Bat to Exe Converter", batch files will work perfectly fine as long as either the batch file stays running for the duration of the game/emulator process or alternatively if you use a "LauncherToExe" entry in the config file. I'm not sure what to tell you about the DOSBox that ships with LB... There are a whole lot of people who are using the feature on a daily basis with no problems. On the proxy failing... again, that is something to do with your machine. On a normal setup, the proxy exe will only run for the duration of the game/emulator and if there is a background proxy process running when another wants to start, it will be forcibly closed (it will also be forcibly closed upon LB startup/shutdown. I'm sounding like a broken record at this point, and you can clearly take my advice for what it is, but there is very obviously something strange going on with your setup. As far as the location of the plugin, the plugin instructions very clearly state where the plugin needs to be installed. Furthermore, if you want to test whether the plugin is working for you at all, probably starting with the most complex use-case is not a great starting point... Finally, concerning the "brittleness" of the plugin... Please come back after you've spent several hundred hours trying to develop such a solution for software such as LB that doesn't offer a plugin API with any of the necessary features, a undocumented Steam API with no up-to-date 3rd party implementations, with Steam updates that modify the needed vtable offsets every update, and after offering a free plugin with free personalized support to scores if not hundreds of users. Every step necessary to make this plugin work is necessarily an undocumented workaround to try to bypass intended or unintended limitations by multiple software products from different vendors. I test every update on 5-6 different VMs with different Windows versions and different configurations before releasing publicly. l can't guess what specific issues or oddities are going on with your machine that are causing issues. What I can assure you is that if you install a fresh copy of Windows 10 (any version) onto a VM and install both Steam and LB along with my plugin (by following the simple instructions provided), it will work exactly as intended. At this point, with you having named about 14 different issues you've run into, yet not even having tried just a simple, basic game launch, its a little hard to provide any advice on how to move forward. I would be happy to login to your machine remotely using TeamViewer if you'd like me to take a look... I understand people's hesitance to have some login to their machine remotely, so if that doesn't suite you, then boot up a VM and I can log into that (although if its a fresh VM, I suspect you're not going to see any of these problems). You'll have to excuse me for being a little bit frustrated... It just makes me a little angry when you assume that every issue you are having is somehow related to my plugin "not working" when in fact there are many people using it on a daily basis with no issues whatsoever. If you think you can do a better job, then please, by all means, jump in. I think you'll quickly figure out trying to do what the plugin does is a damn quagmire.

Edit: So I gotta apologize for being a bit of an ass earlier when I posted this... I shouldn't have so publicly vented my frustration. I would be happy to help you get the plugin working on your machine but to do so, we are going to have to start simple first. A fresh LB installation with the plugin installed according the instructions given on the plugin download page. From there, we will ensure that we can turn on debug logging and that that is working. From there, I can show you how to use the Bat to Exe converter to get eXoDOS (or whatever other "bat" launchers) working. My Steam info is posted on the plugin download page. Just shoot me a msg and I will gladly walk you through the process. Trying to do it through forum messages just isn't going to work.

June 20, 2019

It sounds like multiple copies of the plugin are loaded.. A 2nd LaunchBox process running would explain that perfectly... Although I can't say I've ever seen 2 instances of LaunchBox running simultaneously... Clearly you have something strange going on. Btw, to use the plugin you need to have Steam running when you open LB. If you close or restart Steam while LB is running, you must restart LB. There is a lot of very complex logic going on under the hood... LB does not facilitate what my plugin does in any way.. I'm fighting against LB at every step to do what the plugin needs to do to accomplish its purpose.

June 20, 2019

11 minutes ago, JunkRunner said:

If you could push the code to github I’ll attach visual studio to the process to track it down.

I see the exception is the LaunchBox logs.

I’m also seeing permissions issues with the DosBox-sl-delete.exe proxy copy.

One machine is on the latest win 10 updates, the other is lagging behind a bit.

Both latest version of steam. I’ve tried LaunchBox 9.6 and 9.9

On one machine I’m running the software on a micro sd. The other is on an external hdd.

It was working for non dos games at some point, but now works for neither...

is is there any hidden registers entries you add?

also the debug logs for the proxy is not being created.

Again... All of these problems seem to indicate some other problem... No, there are no registry entries used with the plugin. If you've changed the config.xml entry to (config.xml must be edited while LB is closed):

and you're still not seeing a debug.log file being created after you restart LB then it could be a number of things. The first and most obvious thing to check (which people do constantly despite being absolutely sure they haven't) is to ensure that there are not 2 copies of the plugin ANYWHERE within the LaunchBox directory structure (in the LaunchBox root directory or any of its subdirectories). If you have 2 copies of SteamLauncher.dll anywhere within the LaunchBox directory structure simultaneously, very weird things are going to happen (such as config.xml changes seemingly not "taking hold", debug logs not being output, etc and so on). You will also see multiple weird exceptions that are actually unrelated to the root problem. This would be my first guess as to what the problem is... If you are absolutely positive that this isn't the case, let me know, and we can continue troubleshooting.

Note: Like I said before, I will do my best to get the source code pushed out to GitHub asap. I've got a million things going on this afternoon, but perhaps later tonight or this weekend... but no promises.

June 20, 2019

If you can't figure out why you're getting that exception despite continued troubleshooting, I might be able to explicitly generate that assembly for you to put into your SteamLauncher directory... It would only be a band-aid for a more serious problem that you have on your machine(s). Assemblies that use an XmlSerializer automatically generate the assembly on the fly using JIT, and I don't have any clue what could prevent your machine from doing that successfully outside of some really strange anti-virus setup or something. I haven't looked into it, but I suspect there is someway to forcibly generate that assembly for testing purposes... and that may temporarily patch the error you're seeing (but again, this is indicative of some larger issue on your machine in relation to .NET assemblies). Let me know if you figure anything out and if need be, I can look into this...

June 20, 2019

14 minutes ago, JunkRunner said:

I’ve now got a slightly different issue which I need to solve first. When I try to launch via steam I get an exception saying that SteamLauncher.XmlSerializers dependency is not found.

Which is weird as it was working before. I’ve tried it on 2 machines with the same results.

Games that we’re launching properly before now just times out with that exception.

I can also only get the overlay working with DosBox Daum. I’m using doom as my test game...

i can get it to put black bands at the top and bottom of the screen for other DosBox builds, I suspect it’s the render pipeline that’s not compatible.

Getting the launcher proxy to work again would be a good start.

Being that I've never heard of anyone having this error before, including numerous people who've installed the latest plugin update, its kind of inexplicable that this would happen to you on 2 unrelated machines simultaneously... unless it is related to specific software that you have installed on both machines... What version of Windows are you running? If you're on Windows 10, what version/update are you running? How are you seeing this exception? Does it pop up in a msg box or are you simply seeing it in debug output in something like Dbgview.exe?

June 20, 2019

On 6/18/2019 at 8:32 PM, JunkRunner said:

I’ve tried it without the eXoDOS bat file by using launchbox’s Built in DosBox function, still no joy. I’ll upgrade Launchbox to the latest version (9.6 at the moment) and try again. But something is off... I’m assuming that when I hit the guide button I should get the steam overlay?

The problem could be a few things... First and foremost, you must ensure that the game you're playing uses a graphics API that the Steam overlay supports. Currently, the Steam overlay supports DirectX 7 - 12, OpenGL, Metal, and Vulkan. It does not support software rasterization. Your best bet is to set the DosBox renderer to OpenGL. You can do this by opening the game's .conf file and setting the 'output' variable to 'opengl'. It should look like this:

output=opengl

Alternatively, you can just set this variable in the dosbox.conf so that it is applied to all games (you can find LB's built-in DosBox conf file at "LaunchBox\DOSBox\dosbox.conf".

If you see a black screen when starting a game, press 'ALT+ENTER' and the game should show up. I just tried playing DOOM using LB's built-in DOSBox and it worked perfectly, Steam overlay and all (note: I changed the output variable in the dosbox.conf file). You can bring up the Steam overlay using your keyboard by pressing "SHIFT+TAB". Try using the built-in DosBox using these instructions and see if you can get it to work. Once we get that working, I can help you to get eXoDOS working.

June 18, 2019

3 minutes ago, JunkRunner said:

Just wondering if this works for DosBox. I’m using eXoDOS and that launches DosBox via a batch file. Any hints on how this plugin works internally (is the latest code on github or something)? So I can figure this out...

The plugin has support for LB's internal DosBox implementation (took a lot of time to add actually). Unfortunately, I have not yet uploaded the latest version of the plugin to GitHub.. I definitely need to do this, and I will try to do it as soon as possible. I'm not familiar with exactly how eXoDOS works, but if it is a launcher exe that then runs a bat file to launch the DosBox game, then you should be able to make it function with the plugin. First, I would just try it and see if it it works, if it doesn't, post back here, and I will give you a couple of easy things to try which should make it work (there are some specific settings you can use in the plugin's config.xml to make the plugin work with "launcher" exes).

June 18, 2019

16 minutes ago, JedExodus said:

Lahma thank you v much for the new version, it works a dream. I may have been one of the ones who downloaded the version that you pulled, (i'm in Ireland so the times line up) but it seems to work a treat regardless. Only home from work now so will change over to the new one.

If you want a tester for the pause screens (which I love btw for the save states) i'll be more than happy to muck in. Sent you a friend request on Steam so drop us a line. Thank you again, you utter legend!

Thanks for the kind words! I got you on my friends list and whenever I'm ready to start testing the pause screens, I will definitely hit you up.

June 18, 2019

Looks like the new update is working well (regardless of whether you're using the latest version of LaunchBox or not) for everyone I've talked to so far. Please let me know if you are having any issues.

June 18, 2019

1 hour ago, Mantis said:
For some reason the new version doesn't work at all. I was using an older version that worked fine yesterday. When it stopped loading RetroArch today I figured I'd look for a new SteamLauncher, and indeed, there are major changes. The problem with the old plugin occurred right after a LaunchBox update I was prompted to download/install today.

I followed all of the instructions. LaunchBox isn't installed on the system drive and I didn't have the DLL blocking problem. Unfortunately the new SteamLauncher does not work either. I wondered if somehow RetroArch had broken. After turning off that Steam toggle, games load fine. I tried loading with Steam both with the toggle on and off. No dice. I haven't tried deleting (or moving or renaming) the config yet as it doesn't appear to be problematic but I will paste it here in case that helps.
<?xml version="1.0"?>
<SteamLauncherConfig>
  <DebugLogEnabled>false</DebugLogEnabled>
  <PreventSteamFocusStealing>true</PreventSteamFocusStealing>
  <UniversalSteamLaunching>true</UniversalSteamLaunching>
  <ProcessStartTimeoutSec>10</ProcessStartTimeoutSec>
  <ProcessWatcherPollingIntervalSec>2</ProcessWatcherPollingIntervalSec>
  <TotalSecondsToPreventSteamFocus>6</TotalSecondsToPreventSteamFocus>
  <DosBoxScummVmProxySleepMs>400</DosBoxScummVmProxySleepMs>
  <CustomPlatformNames>
    <Platform Name="Super Nintendo Entertainment System" Custom="SNES" />
    <Platform Name="Nintendo 64" Custom="N64" />
    <Platform Name="Nintendo GameCube" Custom="GC" />
    <Platform Name="Nintendo Game Boy" Custom="GB" />
    <Platform Name="Nintendo Game Boy Color" Custom="GBC" />
    <Platform Name="Sony PSP" Custom="PSP" />
    <Platform Name="Sega Genesis" Custom="MD" />
    <Platform Name="Sega Dreamcast" Custom="DC" />
    <Platform Name="Sony Playstation" Custom="PS1" />
  </CustomPlatformNames>
  <LauncherToExeDefinitions />
  <RepairPaths />
  <DosBoxExeNeedsRepair>false</DosBoxExeNeedsRepair>
  <ScummVmExeNeedsRepair>false</ScummVmExeNeedsRepair>
</SteamLauncherConfig>
I tried adding you on Steam as that was your first support suggestion but hadn't heard back.

Hey @Mantis, I saw and accepted your friend request on Steam and we chatted for a min, but apparently your battery was about to die. Msg me again whenever you get back on and we will get your problem figured out asap. Hopefully there isn't some problem with the latest LaunchBox version as I actually haven't updated to the latest version myself. I'm actually going to do that right now just to be sure. I don't imagine that has anything to do with your problems since a LaunchBox update has never broken compatibility with the plugin before, but I guess its not outside the realm of possibility. I will talk to you in just a bit.

June 18, 2019

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!

June 18, 2019

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.

June 18, 2019

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.

June 18, 2019

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.

June 16, 2019

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!

June 7, 2019

3 hours ago, Ariakan said:

Hi!

I just wanted to say that, since I created this topic, Beetle PSX HW and PSX-Rearmed cores support CHD format using chdman.exe from MAME.
So now we can have one .cue + one or multiple .bin combined inside only one .chd file, with a better compression size than .pbp !

I haven't try your solution, but thank you posting it!

Very interesting! I've never even heard of the .chd file format, but then again, I don't mess with MAME emulation very much... It sounds like its simply a compressed hard drive image ("Compressed Hunks of Data"). Unless .chd offers some big advantage in terms of compression or something (I can't imagine there is any real significant difference) , I think I personally prefer to stick with .pbp since it is supported by most PS1 and PSP emulators, as well as modded PSP devices. Thanks for the useful information though... I'm sure it will prove to be useful to others.

May 22, 2019

The Steam Beta did indeed break compatibility with the plugin because of changes to some vtable offsets in the steam client DLL. I will try to upload an update shortly that fixes this issue.

May 18, 2019

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.

May 15, 2019

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.

May 13, 2019

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!

May 13, 2019

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.

May 12, 2019

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.

May 10, 2019

For anyone who is interested, there is a VERY easy to use Python script on GitHub called 'binmerge' that was created by 'putnam'. I tried it with a couple of PS1 games that have multiple bin files, and it worked perfectly. Additionally, it only took seconds to create the new bin file (probably because it is not actually modifying any of the data but rather just merging the files and creating a new cue sheet). The description specifically mentions its use in merging PSX bin files.

https://github.com/putnam/binmerge

Just click on the 'binmerge' file, click raw, and then right click and 'Save As'. Make sure to click the 'Save as type' dropdown in the save dialog and change it from 'Text Document (*.txt)' to 'All Files (*.*)' and then change the filename to 'binmerge.py'. You need to use Python 3 (probably 3.4+, although I used 3.7 32-bit). To use it is really simple.

python binmerge.py "PATH\TO\ORIGINAL\CUE\FILE.cue" "NewBinCueFileNameWithoutExtension" -o "PATH\TO\OUTPUT\NEW\MERGED\BIN\AND\CUE\FILE"

The '-o' option is not required, but obviously if you want to keep the name the same as the original file, you're going to need to provide a different output directory so that it doesn't try to overwrite one of your existing files. Just to make it extra clear, I will provide an example below using 'Castlevania - Symphony of the Night (USA)'.

Original CUE File Location:
"C:\roms\ps1\Castlevania - Symphony of the Night (USA)\Castlevania - Symphony of the Night (USA).cue"

New BIN/CUE Name (without extension):
"Castlevania - Symphony of the Night (USA)"

Output Directory ('-o' option):
"C:\roms\ps1\Castlevania - Symphony of the Night (USA)\merged"

python binmerge.py "C:\roms\ps1\Castlevania - Symphony of the Night (USA)\Castlevania - Symphony of the Night (USA).cue" "Castlevania - Symphony of the Night (USA)" -o "C:\roms\ps1\Castlevania - Symphony of the Night (USA)\merged"

Before:

FILE "Castlevania - Symphony of the Night (USA) (Track 1).bin" BINARY
  TRACK 01 MODE2/2352
    INDEX 01 00:00:00
FILE "Castlevania - Symphony of the Night (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00

After:

FILE "Castlevania - Symphony of the Night (USA).bin" BINARY
  TRACK 01 MODE2/2352
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    INDEX 00 50:53:45
    INDEX 01 50:55:45

I didn't really intend to do an enormous writeup on this, but as usual, it looks like I went a bit overboard... Hopefully it will be useful for someone! Oh, and in case someone wants to use this but doesn't want to mess with installing Python and getting all of that setup correctly, I converted the Python script into an EXE (using 'pyinstaller') to make it really easy to use. In the example above, just replace 'python binmerge.py' with 'binmerge.exe'.

Zip file containing 'binmerge.exe':
binmerge.zip

Profiles

Forums

Articles

Downloads

Gallery

Blogs

Posts posted by Lahma