[Resolved] The Luxtorpeda engine select screen appears when starting the Steam client in desktop mode

[ThreeSon]

Not sure if the root cause of this bug is Steam or something else, but it didn't start happening until immediately after I updated to the current Steam Deck beta. So that's why I'm posting here.

I have Luxtorpeda installed via ProtonUp-Qt, which itself was installed from the built-in Discover store in desktop mode. As of the most recent Steam Deck beta update (one of the two that were issued on October 2nd), the Luxtorpeda engine selection screen (which normally should only appear when launching a game for which Luxtorpeda is the designated Steam Play compatibility tool) now appears whenever the Steam client is launched in desktop mode, as if Luxtorpeda has been assigned as the compatibility tool for the Steam client itself.

This occurs regardless of which version of Luxtorpeda is installed (tested with the months-old 70.1.1 and the just-released 70.2.2).

Here's a screenshot of what it looks like when the Steam client is started if Luxtorpeda is currently installed: https://steamcommunity.com/sharedfiles/filedetails/?id=3342108816

There are actually multiple Luxtorpeda windows spawned with each Steam client launch - 2 or 3 usually - that need to be dismissed.


EDIT: This bug appears to have been fixed by a new Luxtorpeda update.

[Broseph Joseph]

lol confirmed, i was about the start troubleshooting this but i guess ill just wait for them to fix it. FWIW the file that is somehow invoking multiple instances of luxtorpeda is "d3ddriverquery64.exe" within steams program folder.

I might steal your post later and open a github issue with it.

[ThreeSon]

Originally posted by Broseph Joseph:

lol confirmed, i was about the start troubleshooting this but i guess ill just wait for them to fix it. FWIW the file that is somehow invoking multiple instances of luxtorpeda is "d3ddriverquery64.exe" within steams program folder.

I might steal your post later and open a github issue with it.

If you think it would help then please do.

[Shockwave S08]

Can confirm that it's happened to me too.

[d10sfan]

I'm the dev of luxtorpeda-dev, not sure how this can happen, but I'll look into it when i can

[d10sfan]

Keep an eye out for luxtorpeda version 71, that should fix the issue.

Steam for some reason is running that exe, probably for something proton related.

The SteamAppId isn't defined in that case, so I just ignore it and exit before launching the UI or anything.

So that should fix it.

[Broseph Joseph]

Originally posted by d10sfan:

Keep an eye out for luxtorpeda version 71, that should fix the issue.

Steam for some reason is running that exe, probably for something proton related.

The SteamAppId isn't defined in that case, so I just ignore it and exit before launching the UI or anything.

So that should fix it.

Thanks pal.

[ThreeSon]

Originally posted by d10sfan:

Keep an eye out for luxtorpeda version 71, that should fix the issue.

Steam for some reason is running that exe, probably for something proton related.

The SteamAppId isn't defined in that case, so I just ignore it and exit before launching the UI or anything.

So that should fix it.

It does seem to be fixed now after downloading v71. Thanks very much.

Could this affect how Luxtorpeda works with games on Steam Deck, as far as you know (any negative side effects)? I'm currently unable to test v71 because of another bug in the most recent Deck beta that is preventing me from enabling Steam Play compatibility.

[d10sfan]

It shouldn't cause any issues with playing games in lux. I did a quick test and everything was fine. Let me know if you run into any issues though

[ThreeSon]

Originally posted by d10sfan:

It shouldn't cause any issues with playing games in lux. I did a quick test and everything was fine. Let me know if you run into any issues though

Thanks again.

[Broseph Joseph]

Fixed.

[UnnamedTheRevenge]

I'm getting this issue now on the latest SteamOS in Desktop mode SteamOS 3.6.20 / KDE Plasma 5.27.10

[d10sfan]

Originally posted by UnnamedTheRevenge:

I'm getting this issue now on the latest SteamOS in Desktop mode SteamOS 3.6.20 / KDE Plasma 5.27.10

Did you update to the latest luxtorpeda-dev?

[MandoSlayer]

Yeah I’m still getting this issue

[d10sfan]

Originally posted by MandoSlayer:

Yeah I’m still getting this issue

Did you update to the latest luxtorpeda-dev?

[ThreeSon]

Originally posted by d10sfan:

Originally posted by MandoSlayer:

Yeah I’m still getting this issue

Did you update to the latest luxtorpeda-dev?

Specifically, the Luxtorpeda version to be on to avoid this bug is 71.0.0, or newer.