[viewer] Massive performance hitch when running two Slipstream viewers at the same time #403

Closed
opened 2026-10-05 01:32:19 +00:00 by slipstream-reports · 5 comments
Collaborator

Source: in-viewer report (Help > Report Bug)

Reporter (avatar name as given; not verified):

(not given)

System

Version: 1.0.0.8
Channel: Slipstream Beta
OS: Microsoft Windows 11 64-bit (Build 22621.4317)
CPU: Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (2904.01 MHz)
Memory: 16314 MB
GPU: AMD Radeon RX 7600
GPU driver: 32.0.31041.1004
Vulkan: 1.4.349; ray tracing: enabled
Window: 1618x1000
Grid: Second Life Main Grid (Agni)
Region: Baltimare
Settings:
  AlchemyRenderTonemapType = 0
  RenderDeferredSSAO = 1
  RenderDepthOfField = 0
  RenderFPSLimit = 0
  RenderFSAAType = 2
  RenderFarClip = 128
  RenderHiDPI = 0
  RenderMaxTextureResolution = 2048
  RenderMirrors = 0
  RenderQualityPerformance = 4
  RenderReflectionProbeDetail = 1
  RenderReflectionProbeLevel = 2
  RenderScreenSpaceReflections = 0
  RenderShadowDetail = 2
  RenderTransparentWater = 1
  RenderVKAOStandard = 1
  RenderVKAlphaShadingRate = 0
  RenderVKGodRays = 0
  RenderVKOpaqueShadingRate = 0
  RenderVKProjectorShadows = 1
  RenderVKRayTracing = 1
  RenderVKRenderScale = 1
  RenderVKShadowResolution = 1024
  RenderVKSunShadows = 1
  RenderVKTAA = 0
  RenderVKUpscaler = 0
  RenderVSyncEnable = 1
  RenderVolumeLODFactor = 3
  UIScaleFactor = 1

Description

When running two Slipstream viewers at the same time, performance was adequate at first. But after traveling around a somewhat populated region for a bit, the performance took a massive hit. The viewer would freeze for a few seconds, then unfreeze for just a fraction of a second, and continue this behavior until I closed the viewer.

Steps to reproduce

not given


Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.

**Source:** in-viewer report (Help > Report Bug) **Reporter** (avatar name as given; not verified): ~~~text (not given) ~~~ ### System ~~~text Version: 1.0.0.8 Channel: Slipstream Beta OS: Microsoft Windows 11 64-bit (Build 22621.4317) CPU: Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (2904.01 MHz) Memory: 16314 MB GPU: AMD Radeon RX 7600 GPU driver: 32.0.31041.1004 Vulkan: 1.4.349; ray tracing: enabled Window: 1618x1000 Grid: Second Life Main Grid (Agni) Region: Baltimare Settings: AlchemyRenderTonemapType = 0 RenderDeferredSSAO = 1 RenderDepthOfField = 0 RenderFPSLimit = 0 RenderFSAAType = 2 RenderFarClip = 128 RenderHiDPI = 0 RenderMaxTextureResolution = 2048 RenderMirrors = 0 RenderQualityPerformance = 4 RenderReflectionProbeDetail = 1 RenderReflectionProbeLevel = 2 RenderScreenSpaceReflections = 0 RenderShadowDetail = 2 RenderTransparentWater = 1 RenderVKAOStandard = 1 RenderVKAlphaShadingRate = 0 RenderVKGodRays = 0 RenderVKOpaqueShadingRate = 0 RenderVKProjectorShadows = 1 RenderVKRayTracing = 1 RenderVKRenderScale = 1 RenderVKShadowResolution = 1024 RenderVKSunShadows = 1 RenderVKTAA = 0 RenderVKUpscaler = 0 RenderVSyncEnable = 1 RenderVolumeLODFactor = 3 UIScaleFactor = 1 ~~~ ### Description ~~~text When running two Slipstream viewers at the same time, performance was adequate at first. But after traveling around a somewhat populated region for a bit, the performance took a massive hit. The viewer would freeze for a few seconds, then unfreeze for just a fraction of a second, and continue this behavior until I closed the viewer. ~~~ ### Steps to reproduce _not given_ --- <sub>Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.</sub>
Owner

Part of #405 (RAM/VRAM management epic).

Part of #405 (RAM/VRAM management epic).
Owner

Possibly the same host-memory exhaustion as #458 (AMD, Windows; a 16 GB machine running two viewers). See the triage there. The fix in progress should help; please re-test on the next beta.

Possibly the same host-memory exhaustion as #458 (AMD, Windows; a 16 GB machine running two viewers). See the triage there. The fix in progress should help; please re-test on the next beta.
Owner

Likely related to #462 (AMD on Windows, high memory while shaders compile). Fixed in 1.1.0 Beta 3; please retest on it.

Likely related to #462 (AMD on Windows, high memory while shaders compile). Fixed in **1.1.0 Beta 3**; please retest on it.

Tested Beta 1.1.0.3 by logging in a busy sim with two accounts. Massive slow downs persisted. Viewer logs sent through in-game IM.

Tested **Beta 1.1.0.3** by logging in a busy sim with two accounts. Massive slow downs persisted. Viewer logs sent through in-game IM.
sky_line added this to the Slipstream project 2026-10-06 15:04:14 +00:00

Tested again on Beta 1.1.0.8, with the Maximum video memory option under Advanced Graphics Preferences set to 3 GB on both viewers, as per instructed given my 8 GB GPU. Was able to go through the same sim used in both tests, but this time without the massive slowdowns previously reported. After going around the sim, I reset the Maximum video memory option back to Auto in both viewers, and sure enough the hitches came back.

Tested again on **Beta 1.1.0.8**, with the _Maximum video memory_ option under _Advanced Graphics Preferences_ set to **3 GB** on both viewers, as per instructed given my 8 GB GPU. Was able to go through the same sim used in both tests, but this time without the massive slowdowns previously reported. After going around the sim, I reset the _Maximum video memory_ option back to **Auto** in both viewers, and sure enough the hitches came back.
sky_line 2026-10-09 04:37:34 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
sky_line/Slipstream#403
No description provided.