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
Normas y directrices sobre discusión
1 
Denunciar este mensaje
I was finally able to get Assassin's Creed to recognise my wireless XBox One controller after enabling the settings mentioned in the above link. Following OP's instructions was not enough.
After you follow OP's x360ce instructions, you have to navigate to the 'Game Settings' tab, add Assassin's Creek and as per the above link, enable COM, DI, PIDVID (typo in link refers to as vidpid) and NAME under Hook Mask. Save your controller settings, exit x360ce and you should be good to go hopefully.
No, it isn't best to rebind the keys like you did as it doesn't actually solve the problem that most users have been having in these last 16 pages. You noted the problem yourself in that the triggers cannot be reassigned (nor can you reassign the right stick to turning the camera). Assassin's Creed I and II (not sure about the other titles) just doesn't seem to correctly identify any controller other than a WIRED 360 controller.
Follow OP's instructions, and then mine, and you'll (hopefully) have a smoother experience.
Ok. Thanks.
During the binding setup, I found that the triggers cannot be reassigned so I bound them to RB(High Profile) and LB(Target Lock) instead of RT and LT respectively. The trigger controls seems to be the only controller options I cannot use.
Acc. to the original Assassins Creed 1 manual for the Xbox 360 version, I only lose the Chase Camera function normally assigned to LB with my setup and nothing else once I assign High Profile and Target Lock to the RB and LB buttons respectively. RB doesn't seem to have an assigned function in AC1, so using that for High Profile doesn't affect me as much.
In AC1 one workaround for the Chase Camera function(normally LB) I found is to press the Left stick down(normally without any function) to assign it that function during binding, just like pressing the Right stick down centers the camera which is its normal function.
However, in AC2 RB functions as weapons selector, so in my case I decided to bind it by pressing Left stick down and then use the dpad to choose the weapons as you would do normally.
Also I also found a way to reassign the right stick to turn the camera by moving the stick Up, Down, Right and Left when choosing the pan camera options. The camera using the R stick seems to work properly after that.
So basically despite the fact the triggers doesn't work on the Xbox 360 or Xbox One, you could find alternative buttons instead to reassign them so you didn't lose any of the control functions you normally would have on the Xbox gamepad on AC1.
I am sure installing the files the OP recommended works more naturally to mimic the original setup, but if anyone doesn't want to go to the trouble of downloading and installing those files, rebinding the buttons during setup works just as well even without the use of the triggers.
My alternative setup for assigning the buttons in the control options for AC1 for my wireless Xbox One controller:
Use left stick to bind movement
Use right stick to pan camera
Use d pad to bind weapon inventory in this order described as hat switch on the PC version:
Up Hidden Blade
Down Fists
Left Short Blade and Throwing Knives
Right Sword
Button 1 or B(Xbox) - Open or Empty Hand
Button 2 or X - Weapons or Armed Hand
Button 3 or Y - Head
Button 0 or A - Feet or Legs
Button 4 or LB (normally LT on Xbox 360 manual) - Target Lock
Button 5 or RB(normally RT on Xbox 360 manual) - High Profile
Button 6 or Left arrow - Map
Button 7 or Right Arrow or Start Button - Pause
Button 8 Press LS down - Chase Camera
Button 9 Press RS down - Center Camera
BTW, does the explanations or references during the game change too as well? Will it say press X or B instead of Buttons? It did not for me even when I reassigned the buttons, so I presume it won't as well even with x360ce.
What page is your post by the way and what did you add?
As for the other Assassins Creed games aside from AC 1 and 2, they all seem to recognize both wireless Xbox 360 and Xbox One natively on PC, so no need to add workarounds or to rebind keys on your gamepad.
Literally above your post.
If you're fine with giving up certain functionality (trigger buttons) and having to re-assign buttons, that's cool. But it isn't the *best* option, no (which I know is entirely subjective). As far as ACI and II recognising XBox One controller natively.. It doesn't. Not for me (d-pad is hat switch, right stick can't re-assigned as it ends up behaving like the left stick, ABXY not recognised for what they are etc) and for other people here and across the internet (google 'assassin's creed xbox one controller fix').
Give x360ce a shot and you might just like it. Or don't, that's cool. I can understand not wanting to install extra crap just to get something working, but x360ce actually gets around Ubisoft's ♥♥♥♥♥♥ implementation of AC on PC (if you can get it working) and forces the game to do what it should have in the first place.
Personally, my experience was unusable triggers and right stick.. So it was the option of either playing with mouse and keyboard or using the controller emulator (which in itself was a pain to setup until I found the wiki that was linked - look above your post from a day or so ago). Essentially, my additional instructions are for people in similar situations.
And regarding the explanations/references in-game to button presses, once the emulator is set up to work correctly, yes it will say X or B rather than button 1/2/3 etc. That's the biggest clue that the emulator has been setup perfectly. Hatswitch will be referred to as dpad, and ABXY will no longer be referred to as buttons. :)
Cool. I might use the x360ce in Assassin's Creed 2 then, since I really haven't started it yet on PC and don't have it on console. I find the instructions telling me to press button so and so annoying so having the instructions given correctly is refreshing.
As for AC 1, I actually have it already on my Xbox One X, where I am halfway finished. I was just comparing that version to the Director's Cut on PC where the lack of native controller support made me decide that it wasn't really worth repeating the game on PC, even though I did start it.
I am bit surprised though that the game didn't recognize your Xbox One controller. You must have the older model Xbox One gamepad. The newer Xbox One S wireless controllers all have blue tooth support which the previous models did not. AC 1 recognized it as a Xinput blue tooth controller in the options because of that.
You would need an Xbox One adapter/receive to help your Windows 10 PC recognize your Xbox One Controller then. Fortunately for me, my PC has a blue tooth receiver already installed which works well my with Xbox One S gamepad.
BTW, do you know if x360ce works with the original Splinter Cell which is another Ubisoft game? I prefer using a gamepad with predominantly stealth games but Splinter Cell on PC was made without a controller in mind a long time ago.
So here's the thing, my Xbox One controller is new (it has bluetooth; bought three months ago, retail, to replace a wired 360 controller that died). ACI "identifies" it as an Xbox One controller in the toggle where you switch between control methods, but doesn't actually register the correct buttons.. Hard to explain, but I'm there's youtube videos out there that show what I'm trying to say. And you don't necessarily need a bluetooth receiver.. You can use the wireless controller in wired mode with an appropriate USB cable (just an FYI). Not sure where the issue lies, may be on the Windows side or it may be on Ubi's code or both.
Not sure whether x360ce is capable of emulating keyboard and mouse through the controller or whether it works with Splinter Cell (the first one, I assume?). Convinction and Blacklist are the only ones listed here - https://github.com/x360ce/x360ce/wiki/Compatibility-List - but I just don't know to be honest. Sucks to hear that Splinter Cell had no controller support, but it makes sense around the time it was released on PC.
Only way to find out is to give it a shot, I suppose. :/ Good luck!
I just found out something. This doesn't work on AC1 but on AC2, I found out that AC2 recognizes a wireless Xbox 360(not Xbox One) controller natively at least with an official Xbox 360 receiver/adapter plugged into the USB port. All the keys in the controller options when choosing Xbox 360 for Windows as your preferred control option registers correct and responds properly in game, unlike what happened when I used my Xbox One gamepad.
Either Ubisoft must have added Xbox 360 support for Assassin's Creed 2, but unfortunately not for AC1 or for the Xbox One gamepad or Microsoft considers the official Xbox 360 wireless receiver I have attached to my gaming PC like it does a wired Xbox 360 gamepad.
I still have my old Xbox 360 gamepad which I was using for my steam link(with the 360 adapter attached) in my bedroom and thought why not try it out on my PC for AC 2 and surprisingly after my Windows 10 PC downloaded some files from MS when it recognized my device which are all official Xbox accessories, it recognized it natively just like a wired Xbox 360 controller.
This doesn't work on AC1 on PC which has the same problem as the Xbox One gamepad, which is ok by me since I have the game(but not AC2) on my Xbox One X and Xbox 360 anyways and just plan to play it there.
This saves me the trouble of having to add those x360ce files to my PC as I will just use my Xbox 360 gamepad for AC2.
All the other succeeding AC games after AC2 recognize either the Xbox One or the Xbox 360 gamepad so you don't need to add files for those.
You press the right trigger to enable high profile on the original Xbox 360 gamepad (if you use x360ce) or bind Right Trigger function to Right Bumper(doesn't have function in original game) to serve the same purpose.
Yeah, I ended up remapping the whole thing. Feels much more natural.
Thanks!
I posted an alternative setup to xbox 360 ce on post #231 if you don't want to download those files. Since the Right and Left Triggers don't work for Xbox One controllers, just bind those keys to Right and Left Bumpers instead. Everything else is the same.
I think using xbox 360ce is better though because not only will the triggers regain their intended function but the instructions during the tutorial will be referring to the normal A,B,X,Y config. etc. instead of Buttons 1,2,3, etc.