FX P3: safety — non-fatal user content, device-lost quarantine, safe start, VRAM cap #546
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#546
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?
Part of epic #542 (from #186). Design + code citations are in the epic; read it first.
Size: M (2-4 d)
Contain broken or hostile effects. Must land before FX is user-visible.
Scope
VK_CHECKon user-content paths:gVkFatalHandlerturns failures into LL_ERRS. Shader-module / pipeline / allocation failure disables that effect with a message instead.robustBufferAccess2/robustImageAccess2on FX pipelines where supported.llvrambudgetvk(refuse to load beyond it; soft pressure disables expensive effects temporarily, per our pressure-degrade rules).vk_device_lost_handler/gpuLostWriteMarker(llappviewer.cpp:4043, :3823) to record "FX active + last FX breadcrumb". The next launch starts with FX off plus a notice naming the effect, and the effect is quarantined until the user re-enables it.--no-fxlaunch switch / setting.VK_LAYER_reshade*) or vkBasalt (ENABLE_VKBASALT).Done when
RenderVKDebugSimulateDeviceLostwith FX on leads to: next launch FX off, culprit named, quarantine persisted.Done: FX P3 (safety: device-lost quarantine, provisional effects, --no-fx, VRAM pressure,
e0329da854). Shipped in 1.2.0 Beta 4/5 (ReShade effects + cel shading).