It's not perfect as it did fix my other games that were messed up from it plugged in and no DS4 subsequently, it messed up Fallout 4. In big picture, you can tailor your button configurations for each game. You have to enter big picture mode to access it. Now what I've done to try and make my controller work for all games is to turn on Playstation 4 Controller Configuration in Steam settings. I may need to try DS4 again, but it messed stuff up for me when I used it. Your other games however will likely be messed up.
#Fallout 4 windows 10 ps3 controller Ps4#
I found that simply plugging the PS4 controller into your computer works for Fallout 4, without DS4 or any program. I have no clue what's up really with DS4Windows and Fallout 4 conflicting with each other like crazy, but this seems to work for me consistently. If all other buttons work too, then you're golden.Īgain, may or may not work.
I test it by pressing the start button, making sure that it opens the menu, and using the touch pad to change into third person. If your start button is keybound to up on the D-pad, your square button rebound to X, then you'll have to do this:Ģ.) Restart the game with DS4Windows stopped.Ģ.5) Your control may be lit up at this pointģ.) When it starts back up, your controls should all be routed to the right buttons, it should work like a charm. Once the controller itself is working, your controls may be pretty screwed up. The native support for dualshock 4 controllers in Fallout 4 works as far as I can tell, it's just DS4Windows that messes it up.
If it doesn't work try exiting DS4Windows completely as well as Fallout 4 first. Make sure that the launcher isn't open while you are opening DS4Windows. Not really sure why it works, but for me it did. (it should say, "No controllers connected.")Ĥ.) While keeping DS4Windows open, launch Fallout 4.ĥ.) Leave DS4Windows running while playing, you can minimize it but don't exit it out. I turned incredibly slow and the button configuration was all crazy, what made it work perfectly for me, was this:ģ.) Hit the stop button in the bottom corner of the window, so that the controller details in the first tab of DS4Windows is gone. Continued abuse of our services will cause your IP address to be blocked indefinitely.TO FIX CONTROLLER NOT WORKING WHATSOEVER:ĭon't know if anything here worked for you, but just exiting DS4Windows made my controller for some reason screw up and not work right. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here. If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior.
Using a badly configured (or badly written) browser add-on for blocking content.Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.