Lutris launches at OpenGamepadUI start

[cprn]

Hi!

1st of all, thank you for all your great work! I'm very new to OpenGamepadUI, but it looks and feels awesome, especially with Steam's BPM being sluggish to the point of unusable in 4K.

That said, I have ~2k games on Steam, and ~1k more on other platforms combined (mostly doubled). I have to wait 3-5 min for Lutris to open each time I start OpenGamepadUI. If I want to just quickly search through all my games on all platforms (e.g. to avoid duplicates when buying a new bundle), it gets in the way.

Can we not start Lutris when OpenGamepadUI is started? I have few Lutris games added to Steam, and starting Steam doesn't start Lutris, so I don't think it's necessary to have it running in the background. And if that's not possible, can starting it be at least deferred until the 1st game is launched, or until OpenGamepadUI opens completely and loads all cached library entries? Maybe a setting for that kind of "lazy loading"?

[strycore]

I've written a patch that improves Lutris library loading times drastically, it should be in the latest version of the plugin.

[cprn]

Sorry for keeping you waiting, but AUR -bin package didn't update yet and -git package seem to be Wayland only (I'm on X.org), so it'll have to wait a bit longer before I can test it. Does this patch solve auto-starting Lutris when I start OpenGamepadUI? Ideally, OpenGamepadUI would not start Lutris at all, just reach for the Lutris database file (if it exists) and update its own database, if necessary.

[strycore]

The problem isn't Lutris starting, that's fine and shouldn't increase load times significantly. The original code was starting Lutris for every game in your library which made library loading really slow if you have more than a handful of games (I have 2500).
With the patch, Lutris is only called once and loading the library is much faster. I don't feel there is a need for OpenGamepadUI to access the database directly, better leave Lutris handle it so it's more future proof.