It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
F4LL0UT: Assassin's Creed 1 and 2. I think the first AC game to actually use Xinput was Brotherhood. With the first two you were much better off using a DirectInput controller.
This discussion suggests the first AC game works fine with the wired XBox360 controller (while some issues with the wireless one).

As I mentioned, at least in the first AssCreed game the Logitech F310 gamepad works fine out of the box when the controller is in DirectInput mode, but in XInput mode the controls are way off.

However, it is odd that the game itself uses XBox360 gamepad-like visual cues for the controls, like asking you to push the red A or green B, if I recall right. That lead me to believe the game supports both XInput and DirectInput, somehow automatically detecting which mode it should use.

After all, many games also change those visual cues depending whether you start using mouse + keyboard, or a gamepad. The most irritating one is Mirror's Edge which uses XBox360 gamepad visual cues if you have merely a gamepad (or something it thinks is a gamepad) connected, even if you want to play with a mouse and keyboard. The only way to get the proper keyboard + mouse visual cues in the tutorial is to disconnect any gamepads and such. Quite hard to play the tutorial when you have no idea which button on the keyboard corresponds to which gamepad button or function...
avatar
F4LL0UT: Assassin's Creed 1 and 2. I think the first AC game to actually use Xinput was Brotherhood. With the first two you were much better off using a DirectInput controller.
avatar
timppu: This discussion suggests the first AC game works fine with the wired XBox360 controller (while some issues with the wireless one).

As I mentioned, at least in the first AssCreed game the Logitech F310 gamepad works fine out of the box when the controller is in DirectInput mode, but in XInput mode the controls are way off.

However, it is odd that the game itself uses XBox360 gamepad-like visual cues for the controls, like asking you to push the red A or green B, if I recall right. That lead me to believe the game supports both XInput and DirectInput, somehow automatically detecting which mode it should use.

After all, many games also change those visual cues depending whether you start using mouse + keyboard, or a gamepad. The most irritating one is Mirror's Edge which uses XBox360 gamepad visual cues if you have merely a gamepad (or something it thinks is a gamepad) connected, even if you want to play with a mouse and keyboard. The only way to get the proper keyboard + mouse visual cues in the tutorial is to disconnect any gamepads and such. Quite hard to play the tutorial when you have no idea which button on the keyboard corresponds to which gamepad button or function...
The Wireless Xbox 360 Controller, always has problems on PC, compared to the Wired Controller.

All Assassin's Creed games support xinput out of the box, they're console ports.

I played all Assassin's Creed games with an Xbox 360 Controller, and never had any problem, has any other game, it's plug and play.
Post edited September 28, 2015 by Kobi_Blade
I love my Logitech Rumble Pad 2. I have it like forever and it still works fine.
Does anyone know how does xbox360 wireless gamepad behave with emulators?
avatar
RottenRotz: Does anyone know how does xbox360 wireless gamepad behave with emulators?
The same as a wired one, once you're connected it's just a 360 controller.
avatar
Kobi_Blade: The Wireless Xbox 360 Controller, always has problems on PC, compared to the Wired Controller.
Wrong, it works flawlessly with any normal Xinput application. The first two Assassin's Creed games are an exception and it's the developers' fault, the X360 controller support is half-assed bullshit there that depends on the device name (which is just wrong). Take it from someone who has been using the wireless controller since 2008 and never had any trouble with any Xinput games.
avatar
timppu: However, it is odd that the game itself uses XBox360 gamepad-like visual cues for the controls, like asking you to push the red A or green B, if I recall right. That lead me to believe the game supports both XInput and DirectInput, somehow automatically detecting which mode it should use.
I believe the first two AC games do not actually support XInput but rather choose an alternate more sensible button preset if they recognize the X360 controller. The problem is that they do so by checking the device name which is different for the wired and wireless controllers and the devs didn't think of including the wireless one.

I can't say for sure, though, if the games only change the button layout (still not supporting the tiggers) or actually fire up XInput, then. I remember actually checking things out by using a custom driver that makes DirectInput controllers act like Xinput devices but that was all the way back in 2008 and I don't remember how AC1 behaved then.

Edit: Oh, nice, just discovered this. Damn, how did I not find that when I played AC1 and 2 last year? -.-
Post edited September 28, 2015 by F4LL0UT
avatar
Cavenagh: you mean it had lag?
avatar
tinyE: No it just didn't set up well, which might have been my PCs fault. More than that, it just felt awful. It was too small, really light; I was afraid I might break the damn thing if I gripped too hard.
I remember the original Xbox controller - there was something you couldn’t call small and light! Everything about that console was huge, even the power supply cable was 3 times thicker than necessary.

Bizarrely I liked it and could use it well, and my hands are absolutely tiny (people often say that and have average hands, I really have small hands - same size as my gf who is 5'2 and has small hands for her size).

On topic, I have that controller OP and it works well. It is a bit light, but that is probably because it doesn’t have vibrate so is missing the metal spinning pieces and small motors. It is accurate though, and works perfectly for me. Keep in mind what I just said above though, my hands are small so general size is something I often cant comment on for other people.
Post edited September 28, 2015 by mabrookes
avatar
mabrookes: On topic, I have that controller OP and it works well. It is a bit light, but that is probably because it doesn’t have vibrate so is missing the metal spinning pieces and small motors.
Imho the best thing about vibration feedback is the weight of the motors.
It's like with expensive cameras, they have to be heavy enough for proper handling.

Greetings from another one with girlie sized hands.
avatar
Klumpen0815: Imho the best thing about vibration feedback is the weight of the motors.
It's like with expensive cameras, they have to be heavy enough for proper handling.

Greetings from another one with girlie sized hands.
I do prefer the extra weight, but I can’t complain; a friend gave me this one that he had barely used and didn’t need when I mentioned I was looking to get one. He just asked for a drink the next time we were out.

It is decent in every other way so I have stuck with it.
Post edited September 28, 2015 by mabrookes
I use a Wii U Pro controller, as I hate the layout and feel of the 360 controller.
avatar
Kobi_Blade: The Wireless Xbox 360 Controller, always has problems on PC, compared to the Wired Controller.
avatar
F4LL0UT: Wrong, it works flawlessly with any normal Xinput application. The first two Assassin's Creed games are an exception and it's the developers' fault, the X360 controller support is half-assed bullshit there that depends on the device name (which is just wrong). Take it from someone who has been using the wireless controller since 2008 and never had any trouble with any Xinput games.
avatar
timppu: However, it is odd that the game itself uses XBox360 gamepad-like visual cues for the controls, like asking you to push the red A or green B, if I recall right. That lead me to believe the game supports both XInput and DirectInput, somehow automatically detecting which mode it should use.
avatar
F4LL0UT: I believe the first two AC games do not actually support XInput but rather choose an alternate more sensible button preset if they recognize the X360 controller. The problem is that they do so by checking the device name which is different for the wired and wireless controllers and the devs didn't think of including the wireless one.

I can't say for sure, though, if the games only change the button layout (still not supporting the tiggers) or actually fire up XInput, then. I remember actually checking things out by using a custom driver that makes DirectInput controllers act like Xinput devices but that was all the way back in 2008 and I don't remember how AC1 behaved then.

Edit: Oh, nice, just discovered this. Damn, how did I not find that when I played AC1 and 2 last year? -.-
I suggest you use google, before saying I'm wrong.

It's a fact the Wireless Xbox 360 Controller, has more problems than the wired one.
avatar
Kobi_Blade: I suggest you use google, before saying I'm wrong.
I suggest you provide a specific example instead of talking out of your ass and then actually requesting that others try to back your very own bullshit. Seven years of intense usage of the wireless controller trump "google it", you know. And you literally said that there are "always problems" (whatever "compared to" is supposed to mean after "always") and that is simply factually wrong.
Well I'm quite impressed with this gamepad, is great for playing Don Bradman's cricket, I tried it with Far Cry 3, But I'll stick to KB+M for that one.

No drivers needed to be installed, just plug and play, and the size is not too bad,. The only problems I have is I keep pressing the wrong buttons.. :(

It also has vibrate [feedback]

Happy

All the best

[edit] How rude of me, thanks once again for all your feedback, it was much appricated, hope the thread helped others as well.
Post edited October 03, 2015 by Cavenagh