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://steamcommunity.com/app/275850/discussions/0/6516193260168028342/
Controllers are best set up through Steam Big Picture Mode which seems more stable. There you can set up the General settings to globally manage a controller, even calibrating them. On a per game basis you can then manage your game's official download and customise them. If configuration has been updated following a major game update then download the Ofiicial Setup again from Hello Games for your favoured controller (generic or proprietory). That will replace any older setup that may have broken because of changes. Use the new official setups to start a new custom setup for your style of play if preferred. Save your setup or share it for others.
I'm using an m1 MacBook with a stadia Bluetooth unlocked controller.
https://hellogames.zendesk.com/hc/en-us/articles/360013870118-I-have-an-issue-to-report-in-NMS
I wonder if bluetooth is an issue? Or would it be the stadia controller software interfering and causing conflicts? I have removed Logitech's third party controller software as I did discover it would cause conflicts with the steam configuration, both trying to drive the controller. Since removing the Logitech driver software, the Steam configuration software recognises it correctly. Also I have far more superior config options today using steam configuration than I would with the original driver. Definitely check no other controller driver software is in use except maybe the very basic OS software that may recognise plugged in devices to your Mac. Any underlying OS device software is best rest to defaults while troubleshooting conflicts.
On Windows 11 the operating system by default recognises any controller connected as a device and provides a pop up UI to calibrate a controller connected to PC. If ever there is a conflict, make sure Steam is not in use and make sure third party software is disabled or removed. Then first test and make sure the controller OS device defaults are reset and buttons and joysticks are calibrated correctly using the OS driver UI. Then set up the controller with Steam knowing the underlying OS is at default and calibrated. Steam calibration is then rarely needed. Without the third party drivers potentially causing conflict Steam config should function as expected. If Valves Steam configuration software does not recognise the Stadia controller Valve needs to be notified. Possibly Hello Games might be notified too on their website help line. In game Hello Game have an option to set up controllers using Steam so they rely on Valve to provide software for various controller types.
I run it on my MacBook M1 Pro, macOS Ventura 13.5.2
I tried multiple things:
- using the controller in wired mode
- using community layouts from steam
- enable steam input
also I could not find the official recommended controller layout that is recommended here:
https://hellogames.zendesk.com/hc/en-us/articles/360003976558-Controller-input-not-working-correctly-Steam-
I opened up a ticket with them, hope they come back to me or include a fix in future patches.
Did anyone figure out a solution yet? 😊
Why not simply get a proper gamepad like the PS5 dualsense?
Or literally any other gamepad i'm sure is better. On used market u get them already for like 20 bucks anyway....
They are great controllers, but obiously NMS will not prioritise the integration of stadia controllers since it is very much an edge case..
Also it is ridiculous to try to call this an "edge case" for why it's not supported, or to suggest that getting a different controller should be the solution. The communication protocol is effectively standardized, for one -- so it shouldn't matter whether the "controller" is a PS5 controller, a Stadia Controller, or hell, the Donkey Kong Bongos -- it all appears as a generic input device for developers. But it's even easier than that here -- the "Steam Input" API already does all this for the developer, and negotiates the controller mapping *for them*.
If they were using the API correctly, it would 'just work' -- which is how other indy developer game companies are handling this perfectly fine. Games developed by smaller teams already get this right, which allows Stadia controllers to work -- it just seems that Hello Games isn't one of them -- which is a shame. Hopefully they figure it out correctly for their _next_ announced game.
Not all controllers utilize the Steam API the same, and that is why some controllers work better than others in a LOT of games, not just NMS. I'm sure there are plenty of people in here that play other games besides NMS that can attest to this.
HG and plenty of other people do indeed simply utilize the Steam API services (on steam versions anyway) to negotiate commands. Therefore, your argument belies itself on why there is a problem.
All you have to do is google 'stadia controller sont work on mac with steam', and watch the pages upon pages of problems go by.
Also, if it were a NMS problem with the Steam API, then why would other controllers work flawlessly? Exactly, the stadia has it's own wonky comms that isn't designed to work out of the box with Steam. That's not HG's fault. Steam has been fighting with controller support forever. That's why there are so many options of different kinds to force different modes, etc.