Formal Performance Regression Complaint: Rendering and Draw Distance #2119
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#2119
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?
The idea
Formal Performance Regression Complaint: Rendering and Draw Distance
To the Longshot Development Team,
I am writing to express serious dissatisfaction with the current state of rendering performance and the apparent direction of recent development.
The draw distance has been reduced, distant grass is no longer being rendered properly, and performance in Hyrule Field has dropped to approximately half the previous frame rate.
Let that sink in: the game is rendering less of the environment, drawing less distant grass, and somehow performing significantly worse.
This is the exact opposite of what a rendering optimization should accomplish.
Reducing draw distance is supposed to reduce rendering workload. If the result is substantially worse frame rates alongside an obvious loss of visual detail, then something is fundamentally wrong with the rendering pipeline or the decisions being made around it.
This is not a minor visual discrepancy. Hyrule Field is a large open environment where draw distance, vegetation rendering, and consistent frame pacing are essential to the experience.
The team needs to investigate:
I would also strongly recommend comparing the current implementation against Hookshot, ReLink 7.9.2, and ReKarinA 1.2.6. These alternatives have demonstrated less stuttering and higher frame rates. There is clearly value in examining what they are doing differently.
A Serious Concern About Development Practices
At this point, the issue is bigger than one rendering bug. The repeated appearance of performance regressions raises serious questions about testing, benchmarking, and technical decision-making.
Users should not have to sacrifice visual quality and performance with every supposed improvement. Nor should users be expected to diagnose basic rendering regressions that should have been caught during development.
Respectfully, the current results give the impression that changes are being implemented without a sufficient understanding of their consequences or adequate testing on real hardware.
Reducing draw distance while simultaneously cutting frame rates in half is not optimization. It is a regression.
Please stop treating intended improvements as proof of actual improvements. Audit the rendering pipeline, establish reliable performance benchmarks, and verify changes against previous builds before asking users to accept them.
The project deserves competent performance engineering, and its users deserve a product that actually gets better rather than progressively worse.
Sincerely,
A concerned user
Anything else
No response
Possibly related, for context: