According to the creator of lsfg-vk:
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. Pancake - Developer of lsfg-vk
The plugin is still the easiest way to use Lossless framegen ATM, but it’s definitely worth knowing about this.
Honestly, I’m just happy to see that everyone involved was able to see that it was just a communication issue and work things out together instead of it turning into a big finger-pointing drama fest.
Kudos to everyone involved for being understanding and collaborative, good people all around.
Looks like there was an update:
Update 7/14/25: Pancake has just posted a new update on the Decky Plugin controversy on the Lossless Scaling discord server:
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: 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).
Pancake - Creator of lsfg-vk
Thanks for sharing, that’s a great additional bit of info on this whole thing.
So does it mean I’ll never see that meme again while using the steamdeck?
Doesn’t seem like that much controversy. Just a plugin that got released early in development and will have to be rewritten at some point. I’d probably hold off until a full release but early showcases I’ve seen of it seem really promising and I’m excited to see the completed version.
Yeah, I’m guessing the guy wrote the plugin and got it working for himself, And then contacted the lsfg-vk dev about releasing it publicly.
The advice about waiting to make the plugin until configuration settings were finalized didn’t mean much right now because the plugin dev likely already had the plugin mostly finished.
The Steam Deck community is super weird about that.
They ferociously defended, for two years, a person who developed a GUI placebo. A Valve developer confirmed it did nothing. Tests showed it did nothing. But you’d be downvoted and even banned for pointing that out.
Then the same person popularized another placebo - again with AMD documentation proving it didn’t work - and once again people loved it.
Decky plugins follow the same logic. Random Reddit users bodging together some abomination of code to claim those sweet upvotes. One very popular plugin, “Is There Any Deal” causes such a massive constant CPU spike you lose 10 FPS on many games.
Its nuts. And Decky breaks itself every other update anyway, for months people blamed Valve for sleep issues that surprise surprise were actually Decky failing to wake up gracefully and taking the entire UI hostage with it.
I’m assuming you’re talking about Cryobyte increasing swap size, which was actually necessary for some games. God of War for example has a memory leak on devices with an integrated cpu/gpu (so handhelds and most laptops), and it would cause a full system lockup and crash after 30min-1hr of playtime. The memory leak would eventually stop around 17.5-18.5 GB of total RAM + VRAM used. Increasing swap file size would let the game run without issues or crashes.
That specific use case shouldn’t be needed anymore since Valve switched SteamOS to use ZRAM instead of traditional swap.
I played God of War, out of spite, precisely when people were making this absurd claim and it had zero issues without Cryoutilities.
Increasing swap wouldn’t fix a crash related to a memory leak, unless you had no swap to begin with, which was never the case for SteamOS.
I 100% had this issue, I could watch the combined memory climb towards 17GB over a play session, and when it got close the system would lock up. This was on an LCD deck, and I was targeting a 30fps with some of the graphical texture settings on high iirc. Some people reported being able to play the game fine, and my best guess is that they were targeting a higher frame rate and had graphical textures turned down. Since the memory leak would eventually stop growing, it’s possible that with low enough settings you might be able to stay under the crash threshhold.
The other possibility is that since it only would crash after playing for awhile, that short play sessions might let you get through without issue. The length of the sessions before a crash would probably be longer the lower your texture settings.
