Low Gpu usage on GTX 1650, causing fps drop and stutter
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- game-dev, performance
Research direction
Start by reviewing the attached savagewind.log and comparing GPU usage and frame timing between Alpha 3 and Alpha 4 on the reported GTX 1650 setup. Check whether the log identifies a bottleneck or relevant subsystem; the report provides no source files or tests to start from. Done means identifying and resolving the cause of the GPU underuse, stuttering, and frame drops.
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
Windows 11 26H2, GTX 1650 4gbytes (dirver 621.14), Intel Core i5 10300H
Where in the game
Great Plateau
What happened, and how to make it happen again
In Alpha 3, the game uses GPU below 50% and ran below 30fps.
In the current version Alpha 4 that I just reinstall, I can finally play at 50-60 fps but there's a lot of fps drop and stuttering through the game, I checked and my game only uses around 30%-60% of my GPU. I think there might be a problem with my GTX 1650.
I tried set up the game in NVIDIA control panel and set the priority of GPU usage on the game, but nothing worked.
Settings
60fps, 1920x1080 exclusive, upscaler off
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
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Revivedx/SavageWindRecomp#530 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Revivedx/SavageWindRecomp#528 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Revivedx/SavageWindRecomp#527 ·
Maintainers usually reply within 1 day
-
RAM usage is highOpenbug needs-info
Difficulty 5/5 Over a week Newbie friendliness 25/100
Revivedx/SavageWindRecomp#525 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Revivedx/SavageWindRecomp#523 ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 10 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/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