Feature Request/Enhancement surrounding the handling of shortcut.lnk files

[klepp0906]

I believe it would be beneficial in not only my particular use case, but in general - to have an option during importation to treat .lnk files as their endpoint/import path’s to the binary instead of path’s to the shortcut. to have a means to allow the steam controls api to see when launchbox launches a non steam windows game.

Ive recently found out this creates catastrophic issues with the passage of controls via steam and using steams integrated controller wrappers.

In short, if I launch bigbox through steam and then launch a game with bigbox which was imported using a shortcut… controls wont work.

At the pc, you can start the game via another means whether it be outside of steam (and losing steam control handling) or adding the game to steam itself and starting it there, which brings in redundancy and diminishes a huge perk of launchbox/bigbox itself.

Where this becomes an even bigger detriment is when using steam to play remotely via steam link or steam link app, which again - is a huge chunk of what bigbox is suited for. If i start bigbox remotely, then fire up a windows game - i have no controls. Useless if said game is added via .lnk. One could import every non steam game by adding the exe instead of the lnk but due to the varying depths and sometimes multitude of exes relative to each game, not ideal

I made a forum post here.

https://forums.launchbox-app.com/topic/53063-sort-of-a-feature-request-regarding-lnk-importing/

thanks for your time and work on the project

[klepp0906]

seems I was incorrect. Even adding the exe to BB wont allow it to receive controls if launched through steam which I cant quite understand as emulators do fine. Either way, renders this issue “moot” at least for now.

[klepp0906]

So I decided to re-open this/keep it open. At least until someone on the LB team can advise if its handle’able or whos side of the fence it falls on.

The issue seems to not be resolved even if the windows games are added as .exes instead.

BB through steam passes controls to all emulated games on all platforms. The only thing that will not pass is Windows games launched in such a fashion.,

Even though the .lnk vs exe issue is a thing, i dont think it applies here.

I think the now-issue is when BB launches an emulated game through steam, steam sees the emulator launched and thus gives it the emulators controls.

When BB launches a windows game through steam, its not seeing the executable to pass controls to. Or something. Again, why this is different with emulated stuff is waaay above my paygrade, hence my keeping this open.

[klepp0906]

closed. discovered the root of the issue which is likely not easily able to be circumvented.

the short of it is, steam sees it as a launcher. If i disable “use desktop config in launcher” voila, I have controls passed.

So unless a way exists for steam to see the game as the game, not a launcher when launched through BB. No bueno.

I tried with it imported as .lnk and exe to LB. Circumstance was identical.