Skip to content

insomnious/Vortex

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Vortex

Building from source code

To build from source you have two choices.

1) Automatic (mostly):

  • Download bootstrap.ps1 and run as a powershell script
    • In the dialog that shows up, select a build directory (should be a clean/new one)
    • This script will try to download and install all dependencies, then check out and build vortex
    • The dependencies are not installed headless so you have to click through the dialogs but it's only guaranteed to work if you keep the defaults

2) Manual:

  • Before you can build vortex you need to download and install a couple of dependencies. If any of the download links is no longer valid, try google or a search engine of your choice.
Node.js
  • Download installer from nodejs.org and run the installer
  • Version should not matter, the latest LTS version should be fine
  • Verify that Node has installed successfully by running node --version in your cmd or terminal
Yarn
  • Run npm install --global yarn
  • Verify that Yarn has installed successfully by running yarn --version in your cmd or terminal
Git
  • Download installer (64-bit) from git-scm.com and run installer
  • Verify that Git has installed successfully byb running git --version in your cmd or terminal
Python
  • Required for one of the build tools (node-gyp). At the time of writing versions 3.7-3.10 are known to work
  • Download installer (64-bit) from python.org and run installer
  • Make sure to have it added to PATH, otherwise defaults are fine.
Visual c++ build tools 2022 or Visual Studio 2022 (Community Edition)
  • Download installer from visualstudio.microsoft.com
    • You may have to google around for this as Microsoft tends to change their sitemap all the bloody time
  • In the installer, make sure you enable the build tools themselves, the latest windows SDK (version doesn't actually matter) and ATL headers. Everything else is optional.
Set up yarn to use C++ build tools
  • Run yarn config set msvs_version 2022 --global
    • This sets up yarn to use the c++ build tools we just installed, you probably only need to do this if you've also installed other versions of Visual Studio. Can't hurt though

Cloning and building the Vortex source code

  • Create and cd to an appropriate directory (i.e. c:\projects)
  • git clone https://github.com/Nexus-Mods/Vortex.git from the created directory
    • this should create a new directory vortex in the current working directory (i.e. c:\projects\vortex)
  • Go into the vortex directory cd vortex
  • Switch to an appropriate branch, if necessary
    • git checkout some_branch
  • For development
    • yarn install to install dependencies
    • yarn build to build
    • yarn start to run
  • For production
    • The scripts (electron-builder-oneclick.json and electron-builder-advanced.json) are set up to require code signing with a certificate you don't have so change that
    • yarn dist to build (this will take a while)
    • Find the installer and an already unpacked version in dist

If something goes wrong:

The build tools are unfortunately not particularly robust, so the build may break for various reasons (i.e. network problems, dependencies that changed remotely, ...) and leave the checkout in an inconsistent state. In that case you will have to see if the error is something that needs to be fixed, then restart from the last step that failed.

The automatic variant will skip dependency download and install if the download was installed previously. If a dependency install failed for some reason or you cancelled it, you will have to manually install that package (see the downloads directory).


Further Information

Reporting bugs

Please report issues to the issue tracker on github. Please always include at the very least the following information:

  • The exact version of Vortex you're using
  • Your operating system
  • What you were doing when the bug happened
  • What exactly the bug is (crash? error messages? unexpected behaviour?)
  • If you get any error message, include the full and exact error message. Do not paraphrase, do not leave out information that looks cryptic or unimportant to you
  • The log file (see below)
  • Ideally also the application state (see below)

All data the client generates (including settings and logs) are stored at

C:\Users\<username>\AppData\Roaming\Vortex (releases)

or

C:\Users\<username>\AppData\Roaming\vortex_devel (development build)

If you need to report a bug, the following files inside that directory may be useful in addition to the error message displayed on screen:

  • vortex.log (logs are rotated at a certain size, this is the latest one)
  • state\* except global_account (that one contains keys and passwords so sensitive information)
  • <game>\state* (if the bug pertains to a specific game)

About

Vortex Development

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 86.2%
  • SCSS 9.3%
  • JavaScript 4.3%
  • HTML 0.1%
  • PowerShell 0.1%
  • NSIS 0.0%