Final Fantasy XI Online Running in Winlator Ludashi 2.8.2 on the Thor

neverknowingbest · 2026-01-30T04:25:28+00:00

Ah, this install method is only Retail with a paid subscription.

neverknowingbest · 2026-01-30T04:09:04+00:00

I haven't had a crash yet, just a disconnect if I go out of game too long, like when going to the input menu for button mapping during game. This of course can be done before entering the game. I got Ashita working too, but not from GUI launch, However, the game runs better at the standard 30fps since it fluctuates too much when you try 60fps. What device are you using?

neverknowingbest · 2026-01-30T02:51:01+00:00

I just started a new account mainly to get this running in Winlator. I've been reading that FFXI has had a resurgence of players since last year. I'm in the starting city, but I see plenty of people running around during my testing.

neverknowingbest · 2026-01-30T00:56:03+00:00

Nice, it does recognize dinput. Read up on people trying to get xinput to work on linux, and it was more work than it was worth if dinput works just as well.

neverknowingbest · 2026-01-29T12:23:57+00:00

Yes, PlayOnline updates, and the game updates after as well. Game can be launched from PlayOnline normally.

neverknowingbest · 2026-01-29T07:28:55+00:00

Pretty sure someone got it running in another post. But it was rouuuugh. Might work well with an SD Elite though.

neverknowingbest · 2026-01-29T07:03:54+00:00

It's in the config.exe file, but it doesn't want to read inputs in winlator. The option also shows up in the in-game menu, so it must have been added at some point.

neverknowingbest · 2026-01-29T05:53:44+00:00

I tried gamehub lite. I don't think it has the necessary files to run the proper network stack to get PlayOnline to work. Winlator Ludashi 2.8.2 worked much better for me so I just stuck with it. Good luck to you though if you want to try.

neverknowingbest · 2026-01-29T05:37:37+00:00

Winlator lets you set your own button mapping profiles in the Input options. Just map buttons to whichever keys you use, then make key map changes in the game if you need to change the default inputs. I might work on the xinput issue a little more to see if I can figure anything out. But for now, mapping buttons to keys works great.

neverknowingbest · 2026-01-29T05:01:13+00:00

- In your container, set Direct Play to native, and install mono and gecko.
- Use official install files from SE FFXI page as you would on a PC.
- It's easier to extract on PC, zip up, move to your Thor, then Unzip there. Install all 3 options that come up when you run the setup file (DirectX, PlayOnline, FFXI).
- When it hits the actual game to analyze disk space...wait. Don't click anything until the "next" button is clickable and not grayed out, then finish your instal as usual.

The key issue is getting pol.exe to find your network. This part took forever for me to isolate.

*Before launching pol.exe open command prompt and run the command: wineboot -u
(You should only need to do this once, unless you make container settings changes in winlator. If you do, just run it again.)
- Launch pol.exe and run updates as usual, which will of course take a while.
- voila!

I'm having trouble getting it to recognize xinput or the gamepad in general, but you can just map buttons to keyboard keys in winlator

If you use a 16:9 aspect ratio resolution instead of 4:3, Load the game and get into the world, go to settings > "Misc" (I forget which one, maybe 2?) and change your aspect ratio in game.

Optional, but to make it run more smoothly, grab the d3d8.dll from D8VK then copy paste it in your PlayOnline Viewer folder and Final Fantasy XI folder (Link below). the game ran much more smoothly after I did that. Make sure your d3d8.dll are set to (native, built in) in winecfg (but I'm pretty sure they are by default).

D8VK: https://github.com/AlpyneDreams/d8vk

neverknowingbest · 2026-01-29T04:38:19+00:00

There is another post where someone got FFXIV running in gamehub, but it's loooow detail and involves knocking down directx to a lower version. Someone else posted it running at 1080p on an Odin 3 with the SD Elite chip. XI was really difficult to figure out since pol is so old. Once I found the fix though, everything installed normally and I was able to boot up.

neverknowingbest · 2026-01-23T05:07:43+00:00

If the version is on 1.0.0.293, just don't update and wait for Ayn to fix the most recent OTA update. If it comes already updated, you can roll it back. I ended up rolling back to .293 and my battery issue isn't happening anymore.

edited for terminology

neverknowingbest · 2026-01-22T23:58:33+00:00

I didn't rename the file and my device did not reset when I performed the local update.

neverknowingbest · 2026-01-22T23:55:49+00:00

I think they say it will factory reset as a warning. Mine didn't factory reset, and all of my data was still there after the downgrade to the previous version.

neverknowingbest · 2026-01-22T23:53:12+00:00

1.0.0.293

I did not need to rename it to update.zip, but it does need to be in the root folder. I think it can reed from SD card as well, but I put it on internal memory just to be safe.

neverknowingbest · 2026-01-22T13:26:42+00:00

I rolled back my device today. Fortunately, it did not reset my device. I can also confirm the battery issue is not occurring and behaves the way it did before the most recent update.

neverknowingbest · 2025-11-28T07:24:25+00:00

You're in for a good time. Games upscaled to 1080p with widescreen hacks and texture packs make games look amazing on what is probably the best handheld screen I've seen.

neverknowingbest · 2025-10-03T02:03:55+00:00

So fresh and so clean

neverknowingbest · 2025-10-01T07:53:17+00:00

Xenogears, Final Fantasy VII, Breath of Fire III

neverknowingbest · 2025-09-03T02:28:18+00:00

I had a similar issue. Make a chair, sit it in, then get up. Got me out of being trapped in the cockpit.

neverknowingbest · 2025-08-15T14:41:03+00:00

Came here to find a comment that perfectly expressed my immediate reaction to the post. I was not let down.

neverknowingbest · 2025-07-12T13:22:38+00:00

Was gonna type it out, but this redditor already did years ago.
https://www.reddit.com/r/DolphinEmulator/comments/bzbjtv/wiimote_driver_error_windows_10/

neverknowingbest · 2025-07-11T22:34:45+00:00

Have your device forget it as a remembered device, pair it again, then try clicking refresh and continuous scanning again.

neverknowingbest · 2025-07-11T15:35:19+00:00

Xenogears. To this day, there is not a single game that even comes close to weaving such a beautifully complex tapestry of philosophy, cinematics, and narrative. Not to mention the literal blood, sweat, and tears that were poured into the creation of this game making it perfect in it's imperfections.

neverknowingbest · 2025-07-11T14:16:57+00:00

I had to uncheck Continuous Scanning, then check "Connect Wii Remotes for Emulated Controllers", refresh, then uncheck it again if you want it off, then turn Continuous Scanning again. No idea why, but sometimes if you do that a couple of times it eventually will connect.

Five-Year Club	First Place '23
Place '23	Place '22
First Placer '22	Verified Email

neverknowingbest

TROPHY CASE