Rock edges disappear when Draw Distance is set to High

Open
#384 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, wasm

Research direction

The report is a rendering bug where rock edges vanish only at the High Draw Distance setting, with Medium and Original correct. The payload names no source files or tests, so start by finding where the Draw Distance option feeds into the renderer's culling or level-of-detail path. Done means the rock geometry renders the same at High as at Medium, confirmed with the attached reproduction video.

Written by the indexing model from the issue text.

Description

bug
Before you start
Savage Wind version

0.4.1-alpha.4 (latest)

Game version

1.9.0

Your PC

OS: Windows 11 26H2 NVIDIA Driver: 621.01 CPU: AMD Ryzen 7 9800X3D GPU: NVIDIA GeForce RTX 5070 Ti RAM: 32 GB DDR5 6000 MHz

Where in the game

Gerudo Mountain

What happened, and how to make it happen again

Description

When Draw Distance is set to High, parts of a rock's edges disappear or become invisible.

Switching Draw Distance to Medium or Original restores the missing geometry.

Steps to Reproduce

Set Draw Distance to High.

Observe the edges of the affected rock.

Change Draw Distance to Medium or Original.

The missing edges become visible again.

Expected Behavior

Rock geometry should remain correctly rendered regardless of the Draw Distance setting.

Actual Behavior

Parts of the rock's geometry disappear when Draw Distance is set to High, while Medium and Original render correctly.

PC Specifications

CPU: AMD Ryzen 7 9800X3D

GPU: NVIDIA GeForce RTX 5070 Ti

RAM: 32 GB DDR5 6000 MHz

Motherboard: ASUS TUF Gaming X670E-PLUS

OS: Windows 11 26H2

NVIDIA Driver: 621.01

Video Evidence

A short video demonstrating the issue and comparing High with Medium/Original Draw Distance settings is attached.

Settings

120 Fps

savagewind.log

savagewind.log

https://github.com/user-attachments/assets/1089d328-53d4-40b1-b092-49c672d5b3be

Before sending
  • This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
Dominant language
C
Stars
811
Forks
37
Avg merge
17m
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Revivedx/SavageWindRecomp

All issues in Revivedx/SavageWindRecomp

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.