Skip to content
VSPT

Release by release

Before a release goes out it is flown against the one before it, to catch anything that has become slower. This page is those flights since 0.2.3. What the current version costs, setting by setting, is in the performance guide, and every other number is on the measurements page.

The frame rate of each release with 0.2.3 as 100, standing in a village and flying over new ground:

Release Standing Flying
0.2.3 100 100
0.2.4 99 99
0.2.5 97 98
0.2.6 122 114
0.2.7 123 114
0.3.0 122 111
4.0, on Vintage Story 1.22.7 120 111
4.0, on Vintage Story 1.23.0-pre.1 121 112

Each release’s figure is the one before it times the change measured between the two, in the flights below. It is a rough guide, since the steps come from different evenings.

Each row is a release and the version it was flown beside, on one evening in 2026. The figures are traced frames a second, the frames VSPT renders before any frame generation: the older version’s first, then the release’s.

Shown at 3840x2160 through DLSS Ray Reconstruction, Ultra Performance.

Release Flown Against Standing Flying Trace, standing (ms)
0.2.4 15 Oct 0.2.3 87.2 → 86.2 (−1.1%) 72.6 → 72.2 (−0.6%) not recorded
0.2.5 17 Oct 0.2.3 86.6 → 83.6 (−3.5%) 73.3 → 72.1 (−1.6%) 4.77 → 5.00
0.2.6 19 Oct 0.2.3 86.8 → 106.0 (+22%) 71.7 → 81.7 (+14%) 4.82 → 2.87
0.2.7 22 Oct 0.2.6 106.3 → 106.9 (+0.6%) 81.8 → 82.0 (+0.2%) 2.96 → 2.92
0.3.0 27 Oct 0.2.7 104.3 → 103.7 (−0.6%) 84.2 → 81.7 (−3.0%) 2.99 → 3.01

Shown at 3840x2160 through DLSS Ray Reconstruction, Performance, on a 120 Hz display with VSync. More than twice the pixels are traced here, so every figure is lower than in the table above, 0.3.0’s included: 0.3.0 itself flies at 60.6 frames a second this way, where it flew at 81.7 the other.

Release Flown Against Standing Flying Trace, standing (ms)
4.0, on Vintage Story 1.22.7 22 Nov 0.3.0 62.8 → 61.7 (−1.8%) 60.6 → 60.6 (0%) 6.27 → 6.49
4.0, on Vintage Story 1.23.0-pre.1 22 Nov 0.3.0 on 1.22.7 62.8 → 62.3 (−0.8%) 60.6 → 61.4 (+1.3%) 6.27 → 6.39
  • Each row is one evening. The release and the version beside it were flown in turn, minutes apart, on the same PC at the same settings. A setting the older version does not have was set to behave as that version does.
  • Compare the two figures in a row, not one row with another. The same version reads a few frames a second differently from one evening to the next, and the two tables trace at different sizes.
  • This is one card. The rows say how the versions compare on an RTX 5080, not what frame rate your card will give.
  • 0.2.4 and 0.2.5 between them gave the graphics card 0.2 to 0.3 ms more to do in a frame. 0.2.4’s flights had no frame longer than 50 ms, where 0.2.3’s had one or two a minute.
  • 0.2.6 is the large step. What you have switched off is no longer compiled into the shaders, and the trace became 34 to 40% shorter. Standing it traces 22% more frames a second, flying 14% more.
  • 0.2.7 kept that frame rate and made the game’s own frames steadier: the slowest one in a hundred went from 13.0 to 11.2 ms standing.
  • 0.3.0 is level standing and about 3% lower while flying, where the processor has a little more to do for each frame as new ground comes in. With bounces traced at three pixels in four, as 0.3.0’s High preset has them, it traced 106.5 frames a second standing against 103.7 at every pixel.
  • 4.0 stays within about a frame a second of 0.3.0 standing, flying and settled, on both game versions it is built for. What else it changes is in the performance guide.

A generated village on an NVIDIA GeForce RTX 5080 with a Ryzen 7 5800X3D, view distance 832, frame generation off. The view stands still, then flies level over new ground for a minute at 20 blocks a second. Each figure is the median of the rounds flown that evening, usually three or four (0.2.7’s row is a single round), and a round in which shaders were still compiling is left out.

From 0.2.6’s row on, the flights have stepped water on, as those versions ship it; 0.2.3 has no such setting. The NVIDIA driver was 617.14 for the first flights and 621.01 for the last. Each release was flown while it was being prepared, so a row is of its code within a few days of the released files, not of the files themselves. Versions before 0.2.3 were not flown this way, so the table starts there.