Victory Alpha 0.4.3 / Installer transparency
What the installer does
Victory uses third-party software to run the game and to prepare data from your own WC3 installation. Here is exactly what the published Alpha 0.4.3 installer copies, downloads and runs.
← Downloads and installation instructions
Before you install
Microsoft Visual C++ is the shared Windows prerequisite. The other setup tools are bundled with Victory or downloaded into its own user-data folder. The current installer automatically prepares the media and installs the four ready-baked planets; it does not offer individual opt-out boxes for these steps.
You do not need Epic Games Launcher, Unreal Editor, Visual Studio, Build Tools or the Windows SDK. The downloadable Victory installer does not install them. It also does not install a GPU driver, SteamVR, Meta Quest Link or Virtual Desktop.
What happens during setup
- You choose a destination (default
%LOCALAPPDATA%\Programs\Victory) and your own WC3 folder: the GOG DOS release containingDATA.DAT, or the 30th Anniversary Edition’s main folder. The installer suggests a copy it finds in GOG’s or Steam’s usual places (Steam: every library listed in Steam’slibraryfolders.vdf); it only reads those folders. With the 30th Anniversary Edition a Cinematics page then asks which set to play: Remastered, Remastered upscaled (ODVS’s 4K Video Pack when it is installed in the edition) or the original 1995 cinematics. Setup prepares only that set. - Setup copies the game, assets, runtime libraries, Victory icon, licences, setup scripts and a private Python runtime into the chosen Victory folder. This payload is approximately 4.7 GiB, including the four ready-baked planets and the enhanced room artwork, before local game data is generated.
- It removes the older per-version Victory Alpha … shortcuts and creates the Victory Start menu folder with Victory, Victory VR (experimental), Import HD Videos and Uninstall Victory. A desktop shortcut is optional. Windows receives a per-user uninstall entry.
- It launches the bundled Microsoft Visual C++ x64 redistributable with
/install /quiet /norestart. Windows may request administrator approval for this shared prerequisite. The Victory files themselves use a per-user installation. The command does not force a restart. - Using the bundled Python, setup runs
setup.py --media --terrain --game <your WC3 folder>. It verifies the original game, downloads the tools listed below over HTTPS, checks their pinned SHA-256 hashes, prepares the local data described below and unpacks the ready-baked planets. Keep the preparation window open until it finishes.
These are the operations performed, rather than a guarantee of the order in which overlapping prerequisite and preparation windows appear. Allow 20 minutes or more for first-time preparation; the time depends on your PC and internet connection. If preparation fails, setup shows an error and the game is not ready even if its files were copied.
Components already inside the installer
- Microsoft Visual C++ x64 Redistributable 14.50.35719.0
- The game’s shared C++ runtime prerequisite. Its installer is bundled under
Engine\Extras\Redist\en-usand may install or update the Windows runtime. An ARM64 redistributable EXE is also present in Unreal’s staged files, but Victory’s recipe explicitly runs only the x64 EXE. - Python 3.13.17, embedded 64-bit distribution
- A private interpreter under
<Victory folder>\tools\python, bundled from python.org. It runs setup, the launcher and the HD-video importer. Victory does not register it as a system Python or add it to your permanent PATH. - Unreal Engine 5.8.4 game runtime and supporting libraries
- These are app-local files used by the compiled game, not the Unreal Editor or a separate engine installation. The staged package includes Direct3D 12 and DirectML DLLs, XAudio2, OpenXR loader, Ogg/Vorbis, MSQuic, ONNX Runtime, TBB, DbgHelp, NVIDIA Aftermath, WinPixEventRuntime and Vulkan diagnostic-layer files. Unreal also staged GPU-dump viewer files. Copying these libraries does not install a graphics driver, a VR runtime or a standalone application for each library. Exact filenames, sizes and hashes are in the payload inventory below.
- Ready-baked planets (Victory-Terrain.zip)
- The four planetary terrains (Alcor, Freya, Hyperion and Kilrah), baked by the Victory team from Wing Commander III’s elevation data with Victory’s own bake tool. Setup checks the bundle’s SHA-256 and unpacks it into your user-data folder. No terrain is computed on your PC.
- Enhanced room artwork (Victory-Room-Art.zip)
- Upscaled Victory room artwork with AI-created widescreen extensions, checked by SHA-256 and combined locally with your original room data.
Automatic third-party downloads
The three packages below are fetched during the standard first-time setup. FFmpeg and FluidSynth are unpacked portable tools; the soundfont is a data file. Earlier alphas also downloaded NumPy, SciPy, Numba and llvmlite to compute the planets; Alpha 0.4 ships the planets ready-baked and no longer downloads them.
| Component / version | Why Victory uses it | Source |
|---|---|---|
| FFmpeg (GyanD essentials build) 9.0.2 | Converts original cinematics, audio and comm media. Its ffprobe tool also checks codecs when you import an optional HD video ZIP. | Exact download Project / release |
| FluidSynth 2.5.1 | Renders the original MIDI music to playable audio. | Exact download Project / release |
| GeneralUser GS soundfont GeneralUser GS 2.0 | Provides the instrument sounds used by FluidSynth; this is a sound bank, not an application. | Exact download Project / release |
Downloads come from GitHub / its download hosts and raw.githubusercontent.com, as shown in the exact links. Windows’ existing curl.exe performs the HTTPS downloads; Victory does not install curl. Archives are checked against the hashes in the dependency manifest before use. A mismatched download is rejected. The manifest still lists the four terrain libraries for developers who bake planets themselves; setup does not use them.
Downloaded archives and extracted files are kept at %USERPROFILE%\.local\share\star-agent-wc3\tools\<component>\<SHA-256>. During extraction, setup uses a short temporary folder directly under tools to avoid the long-path failure in Alpha 0.3. Verified downloads and completed setup stages can be reused on a later setup run.
Room artwork and data prepared from your WC3
Setup reads the original installation without changing it. It creates the following caches under %USERPROFILE%\.local\share\star-agent-wc3:
fmv-cache\original: original cinematics converted locally to H.264/AAC for playback, including original branch timing and silent clips. The original game is required; these videos are not bundled.gameflow-cache-4k-wide: the enhanced room cache, assembled locally from your verified original room data and the included upscaled artwork with AI-created widescreen extensions. Artwork checksums are verified; current campaign data and the original cache are preserved. Older first-frame room caches are rebuilt with complete animation frames; their previous copies are retained. No image-generation service runs during installation.gameflow-cache: room/gameflow data, TOBI, loadout and simulator data.missions-cache: decoded mission data.dialogue-cache: decoded dialogue data.flight-audio-cache: flight sounds.cockpit-art: cockpit/loadout images processed with the local Scale4x algorithm.terrain-cache\alcor,terrain-cache\reactor,terrain-cache\tstplntandterrain-cache\kilrah: four 4096 × 4096 planetary terrain caches (Alcor, Freya, Hyperion and Kilrah), unpacked from the ready-baked bundle in the installer.fmv-cache\engine-ea30andcomm-cache-ea30(30th Anniversary Edition only): the edition’s remastered cinematics and HD comm videos, copied as they are from your own installation of the edition.comm-cache: comm portraits/video frames and associated data.audio-cache: converted music and room audio, using FFmpeg, FluidSynth and GeneralUser GS.
windows-setup.json records your selected original-game path, archive fingerprints and completed stages. install-logs holds diagnostic logs from the start of preparation, including original-game verification and dependency failures. Setup uses a lock to prevent overlapping runs. Old or incomplete cache folders are preserved under .old; audio conversion uses temporary .staging files and removes that run’s successful temporary inputs after completion.
The setup scripts process your game files locally; they have no step that uploads your original game files. The listed downloads still involve ordinary network requests to their publishers.
The launcher and control profiles
The Victory shortcut opens a launcher using the Windows PowerShell already on your PC. It reads local installation status, offers original-game preparation and optional HD import, and starts the game in desktop or experimental VR mode. It does not install PowerShell.
When the launcher opens, it reads https://victorywc3.info/downloads/latest.json to see whether a newer release exists. If that release publishes an update package, the launcher offers Update to …: on your click, it downloads only the files that changed from victorywc3.info/downloads/store/, verifies the release index’s Ed25519 signature and every file’s SHA-256, replaces the changed files while keeping a backup (restored if anything fails), and runs setup again with your original game. Otherwise it links to the download page. It sends no game files or profiles.
Co-op (experimental) contacts victorywc3.info (UDP port 7779) only when you open CO-OP: it sends the nickname you choose and, once you are linked with a friend, the game state the two games share. Linked games then try to connect to each other directly.
Saved control profiles are stored separately under %USERPROFILE%\.local\share\star-agent-wc3\control-profiles. An upgrade preserves these profiles, campaign saves and imported HD videos.
Optional HD videos and VR
For existing Alpha 0.1 installations only, the small HD Video Update updates scripts\wc3-windows\import_videos.py and launch.py inside your chosen Victory folder. It keeps each previous script with a .before-hd-update suffix. The launcher change enables compatible Windows movie playback. It adds no services, codecs or separate uninstall entry, and leaves saves and videos unchanged.
The installer does not download an HD cinematic pack. If you already have ODVS’s HD Video Pack 2.0 or the cd1188 English pack, the separate Import HD Videos shortcut opens a Windows file picker using the existing Windows PowerShell. It verifies your original WC3 installation, uses the FFmpeg package’s ffprobe to check the clips, maps filenames to game branches and copies their encoded video into fmv-cache\engine. AAC and Opus audio are retained; other audio, including AC-3, is converted to AAC with FFmpeg. The video is never re-encoded. Both root-level clips and clips inside one enclosing folder are accepted. Repeat imports check source and output hashes and skip completed clips. Different existing clips are preserved. Windows PowerShell is not installed by Victory.
The experimental VR shortcut requests OpenXR and relies on a PC VR runtime you install and configure separately. Its presence is not confirmation of Meta Link or Virtual Desktop compatibility.
System changes and removal
Victory’s scripts do not permanently change your account’s PATH or HOME variables. The launcher sets HOME to your actual user profile and WC3_PATH to the verified original-game folder only for its game process. WC3_GAMEFLOW_CACHE selects the prepared widescreen rooms for that process. Media-tool PATH changes and terrain-library paths are confined to setup’s child processes.
The installer recipe does not add firewall exceptions, scheduled tasks or background services. Windows may show a firewall prompt when the Unreal game first launches; that is a separate Windows permission prompt, not another third-party tool installation.
Uninstall Victory removes the installed app files, shortcuts and its uninstall entry. It deliberately leaves your saves, generated caches, downloaded tools, logs and imported videos in %USERPROFILE%\.local\share\star-agent-wc3. It also leaves the shared Microsoft Visual C++ runtime installed because other programs may use it. Your original WC3 installation remains untouched.
If you want to remove Victory’s remaining user data, back up any saves first, then remove that specific star-agent-wc3 folder yourself. The downloaded installer ZIP and its extracted EXE/BIN files also remain wherever you saved them.
Sending logs to the developers
New in Alpha 0.4.1. Nothing is sent unless you choose Send logs to developers in the launcher and confirm. A report contains the game log of your last two sessions (hardware, controllers, errors, frame hitches), the latest setup log and the installation status the launcher shows. Before sending, the launcher removes your Windows account name, computer name and machine identifiers; Show me the files first opens exactly what would be sent. Saves, settings, your original game and movies are never read. The report goes over HTTPS to victorywc3.info, which stores it without your network address, answers with a short code and deletes it after 30 days. Reports cannot be downloaded from the site.
Check the published package
Full payload file inventory, sizes and SHA-256 hashes · Exact download URLs, versions and pinned hashes · Known limitations
The payload inventory records the files before installation; locally generated caches, downloaded dependencies and Windows’ uninstall files are separate. This inventory describes the published Alpha 0.4 installer.
Optional TrackIR
Experimental TrackIR support uses the TrackIR software you install separately. Victory does not install a TrackIR driver, download its runtime or include a vendor DLL. Without TrackIR, normal camera controls continue to work. VR uses the headset instead.