Idea: Use a distinct NVIDIA GLCache identity from Hookshot #1289
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1289
Loading…
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?
Reported on Discord
What you want and why
Please can the directory / name or the NVIDIA GLCache for shaders be changed so that it is different to the one that Hookshot uses as they constantly overwrite eachother.
The reporter wants to test both Longshot and Hookshot without their NVIDIA shader-cache entries apparently colliding. The exact mechanism, and whether Longshot can control the driver-managed GLCache identity, are not established.
What is still unknown
Related but different: open Longshot#737 proposes a shared Longshot shader-cache store across game folders; it does not propose changing NVIDIA's driver-managed GLCache identity. Longshot#1156 tracked repeated pipeline loading and increased RAM after clearing NVIDIA's cache; the reporter says this was resolved in Nightly 376.