Test plan: fly across all of Zindra (mainland) at max flight speed -- the region-crossing / streaming / memory endurance test #469

New issue

Open

opened 2026-10-05 22:16:28 +00:00 by sky_line · 1 comment

sky_line commented

2026-10-05 22:16:28 +00:00

Owner

Stress test: fly the full width of Zindra (the Adult mainland continent) at maximum flight speed without stopping.

Per Rye (Alchemy), this is the "your viewer's not shit" test: a viewer that survives it handles sustained region crossings, constant object and texture churn, and memory pressure. Run it before each stable release, and whenever memory, streaming or region code changes.

Setup

Use the build under test, with logs at the default level. Turn on RenderVKVehicleDiag only if investigating.
Before starting, note: draw distance, graphics preset, RAM/VRAM budget settings, GPU, driver, OS and RAM.
Set flight speed to maximum: a flight-assist HUD at max multiplier, or the viewer's own fly-speed option if available. Record the method and the speed used.
Start at one edge of Zindra. Pick a straight route across the continent (west→east or north→south), and note the start and end SLURLs.
Run at least two passes: one at the default draw distance and one at a high draw distance (e.g. 512 m+).

During the flight, record

Stability: no crash, freeze, device lost, or "Low system memory" emergency.
Region crossings: no long stalls, no rubber-banding or teleport-back, and no stuck "waiting for region" or missing neighbours.
Memory: RSS and committed memory (Task Manager / top), VRAM, and the MemTimeline / VKMem / hostmem log lines. Watch for steady growth that doesn't level off (leaks), and check that old regions really release (#433 / #290 hitches).
Streaming: textures and meshes load ahead of you, nothing stays permanently blurry or grey, and no objects are left over from regions you've passed.
Frame rate: typical and minimum FPS, and any hitch over 250 ms with its location (use the VK_HITCH lines).
Rendering: no flicker, missing terrain, black or white objects, or broken water at region edges.

Pass criteria

Completes the full crossing at least twice without crashing.
Memory levels off (no unbounded growth). After landing and idling for 2 minutes, it falls back toward the pre-flight baseline.
No hitch over 1 s, other than at region crossings that also stall in LL's or Firestorm's viewer on the same route (compare if possible).
Textures and meshes recover to full detail within normal time after stopping.

On failure

File a bug with the log, the location (SLURL or nearest region), the time into the flight, settings and hardware. Use Help > Report Bug, which includes memory info automatically.
Link it here.

Results log

Date	Build	Hardware	Draw distance	Result	Notes

**Stress test:** fly the full width of **Zindra** (the Adult mainland continent) at maximum flight speed without stopping. Per Rye (Alchemy), this is the "your viewer's not shit" test: a viewer that survives it handles sustained region crossings, constant object and texture churn, and memory pressure. Run it before each stable release, and whenever memory, streaming or region code changes. ## Setup - Use the build under test, with logs at the default level. Turn on `RenderVKVehicleDiag` only if investigating. - Before starting, note: draw distance, graphics preset, RAM/VRAM budget settings, GPU, driver, OS and RAM. - Set flight speed to maximum: a flight-assist HUD at max multiplier, or the viewer's own fly-speed option if available. Record the method and the speed used. - Start at one edge of Zindra. Pick a straight route across the continent (west→east or north→south), and note the start and end SLURLs. - Run at least two passes: one at the **default draw distance** and one at a **high draw distance** (e.g. 512 m+). ## During the flight, record - **Stability:** no crash, freeze, device lost, or "Low system memory" emergency. - **Region crossings:** no long stalls, no rubber-banding or teleport-back, and no stuck "waiting for region" or missing neighbours. - **Memory:** RSS and committed memory (Task Manager / `top`), VRAM, and the `MemTimeline` / `VKMem` / `hostmem` log lines. Watch for steady growth that doesn't level off (leaks), and check that old regions really release (#433 / #290 hitches). - **Streaming:** textures and meshes load ahead of you, nothing stays permanently blurry or grey, and no objects are left over from regions you've passed. - **Frame rate:** typical and minimum FPS, and any hitch over 250 ms with its location (use the `VK_HITCH` lines). - **Rendering:** no flicker, missing terrain, black or white objects, or broken water at region edges. ## Pass criteria - Completes the full crossing at least twice without crashing. - Memory levels off (no unbounded growth). After landing and idling for 2 minutes, it falls back toward the pre-flight baseline. - No hitch over 1 s, other than at region crossings that also stall in LL's or Firestorm's viewer on the same route (compare if possible). - Textures and meshes recover to full detail within normal time after stopping. ## On failure - File a bug with the log, the location (SLURL or nearest region), the time into the flight, settings and hardware. Use Help > Report Bug, which includes memory info automatically. - Link it here. ## Results log | Date | Build | Hardware | Draw distance | Result | Notes | |---|---|---|---|---|---| | | | | | | |

sky_line added the

labels

2026-10-05 22:16:28 +00:00

sky_line referenced this issue

2026-10-06 09:30:24 +00:00

Octree removal 5: replace object-cache interest management (VOCache partition cull) #479

sky_line added this to the Slipstream project

2026-10-06 15:04:14 +00:00

sky_line referenced this issue

2026-10-07 01:00:55 +00:00

Octree removal 5: replace object-cache interest management (VOCache partition cull) #479

sky_line added the

status

testing

label

2026-10-09 08:46:39 +00:00

sky_line commented

2026-10-10 05:48:24 +00:00

Author

Owner

Run 2026-10-09 on 1.2.0 Beta 7 (1.2.0.7): full max-settings flight across Zindra (the whole continent) with no issues -- no disconnects (network draw distance + 25-region ring + stall guard), memory stayed bounded (~11 GB peak, down from 57.9 GB before the fetch / worker bounds). Keeping this ticket open as a repeatable pre-release test.

sky_line referenced this issue

2026-10-11 13:25:12 +00:00

[viewer] Disconnecting on Mainland #570

sky_line removed the

status

testing

label

2026-10-18 22:22:35 +00:00