Update 14/07/2025 at 17:50 UTC - the developer of lsfg-vk, "Pancake", issued a new statement about the situation. This was posted into the Lossless Scaling Discord:
Update on Deck Wizard's video and the Decky plugin
Hello everyone! I'd like to clear up some things after the previous announcement, which caused way too much unnecessary drama.
Behind the scenes, I've been talking to both Deck Wizard and Kurt (xXJSONDeruloXx on GitHub), who is the creator of the Decky plugin. The situation we got into was caused purely by poor communication, so we sat down and discussed the future of the plugin together.
Let's get into the news then.
The Decky plugin will remain unofficial and unsupported in this discord, not as a means to discourage using it, but rather to keep the growing load of support away from me, as I have barely anything to do with the plugin. Together with Kurt and Deck Wizard we've fixed the major labeling issues in the plugin, as well as created an update video on Deck Wizard's channel that you can watch here:
https://www.youtube.com/watch?v=rhkCev9M6lM
Future support with the Decky plugin will happen in the Discord server linked in the video description and depending on which category your issue falls into, you may be forwarded to this discord instead.In the future, some pretty big changes will be coming to lsfg-vk which will likely require a portion of the plugin to adapt. I will be working with Kurt to get the changes into the plugin as quickly as possible, however this warrants a whole other announcement and I can't promise any timeframe (it could be hours, days or weeks).
Original article below:
There's some drama in Steam Deck land with a Decky Loader plugin, that works with Lossless Scaling Frame Generation from the new lsfg-vk project for Linux.
The lsfg-vk project itself was first covered here on GamingOnLinux on July 7th, and the developer has recently managed to upgrade it with the help of the original Lossless Scaling developer. It's still a work in progress and a little rough but it does work.
Since there was a lot of excitement around it, a different developer decided to make a Decky Loader (see my Decky Loader guide) plugin (GitHub) to make it easier to work with it on SteamOS / Steam Deck. It was then showcased by the YouTube channel Deck Wizard but now onto the drama…
The creator of lsfg-vk, "Pancake", posted this to the Lossless Scaling Discord server:
Important information regarding the Decky plugin and Deck Wizard's video
A couple of hours ago Deck Wizard has made a video on Lossless Scaling in which they present a new Decky plugin for lsfg-vk.
On Reddit, the creator of that plugin claimed they had collaborated with me to create this, however this is incorrect and was likely the result of a language barrier.I was asked to collaborate, but I instead requested them to wait with the plugin until the new configuration system was written, as otherwise a large portion of the plugin would have to be rewritten to account for it. They did not listen and pushed the plugin out without communicating with me beforehand.
As a result of this, the plugin already has many issues such as incorrect labeling of options and misleading descriptions of other options. Likely in collateral, the video created by Deck Wizard further spreads these wrong explanations. I want to clear up these things.
First of all, the settings recommended by Deck Wizard are 30% flow scale and no performance mode. I can not state enough how terrible these options are. With 30% flow scale, internal calculations are happening in 96x54 images with some going down to 2x1, producing extremely inaccurate results.
Instead, it is recommended to keep flow scale at 85-100% with performance mode enabled, as this gives a much larger performance boost while retaining immensely higher quality.Clearly all of this is simply a result of poor communication and as such I will not support the Decky plugin. Do not ask about help with lsfg-vk when using the Decky plugin. Perhaps in the future an official lsfg-vk Decky plugin can be made in actual collaboration with me.
This all seems a bit dramatic. But I don't blame the developer of the original Linux tool wanting things to be correct and ready for it to not be disappointing for users, and not to overwhelm them.
Hopefully this situation will have a happy ending.
Gonna give it a wide berth for a year or two I think!
So I installed 'lsfg-vk', blind - (stupid I know) and ended up in a situation where I could not unpick it from my cachyOS machine.
I have no idea how you did this unless you manually compiled it and installed the files into the system, in which case you should be able to manually delete all the files.
As for the drama, it's just a disclaimer right? I would put out something like that. Just to avoid confusion. Otherwise the dev will get support requests for software he is not responsible for.
I have no idea how you did this unless you manually compiled it and installed the files into the system, in which case you should be able to manually delete all the files.
You would think, but how does someone manually compile and install "blind"? That would take at least some thought to pull off and most likely some reading of the instructions. I'm very curious.
I was asked to collaborate, but I instead requested them to wait with the plugin until the new configuration system was written, as otherwise a large portion of the plugin would have to be rewritten to account for it. They did not listen and pushed the plugin out without communicating with me beforehand.What the lsfg-vk dev said was pretty reasonable.
Some people are just way to desperate to have lsfg working on Linux already.
We didn't even have any perpective of having access to that software before and now we have.
Just calm down and wait for it to be actually ready.