Read the release notes for more details on the various launch options and script features.Ĭertain other mods such as texture packs may require some additional components to work properly. This approach can be used for running other launchers & mod managers etc. Run the start script with no arguments to bring up the menu, select the option to create a shortcut, and set the shortcut arguments to: runwine=nvse_loader.exe You can create a shortcut to use NVSE automatically. You can then launch it by running the start script with the argument: runwine=nvse_loader.exe Install NVSE into the game's directory inside the Wine prefix as you would on Windows (this can be found at /prefix/drive_c/Fallout New Vegas) The start script includes options for running custom commands and creating custom shortcuts for mods, tools/utilities etc. If anyone runs into any problems with this then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ & Discussion and/or The "Judas™ does this run in Wine" thread v1.173. This will be stored in ~/.cache/wine to save having to redownload it if it's needed again for something else. In addition to Wine and Winetricks, Wine Mono will also be downloaded. Wine and Winetricks will be downloaded automatically if not present to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap User data is stored under ~/.local/share/falloutnvįull details are in the readme.txt and release notes. (to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings) The start script also includes options for creating a shortcut, configuring the wrapper etc. From there simply run the start script to play. The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). The build path can also be set with the WINEWRAP_BUILDPATH environment variable. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. If the installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="" or by setting an environment variable named WINEWRAP_RESPATH containing it. Simply run the build script to create the wrapper. I've put together a Wine wrapper for Fallout: New Vegas, allowing it to be played on Linux almost like a native game & with no Wine knowledge required.
0 kommentar(er)
