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
Please make your config available to the community, OP.
Yeah, I figured that out aswell in the meantime. Thing is, they're both labelled Director's Cut :P
Yup, but did you get the real Director's Cut to work with the steam controller?
Not sure which is which. One worked, the other didn't :/
The original Wasteland 2 does not say Director's Cut on the title screen. That one, the steam controller works fine, but I stopped playing it once I found out I was missing out on all the goodies that the Director's Cut comes with . . . Guess I'll have to wait.
Pfff, yeah. That's a dilemma. I thought the one that worked was the Director's Cut.
Sorry for my english.
I just got a Steam Controller a few days ago and its growing on me pretty fast. Loving it more and more as the days go on. Anyway I have Wasteland 2: DC and wanted to use the Steam Controller with it. I ended up making a custom profile, but failed to realize the game had native support for the Steam Controller.
I went through the same song and dance that you guys did; fired up the game, went into option, went to place to change the control input, selected Steam Controller, pushed A, and nothing. Like a moron, I did it like 20 times only to have the same results lol. I combed the discussions and forums (this thread included) and no one could seem to get it working. We were all having the same results.
Well, I'm happy to report, that I got the Steam Controller working natively with Wasteland 2: DC, by selecting it in the options, and pressing A. Here's what I did and I sincerely hope this helps someone out as I about drove myself insane:
1. Crank up Wasteland 2. It doesn't matter how you do it, Steam Link, Big Picture, Small Picture whatever. Just start up the game.
2. When you get to the title screen go ahead and fire up the options screen.
3. If you're using the Steam Controller, drop to the configuration page where you load in your profile.
4. Export your profile and save it so you can load it back in, just in case this doesn't work for you. or you hate it.**THIS IS A VERY IMPORTANT STEP. SAVE YOUR CONFIG**
5. Go back to the screen where you can browse profiles and configs, this time select TEMPLATES.
6. I selected the Template for Gamepad with Camera controls. Apply the template.
7. Check the template and make sure the buttons (A,B,X,Y) are mapped to those buttons. Basically you want the buttons and triggers pointed to their native mappings and not the custom mappings. **AGAIN, KEY STEP. THE ROOT OF THE PROBLEM FOR EVERYONE IS CUSTOM MAPPINGS**
8. Now, that you have selected a generic template, AND you have confirmed that ALL buttons are pointing to their native mappings (A,B,X,Y points to Button A, Button B etc etc, same with the triggers), go to that pesky options screen in Wasteland 2: DC, select the Steam Controller, and press that godforsaken A button. When you do, because A is now pressing Button A and not Tab or Enter, it will give you ALL the native mappings, and the game will play like it does on the consoles with all the PC patches and trimmings.
Now, I can't wait to get done with my day so I can come home and play this game using my steam controller!
This may work for other controllers as well, if you're using custom mappings. Bottom line my friends, get rid of the custom mapping, and the controller will be recognized just fine, when you select it out of options.
Hope this helps someone!
TL;DR - The custom mappings are screwing things up. A no longer presses the A button when you do that. It presses a key on your keyboard or a mouse button or whatever you have it mapped to. Set it to a default template, verify that A is in fact pressing the A button, then try to point the game to the controller.