Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
So I had been having a similar issue when trying to play Project Cars 2 with in home streaming using an xbox one controller. Through trial and error, I did manage a simple solution that worked for me. Not sure if it will work for you or not, but worth trying if all else fails.
On the HOST computer, plug in an xbox one controller (even though it won't be used). Run Steam in Big Picture Mode.
On the CLIENT computer, you can run Steam in either Big Picture Mode or normal - doesn't seem to matter. Plug in another xbox one controller to the CLIENT machine. Play game. Works for other games too, not just PC2.
Seems the issue is with Steam and the key is having a controller plugged into the HOST machine so the client can be configured properly. A simple fix but it worked - finally.
I started Big Picture mode on HOST, plugged in the controller.
Then started the stream on CLIENT.
After the game has started I plugged off the controller from the HOST and plugged it into CLIENT.
It works for me.
Posting this because i just spent the last 4 hours trying to solve my issues with the Xbox controller not passing inputs through in home streaming to my game.
The issue:
certain games would work perfectly with the Xbox controller (like Rocket League, Divinity Original Sin and Overcooked) and others simply wouldn't work at all (like Cuphead and Moon hunters)
even though they have full controller support
I knew it wasn't the controller on the client PC, as it was recognized by BPM and would even pull up the steam overlay once in game, It seemed like the input wasn't being passed to the game program. Keyboard Input worked wonderfully all the time.
I figured out purely by accident (in frustration I was mashing buttons on my controller) that the window name (on the Host PC) was labeled as a MSI afterburner window, and that didn't make any sense to me.
So I tried disabling MSI afterburner and the RivaTuner Statistics Server on the Host PC.
BOOM! problem gone - but I like using Riva and MSI for temp monitoring, and FPS counter.
The conflict reminded me of a similar issue I had with CS:GO and Rocket League in regards to a conflict between Riva and the steam overlay, ultimately I changed how Riva hooked into the games themselves.
This got the gears turning, I did some digging and found the encoding for in home streaming is done by the "Steam Client Bootstrapper"
This is essentially part of Steam.exe. So I simply added Steam.exe to the application profile properties and set the application detection level to none.
now all my Xbox 360 and Xbox one controllers work with all the previously afflicted games.
No silly plugging in and unplugging of controllers, as suggested by others.
Hope this helps someone save some time.
TLDR; - I use RivaTuner Statistics Server, I added steam.exe to the list of custom profiles, and disabled application detection on the Host PC.
Now all my games work wonderfully.
I'm thinking that when you plugged the steam controller in the client automatically switched all of the settings to it and turned off / made a mess (possibly deleted?) the xbox controller settings.
I did. I tried every mentioned solution in this thread.
Unchecking all the controller boxes, checking the ones for the 360 controller/ generic controller on both the client and host pc, and enabling controller settings per game too, and in In all possible combinations.
Making sure I was not using beta steam / using beta steam
As I said I spent 4 hours on this, what worked was turning off application detection in rivatuner for steam.