Final Fantasy XI Online

Final Fantasy XI is the first online Final Fantasy RPG from Square Enix.

Application Details:

Version: Final Fantasy XI
License: Retail
Votes: 404
Latest Rating: Silver
Latest Wine Version Tested: 4.11

Maintainers: About Maintainership

Link Square Enix account managment Free Download Installation Media

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Install, Configuration, Gamepad input (Old Logitech Dual Action), Updates (with minor hiccups), General Gameplay. This was installed using the downloadable installer from the FFXI Website.

What does not

PlayOnline Splash Screen does not display properly

"Opening Movie" option does nothing.

Minor Graphical Glitches, including glow appearing outside glow boxes, and wall/floor seams being visible from adjacent rooms.

 For all intents and purposes, though, it's flawless


What was not tested

balls-to-the-wall combat (1v1 combat was tested), manual registry config.

Hardware tested


  • GPU:
  • Driver:

Additional Comments

Wine needs to be set to Windows 7 Mode No DLL Overrides are needed with this wine version If you are on a 64-bit install, be sure to prefix anything passed to wine with 'WINEARCH=win32' Recommend using your GPU's binary driver. Recommend configuring FFXI to run in Windowed Mode Recommend manually altering config in registry, as some resolution options are not available May give a few hiccups during install and/or update, which can be safely ignored.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowGentoo Linux x86_64Jun 24 20194.11Yes Yes NoSilverChiitoo 
ShowmacOS Mojave 10.14Feb 15 20194.1Yes Yes NoPlatinumChristopher Strom 
ShowGentoo Linux x86_64Jan 08 20194.0-rc3-stagingYes Yes NoSilverPandoraxero 
ShowGentoo Linux x86_64Oct 15 20183.18N/A Yes YesGoldMegas of Vecanti 
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Nov 03 20183.0.3Yes Yes NoPlatinumChristopher Strom 

Known Bugs

Bug # Description Status Resolution Other apps affected
28861 Final Fantasy XI hangs after character selection NEW View
32931 FFXI Amazon Downloader crashes when trying to download install files NEW View
40794 PlayOnline Viewer crashes when using a game controller. UNCONFIRMED View
41641 Final Fantasy XI: incorrect face culling; no glitches when disabled UNCONFIRMED View
42008 Final Fantasy XI Online: Opening movie doesn't play. UNCONFIRMED View
45520 Install Shield fails on 64bit prefix with Silent install UNCONFIRMED View

Show all bugs

HowTo / Notes



The PlayOnline Viewer and Final Fantasy XI installation/data files can be downloaded from the PlayOnline website(s):

During the installation process of Final Fantasy XI, a window with only borders, and no rendered content may be seen, and the 'msiexec' process can be using up to 100% of a single CPU core while possibly processing the 'FINAL_FANTASY_XI.msi' file probably. This can take up to at least four (4) minutes, but should eventually complete.

Last updated until this point: 2019-06-14


Windows 7 needs to be set as the reported Windows version, or the game client will crash after accepting the licence agreement.

Everything imaginable in-game works, though the game can be quite heavy, depending on settings (especially due to the shadows).  Using CSMT from Staging helps with FPS by allowing more CPU to be used.


A PS2-controller via a simple USB-converter works flawlessly (aside from sometimes when entering the game, and the analog mode is off, the player character and the camera will start moving by themselves, but they stop when the analog mode is enabled (whether or not this would happen on Windows as well is unknown at this time)).

Japanese Input

Requires the Japanese PlayOnline Viewer software, as is intended (using 'uim' to switch input methods).

Works while in PlayOnline Viewer, but not while in-game.  This may be due to how things are built-in.  It is possible to paste text from outside the PlayOnline Viewer into it, but the same is not true for the actual game client.

Known Issues

  • The PlayOnline Viewer splash image is "transparent" (works with Wine Staging).
  • The opening movie does not play correctly, but the audio can be heard (for about 10 seconds, then it's skipped).  This seems to be regression (bug 42008).
  • Sometimes, usually only after having gone back to the PlayOnline Viewer from the game, the application will crash when re-launching the game from the viewer (backtraces speak of the (proprietary) nvidia-drivers).
  • The PlayOnline Viewer graphics are not updated when moved to a secondary monitor, looking like a hang (audio still plays, and it is possible to interact with buttons and such).  The actual game client doesn't have this issue.
  • Using the Japanese client, typing Japanese in-game doesn't work via 'uim', probably because the thing is heavily built-in (text can't be 'pasted in' even).
  • Using the Japanese client, having the opening movie enabled will crash the client when launched from the PlayOnline Viewer. 

The following information may be largely out of date since 2016-12-19 or earlier.

HOWTO - Final Fantasy XI: The Ultimate Collection 2011

This HOWTO will help you get Final Fantasy XI setup on your machine using "The Ultimate Collection 2011" retail package, or equivalent media. Here you will also find a guide to get the PlayOnline Viewer running. This HOWTO is complete to the best knowledge of its creators, however, there may be some errors that have not been resolved.

Please note that in order to run this game, you will most likely NEED the proprietary drivers for your graphics card(s). Open-source drivers are known to have problems with 3D rendering, and may render many things incorrectly or slowly. Please bear this in mind when submitting test results, as well.


  • Insert "The Ultimate Collection 2011" dvd into your dvd drive.
  • In a terminal session, type in "wine /path/to/dvdrom/PlayOnline/setup.exe".
  • From here, you will be guided by a setup wizard. Choosing all defaults is acceptable.
  • After the PlayOnline Viewer is finished installing, click finish on the wizard if you haven't done so already.
  • Type in "cd/path/to/dvdrom/INST1" to go into the install directory for Final Fantasy XI.
  • Type in "wine setup.exe".
  • A wizard will appear that will guide you through setting up Final Fantasy XI. Again, choosing all defaults is acceptable.
  • After installation is complete for Final Fantasy XI, you may be given a choice to restart your machine. Choose "No, I will restart my machine later" and click finish.
  • From here, type in "cd/path/to/dvdrom/INST2".
  • Type in "wine setup.exe".
  • Follow the wizard for setting up Rise of the Zilart, choosing all defaults, and selecting to restart your computer later, if prompted.
  • Type in "cd/path/to/dvdrom/INST3".
  • Type in "wine setup.exe".
  • Follow the wizard for setting up Chains of Promathia, choosing all defaults, and selecting to restart your computer later, if prompted.
  • Type in "cd/path/to/dvdrom/INST4".
  • Type in "wine setup.exe".
  • Follow the wizard for setting up Treasures of AhtUrhgan, choosing all defaults, and selecting to restart your computer later if prompted.
  • Type in "cd/path/to/dvdrom/INST5".
  • Type in "wine setup.exe".
  • Follow the wizard for setting up Wings of the Goddess, choosing all defaults, and selecting to restart your computer later if prompted.
  • You may now umount your installation media. Be sure to store it in a safe place.

Overriding DXDIAGN.DLL

  • Obtain a copy of the file "Dxdiagn.dll" from a Windows XP install (It'll be in the System32 Directory)
  • Copy said file into your WINE installation (.wine), place it either in the Windows folder or the System32 folder, either is fine.
  • Open a terminal and navigate to the directory you placed Dxdiagn.dll into.
  • Run the following command: "wine regsvr32 dxdiagn.dll". Additionally try running "wine regsvr dxdiagn.dll".
  • Open winecfg and navigate to the overrides.
  • Set a new override for Dxdiagn.
  • You should be set to go.


  • Here the PlayOnline Viewer will be updated. Follow the instructions to update the viewer.
  • After PlayOnline Viewer is updated, the viewer will ask you to click next to restart it. Do so, and PlayOnline Viewer Should restart.
  • Once logged in, you may run Final Fantasy XI. It will be updated upon running them for the first time, this is the perfect opportunity to eat some cheesecake, because the initial update could take hours. Do note that if you have registered the registration codes for any of the Abyssea expansions it will be automatically downloaded and installed in the update.
  • Once the update has completed, Final Fantasy XI should launch with your desired settings.
  • Go to a heavily populated area, and type "/yell Final Fantasy XI Runs In Linux!!" into Final Fantasy, and press Enter

Running more than one instance of FFXI:

  • In a shell do:
    WINEPREFIX="/home/$USER/.wine-second" wine /path/to/first/full/FFXI/Install/pol.exe
  • This will create a new instance directory for wine in your home folder. It will be named .wine-second
  • You will get a few errors. You can dismiss all of them.
  • Use your favourite file handling utility and copy the complete PlayOnline folder from your previous (/home/yourname/.wine/drive_c/Program Files/) wine instance to your new instance. (Yes you will need two installs of FFXI for this to work)
  • Make sure you copy your original install from it's root folder in the Program Files directory to the Program Files directory of your new wine instance. The folder named PlayOnline is all you need to copy.
  • Now you should have one original install in:
    /home/yourname/.wine/drive_c/Program Files/PlayOnline/
    and one copy of that install in:
    /home/yourname/.wine-second/drive_c/Program Files/PlayOnline/
  • In a shell do:
  • Now make sure that the root of the registry is selected in the tree structure on the left hand side. In English the root is called 'My Computer'
  • Now click the following sequence in the Regedit menu bar:
    'Registry -> Export registry file'
  • Select a location to save your registry export. (Suggest saving to desktop for easy removal after you are done)
  • Close the registry editor.
  • In a shell do:
    WINEPREFIX="/home/$USER/.wine-second" regedit
  • You are now editing the registry information for your new instance of wine.
  • Once again; select the root of the registry (My Computer). Then click the following sequence in the registry editor:
    'Registry -> Import registry file'
  • Select the file you saved in the previous regedit instance. (The one I suggested you save to your desktop)
  • Once the file has been imported... (might take a while depending on size of registry) you are ready to start using two instances of FFXI at the same time on the same computer.
  • You may now delete the .reg file that you saved to your desktop.
  • To start the first instance of FFXI use:
    wine /path/to/first/full/FFXI/Install/pol.exe
  • To start the second instance of FFXI use:
    WINEPREFIX="/home/$USER/.wine-second" wine /path/to/copy/of/full/FFXI/Install/pol.exe
  • The default path to an install is: /home/username/.wine/drive_c/Program Files/PlayOnline/
  • This guide is crude and in an initial stage. In time it will be >optimised.

Other Recommendations/Info:

  • Disabling shadows altogether causes a speedup.
  • Desktop Effects (Compiz) should be disabled if flickering of the screen occurs.
  • Please use the latest version of wine if possible, if not, there is a list of known working versions at the bottom of this guide.

Christopher Strom


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Doesn't work on either 4.1 or 4.9
by Brandon on Sunday June 9th 2019, 9:31
Doesn't work at all. Crashes loading POL
RE: Doesn't work on either 4.1 or 4.9
by Chiitoo on Friday June 14th 2019, 6:28
Is this with the new installer?

Are you able to install and update the PlayOnine Viewer, or does it go bad already before those parts?

Could you grab the terminal output from the run, and send it to a 'pastebin' service, and link to it here?

2019 Reassessment
by Pandoraxero on Tuesday January 8th 2019, 5:29
Just did a reassessment of the game on 4.0 rc3 (Highest Version I could find an overlay for in Gentoo)

Didn't exactly run as expected. I assessed it the same way a total noob would. ...or at least a total noob who somehow knows how to use portage overlays. No real modifications (except setting the res to 1600x900. Home Point Warping crashed the game.
I'm going to try the an ancient tech support trick, which is known to all but the noobest of noobs, I guess that would make them... n00bs (because double zeros. ...Amirite? ...Guys? *sigh*
Okay. Ill-conceived lame pun aside, I'm gonna turn my Linux rig off... stand outside in the apparently rainy weather smoking a cigar on a covered porch for about an hour... then turn it back on again... then RE-reassess the game. Who knows, maybe my dual 780Ti's are running too hot or something.
RE: 2019 Reassessment
by Chiitoo on Tuesday January 8th 2019, 7:29
Which overlay were you using? I don't think we have any official ones with release candidates on Gentoo.

We tend to skip those for a reason, but you can always use the '9999' to get them if you like. :]

I have not had the issue with home-points that you mention. Perhaps I just conveniently dodged that bullet by not following the tags too closely (currently at rc5).

The only real issue that I have had, (though only really an issue if you ever move the mouse around) is which is also now fixed.

That, and which is still around.

It would probably be a good idea to try with an official Gentoo ebuild too, though it may be unlikely to fix the issues you have been seeing.

RE: 2019 Reassessment
by Pandoraxero on Tuesday January 8th 2019, 8:09
overlay I'm using is unofficial, "hossie"
I ran a search for wine overlays for Gentoo and came up with this list:

Which seems to be about the most comprehensive list I can find. I'm considering 9999, but like I said elsewhere, that's an unofficial version, and its results don't really count for testing purposes. As it stands, the game's only KINDA playable... IF you're lucky.
I do understand the rc releases being only about a week apart from one to the next being more than a minor hassle to the Gentoo maintainers, though.
What USE flags do you have enabled for wine? I have USE="X alsa cups fontconfig gecko jpeg lcms ldap mono mp3 ncurses nls opengl perl png pulseaudio realtime run-exes sdl ssl threads truetype udev xcomposite xml" for wine-staging
RE: 2019 Reassessment
by Chiitoo on Tuesday January 8th 2019, 8:47
If you use the environment variables I mentioned, you can get any officially released version you want with 9999. In a sense, I would say that it would count more as a test result, than one with an ebuild from an unofficial source does. :]

Which version of nvidia-drivers are you using (415.25 here at this time)?

Also, could you grab the terminal output from a session where you experience a crash, and throw it into a 'pastebin' of some kind (and link to it here)?

I haven't actually tried Wine-Staging for FFXI in a while. It causes my whole desktop go wonky (windows turn black and stuff like that). It may be caused by some setting in the prefix that I have set in the past, however, though I think this one should be relatively clean. I'll need to look into that more with time at some point.

Here are my usual flags:

app-emulation/wine-vanilla-9999::wine was built with the following:
USE="X alsa fontconfig gecko gstreamer jpeg mono mp3 ncurses nls openal opengl png ssl threads truetype vkd3d vulkan xinerama xml -capi -cups -custom-cflags -dos -gphoto2 -gsm -gssapi -kerberos -lcms -ldap -netapi -odbc -opencl -osmesa -oss -pcap -perl -prelink -pulseaudio -realtime -run-exes -samba -scanner -sdl (-selinux) -test -udev -udisks -v4l -xcomposite" ABI_X86="32 64 (-x32)"
CFLAGS="-march=znver1 -O2 -pipe"
CXXFLAGS="-march=znver1 -O2 -pipe"

app-emulation/wine-staging-9999::wine was built with the following:
USE="X alsa fontconfig gecko gstreamer jpeg mono mp3 ncurses nls openal opengl png ssl (staging) threads truetype vkd3d vulkan xinerama xml -capi -cups -custom-cflags -dos (-ffmpeg) -gphoto2 -gsm -gssapi -kerberos -lcms -ldap -netapi -odbc -opencl -osmesa -oss -pcap -perl -pipelight -prelink -pulseaudio -realtime -run-exes -samba -scanner -sdl (-selinux) -test -themes -udev -udisks -v4l -vaapi -xcomposite" ABI_X86="32 64 (-x32)"
CFLAGS="-march=znver1 -O2 -pipe"
CXXFLAGS="-march=znver1 -O2 -pipe"
RE: 2019 Reassessment
by Chiitoo on Tuesday January 8th 2019, 8:55
Just remembered that it's not too long from now, when I did experience some rather random-like crashes myself... but they were very rare, so I'm not too certain it could have been what you are seeing. It very well might have, however.

I haven't seen them in a while now though, so I'd definitely encourage you to at least try with rc5 via the 9999, or wait for the 4.0 release for a re-reassessment. :]

Also, if possible, try Wine-Vanilla as well (which I mainly use for FFXI, so there might be things happening with Staging that I know not about).
RE: 2019 Reassessment
by Pandoraxero on Tuesday January 8th 2019, 7:49
The problem appears to be less consistent, but more widespread, than my initial tests implied. The cutscene for leaving the castle in San d'Oria also seems to trigger the issue. what's worse, when trying to get more output from winedbg using the "Program Error" window, it brings up the window... but I can't interact with it. I can go for the slightly more risky proposition and run wine-9999 in Gentoo, but results from that don't count as actual test results, since it's not an actual version.
RE: 2019 Reassessment
by Chiitoo on Tuesday January 8th 2019, 7:54
You can usually use 'EGIT_COMMIT' to get a specific tag with the 9999 versions, or use the Wine-specific ones we have.

See for example:
RE: 2019 Reassessment
by Chiitoo on Tuesday January 8th 2019, 7:57
Way to submit early, me.

Of course it would be best to use an officially released version from the official Gentoo ebuild repository, instead of something from an overlay or the 9999, but I just wanted to mention these tricks since we do indeed skip release candidates, and since there seem to be users wanting to test using them. :]
RE: 2019 Reassessment
by Pandoraxero on Monday January 14th 2019, 11:01
I used this method to get rc6. Or perhaps... git rc6? Because I'm using git.... right? ...geez, tough crowd...
I'm not going to review it because I still have the same problems.
Thought I saw one post where you asked what nvidia-drivers version I'm using... probably been deleted, since I don't see it anymore, but in any case, I'm using 415.23. looks like 415.25 is available, but I don't really think this is an issue with graphics, since the issue is intermittent, with no guaranteed means by which it can be made to present itself... aside, perhaps, from repeatedly HP warping. and it's not just HP Warping that causes it.

Now, I should note that I'm NOT using the WINEARCH variable... so I'm not sure whether or not that has anything to do with it. Debug info shows Platform: i386 (WOW64)
Should I try running it with the WINEARCH set, or is that just my, uh... suspicions from past testing talking? Because as I recall, the game didn't ALWAYS work without setting WINEARCH. ...And I've been on the FFXI/Wine effort for over a decade.
RE: 2019 Reassessment
by Chiitoo on Monday January 14th 2019, 19:30
The comment is still there ( ), a bit towards the top from this one. We've got multiple 'threads' of replies going on here now, which is probably why it got “lost”. :]

I'm not blaming the nvidia-drivers (yet), just comparing out set-ups so as to get a better idea of what might make the difference.

I have been mainly using a 32-bit prefix, but I'll create a WoW64 one to test this out. I should actually have one around already, as I was mainly using that before creating this to test something else... I don't remember having issues with it before, aside from something during the installation phase, way back.

With regards to Home Points, I tend to make use of them extensively while doing Ambuscade, every few minutes or so, so if it's triggered by something during changing areas for example, I definitely should be hitting it too.
RE: 2019 Reassessment
by Pandoraxero on Tuesday January 15th 2019, 1:23
Okay, I see it now. Yeah, musta got lost.

I'll try with a new WINEPREFIX and WINEARCH=win32
This may or may not help depending on the actual nature of the issue, but it's worth a shot. If it does help, I won't be able to rate the game as platinum because of the workaround.
RE: 2019 Reassessment
by Pandoraxero on Tuesday January 15th 2019, 6:01
I was almost convinced setting win32 did the trick. then I talked to the NPC to zone out of the castle in sandy. I don't know what it is, but SOMETHING is causing issues here. WINEARCH=win32 seems to make the game slightly more stable... but when things like this happen, it raises a question.
I get the following output:
0031:err:d3d8:d3d8_device_upload_sysmem_vertex_buffers Failed to update buffer (I don't have timestamps enabled so I'm not sure if that has anything to do with it)
wine: Unhandled page fault on read access to 0x00000120 at address 0x79ee23f0 (thread 0135), starting debugger... (and the debugger doesn't start. It must have crashed PRETTY HARD.)
RE: 2019 Reassessment
by Jeffrey K Berhow on Sunday January 27th 2019, 2:14
This is what I got when the first portion of the Lower Delfutt's Chains of Promathia cutscene ended.

0009:err:d3d8:d3d8_device_upload_sysmem_vertex_buffers Failed to update buffer.
wine: Unhandled page fault on read access to 0x00000084 at address 0x7cbfeb39 (thread 0009), starting debugger...
00cb:fixme:dbghelp:elf_search_auxv can't find symbol in module

In the Staging tab of winecfg, I unticked "Enable CMST for better graphics performance (deprecated)" and was able to get through the cutscene.

Everything seems to be working now.
by Pandoraxero on Saturday December 3rd 2016, 9:17
Just so everyone knows, I am one of the people who pushed for the imm32 sanity check patch (which saw this game go from Garbage to Gold) 8 years ago. I see this as a good time to re-assess the situation, and now I'm running Debian, with the intent of getting a clearer picture of the present state of this project on a base binary distro (which has forked more than any other distro, and most notably is the parent distro of the *buntu distros, and mint, among others)

After completing my assessment of the status on Debian, I intend to touch other base or near-base distros. My agenda currently includes Fedora (near-base), Slackware (base), FreeBSD (base, non-linux), and finally, I will be re-assessing the situation with Gentoo (base, though I suspect Chiitoo may also be working this part of the operation right now).

At each step, I'll be providing test results, and writing a How-to. The test results will be published, but the How-to will not be finalized, let alone published until I find an appropriate version of wine upon which to base it, and wade through the intricacies of each distro.

This will be a slow process, and could easily take 3 months, or possibly longer (I suspect FreeBSD and Slackware will be the hardest for me to work with, considering my lack of experience with them). I will be finishing up with Gentoo, since it's what I've been using for a decade. Essentially, these different distros will be taking me out of my element, for the sole purpose of achieving a fresh perspective on the status of this particular game on wine as a whole, rather than its status on just one distro.

If I'm not covering your distro of choice, well... I'm sorry, but I don't have time to touch on every single *buntu, *BSD, and all the numerous forks of Debian, Red Hat, and Slack. I'd be working this piece for another 8 years if I did that. My goal is to evaluate distros which have demonstrated, and continue to demonstrate, longevity. This essentially means base and near-base only.
RE: Re-assessment
by Michael D on Wednesday December 7th 2016, 8:05
Your work is much appreciated. I will also be submitting tests again. Hopefully I can contribute, rather than just create headaches for you.
RE: Re-assessment
by Pandoraxero on Wednesday December 7th 2016, 9:59
Well, so far, fedora's giving me nothing but a truckload of derp on install, complaining about missing mono and stuff. I got what I believe to be an effective-enough workaround. I've been tried and tested, but I won't accept defeat. (Bonus points if you can name where that line's from, without googling it.)
RE: Re-assessment
by Michael D on Wednesday December 7th 2016, 10:16
I had to do a winetricks dotnet20 in a 32 but prefix to get it installed on kubuntu 16.10
I'll be reactivating my account to test fully, but pol updated fine.
Sorry I can't place your reference. However, for when the day is long, forever carry on.
RE: Re-assessment
by Chiitoo on Thursday December 15th 2016, 3:49
Which installer were you using?

I only needed to set the reported Windows version to 7, when using the installer from the PlayOnine site (to get into the title screen, after the licence agreement). This is the only thing keeping it from being Platinum, but that should soon change, with the default becoming Windows 7 some time after 2.0 release. \ö/
RE: Re-assessment
by Pandoraxero on Monday December 12th 2016, 6:44
Well, I've stumbled upon the beast that is the reason I hold such disdain for binary distros... I'm co-posting this to the forums, but I figured I'd mention it here, too. This is on Fedora25. I think Fedora might have forgotten a dep or two...

bash-4.3$ wine32 C:\\Program\ Files\\PlayOnline\\SquareEnix\\FINAL\ FANTASY\ XI\\ToolsUS\\FINAL\ FANTASY\ XI\ Config.exe
fixme:winediag:start_process Wine Staging 1.9.23 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on
fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
err:d3d:match_fbo_tex_update FBO status 0x8cdd
err:d3d:match_broken_arb_fog FBO status 0x8cdd
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0
bash-4.3$ wine32 C:\\Program\ Files\\PlayOnline\\SquareEnix\\PlayOnlineViewer\\pol.exe
fixme:winediag:start_process Wine Staging 1.9.23 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
err:d3d:match_fbo_tex_update FBO status 0x8cdd
err:d3d:match_broken_arb_fog FBO status 0x8cdd
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0
RE: Re-assessment
by Pandoraxero on Tuesday December 27th 2016, 1:56
I have recently come to the conclusion that this game is, in fact, easier to install and run in wine... than it is on Windows 10. There's been enough people complaining about Windows 10, and this most certainly confirms that there is good reason behind the near-unilateral hatred Windows 10 has been getting... and continues to get. Wine has been getting consistently better over time, but catching up to windows has been a cat-and-mouse game for over a decade. As resentment towards the newsances (see what I did there?) of higher and higher Windows Versions grows, I think people will eventually start looking for a new OS... but then I said the same thing a decade ago when Vista had its RTM, and the net change so far has been negligible, although the non-GNU, yet Linux-based, Android OS is showing a substantial market success.
Japanese input?
by GF on Thursday September 8th 2016, 13:08
Is anyone aware of a way to get Japanese input working? My locale, keyboard, and FFXI client are in Japanese, and I can read what others write, but cannot type back in Japanese. When I write in Japanese the usual prompt appears below the FFXI window, but the characters themselves never appear in the FFXI chat log. I'm on wine 1.8.4 and have also tried this with the English client.
RE: Japanese input?
by Chiitoo on Thursday September 8th 2016, 13:24
As far as I'm aware, it should be possible only in the Japanese client (without modifying the client).

That said, I've never even tried to input Japanese into an application running via Wine, only native Linux applications (via uim), and as such, I don't have any immediate ideas on what the issue could be.

Are you able to input Japanese into other applications running via Wine?
RE: Japanese input?
by GF on Thursday September 8th 2016, 13:38
I hadn't actually tried before.. but just did, and can enter Japanese text in fine with WINE's Wordpad.
RE: Japanese input?
by Chiitoo on Thursday September 8th 2016, 13:53
OK that's very good to know. If it works in other applications, it would seem to me that it might be time to open up a bug!

I don't have the Japanese client, so I can't help by testing this myself... although I guess I should be able to get it from the official website nowadays, and there we go, downloading it now.

I'm not sure when I'll have the time to do it, but I'll give it a go.
RE: Japanese input?
by Pandoraxero on Monday December 12th 2016, 9:20
The last time I tried it, which, as you probably guessed, was 8 years ago, it DID NOT work. The game would run, but switching to Japanese input did not work, presumably because the IMM/IME was not 100% compatible with what the JP version was expecting. That may have changed, though. It was a real bummer for me back then, as, in addition to college classes, I was using FFXI as a platform to get a better grasp on the Japanese Language. The download from the JP site is, of course 100% legal... though 8 years ago, it did not exist, so I had to pirate the Japanese version, if getting a disc for an MMO that requires a user account and monthly payments can be described as "piracy"...

Operating off my knowledge from Windows: notably, Final Fantasy XI itself fully supports Japanese input, regardless of region, it's just disabled by detecting what PlayOnline version is being used (which explains how windower made it work on US and EU versions. Its IME plugin alters that part of the detection, but leaves it so that the ingame text is still in... whatever native language. I think the only options were EN, DE, and FR). So you don't need to reinstall everything, just PlayOnline. You can use registry hax to migrate your US, EU, or JP settings, verbatim, to any other region, that way you're not wasting drivespace (Which, 8 years ago, was NOT CHEAP)
RE: Japanese input?
by Chiitoo on Thursday December 15th 2016, 0:10
Apologies for the delay!

I finally put some time into trying this out, and while it took a while for me to figure out, it seems to work at least in the PlayOnline Viewer.

In short, have 'app-i18n/uim' (Gentoo package naming) and its dependencies installed, have 'uim-xim' running, and start the application with XMODIFIERS="@im=uim" set (either on the command-line, or exported for the shell).

I can then switch the input method via the global hotkeys set via uim settings.

The IME controls on the lower right part of the screen don't seem to be usable for me though. It did curiously say 'ON' before I got it working. Now when I have it working, it says 'OFF'. :]

The fact that it does work in Wine notepad there, but not in-game is curious as well. Regardless, I hope this will be of help. If you can confirm that it does work for you in PlayOnline Viewer as well, but not in-game, let me know and I'll test that out as well (may test it anyways at some point, as it shouldn't be too big of a deal to update the client with my already up-to-date files).
RE: Japanese input?
by Chiitoo on Thursday December 15th 2016, 5:08
Bäh! I knew it was too easy.

Does not work in-game, at least not yet. Now that I think about it, it does make sense, because the Japanese Input Method is more or less built-in to the game client, as far as I understand it, and it's not even possible to paste text into it. This may explain why 'uim' works for PlayOnline Viewer, since it's possible to paste text into that.

I feel it may require considerable work to have it working in-game, via Wine, but I will hope I'm wrong... :]
RE: Japanese input?
by Pandoraxero on Thursday December 15th 2016, 8:56
You are correct that it is built in to the game itself. My best guess is that such a method was required for cross-compatibility between PS2, PC, and XB360, but the console versions have been decommissioned, so those are hardly relevant. I think Ganiman and I were trying to get it to work 8 years ago, with some assistance from Aikar (makes sense, as Aikar was partly responsible for the Windower project). A fruitless endeavor, but things may have changed in 8 years.

If it weren't for Aikar, I would have likely never figured out that the JP version of PlayOnline could be used with a NA FFXI install. I'm all but done testing on Fedora. I still have Slack and FreeBSD to go, then I get Gentoo back in its place for testing, then test with Knoppix, then back to Gentoo to see if I can give JP input the old college try.
WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Megas of Vecanti on Friday March 21st 2014, 14:54
About 0.5% of the time, correctly pressing your stick in the direction of an arrow will cause the game to crash. (Both instances resulted from pressing a silver arrow; unsure if there's any correlation.)

Tested at the moat North of the entrance to Port Windurst in West Sarutabaruta while using the Carp Route for skillups. (One RoE (Reel In Small Fish I) was active, though it probably had nothing to do with the crash.)

I've crashed twice. Both stack traces ended up being identical to each other and both resulted in the culprit being:
"0x012f1cf2: divl %esi,%eax"
Since the last few times we got a crash that involved ASM code, it was on the Test Server with unfinished stuff, _IT MAY BE THAT THIS CRASH IS IN THE WINDOWS VERSION AS WELL_. Further investigation is going to be required and if borne out, the bug should be reported to SE. Chitoo? You out there?

To warrant further investigation, the full stack trace:

Good luck. We'll need it. XH
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Chiitoo on Friday March 21st 2014, 16:11

I had this weird feeling, after seeing the huge arrows in a picture at the Japanese forums before the implementation, that they might be trouble.

I have not had any crash happen yet, but I'll see if I can't lure it out.

I've actually been fishing quite a bit during the past few months myself! Got the two best rods and skill from 45 to 93, so the adjustments were something I was looking forward to quite a bit.

As a side-note, with regards to “moving the mouse cursor off any side of the FINAL FANTASY XI window can often cause the mouse input to endlessly move in that one direction”, I'm wondering if that's not the 'screen-edge panning'? (Config, Mouse/Cam, Screen Edge Panning...)

I can't remember at this time if it's possible to have it 'stuck' like it oft does with Wine, but I would guess so (would need to confirm, however).
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Megas of Vecanti on Friday March 21st 2014, 16:55
For best replication, try to fish in that moat I talked about and start "Reel In Multiple Small Fish I"; it seems you're almost guaranteed to get that crash by at least midway into the second repeated objective.

Good luck! (Still 20-something and I have to get skill on Dark Bass now...Which isn't happening so I'm considering moving on to the next location. I need me that Shaper's Shawl. /sigh)

Oh wow...I didn't even know that setting existed. I'm ashamed. XD I turned it off; will monitor what happens over the weekend. Thanks!
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Chiitoo on Thursday March 27th 2014, 7:58
I've still not had this happen to me. I've not yet tried to go after your steps, however. I would need to use another character for it, since my 'main' one has “too high” of a skill so that the fish below level 60-70 take their stamina down by themselves pretty quickly. ^^;

I have, however, been fishing cave cherax and liks a bit, and have yet to experience the crash. Matsya seem to be impossible with my skill level after the change (was easy before, just more rare to catch one than now, it seemed). Perhaps the mooching will help...


Someone posted this at the official forums:

If the post does not exist at some point, it was about a divide-by-zero crash during fishing. I suspect it may well be removed due to the more or less obvious violation of the user/software agreement, and/or terms of service, that may or may not have been occurred to get that data.

Either way, I probably guess that it may indicate the crash indeed happening within the natural habitat, too.

I'll still try to put some time into trying to get it to happen here, and possibly see if a temporary fail-safe could be created.
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Megas of Vecanti on Thursday March 27th 2014, 11:11
Hmm...SE may actually overlook the means of obtaining the data given the nature of the bug. We'll see.

Either way I suppose this'll be fixed in April at the latest. Good catch! It really does seem WINE is getting to emulate FFXI bug-for-bug now. XD
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Chiitoo on Thursday March 27th 2014, 11:24
I forgot to do this earlier, but I also checked the Japanese side of the forums. I believe the issue has been reported there as well, and has been moved to 'Confirmed/Planning to Address'.釣りをしているとエラーで落ちる事がある
RE: WARNING: New fishing system (March 2014 Version Update) will occasionally crash the game
by Megas of Vecanti on Thursday March 27th 2014, 11:31
That conclusively settles it, then. We'll probably have an Emergency Maintenance in the next couple of days. XD

[Close Ticket]
WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Tuesday August 20th 2013, 23:13
As you may or may not know, the 08/20 Test Server update enabled a preliminary version of the new, revamped PC UI talked about at VanaFest last year. You can enable it by going into the Test Client's ToolsUS/FINAL FANTASY XI Config.exe, scrolling over to the "Misc." tab, and checking the box next to "Enable New UI" at the bottom.

Currently, though, it's unusable on WINE 1.7.0: the game crashes with an Unhandled Exception ("divide by zero in 32-bit code (0x022dd4ba)"; "0x022dd4ba: divl %ecx,%eax" according to the dump below) right after it draws the first new UI element (the right-facing arrow which would be next to the "Accept" option) on the "rules of conduct" disclaimer screen.

Any people in a position to fix the bug will want the full crash dump with symbols enabled, which is here:

This obviously needs to get working: good luck to all of you willing to make it work ASAP!
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Thursday August 22nd 2013, 6:17
Indeed. I put about 12 hours of staring at relay and other traces as well as the Wine code, and while I am quite confident I know why the crash happens, I haven't been lucky enough to stumble upon a fix. I also don't know enough to fix it myself without some help, and wasn't lucky on that at IRC.

My content ID will become inactive in a day (if it's not already), so I wont be able to test it more. :/

In short, it looks like being pretty much what bug 20847 describes. It looks like it's looking for the Alps Condensed font, uses AR PL UKai CN instead, and there are being zerœs returned (I tried different fonts, even the Alps Condensed, which it wouldn't use even.

Just some quick thoughts before thunderstorm breaks things.

Good luck!
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Thursday August 29th 2013, 17:53
Heh, I guess staring at code and backtraces for a few days sometimes yield some sort of results:
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Sunday September 1st 2013, 20:33
Wow, nice detective work. That fix should be pushed upstream ASAP; bug the IRC channel. XD
Can I get that fix in the format of a diff/.patch file so we have something to link others to?
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Pandoraxero on Monday September 2nd 2013, 17:57
Agree. We... or rather... the wine devs... need a patch file to work with.

Megas, Chitoo? the two of you are starting to remind me of myself and Ganiman about 5 years ago... Those were good times... in either case, enjoy your cheesecake.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Tuesday September 3rd 2013, 23:40
Hey, stop acting like this is over. XD It won't be until 20847 is legitimately fixed and the new UI can actually work out-of-the-box. If we can get past this hurdle, it _should_ be the last major change to the FFXI client until such time as SE cuts the PS2 cord and goes full DX9. (And we can concentrate on those remaining graphical flaws which may or may not be WINE's or SE's fault.)

Stay frosty.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Pandoraxero on Wednesday September 4th 2013, 9:07
In my experience, it's about the closest thing to nailing a bug. We have the solution, now we need a diff/patch, and need to popularize the diff/patch such that enough people KNOW about it, and it starts gathering attention from the wine devs. That's what Gani and I did... that's the reason you see the ratings on this game jump from garbage/bronze to silver at around this time 5 years ago. I called it cheesecake soon's the third person came in rating it silver.

Unfortunate part with this one, though, is that we don't have a sudden, otherwise inexplicable jump in the game's ratings to draw attention to it. The IRC method may be the most viable.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Monday September 9th 2013, 11:35
Sorry for the late reply.

Making patches is trivial, making a real fix is another story. I don't believe this is a proper way to fix the issue(s), as it's simply forcing a returned 0 into a 1. It doesn't cure the cause, and I highly doubt it would ever go into the Wine tree (that is, I don't think Julliard would approve, and I don't think I would either!).

I guess the actual issue lies within the code of FINAL (or FAINAL, heh) FANTASY XI Online, and I'm not too sure they will ever fix it, as it's likely not affecting Windows. We can find a graceful way to deal with it, something like replicating a bug, or insane behaviour, rather.

I made sure with Austin at IRC that they, too, think that it's probably not worth a new bug as it's very similar indeed to 20847, and they will probably be handled in the same way,.. eventually.

Anyblue, since I stated the patches would be trivial to make, I guess I should deliver some, if you really really want me to! Had to do a bit more since there seems to be regression in git since few days ago, namely the commit:

I also found an additional crash when opening the job-selection window. Quick trace and just as I guessed, it uses the glyph 3000 as well (added it to the patch).

Furthermore, one additional patch for Gentoo, as the latest versions (including 1.7.1) do not build before this bug is handled:

Patch to work around the division by zero for wine-1.7.0:

Patch to revert the msxml changes for wine-1.7.1-158-g88c2a18:

Patch to revert regression inducing changes for wine-1.7.1-158-g88c2a18:

Patch to work around the division by zero for wine-1.7.1-158-g88c2a18:

And finally, an all-in-one for wine-1.7.1-158-g88c2a18:

Note that I'm not aware what sorts of issues these patches could possibly cause, so do use them at your own peril. ^^;

I did try to make sure to test them all individually, so they should be OK concerning their functionality, but I seem to have a habit of making weird mistakes like forgetting parenthesis somewhere or something like that, So if something doesn't click, apologies for that in advance from Dragoy (of Fenrir)!
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Friday September 20th 2013, 11:46
I brought up the “regression in git” matter with the Fellow with Strings and as of:


Patch to revert regression inducing changes for wine-1.7.1-158-g88c2a18:

is no longer needed.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Sunday October 6th 2013, 19:52
Tested on vanilla 1.7.3-144-g6d03ce8 off of git. Awesome job! It's buggy and slightly crash-prone (in ways that make me suspect that the UI code itself is at fault) but it does work as advertised.

I need to know how we can get the UI font working, though--It defaults to Times New Roman. Is there any way to get WINE to parse that Alps Condensed font internally?
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Monday December 30th 2013, 7:53
Toadally forgot I didn't reply to this yet. Sorry!

Firstly, not that I have tested it too much (very few times have I logged on the test-server after the divide by zarrro bug), but the while I did, it didn't crash for me after the fix.

Are there any specific things you experienced that with? I feel as if the new UI might not be working too much different from the old one in ways, as there's quite the performance drop when it's visible compared to how the game is running while it's hidden.

I should like to test it on Windows, but I've been too lazy fer that.

As for the font, I'm not entirely sure what it would require for Wine to use it. I merely tried copying it in, and even removing the ones it looked like it was substituting it with, but it would simply use another one instead (perhaps it didn't seem like a valid candidate for some reason).

I didn't look into that any more than that, and I haven't been hanging out in the IRC lately, but I'll definitely make a note of it here if I ever get to it!
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Monday December 30th 2013, 10:04
Yeah, the only issue for me is the font--the internal Alps Condensed is completely ignored and the new UI defaults to 8px Times New Roman. It seems to work fine except for that.

The font that WINE saddles the UI with is barely readable. It really warrants investigation. Haven't tested the UI extensively after the recent Test Server update, though, so at the moment I'm unaware of any new issues.

(If all goes well, BTW, I'll be submitting a new general test result in a few days.)
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Thursday January 2nd 2014, 16:13
Well, against my beliefs, I've solved the mystery. Or so I maybe think.

I'll try not to go on for pages about what all I did during the few days I looked into it, as it was very much a learning experience; new grounds for me, so to speak.

So... after I confirmed that no matter what I did, 'AR PL UKai CN' was chosen for me, as was the first time I looked into this a bit, and if that was not available, then another one from the arphic fonts was used. It was chosen even if I forced substitution via the registry (more on this later on).

When I noticed that, I started to look more into the 'Alps Condensed' font itself. Fontforge immediately reported various errors, ones that which might cause Windows to ignore the font altogether, so I fixed things here and there to no avail.

As I was testing the font in Notepad, where it worked(!), I noticed that the charset that was requested for it was 0 there, while FFXI requests 128. As one might suspect, this seems to refer to SHIFT-JIS (if I understand things right).

See where I am going with this yet?

Earlier on, I was looking at the images at the official forums ( ), and comparing the font in them to 'Alps'. It was quite clear that in those images, the font is not being used either! The 'G' and 'R' for example give it away very quickly.

I suspect Windows rejects the font as well, since it has no support for the 128 charset (or it's broken; can't tell for the time being). It sort of looks like a mix of 'Arial' (Arial Unicode?) and 'Times New Roman'... or something like that.

I believe I confirmed this all by hacking on the Wine 'freetype.c' a little bit, making it so that if it sees the particular font, and codeset 128, the DEFAULT_CHARSET would be forced.
This allowed 'Alps Condensed' to be /finally/ used, but any Japanese that still is around in some menus would be seen as 'blocks', as I more or less expected.

It's possible to substitute 'Alps Condensed' without altering any actual code, as long as the font used has support for the 128 charset, such as 'MS Gothic'. Earlier I had only tried 'DejaVu Sans', which was the first and pretty much only font that came to my mind without thinking about it further.

For example:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]
"Alps Condensed"="MS Gothic"

So all in all, it would seem to me as if Wine is actually doing things correctly here. Which font it chooses varies with what is available (arphic fonts likely being on the very top). I guess they haven't decided on the font at the SqEX side yet.

Japanese character display is of course desirable due to the fact that there be Japanese players around on the same servers.
I guess they should look into another font... though who knows; perhaps one will be able to select from several, but I guess I might even report this at the official forums. Not that they'll think much of it, I'm sure.


That's all fer now, methinks.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Thursday January 2nd 2014, 17:13
Interesting stuff. MS Gothic seems to be close to what SE was using in the screenshots, though the antialiasing makes it a tiny bit difficult to read (regardless, a massive step up from AR PL UKai CN!). Otherwise I think you've nailed it. Thanks!

BTW: for people who don't want to or can't download Windows corefonts, monafont ( ) seems like a suitable alternative as it's a spitting image of MS Gothic (probably by necessity, as monafont's targeted specifically at recreating 2ch ASCII art).

Also: is it just me or did the new UI reduce the framerate by about 10 fps this update...?
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Thursday January 2nd 2014, 19:30
Aye, there should be quite a lot of options out there for CJK fonts.

I was going through what I happened to have, and I must say 'mikachan' looks pretty fun, and rather fitting!

I can't say if the FPS is worse than before. It has been a while since I visited after all, and I didn't spend much time with it. I can say, however, that similar to the old, current UI, there's a big impact on the CPU use and FPS coming from the UI in general.

With this new one it's rather big, too.

I'm wondering if it can actually be font-related'ish. I noticed that the font debug channel alone is able to bring the game to a crawl. One time I counted about 24 lines being repeated over and over so fast that the file was over 1 million lines long in... 30-60 seconds I believe it was.

I tried the old UI and some Counter-Strike: Source to compare, and while they do similar things, they do it quite a bit less. I do wonder if there might be a place for a performance improvement there, but I can't tell. It could be something d3d-related just as well.

By the by, opening key-items that haven't been checked before produces a segmentation fault here! I might guess it could have something to do with nvidia-drivers, as I seem to be having such an issue with Terraria as well with new enough drivers, but a quick relay debug look-see shows something about 'want to examine the key item?' and then speak of a 'data/ffxi_menu_window.png', which I can't seem to find...

A missing file altogether?

RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Thursday January 2nd 2014, 19:54
It's altogether possible that the framerate reduction is the result of font issues. I can't personally tell at the moment.

And yes, I just recreated the crash and the backtrace points to "0x040a0000: movb 0x1(%ebp),%dl" as the culprit. If you have something similar then I can assume it's the same thing.

(And BTW: unless you have something to decompress and search the .dat files, most likely you won't find that image. I doubt SE would leave anything out in the open.)
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Thursday January 2nd 2014, 20:21
I don't actually get a backtrace as you seem to. It just very quickly segmentation faults away before anything like that is produced.

As for the files, yeah, I don't tend to do /that/ sort of mining, but the references seemed to be to an actual png-file, possibly under one of the data paths under PlayOnlineViewer installation path where one can find some menu files in png form, though they don't quite seem readable.

You might be correct though.

I also did a file-check to be safe on having all the required files, but no problems were found.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Friday January 3rd 2014, 10:43
Confirmed key item crash on Windows, as well as Alps font not being used even if it is installed.

Also noticed that, in my mog house, FPS would go downwards to 20 or even slightly below (it's literally full (80 items) of event items from holiday trees to the spinet and nearly all of the statues etc., which is nice to see as I had imagined it to be a Wine thing mostly.

When playing with Wine though, I tend to force the CPU to do things a bit more so I actually might get better performance when using Linux, it seems. ^^
It's been about 3-4 years since I last played FFXI on Windows, so I wouldn't remember (I believe last I booted Windows at all was on 15th of June; but it was useful today, although it failed updating itself, but I digress).

So, sum-summarum: Windows does not use the Alps font, 'key item crash' is not Wine related (working “as intended”), and performance drop induced by the UI is also very noticeable when running natively on Windows.
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Megas of Vecanti on Friday January 3rd 2014, 20:34
Oh wow. Yeah, I guess both the crash _and_ the font issue need to be reported to SE on the official forums if they haven't already.

It's also gratifying to see WINE maintain a kind of performance edge. I'd long ago noted the difference in login speed between the few times that I'd logged in on native Windows and WINE--there's like a second-and-a-half reduction on WINE; barely noticeable but nevertheless there.

I guess that wraps things up until the next Test Server update. Kudos all around, man! Thanks for taking the time to boot into native Windows. XD

(BTW, there's actually _one_ issue that needs explanation: the Opening Movie. Have you ever gotten it to work? Supposedly it works if you use native d3dx9. Tried it and no dice.)
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Friday January 3rd 2014, 20:56
I didn't see it reported yet; not even on the Japanese side, and I only looked at some of the more recent posts the last time I checked. I remembered the recent update doing something with the key items, but I can't remember why, or what (probably nothing).

Will look more into it sooner or later.

(As for the Opening Movie, I can't remember my experiences playing it via Wine at all... Will definitely look into it, hopefully sooner than later, and will post a comment if I can find anything interesting at all.)
RE: WARNING: New UI on Test Server Client CRASHES FFXI on disclaimer screen!
by Chiitoo on Wednesday October 2nd 2013, 17:41
As of

this issue (division by zero) should be (properly) fixed, and from a quick test, it looks like it is.

Fer now, at least. ^^;
Gentoo use flags?
by Claquesous on Thursday June 27th 2013, 0:24
Can someone who is successfully using Gentoo amd64 please post their emerge output?

This is my output, but PlayOnline crashes before it even loads the GUI. The error seems to be out of dsound.

[ebuild U ~] app-emulation/wine-1.6_rc3 [1.5.10-r1] USE="X alsa fontconfig* gecko jpeg mp3 ncurses opengl perl png prelink run-exes%* samba ssl threads truetype udisks* xml* -capi -cups -custom-cflags -gphoto2 -gsm -gstreamer -lcms -ldap -mono* -nls -odbc -openal -opencl -osmesa -oss -pulseaudio -scanner (-selinux) {-test} -v4l -xcomposite -xinerama (-gnutls%) (-win32%*) (-win64%)" ABI_X86="32%* 64%* (-x32)" LINGUAS="en%* -ar% -bg% -ca% -cs% -da% -de% -el% -en_US% -eo% -es% -fa% -fi% -fr% -he% -hi% -hr% -hu% -it% -ja% -ko% -lt% -ml% -nb_NO% -nl% -or% -pa% -pl% -pt_BR% -pt_PT% -rm% -ro% -ru% -sk% -sl% -sr_RS@cyrillic% -sr_RS@latin% -sv% -te% -th% -tr% -uk% -wa% -zh_CN% -zh_TW%" 0 kB
RE: Gentoo use flags?
by Megas of Vecanti on Thursday June 27th 2013, 16:48
The emerge output would typically only help you in the event of a build failure. That isn't the case here--the issue here is most likely with the emulation, which means you need debug output from WINE itself.

Please enable debug symbols by rebuilding your current version of WINE with:

FEATURES="nostrip" emerge wine

Once it's rebuilt, run POL, request the debug output from the "pol.exe has failed and has to close" window as soon as it crashes. Copy the _full text_ of that output into the "New Paste" text field on and click Submit. Copy the link to the file you just made and paste it here. (Copying the entire debug output into a reply can flood out other messages and is advised against!)

The Backtrace section will most likely tell us where things went wrong, but the other sections may also hold clues.

Good luck!
RE: Gentoo use flags?
by Claquesous on Tuesday August 13th 2013, 19:36
I finally found some time to do this. Here's the link:
RE: Gentoo use flags?
by Megas of Vecanti on Saturday August 17th 2013, 14:54
The error that causes the unhandled exception is:

>0x7d7f1545 DSOUND_ReopenDevice+0xaa5 in dsound: divl %ecx,%eax

...So you're correct. The problem seems to be occurring when dsound tries to initially open the device and fails.

There are several ways you can try to fix this:

-Run winecfg _from the console_. From the Default Settings selection, confirm you can play the Test Sound from your current device. _When pressing the Test Sound button, note any errors in the console._ If the sound doesn't play it may be the Output Device you're using. Check your audio drivers, or try another device if available. Post any command line errors here if you get any.

Do the same from the pol.exe application settings, just to make sure. (You shouldn't typically have to change anything here--chances are that if the default audio settings aren't working, they probably aren't working with other WINE applications either.)

-In winecfg, check the Windows Version set for pol.exe. It should be "Windows 7." Set it to that if it isn't. (This may not have anything to do with dsound, but it might help!)

-In winecfg, Check Libraries from the Default Settings selection. If there's an existing override for dsound, check to see whether it's set to native or builtin--FFXI seems to play nicer with WINE's own builtin .dlls. If it is _not_ set to builtin in Default Settings, go into the pol.exe application settings and, if one doesn't exist, create an override for dsound. Set it to "builtin." (If one exists, set that to "builtin" instead.)

-If all else fails (NOTE: YOU SHOULD NORMALLY NOT _EVER_ HAVE TO DO THIS!): ensure all dsound overrides on pol.exe are removed, install the latest winetricks script and issue the following command:

winetricks d3dx9

This will install DirectX9 and make that version of DirectSound the default across all applications without overrides. See if that works.

Good luck!
RE: Gentoo use flags?
by Claquesous on Sunday August 25th 2013, 0:36
I took your suggestion and played with my audio settings in winecfg.

My audio settings seem to be a bit unique since I connect my PC directly to my TV via HDMI. This was something that took me a while to configure under Gentoo originally.

Anyway, I tried setting it I believe to HDMI 0, and lo and behold the game just loaded instead of my customary immediate dump. I then turned it back to System Default and it croaked again. I closed winecfg and loaded the game and logged in to make sure everything works (which it does).

The funny thing is after logging in I went back to winecfg and my audio is set to System Default and the option I chose isn't there anymore. As long as the game loads I don't mind.

I do notice at least one controller bug has been fixed, the audio seems to have less hiccups, and I'm sure there are many other fixes too, so I greatly appreciate the help finally upgrading to the latest and greatest wine.
Present Status - Glitches and Workarounds
by Pandoraxero on Thursday May 30th 2013, 10:34
The logout/shutdown crash glitch
-I've managed to isolate the cause of this glitch to something easily user-controllable... namely, the "show opening movie" option on the ffxi config. I have no idea why, but somehow, disabling this option prevents the crash from happening.

Crash after Disclaimer
-If FFXI loads, but won't get past the little disclaimer thing without crashing... you MIGHT be in WinXP mode. Try setting Win7 mode. It should work then

-If you're having problems with installation, specifically, if the installer is giving you a "1628: Failed to complete installation" error message, your WINEARCH is likely set to win64. This seems to be the default for 64-bit systems. To fix this, backup or delete your current ~/.wine and run WINEARCH=win32 winecfg. This will setup a new prefix that will run the 32-bit installers without flaw.

-In addition, the installers all seem to throw the same error messages to console towards the end, namely:

err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x80000002a
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2800-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2800-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2800-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2800-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2800-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108

...these messages do not seem to affect the install itself, as the game runs as well as it would on a similar windows system

Graphical Glitches:
-Specifically, the only graphical glitches that have stuck out to me are things like glow boxes (like fireplaces, or the entrances to the Bastok MH at night) extending beyond their normal visible bounds (does not affect gameplay), and other little things, like that little fountain kind of across from the L.Jeuno AH. Its "Water" displays outside of its normal bounds, too... but has no effect on gameplay.

Please, if you are testing this game, bear all this in mind... especially the win32 thing. This game does not deserve the garbage ratings it's been getting, just like the number 2 game on the top 25 doesn't deserve the "Gold" rating it's got. I seriously can't eat my cheesecake in peace knowing this game's fallen so far.
RE: Present Status - Glitches and Workarounds
by Megas of Vecanti on Wednesday June 5th 2013, 11:00
I've mentioned before that setting a native msctf.dll resolves the shutdown/logout crash for me. I've had "Display Opening Movie" enabled at the same time without any issues.

(Though the opening movie still doesn't display for some reason; this isn't something I can pin down since I'm not certain _when_ the opening movie is supposed to display on the PC version. A while back someone mentioned that some version of native DirectX through winetricks makes the opening movie actually work, but I've never seen that happen.)

The main issues that stand out to me now are the glow containers and, more importantly, the unfiltered textures: it's annoying to have to be in Adoulin at night and all of the street lamp glow decals look like they're 10x10. That _can't_ be right...
RE: Present Status - Glitches and Workarounds
by Pandoraxero on Wednesday June 5th 2013, 12:42
I tend to go for minimum overrides. It's better, in my opinion to have Wine run with NO overrides at all. And that's what I've managed to get. That's really the intent of Wine: to pretty much invalidate Windows' reason for existing as a desktop system. clearly, msctf and the dx subsystems need work. ...converting calls from DX to GL is not exactly an easy task to accomplish, either, and, frankly, I'm surprised wine is able to do it as accurately as it does in the first place.

Odds are, though, if there's a problem, the solution is probably something GLARINGLY SIMPLE. We solved the imm/ime bug in 2008 with a relatively simple sanity patch, which got committed sometime in 2009, I believe. Irony of that situation was, the cause of the problem back then, and the course of action needed to fix it were all outlined in simple terms on MSDN.

Clearly, a number of things have improved with the Wine project in general since 2008 when I came on the scene... or at least, the project in regards to FFXI.

The opening movie is unimportant to gameplay, anyways, but I'm pretty sure when I first played (on windows), it came on BEFORE the little disclaimer screen thing.

I'll look into the glow decals in Adoulin. I've already submitted two images showing box flaws (one glow box and one fountain/water box)

Really, the more images we can get that highlight the graphical flaws, the better. So if you can get a screencap of it, and submit that, it'd help a little.
RE: Present Status - Glitches and Workarounds
by Megas of Vecanti on Thursday June 6th 2013, 19:33
Hey, I just made this imgur album with a decent selection of the most prominent texture filtering issues. Hope This Helps:

I can totally understand why it's important to have an app running without DLL overrides (it's one of the official requirements for Platinum, after all) but from a realistic standpoint, I also want the game to work in the meantime--and it tends to be a very long time before WINE devs get around to sorting most builtin issues out. =\

And I understand that getting the Opening Movie isn't necessary to make the game playable, but it _is_ a feature of the application and therefore one that should be factored into proper emulation in the long run--plus, whatever's blocking the Opening Movie may be blocking other apps as well. "A rising tide favors all boats" etc..
RE: Present Status - Glitches and Workarounds
by Chiitoo on Thursday June 6th 2013, 20:46
I can't say for sure, but I think at least the

is actually how it is supposed to be (as in, you see the same while running the game in its native environment).
With that in mind, I think there is a good chance that many, most, if not all of that can be re-produced in Windows.

Have you tried that?

At least I seem to remember seeing the block-pattern way before moving on to Linux some 3 years ago.
My memory might well fail me though!

I'll try to look into the opening cinematic some time soon (I hope), and see if I can dig something up.
RE: Present Status - Glitches and Workarounds
by Megas of Vecanti on Friday June 7th 2013, 14:26
Well, I don't run Windows natively, but if these filtering issues happen on Windows as well...I suppose it just can't be helped, then. =\ Really not good.
RE: Present Status - Glitches and Workarounds
by Pandoraxero on Friday June 7th 2013, 19:36
Well. I know the thing with the clouds is in windows. As far as the lamps/lighting ... or the Vunkerl cloud textures... Never really paid attention to them on windows.
RE: Present Status - Glitches and Workarounds
by Pandoraxero on Thursday June 6th 2013, 20:56
Hm. I see your point on the filtering... The clouds, though, I've noticed that same thing looking UP at the clouds in Konschtat back in 2005... on Windows. So that's more of a game issue and less of a wine issue. I'll have to get access to Adoulin and swap out my drives so I can see if the same thing happens in Windows with the light decals, though.

And I see where you're coming from on the movie thing, too. There's two important factors regarding that particular issue. The first, and most glaring, is the crash if no DLL overrides are present and "Show Opening Movie" is ticked. The second, while not important to gameplay for this game in particular, is that the video doesn't display without very specific settings... and you're right in saying that it could negatively impact playability of other games... or worse, usability of other apps in general.

The imm/ime issue in 2008 was a simple fix. This one, though... totally different story. It's clear we're dealing with an issue across multiple dlls.

I'd hesitate to call it a cascading failure, too, though. ...But the only way to determine if it IS a cascading failure is to somehow get the video to play, WITHOUT the msctf override. If the video can be played WITHOUT that override, but the game still crashes on /shutdown, then there are two independent, connected, but non-cascading failures in the builtins. On the other hand, if the video plays AND /shutdown or logout works properly, then it's a localized problem with the DLLs responsible for playing the video - and a cascading failure.

I'm a network engineer by trade, so I understand all about cascading failures. wine is notably unstable... and I don't mean that in a BAD way, I just mean everything is under constant development. It's possible this could be an issue with BOTH system libs. on the other hand, it could be an issue with one, that's causing an issue with another, that's causing the game/POL to crash on exit - a cascading failure... I'll have to look into it sometime.
A few odd items and a thought
by Astrit Prower on Sunday January 18th 2009, 1:42
Amongst my latest test I found a few interesting items. The first was the graphics. I don't know how but FFXI looks crisper in WINE than a real windows install, not to mention faster loading. The POL viewer doesn't crash when I try to access my mail in WINE.

Again I don't know what it is, but some windows apps are running better in WINE the windows. This also applies for other apps I maintain.
Multiple instances of FFXI
by Peter Andersson on Thursday October 23rd 2008, 9:05
Hello everyone.

Today I added a small guide on how to run more than one instance of FFXI at the same time on the same computer.

If you are one of all the people that like to play more than one character at a time I believe you will find this most useful.

Right now there are several draw-backs with the guide and it's methods. They are, at best, crude. I will keep on improving them.

Main problem right now is that it seems there is no way around the fact that you need a separate copy of the new instance. This is because wine seems to put a virtual lock on the files of the first instance.

An optimized way to export the registry data would be to know exactly what data to export and then just process those registry paths. I will see what I can dig up. Maybe someone here knows exactly what needs to be exported.

All the best.

RE: Multiple instances of FFXI
by Peter Andersson on Thursday October 23rd 2008, 9:12
I should also add that I pruned the Install/Config guide to reflect recent progress.

Also performed some tests on a Intel C2D @3GHz 6GB of RAM and a GeForce 8600 GT GPU on Ubuntu Hardy. Ran two instances of FFXI on a dual head system. The result is very pleasing. I am happy to report that running one or two instances made more or less no difference in performance.

Take care,

Necessary hacks.
by Pandoraxero on Saturday August 30th 2008, 0:11
I've been working somewhat in collaboration with ganiman today. i posted my data on ffxiclopedia forums, and allakhazam. Here's a condensed version:

- POL and FFXI installations should work perfectly.
- Set POL to run in a window and edit the registry so that the window dimensions are 640x480 (C:\\Program\ Files\\PlayOnline\\SquareEnix\\PlayOnlineViewer\\polcfg.exe, HKLM\\Software\\PlayOnline[US|EU]\\SquareEnix\\PlayOnlineViewer\\Settings)
- when launching POL before or after the update, you may need to register a copy of dxdiagn.dll from a windows xp install and set dlloverride to native
- after the ffxi update, it will most likely fail to launch, what you need to do is open the FFXI config utility and set ffxi to windowed mode, then go to the FFXI section of the registry and edit 0001 and 0003 to your desired ffxi window width, and 0002 and 0004 to height. (C:\\Program\ Files\\PlayOnline\\SquareEnix\\FINAL\ FANTASY\ XI\\Tools[US|EU]\\FINAL\ FANTASY\ XI\ Config.exe, HKLM\\Software\\PlayOnline[US|EU]\\SquareEnix\\FinalFantasyXI)
- if there's a problem connecting to lobby server, and the problem's persistent, you need to set your hostname to localhost
RE: Necessary hacks.
by Pandoraxero on Saturday August 30th 2008, 0:14
Oh yes. forgot to mention, you can get it to run at full speed by selecting yourself (F1) and opening a menu (Enter) and entering a chat dialog with yourself (Enter)

After that, you can get regular keyboard input by activating a macro with a chat line. the default TP macro should do.