-
-
Notifications
You must be signed in to change notification settings - Fork 2
FAQ
No. Optimum is a standalone client. It replaces the engine DLLs, not a zip in your Mods folder.
No. Optimum works with any server running the matching Vintage Story version.
Optimum does not give gameplay advantages. It renders the same world the same way, just faster. Server admins cannot detect it because it does not modify network behavior. That said, check your server's rules if you are unsure. Some servers have blanket "no modified clients" policies.
Yes. Optimum reads the same data folder format as vanilla. Point it at your existing data path with --dataPath or let it use its own. You can switch between Optimum and vanilla on the same world without migration.
No. Optimum is distributed as source. You download the source, run the build script for your platform, and the build downloads the official client (~590-610 MB) on your machine and produces a ready-to-run folder. Optimum itself ships no game files, so the source download is small.
The build targets x64 on Linux and Windows because Vintage Story has no official ARM client for those platforms. On ARM hardware, the x64 build runs via emulation (box64 on Linux, Windows-on-ARM). macOS Apple Silicon uses the native osx-arm64 client.
Expected. A build produced without an Apple Developer certificate is unsigned. Right-click the app, select Open, confirm the dialog. This happens once. To sign it, build on macOS with an Apple Developer certificate.
Run your original Vintage Story client. Your worlds and account are untouched. Optimum writes settings under Optimum* keys in clientsettings.json; vanilla ignores them.
It depends on your hardware, view distance, and scene complexity. Frame pacing improvements are noticeable on any hardware (stutter reduction). GPU-bound players in water-heavy biomes or with SSAO enabled see the most shader-side gains. CPU-bound players with high entity counts benefit from the distance gates.
The source is GPL-3.0 with the Commons Clause. Pull requests are welcome. Read Building from Source to set up the dev environment.
Known bug in 0.2.1: the chunkculling thread died on every world load with Field not found: 'ClientWorldMap.chunksLock'. Fixed in 0.2.2. Reinstall from the 0.2.2 release; the broken DLL lives in your install folder, so updating requires a rebuild.
A partially extracted or corrupted game download poisoned the build cache. Since 0.2.2 the installer detects truncated files, discards the bad extraction, and asks you to re-run. On older versions, delete the .vanilla folder next to the installer (or the Optimum install) and reinstall.