https://bugs.winehq.org/show_bug.cgi?id=46556
Bug ID: 46556 Summary: FINAL FANTASY XI and FFXiPadConfig.exe utility no longer detect Logitech F710 via (emulated) DirectInput; under XInput, detects Axes 5 and 6 as buttons Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs@winehq.org Reporter: emegas@vecanti.org Distribution: ---
Created attachment 63427 --> https://bugs.winehq.org/attachment.cgi?id=63427 Backtrace
When using a method to change areas that involves an NPC or non-player object, there is an high chance that FINAL FANTASY XI will crash directly after the menus load in the new area--always immediately after the "== Area: [name] ==" identifier is displayed in the log--before the player or NPCs have a chance to load into the map. (Restarting the game afterwards will always load the new area successfully.)
Home Points, Survival Guides, the Mog Garden NPCs in front of the entrances to the Western Adoulin and Eastern Adoulin Rent-a-Rooms, Waypoints and Proto-Waypoints, and using a Warp Ring (thus opening up the likelihood that _any_ type of magical or item-triggered area change can cause it) all appear to cause the crash.
On the other hand, changing areas via "zone lines" (walking between them), the "Button" in Ru'Lude Gardens and changing areas from within a Mog House do not _not_ seem to cause the crash.
Probably the easiest way to repro this is to use a Home Point to change between different Home Points within the same city until the crash is seen (ex. Bastok Mines #1 -> Bastok Markets #1 -> Port Bastok #1 -> repeat).
Tested and confirmed in both 4.0 release and wine-4.0-251-g7003ba44892 (vanilla and staging). The debug information attached is from wine-4.0-251-g7003ba44892 (vanilla).
(Tested on Gentoo Linux kernel 4.20.5 with nvidia-drivers 415.27)