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.
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.