xbox rog ally x running officaly steam os graphical bugs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- linux
- Domain
- desktop
Research direction
The report is a graphical artifacting bug on SteamOS with a Z2 Extreme APU, with the attached savagewind.log and a video as the only evidence; the issue does not name a file or function. Start by reading the attached log for GPU or renderer errors and checking whether the artifacts follow the FSR and async settings it lists. Done means the cause is identified or the report is narrowed to a reproducible case, which likely needs the same handheld hardware.
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
xbox rog ally x z2 extreme steam os official
Where in the game
everywhere
What happened, and how to make it happen again
weird graphical artificing happening when roaming around I'm using a xbox rog ally x running a z2 extreme apu running on official steam os
https://github.com/user-attachments/assets/26c79c6a-6605-47a2-b2bb-1126564b3235
Settings
60 fps high shadows fsr on async is on at 1080p
savagewind.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
-
aspect ratio 16:10Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Revivedx/SavageWindRecomp#402 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Revivedx/SavageWindRecomp#449 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 18/100
Revivedx/SavageWindRecomp#448 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Revivedx/SavageWindRecomp#447 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Revivedx/SavageWindRecomp#446 ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/open-bastion#425 ·
Maintainers usually reply within 1 day
-
question
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
follow-up Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
moonbitlang/async#713 ·
Maintainers usually reply within 1 day
-
examples/dnsdoctor: cleanup.sh stops at the first missing piece of a setup.sh that did not finishOpenseverity: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
luainkernel/lunatik#2263 ·
Maintainers usually reply within 1 day