You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As of CP2077 Update 2.2, child processes spawned by the base Cyberpunk EXE are no longer reniced. In my GameMode settings, the renice value is set to 10, and previously GameMode would properly renice the base process and all child processes to -10, but now only the base process is reniced.
To Reproduce
Steps used to reproduce the behavior:
Have Cyberpunk 2077 (Update 2.2)
Ensure GameMode is set to renice to a non-default value (e.g. -10)
Run a system monitor application (e.g. htop)
Run Cyberpunk 2077
Observe the system monitor and see child processes are not reniced, except one (which is probably the base process)
Expected behavior
All child processes are reniced to the level set in the GameMode settings
System Info (please complete the following information):
Arch Linux
GameMode v1.8.2
Additional context
I understand if this is not a bug on your side, since it was introduced with a Cyberpunk update. Cyberpunk still runs perfectly fine, so it's not urgent. However, I thought I would bring this behavior to your attention.
The text was updated successfully, but these errors were encountered:
Describe the bug
As of CP2077 Update 2.2, child processes spawned by the base Cyberpunk EXE are no longer reniced. In my GameMode settings, the renice value is set to 10, and previously GameMode would properly renice the base process and all child processes to -10, but now only the base process is reniced.
To Reproduce
Steps used to reproduce the behavior:
Expected behavior
All child processes are reniced to the level set in the GameMode settings
System Info (please complete the following information):
Additional context
I understand if this is not a bug on your side, since it was introduced with a Cyberpunk update. Cyberpunk still runs perfectly fine, so it's not urgent. However, I thought I would bring this behavior to your attention.
The text was updated successfully, but these errors were encountered: