Quoting: Comandante ÑoñardoC'mon!
With WINE-GE, Lutris was already a clic'n'play experience.
This mutant spawn is not even available by default...

Please, can someone else continue with the old but good wine-ge project?

The simpler things are, the more complex people see them 😅

View this comment - View article - View full comments

Quoting: lectrodeThe new versioning system looks nice, but seems to have a notable flaw when it comes to troubleshooting/determining which change caused a particular issue.

Specifically, it only works one-way: if you roll back to a prior version, all versions that happened after that are deleted. Any changes you had after that point you'll need to redo manually.

This is an intentional limitation of the chosen versioning system [External Link], which can help simplify things, but also means you need to be aware that the action of rolling back cannot be undone.

FVS per concept does not allow travel to the future, so all the States after the restored one are deleted.

Travels to the future is something I want to allow in the near future, but it requires further investigation as it will be necessary to add branches to vs

View this comment - View article - View full comments

Quoting: McCartheeThis is good. For whatever reason the Wine-GE versions are weeks out of date in Bottles.

Our repositories are public, everyone is free to contribute by adding new versions of wine 👀

View this comment - View article - View full comments

Quoting: wolfyrionI have Just install the latest version from AUR and Flatpack to see what is the fuss about it...

Both versions ...Crashing all over the place!
A lot of bugs , I cant even press the next button.
Had to press ALT+F4 to close the tips popup.
Tried to install something - crashed...
open it again - crashed...

Can you send a report on GitHub?

View this comment - View article - View full comments

Quoting: Purple Library GuyBut if you don't update your Wine version, it'll be old Wine in new Bottles.

Ya, not. You can use wine from your system but Bottles will still install its (constantly updated) own and will always default to that.

Edit: Oh wait, maybe that was a joke :S

View this comment - View article - View full comments

Quoting: chrisqThere should to be a way to specify multiple locations of bottles.

We have planned to implement it and will arrive soon, we are looking for the right workflow.

Quoting: NociferSeeing as you're here and willing to answer questions, I have one: why have you (the Bottles devs) seen fit to re-invent the wheel and opt for a new, custom system for installing external requirements instead of using good ole Winetricks? On the one hand I can understand it (tighter control over the procedure and simpler/prettier to use because it's integrated right into the UI) but on the other hand it opens the door to an array of new issues, the main one being that some stuff that install just fine with Winetricks (notably the dontnet35 package) fail to do so with Bottles, because Winetricks takes into account possible Wine bugs and implements workarounds for them, while Bottles right now doesn't. Another issue is with the checksums, which seem to go bad every other day or so.

I'm all for having a tight GUI without external nuisances (like Winetricks, which is horrible as an app) but it should be made certain that at least the essential stuff (i.e. all the ones that you have implemented) Just Work™. And unfortunately, guaranteeing that the essential stuff Just Work™ means doing the necessary research and implementing workarounds for any and all obscure quirks - which is what Winetricks is all about.

There are more reasons that led us to replace winetricks (we held it from 2017 to 2019) for our dependency manager:

- as you predicted the first reason is integration, this understood as integration of the entire Bottles infrastructure and not only the GUI (where the user must be able to have at least visual feedback of what is happening), the manager must be able to communicate harmoniously with all the components of the project (as is the case now)

- we needed a cleaner and more organized method for addictions, winetricks is a fantastic project but it is based on a file of infinite length, we want a repository that can be easily extended and which can handle a dependency tree for cascading installations

- we needed a method to manage dependency conflicts, being able to declare with which dependencies one conflict (not yet implemented)

- we wanted a faster method, winetricks in some cases can really take a lot of time while on Bottles it is faster for a series of factors given by the development and its structure (and the different methods by which they are installed in Bottles)

Regarding the problems with dotnet, there were a number of problems caused by an error in the Windows version change method. We have fixed it with latest update.

About checksums I don't know, winetricks also uses checksums to validate downloads, links and process are the same. Regarding having to constantly update them .. well it's a problem that also has winetricks but happens at most once a month if not more.

Regarding dependency manifests, we have been hit by some bugs but at the moment all methods (the actions) are fully functional and are constantly updated and extended release after release. We are writing documentation for maintainers explaining how to use each action, this should greatly facilitate the collaboration process. In any case, to date, to make a dependency, it is enough just to create its manifest, unless you need particular actions which are not available but it is enough to apply.

There are other details about this in the documentation.

View this comment - View article - View full comments

Quoting: kibasnowpawThis is way to complicated to use and it don't feel user friendly at all and a stuff is missing or not working. i still feel like lutris is a better options here or if you somehow can miss mass this two.

Our focus is on ease of use. What and how should we improve?

View this comment - View article - View full comments

Quoting: Comandante ÑoñardoI am testing it, and I wonder how to change the default location for the bottles...

We will support this in the future :)

View this comment - View article - View full comments