[viewer] Weird apha glitching #717
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#717
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?
Source: in-viewer report (Help > Report Bug)
Reporter (avatar name as given; not verified):
System
Description
Steps to reproduce
Log excerpt
Full scrubbed excerpt: slipstream-log-excerpt.txt
Last 40 lines
Screenshot
Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.
Being investigated.
Okay to add to this, changing outfits and rewearing it reactivates the glitch.
Hardening pushed to main: alpha analysis re-arms after an RGB decode, and a decisive result survives a newer decode. A BOMAlpha log line now records the alpha decision for BOM faces. Needs a retest by the reporter.
Issue still persistent on 1.3.0.7beta (right root is blending, left is masking, no additional mesh layers attached | See first two images)
Removing alphas and readding them only seems to fix the masked foot visually. (Last image)
I am unable to replicate this issue in beta10!
Fixed in Slipstream 1.3.0 (stable): https://git.slipstreamviewer.org/sky_line/Slipstream/releases/tag/v1.3.0
If you still see this on 1.3.0, reply here and we'll reopen it.