May have to wait
by Zak on Monday February 25th 2013, 10:41
The game and lobby servers are slammed at the moment, I am getting "World is full" errors and "can't connect to lobby" errors. I will try and test more later when things have calmed down. I am on 2 servers so I have 2 chances to test after slots open up again.
by Michael D on Saturday February 23rd 2013, 1:43
Just a quick reminder about the Non-Disclosure Agreement, we may not post any... ANY screenshots of the program until the NDA is lifted. all submitted screenshots will be rejected until NDA ends. Thank you all for the hard work.
It's Alive ! !! !
by Chiitoo on Saturday December 15th 2012, 16:44
Well... more or less.
== Prequel ==
The very first time, I tried to let the installer go with the DirectX update, but this would eventually lead to a DirectX error (scrambled text no doubt due to missing fonts). Probably the same error that was described in the first test result.
I'll try to describe the way I went in short, and as accurately as I can remember as well as without violating the NDA. This much should be OK... I'd imagine. I did do it all spanning over a few days, so memory faults may occur, but I did just go through the steps again while writing, so they should be quite spot-on.
I'll also leave a short summary to the bottom for the impatient.
The goal was to start with a clean prefix, and use winetricks as little as possible (the majority of the dlls required don't seem to be available via winetricks yet as far as I understand).
Using the default win64 installation comes to a wall when Internet Explorer parts are needed, and winetricks does not want to install ie8 onto a win64 installation (I haven't looked around if there's a way... around).
So with that said, a win32 prefix was used.
== DirectX Needs to Be Updated ==
The following dll-files were needed to get past the DirectX update-wants of the installer (from Windows 7 SysWOW64):
The installer's splash-screen doesn't show up properly, but I didn't look into that yet. However, it should install what need be now.
== Version Check ==
Next up, a display of funky symbols dancing around the version check box. Albeit cool, one might want to install some fonts to actually be able to read some of these things. Corefonts will do the (wine)trick, but some more is needed for certain error boxes as well as to get rid of squares masking the password(s) instead of the round things. For Japanese, the CJK fonts are more or less obviously required. Personally, I used the allfonts method provided by winetricks. I did not feel like spending that much time into this particular aspect yet.
These fonts are not used in-game from the looks of it (I didn't install them into the test prefix that I ran this write-up with, and was able to see even the hiragana, katakana, and kanji properly).
The version check will also fail with , which can be remedied with winhttp override. I used winetricks for that since I'm rather sure it needs more than just setting the dll (thinking of urlmon and friends, as I did try just with adding winhttp).
== Launcher ==
Now one should have the launcher... er, launched, with or without fonts.
It will function in a bit of a weird manner, usually all or most of it being black before clicking somewhere inside it. Logging in will fail, with or without credentials, the error being something like: -2147467263.
If only they created a proper launcher, but no; we need Internet Explorer. This can be remedied with ie8 via winetricks. The screen will then also fully load without clicking around.
Just like in the old XIV launcher, parts of it will show up Japanese regardless of language choice. I suspect it has something to do with ie8, because they are browser objects after all.
Logging in should work now, and the download for the game files should start. When the download is cancelled, the launcher will (sometimes) crash. If it does not, it will return to the log-in screen, where the previously Japanese parts are now in English as well (assuming English was the language in use). The launcher also seems to occasionally select the wrong language (gone through them all at this point for me).
Weird enough, on Windows, the images for the links to the forum and official website were not displaying for me, while in Linux they work.
After the game is up-to-date, the launcher crashes with speak of the module msxml3 in the backtrace. Setting override from winecfg is enough (winetricks works as well, though).
== The Game ==
Next, the actual game-client will start, and rather spectacularly crash, which can be remedied by doing:
- wine regsvr32 xaudio2_7
Now the game is playable, however, the very first cutscene leads into the being stuck in the 'Now loading' screen. From ever since the title screen, the graphics are 'flashing' or 'blinking' occasionally. It's as if the overlaying graphics are 'gone' for a moment, or 'covered' by the background. The character selection screen's background is what can be seen flashing there. While in the loading screen, the actual in-game graphics are seen, and I am actually able to rotate the camera (but that is all as far as I can tell).
If WINEDEBUG=d3d (or relay) is used, the flashy blinking happens a lot less (which generates a lot of output, making the game run slow even if redirecting the output into a file). I did try probably everything that winetricks offers what comes to the settings, but nothing seemed to change this behaviour.
== Video ==
While I was stuck in the now loading/video part mentioned up there, I followed the ole:errors and buddies to the following dll-files, and I believe I actually got the video to play, I think. I couldn't see it, but I could hear the audio changing while the screen remained as is:
Override for quartz may or may not have been needed, I forget.
The unfortunate fact that it uses asf/wmv is obviously not fun. Actually, as I watched the opening cutscene on Windows 7, it didn't have the audio for the spoken dialogue (it did earlier on another machine, but perhaps they simply introduced a bug there in between). Perhaps it's the same reason for why the video that could be selected in the title screen of the first version of XIV didn't play as well (I never looked into it).
== General Thoughts ==
So, it is playable, if you can skip the video (play past it on Windows for example).
The flashing 'overlay' will continue in the game, which means that the user interface is occasionally 'blinking'. There are some times when it doesn't do it for a good while, but at other times, the graphics go quite nuts as if the GPU was melting! Makes an interesting 'laser-show' indeed. Generally it isn't that bad, though.
As for FPS, at quiet places, I can get to the maximum of 60 with decent settings. I believe it dropped to 20-30 with maximum. Away from the corner it would be around 10-15, but with a little less intense settings, I'd get up around the 30-40 mark for the busy times I believe. On Windows, my computer runs it at 60 for most of the time with high settings, but I forget how much it drops with maximum... I'll try to make more notes next time.
== System Info ==
- Asus ENGTX 275
- Mem: 8186144k total
== In Short ==
Short-list of steps ensues (omitting WINEPREFIX since that's more of a personal thing):
Borrow the following files from a 64-bit Windows 7 installation:
Inspect the opening cutscene more deeply (or alternatively, stare at the loading screen).
== Afterthoughts ==
So yeah, that about it for my experiences so far, I think. I did try running two clients at the time, which leads into a weird slowness of everything. CPU usage isn't bad at all, but I guess my poor little GPU is being torn apart (wasn't going any more hot than usual).
The blinky flashing seems somewhat familiar to me, as if I had read/seen it somewhere before, but I just can't remember.
I hope this will be of at least a little bit of help to someone, and I hope I didn't forget too much. I do feel like I did forget something(s), but oh well... there you have it.