Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
You replaced a file with itself?
I am using a classic Playstaion 2 controller for all of my games (which effectively is a generic controller, using a dongle / I prefer this controller) with Big Picture and I am quite disappointed to learn that no method I tried using x360ce with xinput1_3.dll or xinput1_4.dll, HookCOM setting ect, literally every setting possible, has not lead to any success using a generic PC controller with this game.
This basically renders this game unplayable for me because I like loading my PC up into Big Picture in my living room. Even more frustrating is the fact that I bought this game lead to believe, as the store page sais, has full controller support. Even if it would require and XBOX360 controller, all games that have this requirement work with x360ce. This game doesn't. Yet the store page doesn't say that this game requires and XBOX360 controller. Fairly disappointing to say the least.
So, in order to fully enjoy this game, I now have to dish out, on top of the 15eur (which no, dear developer, is not the same as 15$) I already payed, another odd 50 EURO to Microsoft to recieve the experience I desire.
Not what I was hoping for when I bought this game in good faith. On top of that, there is no word from the developer or Devolver Digital. Fairly disappointing.
Since developer apperently can't be arsed, if anybody finds a sollution please post it here, thank you.
"Full controller support" does not mean that the game will support ALL controllers. All it means is that you will be able to play a game, from installation (via Big Picture), through to the end, exclusively with a controller.
The pricing of € = $ has been something developers have fought with for a long time. It's a lazy translation of price on Steam's end.
I have no idea what you'll find, so this could take a bit of work. Hopefully, you end up finding what I'm looking for. For reference, what we're looking for is something similar to this:
6d0416c2000000000000504944564944,Generic DirectInput Controller,a:b1,b:b2,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b4,leftstick:b10,lefttrigger:b6,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b11,righttrigger:b7,rightx:a2,righty:a3,start:b9,x:b0,y:b3,platform:Windows,
Hopefully this works.
Also, one last question: What operating system are you on?
Hello friend, first off, thanks for your reply.
I'm running Windows 7 64-bit. And as I said earlier, using a genuine Sony Playstation 2 Dual Shock controller. I tried to setup the controller in the Big Picture settings, with no success unfortunately. What the Steam settings are telling me is that it detected USB Twin stick controller, and doesn't let me rebind the buttons for it. I have been trying to use Xinput Wrapper for DS2 which are supposed to work, but didn't for me.
I'll give it a last shot by trying to use MotionJoy's DS3 Tool which is supposed to work for DS2 controllers. At any rate all of this is probably more trouble then it's worth unfortunately.
In any case, thank you for trying to help out ;)
Inside the data folder for Titan Souls, there is a "controllerdb.txt" file. Inside this, there are several strings per OS, each one corresponding to a different, unique controller. I'm thinking that this game doesn't directly support xinput, but instead, supports this list of controllers directly.
Now, each line in this file is an SDL string that identifies a controller and binds each key. The beginning of this string is an identifier for the controller you're using. So I'm wondering if the game would bypass any emulators, and interact with the controller on a hardware level. If that controller isn't recognized, it won't work.
If we COULD configure your controller via Big Picture, then inside the config.vdf file, we would find another SDL string, which I'm hoping we could add to the list in controllerdb.txt, and have it identify your controller.
---
Unfortunately, I got messing around with this idea via vJoy (virtual gamepad driver), and configuring this virtual controller via Big Picture, and copying the SDL string into the db didn't do anything. As a last-ditch effort, I just deleted controllerdb.txt entirely. And... My controller still worked with the game.
I previously tried changing keyboard controls via game files, and while I could change menu navigation, I could not change character movement. This tells me that this file wasn't actually referenced (at least, not entirely), and despite having an options file to tweak things, the controls are actually hardcoded.
I fear that the controllerdb.txt is another case- A file that looks like it's used, when in reality, the controller support is hardcoded into the game.
It's an incredibly sloppy way to go about programming. Very inefficient, and probably made any debugging a nightmare. It's disappointing, but it is what it is...
You need to get "SDL2 mapping string" of your joystick in some way
and write it to "gamecontrollerdb.txt" in your game directory.
1. Download SDL2 Gamepad Tool[www.generalarcade.com], extract the archive and execute GamepadTool.exe.
2. Press "Create A New Mapping", and press your joystick buttons and sticks as instructed.
3. Press "Copy Mapping String".
3. Edit "SteamApps\common\Titan Souls\data\gamecontrollerdb.txt" and paste.
In the case of my PS2 DualShock2 Controller with USB Converter (ELECOM JC-PS201U),
the mapping string is:
I had a similar issue trying to rebind controls- The controls config file isn't even referenced regarding in-game controls. It's just... there. It's clutter they don't even use.
As long as I wrote mapping string into gamecontrollerdb.txt in the game dir without touching any BigPicture UI, it actually worked.
Let me try BigPicture and find out that tonight.
All my controllers natively work with the game, so I installed vJoy and attempted it with that. Maybe that just doesn't work.
I removed mapping string above from gamecontrollerdb.txt in the game dir,
configured my controller at BigPicture, and then confirmed working on the game!
I also tried vJoy.
I configured at BigPicture with vJoy feeder, but didn't work at the game...