🛈 Announcement
Greetings! Far Cry forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game.
  1. #1

    PSA: If You Have a Controller and Cannot Reverse or Descend

    Some people have had issues using reverse in a vehicle and descend in a helicopter when playing with a controller. The issue is that those commands do not have a binding to a trigger or button.

    Today, I received a reply on a support ticket regarding the issue (see below).

    The TL;DR is they aren't going to resolve the issue because they only support Xinput controllers - even though I am using an xinput controller.

    The controller I am using and sent information on is a Rock Candy XBOX 360 wired controller. Not only is it XINPUT, which the very link they sent shows should be supported, but it is manufactured under license from Microsoft. According to their own documentation regarding supported peripherals, there is absolutely no reason not to address this issue. It's kind of funny that support advised that if I want to use a controller in FC5, I should use a controller supported by the game. Newsflash guys - I am!

    I'm not sure why this issue is getting the brush off, but apparently that's exactly what they are doing. If you're having this issue, I recommend submitting a support ticket if you have an xinput controller and cannot reverse or descend. I've already switched to KB&M, but it's not okay to claim to support certain hardware and then back-pedal when someone has an issue.

    Ubi? Comment?


    Email from Ubi Support:

    Thank you for contacting Ubisoft Customer Support.

    Since there are hundreds of models of controllers available, we cannot provide assistance with configuring controllers to work with the game. Should you wish to use a controller, we advise using controllers that are supported for the game: https://support.ubi.com/en-US/faqs/0...Far-Cry-5-FC5/

    While we do not have specific controller troubleshooting, here are some general steps to try:

    1. Download and install any driver updates for your controller from the manufacturer's website.
    2. Make sure that your controller is properly configured in the Windows Control Panel.
    3. Check for any in-game controller settings that may need to be adjusted.

    If you continue to experience issues, please try the steps below:

    1. Open Control Panel, and go to Devices and Printers.
    2. Right-click on one of your game controllers, and click Game Controller Settings. Note the controller's location in the list. If it is not at the top, proceed to the next step.
    3. Right-click and remove all of your other controllers apart from the 360 controller / gamepad, and let them reinstall automatically.
    4. Once complete, right-click and check the list again to see if the 360 controller / gamepad is at the top. If so, try again to see if the game now detects your controller.

    This issue will be forwarded up to the development team; however, any additional information would be posted on our forums and support site if and when it becomes available. My apologies for any inconvenience this has caused.

    Kind regards,
    Share this post

  2. #2
    Considering Exfederalie from the other thread was using a microsoft xbox one controller and still had this issue, that's a pretty ridiculous response from support. And controller complaints since day one have been about both the dpad and the left trigger. And those complaints came from users of all types of controllers, including xbox one and ps4. Why eventually patch one broken part, and not the other?

    Because I already spent almost 2 hours messing around with the game on release, trying to get my 360 controller to work before I refunded, I can't even test my new pdp xbox one controller(that I bought solely for this game), as I can't reach a vehicle without going over the refund period. I am left to decide if I still want the game enough to try it again when it goes on sale, knowing that it likely still won't work. I suppose I should just wait a year or two, for a massive discount, so if it doesn't work, it's less of a loss.

    I am really disappointed that a simple feature that worked in the last 4 Far Cry games, which I replayed in the month before 5 released without any controller issues, has been so broken in this game, and then only half fixed months later.
    Share this post

  3. #3
    I went so far as to offer to mail the controller in question to them so they could figure out a solution. We'll see if they respond to the Support Ticket. From the reply I posted, I got the impression they won't, but you never know.. Since every post on the first page has been replied to be an Ubi rep except this one, I'm not holding my breath for any help here, either. Not sure what else to tell you except wait for the discount.
    Share this post

  4. #4
    ubi--unicorn's Avatar Ubisoft Support Staff
    Join Date
    Mar 2017
    Posts
    9,511
    Hey guys! Can you please provide me with the following information?

    - Do you use any additional peripherals alongside your controller?
    - Can you please try with another controller if you still experience this issue?
    - Do you encounter this issue only with a specific car or with all vehicle?
    - Did this issue occur right from the beginning or did this issue appear after a specific action was performed before?
    Share this post

  5. #5
    Uni - thanks for the reply. These were the initial questions support asked in response to my ticket, but:

    1 - No other peripherals
    2 - Don't have another one to try.
    3 - All vehicles. Also, helicopters don't descend
    4 - Right from the beginning.

    Please take a look at this screenshot: https://imgur.com/a/mTmf27E

    That is from another user who is experiencing the exact problem we are talking about. As you will see, Drive is bound to RT, Brake is bound to Button B, Shoot is bound to LB. Now look at Reverse - there is no trigger or button bound to it. It needs to be binded to LT. When in a helicopter, a similar situation occurs - everything is bound to a trigger or key EXCEPT for descend.

    The triggers and buttons that are bound work fine. And the left trigger works fine on foot. We just need them to figure out how to bind Reverse to LT, and Descend to whichever trigger or button it is bound to on working controllers.

    If you read support's response that I posted, they are saying they won't support controllers that aren't listed on the website. This controller is a supported peripheral. I've sent DXDIAG, MSINFO32 files, screenshots like the one above, and pictures of the device itself. Looking up that model will prove it's supposed to be supported.

    I have seen people with original Xbox controllers that have the same issue. I don't understand why support is responding the way they did.

    Thanks for trying
    Share this post

  6. #6
    I would like to ask if you bought the game through UPlay or Steam. If you are using Steam, try setting the big picture mode controller configuration settings for Far Cry 5 to "Forced Off". However, I have not tried this myself since I plan on getting this game when the DLC bug is fixed. Because of this, it may or may not work since I found this on another forum.
    Share this post

  7. #7
    Originally Posted by SquirmyElk2 Go to original post
    I would like to ask if you bought the game through UPlay or Steam. If you are using Steam, try setting the big picture mode controller configuration settings for Far Cry 5 to "Forced Off". However, I have not tried this myself since I plan on getting this game when the DLC bug is fixed. Because of this, it may or may not work since I found this on another forum.
    Thanks for the tip about steam. I know about that work-around but unfortunately it doesn’t work for everyone, myself included.

    Before the latest bug where gold and season pass owners started losing weapons, I switched to KB&M. Then the weapons bug happened and I decided to put FC5 aside for a while until they fix the issues. Should have waited and purchased at a discount later.

    Fact remains, it’s become a concern not because of using a controller itself, but that the devs aren’t supporting devices they publicly claim are supported. I find that a bit concerning. It sets a precedent, you know? Maybe people don’t have this specific issue, but this error in proper response by Ubi now opens everyone up to problems in future releases. No video? Well, we said we support nVidia but you really need AMD. It’s an exaggeration, I know, but the point is valid. Companies explicitly designate supported devices apart from unsupported devices for a reason. To not stand by their claims later when a problem arises should be a concern to everyone. Even if you are effected by the specific issue at the moment.

    But I do appreciate you taking the time to try and help.
    Share this post