Jump to content
LaunchBox Community Forums

Razor112

Members
  • Posts

    11
  • Joined

Posts posted by Razor112

  1. On 10/26/2022 at 9:32 AM, Lahma said:

    Just wanted to let @Razor112 and @coasternd know that I have not forgotten about their issues with BigBox. I'm sorry that I have not yet gotten around to investigating fixes for the issues noted. Just been really busy with work stuff (and if I'm being honest, I've also been wasting some of my time playing with my new 3D printer 😏). I am going to try to look into the BigBox issues in the next few days though and I will report back here with my findings.

    Sorry for the late reply Lahma. For me, The fix for the big box bug is not that important because of  the selective use feature. If i need a game or a platform to not start through steam i just blacklist those and i don't even have to turn off steamlauncher I tried new steam client beta update with new steam deck ui. Steamlauncher doesn't work but steam deck ui is just beautiful compared to old big picture mode. Even though i don't own a steam deck i actually dedicated one of my laptops to holoiso (unofficial steam os 3 that can be installed to any pc). New deck ui feels natural and responsive also the laptop i'm using holoiso is underpowered but i just drop the resolution to 800x600 and with system wide fsr clears the picture good enough. I think valve really nailed the new steam deck tbh. I agree with you on new controller bindings config screen but i think postives outweights the negative imho.

  2. On 8/24/2022 at 9:20 PM, Lahma said:

    @Razor112, thanks for letting me know the vtables db update worked for you. I appreciate the sentiment but regardless, I'll definitely look into the issue with BigBox. It either needs to be fixed or the option removed. I don't want to leave it in a broken state. If I remember correctly, that feature (including the enable/disable menu item in BigBox) was implemented in a fairly bizarre round-about way due to limitations with the plugin system. I think it uses a dynamic type variable that accesses an unexposed BigBox UI element via reflection. I suspect that the recent BigBox overhaul (I think they redesigned a large part of it, didn't they?) changed something related to the class/method/type name I was accessing via reflection which probably caused the hack-ish workaround to stop working. Hopefully it shouldn't be too big of a deal to fix.

    Honestly, I would really like to implement a SteamLauncher settings UI in BigBox, but I imagine it would take an enormous amount of effort since it would have to be compatible with game controllers and couldn't be reliant on mouse and keyboard. If anyone knows of a BigBox plugin that has UI that can be controlled solely with a game controller and could point me to it, I would really appreciate it. It would be interesting to at least take a look at which libraries they are using and peek at how they implemented controller support. Most likely I won't be implementing such a feature any time soon but I'm not entirely ruling out the possibility.

    I only use your plugin so I can't give you any directions. Maybe one of the moderators can help you to find a plugin that is controlled with a controller in bigbox. You should message them and ask them about it. However, if you can't find a donor plugin to implement I think you should remove steamlauncher menu items from bigbox until you got enough time to implement such feature youself.

  3. 2 hours ago, Lahma said:

    @Corgana and @Razor112, I will look into the issue of not being able to enable/disable SteamLauncher from within BigBox. I literally never use BigBox (except on the rare occasion that I'm implementing some changes for the plugin) so I appreciate y'all letting me know about any issues you come across (because I would never know about them otherwise). Since this isn't a critical issue that entirely breaks the plugin or anything, I'm not going to sacrifice work hours (or other important duties) in order to fix it. Accordingly, it will probably take me at least a few days to look into the issue and push out a fix. I will post here once I've gotten a chance to look into it.

    The vTables update working fine. Thanks for the update.

    And for the bugfix, don't worry about it man. It's not that important as you can always switch to launchbox and can disable it from there. Besides with the addition of selective use feature you don't even have to disable SteamLauncher anymore if you want a game or a platform to not start through Steamlauncher you can always blacklist it.😁

    • Like 1
  4. 15 minutes ago, Corgana said:

    Not sure if this is just me, but attempting to disable the latest version of Steamlauncher in Big Box crashes the program (seems to work fine in regular Launchbox).

    Nope it's not only you. I also have same behavior too.

    @Lahma Here is the error log

    Spoiler

    'Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel' does not contain a definition for 'SystemViewModel'

    App:     Big Box
    Version: 12.14
    Type:    Microsoft.CSharp.RuntimeBinder.RuntimeBinderException
    Site:    System.Object CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, System.Object)
    Source:  Anonymously Hosted DynamicMethods Assembly

       at CallSite.Target(Closure , CallSite , Object )
       at SteamLauncher.UseSteamLauncherSystemMenuItem.OnSelected()
       at Unbroken.LaunchBox.Windows.BigBox.MenuActions.MethodMenuAction.OnEnter()
       at Unbroken.LaunchBox.Windows.BigBox.ViewModels.SystemViewModel.OnEnter()
       at Unbroken.LaunchBox.Windows.BigBox.NavigationManager.OnEnter()
       at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.OnEnter()
       at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.HandleKeyDown(KeyEventArgs e)
       at Unbroken.LaunchBox.Windows.BigBox.Views.MainView.ResetStub(Object init, KeyEventArgs connection)
       at System.Windows.Input.KeyEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
       at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
       at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
       at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
       at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
       at System.Windows.Interop.HwndKeyboardInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawKeyboardActions actions, Int32 scanCode, Boolean isExtendedKey, Boolean isSystemKey, Int32 virtualKey)
       at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(MSG& msg, Boolean& handled)
       at System.Windows.Interop.HwndKeyboardInputProvider.FilterMessage(IntPtr hwnd, WindowMessage message, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

    Recent Log:

       21:44:24 Exception

     

  5. 56 minutes ago, DragoonDemon4 said:

    Hi, I'm trying to use the plugin, downloaded all prerequisites, but when launching a game it doesn't start when I check the log it says this

    2022-08-19 10:40:14 [Error] [SteamShortcutManager] [CreateSteamLauncherShortcut] - An unexpected problem occurred while trying to create a SteamLauncher shortcut.
    2022-08-19 10:40:14 [Error] [GameLaunchingPlugin] [OnAfterGameLaunched] - An error occurred while creating/launching the Steam shortcut: An unexpected problem occurred while trying to create a SteamLauncher shortcut.

    Help me in this, please, I want to launch my games through this plugin and I cant

    New steam client update broke the plugin. It needs updating wait for @Lahma to fix it.

    • Like 1
  6. 5 hours ago, Lahma said:

    Everything looks perfectly fine in your debug.log file and I haven't gotten any other reports of such behavior which makes me believe it has got to be something particular to your setup. How are you starting the temp shortcut from Steam directly? Please post a screenshot of the temp shortcut you are manually starting in Steam.

    Well, Temporary shortcut stays in steam games list for that session until you completely close the steam client from system tray. That's how I managed to set controller configurations for the time being. Weird thing is steam recognizes that it's in that temp shortcut and also games recognizes their respective custom controller configurations. It's just the steam in-game overlay is unaware that you are actually in a game when game starts through steamlauncher so it doesn't switch to big picture in-game overlay. Well, I made a video showcasing the behavior.

    150543375_2022-08-0507-19-56.mkv

  7. @Lahma    I have a problem with the new release. When I launch a game from launchbox with steamlauncher I don't get the steam big picture in-game overlay. However if I start the temp shortcut from steam client directly big picture in-game overlay works properly. Steam input works but overlay considers it as desktop so I can't access controller configuration per game. It just shows the desktop configuration. "Use the big picture overlay when using a steam input enabled controller from desktop" setting enabled in steam client settings. I didn't have any problems in the old version and I didn't changed any of the settings both in steamlauncher and steam client.

    The steamlauncher log is set to verbose log level.  Also GameOverlayRenderer and GameOverlayUI log files for both steamlaucher and steam client is in the attachments. Steamlauncher ones have steamlauncher extension.

     

     

    debug.log GameOverlayRenderer.log GameOverlayRenderer.log.steamlauncher GameOverlayUI.exe.log.steamlauncher

  8. 1 hour ago, CookiePLMonster said:

    FWIW I am encountering the same, on Windows 10, but it only started happening after I wiped SteamLauncher's config.xml. Before that it crashed for me upon opening SL's settings, but not on startup.

     

    EDIT:

    Confirmed - I sourced a premade config.xml and LB now boots. However, it crashes on opening SteamLauncher settings and the callstack hints at the same issue, but with a vtables.xml file:

    image.thumb.png.fca20dcd103ae11f1d6328e4ae5df804.png

    debug.log gets created properly (although empty), so it definitely is not an issue of LaunchBox's directory ACLs.

    I also deleted the old SteamLauncher. I downgrade to old broken version to recreate the config.xml and vtables.xml and upgrade to the newest version without deleting those files everything works normally in the newest version. I talked with lahma on steam and he said he will release a patched version couple of hours later.

    • Thanks 1
  9. The new version of plugin crashes the launchbox on startup. It hangs on loading plugins... then crashes. I use windows 11 Pro.

    Here is the crash log from event viewer

    Spoiler

    Faulting application name: LaunchBox.exe, version: 12.11.0.0, time stamp: 0x6215dcc3
    Faulting module name: coreclr.dll, version: 4.700.21.56803, time stamp: 0x6196f4f7
    Exception code: 0xc00000fd
    Fault offset: 0x0000000000049bd8
    Faulting process id: 0x3294
    Faulting application start time: 0x01d86f46a673085a
    Faulting application path: J:\LaunchBox\Core\LaunchBox.exe
    Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.22\coreclr.dll
    Report Id: aeac69f1-dc5e-40de-a90e-af467d67921c
    Faulting package full name: 
    Faulting package-relative application ID: 

    I also installed fresh windows 11 in a vm and behavior is the same.

    Here is the event viewer log from fresh windows 11 vm. There have pretty much the same error.

    Spoiler

    Faulting application name: LaunchBox.exe, version: 12.11.0.0, time stamp: 0x6215dcc3
    Faulting module name: coreclr.dll, version: 4.700.20.26901, time stamp: 0x5ec48a29
    Exception code: 0xc00000fd
    Fault offset: 0x0000000000049c18
    Faulting process id: 0x1348
    Faulting application start time: 0x01d86fa2bd667ccc
    Faulting application path: C:\Users\Test-VM\LaunchBox\Core\LaunchBox.exe
    Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\coreclr.dll
    Report Id: 8e563f9c-92b9-4c5e-926b-04f097575e63
    Faulting package full name: 
    Faulting package-relative application ID: 

    I also checked the SteamLauncher plugin location but there was no log file so plugin itself didn't produce any.

    I did some research about exception code: 0xc00000fd and it is a StackOverFlowException. So there must be some recursion in the plugin somewhere.

×
×
  • Create New...