Formal Performance Regression Complaint: Rendering and Draw Distance #2119

Open
opened 2026-11-21 20:41:32 +00:00 by bigwiggler Β· 1 comment

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:

  • Why distant grass and vegetation are no longer being rendered.
  • Why draw distance has been reduced.
  • Why performance has deteriorated despite the reduced rendering workload.
  • Whether recent changes to culling, level-of-detail transitions, vegetation instancing, Vulkan synchronization, or GPU workload management are responsible.
  • Why these regressions were not identified before release.

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

### 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: - Why distant grass and vegetation are no longer being rendered. - Why draw distance has been reduced. - Why performance has deteriorated despite the reduced rendering workload. - Whether recent changes to culling, level-of-detail transitions, vegetation instancing, Vulkan synchronization, or GPU workload management are responsible. - Why these regressions were not identified before release. 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_
Member

Possibly related, for context:

  • issue #2111 # Regression Report: Frame-Rate Loss, GPU Compatibility, and Update Workflow (nightly-626 β†’ nightly-695) β€” same broad FPS regression complaint and alternative-fork comparisons
  • issue #950 Idea: More graphics performance and quality-of-life options β€” grass draw-distance quality discussion
  • PR #1382 feat(vk): Grass distance, how far the short grass stays full (Game's by default) β€” merged grass-distance change relevant to vegetation visibility
  • PR #1877 WIP: fix(vk): disable larger grass lists and hold grass distance at the game's reach β€” open investigation of grass draw distance and disappearing patches
Possibly related, for context: - issue #2111 # Regression Report: Frame-Rate Loss, GPU Compatibility, and Update Workflow (nightly-626 β†’ nightly-695) β€” same broad FPS regression complaint and alternative-fork comparisons - issue #950 Idea: More graphics performance and quality-of-life options β€” grass draw-distance quality discussion - PR #1382 feat(vk): Grass distance, how far the short grass stays full (Game's by default) β€” merged grass-distance change relevant to vegetation visibility - PR #1877 WIP: fix(vk): disable larger grass lists and hold grass distance at the game's reach β€” open investigation of grass draw distance and disappearing patches
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#2119
No description provided.