Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
Right click Image File Execution Options go to new, then press key:
Name it "Realm.exe"
Right Realm.exe go to new, then press key:
Name it "PerfOptions"
Right click PerfOptions go to new, then press DWORD (32-bit):
Name it "CpuPriorityClass"
Double click CpuPriorityClass, set value to 3 (This is for priority to be set to high)
I can already set the priority of the OBS below normal or above normal if i want to but the game still uses all the cores.
If you're confused, let me give you an example.
I usually assign the game 6 threads and the rest to OBS. That way, the game doesn't interfere with OBS and vice versa.
Now what's the problem? I can already set the number of cores to be used by OBS but i cannot set the cores to be used by the game, so it uses the cores that OBS is currently encoding at.
Not to mention the microstutters.
Is there a similar registry hack for the affinity rather than the priority?
Again, thank you for your time.