Razor112
-
Posts
11 -
Joined
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Razor112
-
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.
-
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.
-
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.😁
-
Nope it's not only you. I also have same behavior too. @Lahma Here is the error log
-
New steam client update broke the plugin. It needs updating wait for @Lahma to fix it.
-
The update fixed the issue for me.
-
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
-
@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
-
Yes, Yesterday steam client received a update. Vtables need to be updated. @Lahma needs to update those.
-
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.
-
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 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. 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.
