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
1) If the controller is plugged into client, its presence is not detected until after Halo has started. This means Halo does not load in that gamepad and cannot detect it.
2) If the controller is plugged into the host first, then transferred to the client, Halo recognizes there is a working gamepad, however it won't work if I then unplug from the host and then connect the xbox controller to the client. I think this is because Halo binds that gamepad to a certain port, and so when the port is changed from the physical usb on the host to the client's emulated controller, it cannot adapt to accept the input from this source.
So, is there a way to make the host computer recognize and register a controller that is plugged into the client, before the game has started for streaming? If there is, I'm pretty certain Halo would detect that controller, because it exists at startup when gamepads are registered in-game.