Wine Launcher is a Wine-based container for running Windows applications.

Review

Gamepads

Video instruction

- !!!Warning!!!
! Wine Launcher is not a PREFIX MANAGER like PoL and Lutris!
! Don't try to install all your games into it!
+ Use a separate Wine Launcher for each game.

• Portable assembly.
• Easy Wine update and prefix re-creation without losing game progress.
• System isolation, no files are written to the main system.
• Compressing games into squashfs images.
• Integration with Proton, VKD3D Proton, DXVK, MangoHud, vkBasalt, Media Foundation, Gamemode, AMD FidelityFX Super Resolution, ESYNC, FSYNC others.
• Gamepads. Integration with gamepads for games that do not support gamepads. Support for multiple layouts by next_mapping key.
• Diagnostics. Checking the system for correct settings and required libraries installed.
• Patch system. Auto commit the changes in the prefix and the registry.

1. Download the current start (x86_64 only) file from the releases page.
2. Create an empty directory anywhere and move the file there.
3. Make the file executable and run

   chmod +x ./start && ./start

4. Wait for initialization.
5. Close the launcher and move the start file to the bin folder that appears.
6. Done.

mkdir WL; cd "$_"; curl -L https://github.com/hitman249/wine-launcher/releases/latest/download/start --output start; chmod +x ./start; ./start

In one Wine Launcher, it is recommended to install only one game. Then it will be more convenient for you to compress it to save places in the section Tools > Packaging

1. You can run application in the debug mode

   In this mode the dev tools will be available

   env debug=1 ./start

2. Building the project

   sudo apt-get install libxtst-dev libpng++-dev
   sudo npm install -g node-gyp
   npm i && cd ./src && npm i && cd ../
   npm run electron-rebuild
   npm run build

   When build finishes, dist directory will have executable file start

3. Building the project in Docker (required docker-compose)

   ./build.sh

4. Development

   Step 1. Launch Vue

   npm run serve

   Step 2. Run application in debug mode

   env debug=1 ./start

   Step 3. In the opened dev tools bar, go to

   app.href('http://localhost:8080')