[Bug] Yellow map pins (stamps) are not anchored and move with the screen during panning
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start by tracing the map stamp rendering and coordinate transforms from the map UI entry point; the issue does not name files or tests, so locate those in the repository first. Reproduce by placing a stamp and panning the map, then compare how stamp positions are calculated against the map's world position. Done when stamps stay fixed to their geographic locations while panning.
Written by the indexing model from the issue text.
Description
Before you start
- I'm on the latest release, and the bug still happens there.
- I searched the existing issues and this one isn't reported yet.
Savage Wind version
0.4.1-alpha.4 (latest)
Game version
1.9.0
Your PC
OS: Windows 11 | CPU: 12th Gen Intel(R) Core(TM) i7-12700KF | GPU: AMD Radeon RX 7600 (driver 26.10.1)
Where in the game
Map
What happened, and how to make it happen again
On the Sheikah Slate map, the stamps (yellow pins) placed by the player do not remain fixed at their designated coordinates. When panning the map, the yellow icons appear to be rendered in screen-space rather than world-space. This causes them to "move along" with the camera, completely ignoring their original marked position on the terrain
Steps to Reproduce
-
Load the game and open the map. -
Place a yellow stamp (pin) anywhere on the map. -
Pan the map in any direction (up, down, left, or right). -
Observe that the stamps move with the screen's UI instead of staying attached to the map's geography.
I am not exactly sure what triggered this bug. It happened randomly upon launching the game one time, and the issue persists even after completely closing and reopening the game.
°https://github.com/user-attachments/assets/7027e285-29fd-44dd-8573-8d7c76c19419
Settings
60 FPS, 2560x1080, Borderless fullscreen, Upscaler Off
savagewind.log
savagewind.log
savagewind.prev.log
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Revivedx/SavageWindRecomp
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 44/100
Revivedx/SavageWindRecomp#517 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Revivedx/SavageWindRecomp#516 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Revivedx/SavageWindRecomp#515 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Revivedx/SavageWindRecomp#513 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Revivedx/SavageWindRecomp#510 ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sk3llo/ffmpeg_kit_flutter#176 ·
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relativeOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Nimblesite/osprey#370 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100