Lutris has GoG integration and it’s exactly that same 2 step process if you use it (I believe it passes you through 3 screens of options were you invariably do nothing but click “Continue”, so strictly it’s 5 steps were 3 of the are just “Press Continue”)
The difference is that when it does NOT just work, it’s easier to figure out and there are more options to fix it with Lutris + Wine.
I even have some weird weird cases on Steam - like Borderlands 2 were Steam would often and randomly, before actually starting the game spend almost 1h doing shader conversions that if you stopped it the game would fail to start (the solution was to force an older Proton version and now you just get random downloads from the Internet that last a few minutes before the game starts).
IMHO, here too what one sees is the general design philosophy difference between open source software and corporate solutions - the former gives you tons of options and lots of ways to tune it so it looks more complicated to use and has a steeper learning curve but that also means when things go wrong you have a lot more ways to try to fix it, whilst the latter is click & play until things go wrong and then you have very little info and just a few things you can change to try and fix it.
Mind you, Lutris itself seems to be an attempt to also be click & play (hence why you generally get a steam-like experience if you use its GoG integration) but all the “buttons and knobs” are still there (those 3 screens of options that’s usually fine to just press “Continue” on that I mentioned above) just in case you want to muck about with them, making it look daunting to use.
I’m not saying it doesn’t work. I’ve set several things from GoG up using Lutris. But in Steam it’s a two step process:
I want that level of ease from GoG.
Lutris has GoG integration and it’s exactly that same 2 step process if you use it (I believe it passes you through 3 screens of options were you invariably do nothing but click “Continue”, so strictly it’s 5 steps were 3 of the are just “Press Continue”)
The difference is that when it does NOT just work, it’s easier to figure out and there are more options to fix it with Lutris + Wine.
I even have some weird weird cases on Steam - like Borderlands 2 were Steam would often and randomly, before actually starting the game spend almost 1h doing shader conversions that if you stopped it the game would fail to start (the solution was to force an older Proton version and now you just get random downloads from the Internet that last a few minutes before the game starts).
IMHO, here too what one sees is the general design philosophy difference between open source software and corporate solutions - the former gives you tons of options and lots of ways to tune it so it looks more complicated to use and has a steeper learning curve but that also means when things go wrong you have a lot more ways to try to fix it, whilst the latter is click & play until things go wrong and then you have very little info and just a few things you can change to try and fix it.
Mind you, Lutris itself seems to be an attempt to also be click & play (hence why you generally get a steam-like experience if you use its GoG integration) but all the “buttons and knobs” are still there (those 3 screens of options that’s usually fine to just press “Continue” on that I mentioned above) just in case you want to muck about with them, making it look daunting to use.