Time: 6:15pm
Frequency: Possibly every time the game opens following a pc restart.
World name: Cactuar
Character name: C'thuuko Tohka
NPC name: N/A
Monster name: N/A
Class/Level: Dragoon level 60
Party or solo: solo
In-game time: N/A
Area and coordinates: Idyllshire
Steps:
1. Turn on pc
2. Plug in Controller
3. Login to FFXIV
4. Numerous buttons are not mapped properly (X registers as triangle, O registers as X, triangle registers as O, L3 and R3 register as select and start respectively)
5. In controller options in-game, despite buttons at least being read before this point, no buttons can be read when going to configure to attempt to resolve this
Connection Specs
- Type of internet connection/provider: N/A
- Modem maker/model number: N/A
PC Specs
-=-=-=-=- System Information -=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Laptop Model Name: N/A
Laptop Model Number: N/A
Gamepad Manufacturer: Sony
Gamepad Model Name: Dualshock 4
Gamepad Part Number: N/A
Browser Information
- Name and version of the browser currently in-use: N/A
- Internet Explorer Version: N/A
Comments:
This issue has been reported numerous times in the past, as seen in the following links:
http://forum.square-enix.com/ffxiv/t...er-Calibration
http://forum.square-enix.com/ffxiv/t...PS4-Controller
http://forum.square-enix.com/ffxiv/t...ntroller-on-PC
http://forum.square-enix.com/ffxiv/t...guration-on-PC
Each time this issue gets brought up it eventually gets moved to "Resolved issues" despite the issue continuing to pop up and, clearly, NOT BEING RESOLVED. This is unacceptable, and the mod who continues moving these issues to "Resolved" should be disciplined for essentially lying to the playerbase. I'm aware that the issue of the buttons not being mapped right can be solved by editing the .cfg file, but this A) doesn't fix the inability to configure the buttons in-game and B) should not be required for a peripheral that is natively supported by both the hardware and the game itself. Please do not move this instance of the bug into "Resolved" until the bug has ACTUALLY BEEN RESOLVED.