Jump to content
LaunchBox Community Forums

Aetavicus

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Posts posted by Aetavicus

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus

    On 3/6/2021 at 8:33 AM, Lahma said:

    I'm really sorry about not getting back to you yet man.. I've had a LOT going on the past few weeks. The pastebin URL did indeed expire. I do want to look into your issue further though. Unfortunately, it looks like there may be a bigger issue going on with the plugin at the moment. Literally discovered it right this minute. Looks like a recent Steam update might have broken something. I'm looking into it as I type this so let me figure that out first and then we'll come back to your issue.

    Hey, glad to hear you are back!

    I've created a new Pastebin link (permanent this time) in case you would like to look at the debug log again.

    The link is: https://pastebin.com/0AQmKz4q

    As for the main issue you've described, I have not encountered it as of yet as SteamLauncher is still working properly for me.

    My Steam Client version is as follows:

    • Built: 12 Feb 2021
    • Steam API: v020
    • Steam package versions: 1613176728

    @Carl Cross

    FYI, I have tested Yuzu on my end and my SteamLauncher works just fine (Steam overlay opens up in Yuzu).

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted

    On 2/22/2021 at 9:41 AM, Lahma said:

    Sorry I have not responded to you yet. I live in Texas and we've had record low temperatures and I've been without electricity for.. umm.. 4 days? 5 days? Kind of lost track... Anyways, it appears that the electricity is back on for good now. I will look at your log as soon as I can and get back to you.

    Hey, sorry to hear that. Don't feel like you have to rush to fix this as it is not a critical problem for me. Hope your situation gets better!

    Note: The Pastebin URL might have expired by now. Do let me know if you require any additional info from my end.

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus

    @Lahma

    I installed the latest update that you posted but I am still unable to get the plugin to work for GOG-imported games.

    Using the game Dead Cells as an example, it is imported via the GOG importer in LB.

    1. The application launch path is "Games\Windows\Dead Cells\Launch Dead Cells.lnk"
    2. The properties of "Launch Dead Cells.ink" are as follows:
      • Target: "E:\LaunchBox\Games\Windows\Dead Cells\deadcells.exe"
      • Start in: "E:\LaunchBox\Games\Windows\Dead Cells"

    When opening the game from Launchbox, the following happens:

    1. GOG Galaxy client launches
    2. Game launches

    The SteamLauncher plugin does not appear at all during this process (Usually I see the icon appear in the taskbar for other games.) Note that all these was done without changing any of the default SteamLauncher settings.

    Changing the application launch path in LB to "Games\Windows\Dead Cells\deadcells.exe" also results in the same outcomes as above which is pretty strange because if I directly clicked on "deadcells.exe" in Windows Explorer, it will immediately open up the game without GOG. So my guess is something in LB is getting GOG to be launched when the game is imported via GOG. No idea what as I do not see any other configuration parameters in the game details in LB besides the usual metadata.

    I could only get the plugin to work if I delete the existing application in LB and just directly re-import "deadcells.exe" through "Import a ROM" in LB.

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted

    The new update works fine for me.

    Now I am just wondering how to use the plugin with GOG games. Launching any game that was imported via GOG seems to bypass the SteamLauncher entirely (icon doesn't even show up) and I have had no luck with the launcher settings. I could only get the plugin  to work when I imported the game executable through "Import ROM files..." instead of "Import GOG Games...". Something about the latter option seems to be telling LaunchBox to just start the GOG Launcher immediately.

    Did anyone managed to get this plugin working for GOG?

     

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus

    On 1/22/2021 at 4:36 PM, Lahma said:

    Hey @Aetavicus, that is disappointing to hear as I definitely implemented full UTF-8 support a very long time ago. Unsurprisingly, the first culprit which made me realize non-ASCII characters were not working correctly was Pokémon. I can't say I've ever come across an umlaut (¨) in any of my own game titles and this is the first instance I've heard of any problems with it. With that being said, I don't doubt your report at all as there is an undisputed bug in Steam's unicode character handling which is the entire reason there was an issue with titles such as Pokémon in the 1st place. In order to work around that bug in Steam, I have to mangle the UTF-8 encoding in my plugin before sending it to any Steam API method. Since it has been so long since I've dealt with the issue, I can't remember the particulars of it but it is possible that there may be some limitations as to what character sets it is capable of implementing (for example, it may support all UTF-8 characters but it may not be able to display unicode characters that require a full 16 bit representation). I will definitely look at it though to see if it can be fixed.

    One thing you might look at in the meantime is if you can create a non-Steam shortcut within Steam itself using that character. If there is indeed no problem actually creating a non-Steam shortcut with that character in its name (or file path), its likely the problem is related in some way to the function I'm using to mangle the unicode bytes before sending them to a Steam API function. If you get a chance to try it, let me know what the results are. Otherwise, I'll look at it as soon as I can. Thank a lot for the report!

    @Lahma

    I tested this with Pokémon as you have mentioned and can confirm that it works in Steam natively.

    I created a non-Steam game with the following parameters:

    Title: Pokémon SoulSilver

    Target: "D:\Media\Games\LaunchBox\Emulators\DeSmuME\DeSmuME-VS2019-x64-Release.exe"  "D:\Media\Games\LaunchBox\Games\Nintendo DS\Pokémon SoulSilver Version [2009]\Pokémon SoulSilver.nds"

    Start In: "D:\Media\Games\LaunchBox\Emulators\DeSmuME\"

    After clicking Play in Steam, the emulator opened and subsequently launched the game. The game title correctly shows up in my currently playing status.

    Trying to launch the same title in Launchbox however will not work with the SteamLauncher plugin enabled. The icon for the SteamLauncherProxy shows up for a few seconds in the taskbar and then closes automatically.

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus

    Not sure whether this is reported but it seems that the plugin is unable to start the game if the game's title contains special alphabets.

    I was testing out Xenosaga Episode II today and it just couldn't launch the game.

    The full title of the game is Xenosaga Episode II: Jenseits von Gut und Böse and I believe the problem is with the very last word, Böse. Changing it to Bose caused the plugin to work again.

    Update: The plugin could launch the game but resulted in a black screen and PCSX2 gave me the plugin setup window again. Fixed by renaming the folder containing the ROM file to remove any special alphabets as per above.

     

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus

    49 minutes ago, The_Keeper86 said:

    For some reason the plugin will sometimes remove the emulator and instead add in its place "SteamLauncherProxy.exe" as the emulator. I had this problem in the past with PCSX2. Most likely the same issue here.

    I tried changing the Emulator App Path but it keeps resetting back to "..\Plugins\SteamLauncher\SteamLauncherProxy.exe" when the SteamLauncher setting is turned on.

    I'm guessing that this SteamLauncherProxy.exe is supposed to be used in some way but I have no idea how to indicate that rpcs3 is to be used as well. 

    Similarly, I tried this on PS1 and PS2 games as well with the same result. I feel like I'm missing an obvious step here.

    SteamLauncher

    in Third-Party Applications and Plugins (Released)

    Posted · Edited by Aetavicus
    More details

    I am trying to get this plugin working for a PS3 game but have not been successful so far.

    Here's what I did:

    1. Steam is running in the background and in-game overlay is enabled. (I don't use Big Picture mode)
    2. Downloaded the latest version from this forum (v0.9.3.0)
    3. Extracted the SteamLauncher into the plugin folder of LB
      • Currently placed at: C:\Emulation\LaunchBox\Plugins\SteamLauncher
    4. Launched LB and checked that the Steam Launcher setting under Tools is set to On
    5. Attempt to launch one of my PS3 games but an error message will appear saying "The file you specified for the emulator application path was not found".
      • This error only happens when the SteamLauncher setting is enabled.
      • When disabled, rpcs3 starts up and launches the game as per normal.
      • Took at look at the emulation app path and it is currently set to "..\Plugins\SteamLauncher\SteamLauncherProxy.exe" when SteamLauncher is enabled.
      • The sample command would be SteamLauncherProxy.exe "FULL\PATH\TO\ROM\FILE"

    Is there something I am missing in here?

×
×
  • Create New...