-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Assignment Ranges not functioning properly #43
Comments
I'll try to get this added this weekend. Should be a simple enough fix to ignore anything that already has a custom allocation. |
I do not know the backend but I think it may be deeper than that. It seems that the stream process (OBS) is not even being assigned to its own cores. Perhaps it's not fully reading the user provided value i.e. just 9 instead of 9-16 |
On further testing, it seems its only bugged for Stream process if i use the dash |
I'll take a look in to this. |
I have a 8C16T CPU and I intend to do:
6 threads for the game
2 threads for everything else
8 threads for OBS encoding
When I do these settings:
Work/Play:
Custom, 1-6
Stream:
Last Half
Assign Other Processes:
Remaining Cores
Everything works fine, game is assigned first 6 cores and OBS is assigned last 8 cores.
However, if I choose to do this instead which should mean the same thing:
Work/Play:
Custom, 1-6
Stream:
Custom, 9-16
Assign Other Processes:
Remaining Cores
Other processes:
Game:
OBS:
The text was updated successfully, but these errors were encountered: