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
It is not just PCSX2 streaming it is streaming all types of games instead of just emulators. Steam purchased games such as Metal Gear Solid V: The Phantom Pain as well as Lego Star Wars: The Force Awakens are affected.
VALVE Customer support has been happy to help users of DS4 controllers resolver thier issues; however, they have remained mute on this issue.
Valve CS, please respond about pending resolution.
After digging up every thread on broken XBOX360 controller IHS issue, I found a solution that works for me. Caveats: My IHS host is Win10.
1. Do fresh instal of latest Win 10 beta client.
2. Uncheck every box in controller config panel (no XBOX controller configs, etc.)
3. Enable steam overlay on host.
4. Disable MS game bar or whatever the XBOX thing is on Windows 10 Creators Update
5. Restart computer.
This has fixed the issue for both steam link and win 10 to win 10 IHS for me.
For Win 10 to Win 10 IHS, see above for host and streaming client settings.
I hope this helps everyone experiencing the same issue. I tested this on: (1) RetroArch, (2) Lego Star Wars: The Force Awakens, (3) Galak-Z which was not affected by the issue, but I just wanted to check to confirm I didn't break anything else, (4) Metal Gear Solid V: The Phantom Pain.
VALVE Customer Support: Same request as before, please acknowledge this issue and post a response outlining an official solution or pending update. This was a community developed response for what appears to be a long-standing Win 10 Client issue.