Vega Strike 引擎
#====================================
# @file : README.md
# @brief : quick repo guide
#====================================Vega Strike is a Space Flight Simulator that allows a player to explore, trade, and fight in the vast openness of space. You start in an old beat up cargo ship, with endless possibilities in front of you and just enough cash to scrape together a life. Yet danger lurks in the space beyond.
Either install Vega Strike from the binary installer for your platform, if available, or follow the instructions for compiling from source. (Compiling Vegastrike, below.)
bin/vegasettingsbin/vegastrike-engineIf you install Vega Strike version 0.11.0 on Windows, you also need to install Python 3.12.10, separately, for the game to work. This exact version of Python is required. Without it, the game will exit silently as soon as it starts up. See for the download.
(At some future point, we may figure out a better way to handle the Python dependency.)
Vegastrike command line parameters allow for different start settings and are as follows
vegastrike-engine -ddata_dir [-px,y,z] [-jsector/starsystem] missionname
OPTIONS
-d/my/data/dir
specifies /my/data/dir as the path for finding the vega strike data. Re-
quired.
-p1024,2405,1245090101
Forces the player's starting location to be at x= 1024, y= 2405,
z=1245090101
-jgemini_sector/troy
Forces the player to start in the troy system in gemini sector.
missionname
Specifies a mission for vegastrike to run. Default is main_menu.mission.Vegastrike takes a single positional parameter indicating which mission it should load
$ bin/vegastrike mission/explore_universe.mission -d$(pwd)/../Assets-Productionis an example of a valid mission call
the -l flag (must be flushed with the system) will force a player to begin in a star system.
$ bin/vegastrike -lvega_sector/vega mission/bomber.mission -d$(pwd)/../Assets-Productionwill force the bomber mission to run in the vega sector.
Note that the executable names have changed since the 0.5.x releases. Now, you configure game settings using vegasettings, and run the game itself using vegastrike-engine. With the latter, the data directory (-d...) is now a required parameter. This is to allow using the Vega Strike Game Engine with multiple games (asset sets), including Upon the Coldest Sea (vsUtCS), PWCU, and others.
Also note that when you install vsUtCS, it comes with a script called vsettings that automatically runs vegasettings with the correct data directory, and another script called vs that automatically runs vegastrike-engine with the correct data directory. These scripts are the recommended way to run the game Vega Strike: Upon the Coldest Sea. You should see shortcuts to them on your desktop, Start Menu, or similar.
If you encounter any issues while playing, please create an issue with the Vega Strike development team by posting a new issue.
…The Vega Strike Engine Source repository contains a lot of history not all of which is relevant to current developers if they want to quickly download and build something. By default, the full clone will download over 800 MB of data. There are several options to minimize this:
$ git clone [email protected]:vegastrike/Vega-Strike-Engine-Source.git --shallow-since=2023-09-27This will produce a significantly smaller download - in the order of 22-30 MB; well over a 10x reduction.
Install the development dependencies:
a. Run sudo script/bootstrap
b. OR install the dependencies manually. For Debian, Ubuntu, openSUSE Leap, Fedora, and Rocky Linux, you should be able to reference the contents of the bootstrap script to determine what dependencies to install yourself.
On Funtoo(-current):
Most dependencies are already met with a standard desktop Funtoo install. In particular, you want to make sure your "flavor" is set to desktop, and that you have a proper "mix-in" depending on the desktop manager you use. Check your current profile:
$ sudo epro showand if you don't have the desktop flavor enabled, enable it with
$ sudo epro flavor desktopAlso enable the proper mix-in for your desktop manager; for instance xfce:
$ sudo epro mix-in +xfce (or gnome, kde etc)All of the steps above are outlined in the Funtoo installation guide at and you should have done it already in the process of installing desktop Funtoo. The only dependency that you have to install manually is OpenAL:
$ sudo emerge media-libs/openalAfter that you are ready to compile.
Build Vega Strike:
a. Use the build bash script in the script directory.
b. OR configure and compile VS manually, using the ncurses ccmake frontend:
$ mkdir build
$ cd build
$ ccmake ..
$ # (configure/edit options to taste in ccmake, press 'c' to save the selected options
$ # and press 'g' to update the build configuration files used by the make build tool)
$ cd ..
$ cmake --build ./build -j $(getconf _NPROCESSORS_ONLN) # (where the getconf clause returns the number of available CPU threads/cores on the system)
$ mkdir bin
$ cp build/vegastrike-engine build/setup/vegasettings binc. OR configure and compile VS manually, using the command-line cmake frontend:
$ mkdir build
$ cd build
$ cmake ..
$ cd ..
$ cmake --build ./build -j $(getconf _NPROCESSORS_ONLN) # (where the getconf clause returns the number of available CPU threads/cores on the system)
$ mkdir bin
$ cp build/vegastrike-engine build/setup/vegasettings binTIPS:
To enable verbose output for debugging purposes (will show compilation commands), pass the --verbose argument, where supported:
$ cmake --build ./build --verboseTo enable/disable compile-time options with cmake, use cmake -D=. Example:
$ cmake .. -DENABLE_PIE=ON -DUSE_PYTHON_3=ON -DCPU_SMP=2 -DCPUINTEL_native=ON -CMAKE_BUILD_TYPE=DebugNOTE:
On some Ubuntu versions and derivatives, a bug exists whereby enabling
PIE compilation (Position Independent Executables) results in the
file utility incorrectly recognising the compiled vegastrike binary
as a shared library instead of a position independent shared executable
object.
The effect of the bug is that vegastrike can still be started from the command line but that it will not be recognised as an executable by GUI file managers such as Nautilus and Dolphin.
To avoid this scenario, turn off this flag by default and let packagers on other distributions turn this on if their OS is able to correctly deal with Position Independent Executables.
For more info, see:
Download a copy of the assets/game data from here. You can either git clone this repository, or download it as a ZIP file and unzip it.
When you run vegasettings, specify the path to the assets/game data on the command line with --target followed by a space. E.g.:
$ ./bin/vegasettings --target $(pwd)/../Assets-ProductionThe absolute path may need to be supplied, rather than a relative path.
Do the same with vegastrike-engine using -d and no space. E.g.:
$ ./bin/vegastrike-engine -d$(pwd)/../Assets-ProductionLink to list of dependencies in wiki
If there are any problems with this installation method, please create an issue with the Vega Strike development team by posting a new issue.
Vega Strike is now compiling on Windows! There are also installers available for Windows 10 and Windows 11, as of Vega Strike v0.9.0-beta1. If you want to try it out and perhaps offer feedback, that would certainly be welcome.
To compile Vega Strike on Windows, start by installing either Visual Studio 2026 or just the Visual Studio 2026 Developer Tools. When selecting the Workloads and Components to install, include at least "C++ for Desktop" and a recent build of the Windows SDK. Probably Git and the GitHub for Windows extension also. Install the latest Visual Studio updates as well.
Once the Visual Studio Installer finishes, reboot your computer. Then, find Developer PowerShell for VS 2026 on the Start menu; alt-click it ("right-click"); and choose "Run as Administrator." Run:
> Set-ExecutionPolicy RemoteSigned(or another suitable PowerShell Execution Policy of your choice). Type Y and press Enter to confirm. Exit PowerShell. Now reopen Developer PowerShell for VS 2026, this time without Admin privileges, and run:
> script/bootstrap.ps1Once that finishes, reboot your computer again. Finally, open Developer PowerShell for VS 2026 one more time, and run:
> script/build.ps1 -PresetName VS2026Win64-pie-enabled-RelWithDebInfo -BuildType RelWithDebInfo(The build type can also be Debug or Release. Just make sure that it matches the build type stanza at the end of the preset name.)
Assuming all the above steps succeed, you are now ready to run Vega Strike. Note that vegasettings is not currently building on Windows, so you will need to edit vegastrike.config manually as needed.
Finally, note that the location of the .vegastrike folder has changed since v0.5.1r1. It will now be located here: C:\Users\\AppData\Local\.vegastrike.
VegaStrike is now compiling on macOS as well! macOS 13 is the only version that we officially support at the moment, but the game will build and run on other macOS versions as well.
Please note: We only support Intel-based Macs (x86_64) at th
暂无开放 Issues,或尚未同步最近议题。