Skip to content

feat: add a set-fps-limit control command#1969

Open
farnoy wants to merge 1 commit into
flightlessmango:masterfrom
farnoy:set-fps-limit
Open

feat: add a set-fps-limit control command#1969
farnoy wants to merge 1 commit into
flightlessmango:masterfrom
farnoy:set-fps-limit

Conversation

@farnoy

@farnoy farnoy commented Feb 19, 2026

Copy link
Copy Markdown

Preserve control socket if the reloaded config does not change its path. This lets clients keep the connection across preset changes or config reloads.

Update the fps_limiter to directly store the current target, supporting runtime values.

I want to upstream this for use in mangochill

Preserve control socket if the reloaded config does not change its
path. This lets clients keep the connection across preset changes or
config reloads.

Update the fps_limiter to directly store the current target, supporting
runtime values.
@flightlessmango

Copy link
Copy Markdown
Owner

The main reason I’m hesitant to merge this right now is that we’re in the middle of a fairly major architectural shift toward a client/server model, and this change likely wouldn’t be trivially portable to that design.

One option might be to target this toward the server2 branch instead, where most of that work is happening, but I’d like to hear your thoughts first.

If it helps, I’m also happy to talk through how this could fit into the new design, either here in the PR or on Discord, whichever you prefer.

@farnoy

farnoy commented Feb 20, 2026

Copy link
Copy Markdown
Author

I can rework/retarget the change if needed. What's the timeline on server2 and are there any docs on what's changing?

I could just wait until you're ready to promote server2 as 0.9 or the new mainline.

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

Successfully merging this pull request may close these issues.

2 participants