I presume it's similar to what Feral sent you, but if not, open the properties for F1 in your Steam library, go to the Local Files tab and click "Browse Local Files.".
If you'd like to give it a try I've uploaded it to: I was able to get my v2 controller to work after adding a controller file to the game installation specifically for the v2 controller. The controller I initially tested F1 with was a DualShock v1 controller, which it does have support for both USB and Bluetooth, so I'm wondering if you happen to have both a v1 and a v2 controller and it's just the v2 that isn't working.
#Minecraft controller mac Ps4
So, the steps I recommend are, turn your controller off, navigate to controller settings, turn off PS4 Configuration Support, then connect your controller and give it a try in-game again.ĭo you happen to have more than one PS4 controller that you use with your PC? I took a closer look at your logs and it looks like you're using a DualShock v2 controller. If you have a custom colour set for the controller LED you can tell if it's in this gyro mode if the LED is set to your colour. To get access to the PS4 controller's gyro input the controller has to be put into a special mode that it can't be taken out of until the controller is next shut off and turned back on. PS4 controllers over Bluetooth have an additional caveat as well that other controllers don't. On macOS we create a virtual gamepad that we send input through to the game when configuration support is enabled for the controller (we do this to support the controller remapping we allow in Steam), however some games don't support this virtual controller and instead only support the actual controller device. I gave F1 2013 a test with some PS4 controllers I have and it looks like it only supports PS4 controllers when the "PS4 Configuration Support" setting is disabled in Big Picture.
0 kommentar(er)
