![]() ![]() Now try launching the game and the mods should load properly.native is the one you provide, while builtin is the one Wine offers.Confirm with OK until you are back in the Bottles UI. It will appear in the list and should say (native, builtin) next to the name. In the dropdown New override for library, select the name of the DLL you want to add, eg.Below the Add application button is a Windows Version selector, set it to Windows 10 for most games.Back in the Application list, make sure the executable you just added is selected.Replace with the directory where your game is located.local into the File name box and hit Enter, then continue navigating. Navigate to Z:\home\deck, then manually type. local directory will not be visible in the file browser. Navigate to Z:\home\deck\.local\share\Steam\steamapps\common\ and select the game executable, confirm with OK. On the first tab Applications, click Add application.Open Legacy Wine Tools, then Configuration.Launch Bottles and open the bottle for the game in question.For multiple DLLs, separate them with, like this "dinput8.dll,d3d9.dll=n,b". WINEDLLOVERRIDES="dinput8.dll=n,b" %command%, replace dinput8.dll with the DLL(s) you want to load. Instead we have to tell Wine/Proton to override the builtin DLL with the "native" one we provide.Įasier way, thanks to majinavelli: Add a launch option to the game Several games initiate mod loading by adding a DLL (usually dinput8, d3dsomething) into the game directory, basing on the fact that Windows first loads DLLs in the same directory as the executable, then the ones in the system. Alternatively, SteamTinkerLaunch allows running a command inside the wine prefix as well.ĭepending on the game's modding mechanism, the next step may be required in addition. I'll update this on how to create a permanent link to the mod loader so it runs within the wine prefix in case you need it more often.Click the big blue button Run Executable., navigate to the mod loader or patcher and click Run. ![]() Select a game, dismiss the "Missing runner" message, we don't care.After restarting Bottles, your installed games should show up as Bottles on the "Your Bottles" page in a "Steam Proton" section.Start Bottles, go to Preferences, scroll down to Integrations and select "Steam Proton Prefixes".If you have a MicroSD, enter into the box right below "All user files": /run/media/mmcblk0p1.Install Bottles and Flatseal from Discover.Launch Bottles and open the bottle for the game you want to mod. Bottles from Discover store turned out to be the easiest way for me to launch the mod loader/tool.Copy the mod loader to the appropriate location (game directory (see above) especially for patchers, a directory in your home directory, or wherever the instructions coming with the tool say).Some mods patch the executable and many mod loaders only need to run once to setup everything if you found your final mod configuration. DLL files among the copied files, check the section "DLL Loaders" below as well, else the mods will not work. Copy the mod files to the correct location for your game and overwrite existing files if asked.Alternatively, open Dolphin and navigate to /home/deck/.local/share/Steam/steamapps/common (or /run/media/mmcblk0p1/steamapps/common for MicroSD) and find the game directory there.Right-click it, Manage, Browse local files. When unpacking the files on the Deck directly using "Ark", click the "Extract" button, then make sure "Preserve paths when extracting" is seletected in the options on the right, before clicking OK. Generally, adhere to the instructions coming with the mod, like file locations or other usage hints. They should work properly without additional setup. All of this happens in Desktop mode, of course.įor a handful of games, there are Linux native tools, like Scarab for Hollow Knight, hephaestus/modmanager (run hephaestus first) for Hades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |