LizardByte / LizardByte/Sunshine

After updating to the new version of Sunshine, the capture frame rate is significantly lower than the in-game frame rate.

Open
#5,147 11 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
41.3k
Forks
2.1k
Avg merge
23h 47m
Merged PRs (30d)
124

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your issue described in the documentation?

- [x] I have read the documentation

### Is your issue present in the latest beta/pre-release?

None

### Describe the Bug

In-Game Frame Rate and Captured Frame Rate

Image

However, when using UFOTest, the captured frame rate is normal.

Image

I just updated to the latest Release version(v2026.516.143833); I didn't encounter this issue when I was using the previous Release version(v2025.924.154138).

My Hardware Information:
CPU: AMD 9800x3D
GPU: Nvidia RTX 5080

### Expected Behavior

Match the game's refresh rate.

### Additional Context

_No response_

### Host Operating System

Windows

### Operating System Version

Windows 11 25H2

### Architecture

amd64/x86_64

### Package

Windows - msi installer (recommended)

### GPU Type

NVIDIA

### GPU Model

RTX 5080

### GPU Driver/Mesa Version

596.49

### Capture Method

None

### Apps

```json

```

### Log output

```shell

```

### Online logs

_No response_

Contributor guide

Open the contributing guide

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.

Research direction

No source file, test, or capture entry point is named in the report. First reproduce on Windows 11 with the stated Sunshine versions, hardware, and driver, comparing in-game and captured frame rates; the empty capture-method and log fields need filling in. Done means the regression is reproducible and the captured rate matches the game's refresh rate or the cause is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.