Performance or graphical issues on older GPUs/iGPUs? Please attach your log here

Open
  • Is something wrong?
#332 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
game-dev, performance

Research direction

This is a collection thread, not a code change: no file or test is named for a patch. To help, reproduce on older hardware, attach savagewind.log from ~/.local/share/savagewind/ (or next to savagewind.exe on Windows), and run the in-game report command to paste hardware and settings. For slowdowns, add a run with SAVAGEWIND_VK_PROF=2 set. Done means a comment with the log and report attached.

Written by the indexing model from the issue text.

Description

help wanted top priority

Alpha 5 is the "potato PC" update. It brings options below console quality (lower internal resolution, lighter shadows, shorter draw distance and more), support for older GPUs and integrated graphics, and a Vulkan 1.2 path where we can. To aim it at the hardware you actually have, we need reports from it.

Please comment here if Savage Wind has any of these problems on your older GPU or integrated graphics (Intel UHD / Iris, AMD Vega / Radeon iGPUs, GTX 900 / 1000, RX 400 / 500 and the like):

  • Performance: low fps, stutter or long hitches.
  • Graphics: missing or wrong textures, black or flickering areas, wrong colours, broken shadows, water or effects, corrupted geometry.
  • It doesn't start because your GPU only has Vulkan 1.2.

Include:

  • savagewind.log of that run, attached (drag the file into the comment). On Windows it is next to savagewind.exe; on Linux, in ~/.local/share/savagewind/. It already names your GPU, driver and settings.
  • Your CPU, GPU and RAM, and for a laptop, whether it was plugged in.
  • Where and how it happens: the place, the resolution and the fps you see (the performance overlay shows them). In game, the console (F12 or the key left of 1) has a report command. It copies your version, hardware, settings and exact place to the clipboard: paste it here.
  • For graphical issues, a screenshot or a short video, and whether it happens everywhere or only in some places.
  • Optional, very useful for performance: one run started with SAVAGEWIND_VK_PROF=2. On Windows, open a command prompt in the Savage Wind folder, run set SAVAGEWIND_VK_PROF=2, then savagewind.exe. Play a minute where it's slow and attach that log.

Use the latest release (Alpha 4.1) and game version 1.9.0. Crashes and other bugs still go in their own issue through the bug report form.

Thanks for helping us make it playable everywhere!

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.