Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to set minimum fps, fps too low on desktop #249

Closed
hello-world-321 opened this issue Jan 20, 2025 · 4 comments
Closed

Option to set minimum fps, fps too low on desktop #249

hello-world-321 opened this issue Jan 20, 2025 · 4 comments

Comments

@hello-world-321
Copy link

Currently, when nothing is moving on the desktop, the fps drops to 10. Upon moving the mouse it takes some time for fps to gradually increase to 60 (sometimes it doesn't). Mouse movement and animation seem choppy during this time.

The following commits tried to address this issue to some extent. But the minimum fps is still 21.40 with min_fps_factor=3
LizardByte/Sunshine#754
LizardByte/Sunshine#1043

An option to set minimum fps to 60 or allowing fps frame streaming will prevent lag when streaming desktop. This is also one of the most requested features for sunshine.

@ClassicOldSong
Copy link
Owner

I never had latency issues with still images. The FPS lowers for saving bandwidth but as soon as I move the mouse it's totally smooth.

Maybe you need to disable the stats and try again to see if you really feel slow when mouse starts moving.

It's not possible to set minimum fps since Windows only report at this rate when there's only a still image.

@hello-world-321
Copy link
Author

hello-world-321 commented Jan 20, 2025

I never had latency issues with still images. The FPS lowers for saving bandwidth but as soon as I move the mouse it's totally smooth.

Maybe you need to disable the stats and try again to see if you really feel slow when mouse starts moving.

Without the overlay, mouse movement seems slow. It speeds up after sometimes.

It's not possible to set minimum fps since Windows only report at this rate when there's only a still image.

Can we uncap min fps in above patch (allow more than 3) ?

@ClassicOldSong
Copy link
Owner

Can you share your computer specs? I need some more information about how the issue happened

@hello-world-321
Copy link
Author

Can you share your computer specs? I need some more information about how the issue happened

I tried with a different client. It seems to be a client issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants