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
https://gtm.steamproxy.vip/app/353380/discussions/
aa should have no effect on how the frames are processed and passed to the remote play client
mismatched res encode/decode settings can
with an nvidia gpu, use nvfbc to capture
and make sure the host and client res are the same
if the client res is higher than host, you can add it to the host in gpu control panel
and force gpu scaling so the host will always display an image
then tick 'change res to match client'
The steamlink video player is constructed inside a hardware accelerated Qt5 frame that flips DXVA2 video into an OpenGL canvas using Interop extensions, MSAA and FXAA can corrupt the final output by modifying the properties of the canvas prior to presenting the decoded image into the canvas for final rendering on screen.
Thanks for the steam link forum link though.