Hint when a manual video-memory cap is what keeps detail low (subtle, not a popup) #510
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#510
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From #508: a user set Max video memory (
RenderMaxVideoMemoryMB) to 2048 MB on a 6 GB card. Auto would have given about 4.5 GB. The VRAM ladder hit 39/39 within a minute (probes, then draw distance, then render scale 50%, then lower LOD), and they reported it as "objects not reaching high LOD". Nothing told them their own cap was the cause.The owner doesn't want extra popups. Prefer subtle, in-context hints:
Related: the pressure ladder stays soft and automatic. This is only about explaining a self-imposed limit.