This is the official release version; basically the `stable' branch. This version should have the most players available.

Current version number: v0.11.118.246723

Selected Test Results (selected in 'Test Results' table below)

What works

launcher (installing and updating)

What does not

launching the game

What was not tested

Additional Comments

Launching the game in a 32bit Wine prefix throws an error since the 32bit version of the game has been discontinued ( https://forums.station.sony.com/ps2/index.php?threads/game-update-6-17.227720/ ).
Launching the game in a 64bit Wine prefix either fails because of https://bugs.winehq.org/show_bug.cgi?id=38021 or crashes https://bugs.winehq.org/show_bug.cgi?id=38775

Acquire a native Win XP 32bit imm32.dll. You'll find it in C:\windows\system32 or in Service Pack 3 [see PS2 Forums for hints where to get one]

copy the imm32.dll to $WINEPREFIX/drive_c/windows/system32

run: WINEPREFIX=$WINEPREFIX winecfg

in the winecfg window go to the "Libraries" Tab.

There is a small input filed enter "imm32" (without quotes) and click add. In the list below there should now be a entry "imm32 (native,builtin)".

Select the new entry and click "Edit". In the window select "Native (Windows)". Close with OK.

Click OK to save and finish. You're done, you now can continue to install the other needed dlls and Planetside.

Troubles:

When you use a wrong or faulty imm32.dll, every program (including winecfg) will crash, giving you many error messages. In such a case you can revert the override by editing "$WINEPREFIX/user.reg". Use a text editor, not a word processor. Search for imm32, find the line that says "imm32"="native" or similar. Delete this line. Save the file and test if you can run winecfg now.

64bit:

If you happen to use a 64bit wineprefix you need to put the imm32.dll into "$WINEPREFIX/drive_c/windows/syswow64" and set the override in winecfg (step 7 above) to "Native then Builtin". If you put it into system32, 64bit applications will not work correctly.

ARCHIVED (Nov.23) --- Consolidated findings

Archived from Nov.23 - please add a new note if you have more current information, as many of the bugs listed below no longer apply, and there are newer bugs as well, which are not listed below.

Has anyone ever been able to run this in a 64 bit prefix?...
by joseph S on Tuesday June 23rd 2015, 11:28

As the 32 bit client is no more it looks like we are basically starting over here. It looks like everyone has been running it in a 32 bit prefix up to this point. It was running quite well in 1.7.45 32 bit. I am not able to find any clues online anywhere from any person able to run it in a 64 bit prefix.

And the game hangs on that point no mouse cursor, no sound, no ability to tab out / quit the game

I would love to have some way to fix that but I understand if nobody can
Wine 1.7.30 Planetside2 mouse jitter patch installed
All the winetricks from above
And a imm32.DLL from a winxp sp3 32bit install

Ever since the server maintenance on August 5th my hud and menus (login screen, map, options, loading screen animations etc) have been flickering. I could put up with the mouse jittering but this is extremely irritating since sniping is impossible with the Hud turned off.

I have played extensively using old hardware that barely plays the game, so I have experienced the jitter we are talking about for hours and hours. I am also an ex game developer so I have some behind the scenes experience.

The core of the issue is that the mouse input only occurs every several frames. Example: at 16 fps, it may only poll the mouse at 4 fps. The game seems to accumulate the mouse's input during the frames the mouse is not polled, so the entire movement of the mouse between pollings is used to create rotation on the frame it is finally updated. In other words, the game view rotates at an expected average rate, but does not rotate every frame. Several frames will have no rotation and then one will have the accumulation of the previous frames.

This bug of course makes it difficult to aim because there is not immediate feedback with which to view and correct input error.

As has been mentioned, the scene updates at a higher frame rate. This is viewable by using the keyboard inputs to move around and simultaneously moving the mouse. The world will translate at a higher refresh rate than it will rotate.

I find that around 30 fps gives enough mouse feedback to be reasonably playable, but I have noticed that the mouse refresh is still lower than scene refresh at 80 fps or more.

A theory I have about the vehicles having no jitter is that because their input is displayed through simulated acceleration and friction which is updated in the game, the polling of mouse input is still at a lower rate, but just hidden. I have developed this theory after having an exceedingly difficult time straightening an aircraft at lowish frame rates (20 fps). While the rotation of the aircraft refreshed every frame, it was exceedingly difficult to not overcorrect the mouse input -- the plane seemed to throw itself in any direction I tried to steer it.

Mouse Jitter the Unknown
by Michael Speth on Tuesday July 8th 2014, 20:28

Problem:
Rotating the Camera with the mouse causes a jitter

Details:
When using the mouse to rotate the camera while controlling a human (which is most of the game), causes a jitter in the rotation of the camera. Meaning, the camera does not rotate smoothly or even periodically. The camera rotates a few degrees in one direction and seems to move back a lesser amount of degrees in the other direction.

Consider a typical movement of 10 degrees clockwise. In order to get to 10 degrees in windows with a mouse rotation of 1 degree per 1 ms. Without mouse acceleration, the camera would take 10 ms to make the 10 degrees.

Now consider the wine version. In this example, for every 1 degree in one direction, 0.1 degrees are moved in the opposite direction (with a 1 ms per 1 degree assumption). This would increase the time to 11.1ms (0.9 ms per 1 degree). The effect looks like a strange jitter.

The hypothesis that low frame rates causes the jitter is incorrect.

Why?

Low frame rates only intensifies the behaviour described above. Low frame rates in a normal system would cause studdering (a start/stop behaviour). I haven't experienced this type of mouse jitter in a game before.

My Hypothesis:
I don't know the cause. The problem is with mouse input. Is it how the game handles mouse acceleration (if that's the case, why isn't mouse jitter present in tanks or turrets???)? Is the problem with wine direct input? I am not familiar with the wine code and we don't have access to PS2's code. Does PS2 use direct input even or are they using a different input system? I only think a wine developer could reasonably come up with a valid hypothesis. We can only describe the symptoms of the problem.

Progress on Mouse Jittering
by subraizada3 on Wednesday May 14th 2014, 17:49

TL;DR Wine is slow so the game can't get enough CPU so the FPS is low so there is mouse jitter. If the FPS is high, there isn't any.

I think I've made some progress on the mouse jittering 'bug'.

After checking my framerates (alt+f, then alt again), I discovered that I was getting 15-30 FPS at most times. I adjusted some settings, and started getting around 30 fps on ultra settings @ 1080p in VR Training (for some reason framerates go up as I increase my resolution...). The FPS meter was showing my GPU as the bottleneck.

When I went into large battles, the FPS dropped to around 10-15, and mouse lag increased. I found a spot in the warpgate where I got 70 FPS for some reason, and there was pretty much no mouse lag there.

I opened up nvidia-settings, and it reported my GPU usage at 45-55%. Maybe there are issues with loading the models/etc. fast enough...
I edited the UserOptions.ini to get 'true ultra' graphics, and my GPU utilization goes up to 85-90%. So that means with normal ultra settings, the GPU is either not the bottleneck, or something is stopping it from being used.

I set all graphics to minimum, and look at my FPS meter. FPS only increased by about 10 to 40 FPS, and now the CPU is shown as the bottleneck. I once again go into a large battle, and again my FPS drops to 15-20... on the lowest possible settings. Note that I have a GTX 680, under Windows this could get 60+ FPS in huge battles on true ultra settings. Since lowering the graphics settings does not affect FPS much, the bottleneck is clearly the CPU. Which is surprising given that I have an i7-3930k - 6 cores, hyper threading, 3.9 GHz max.
I forgot to measure the CPU usage in-game, but judging the Gkrellm charts, it was about 60% across multiple cores. Which means that the CPU wasn't being fully utilized (I will update this soon with more CPU information).

Overall, the mouse jitter is caused by a lack of FPS, which happens because the game can't get enough CPU power (which happens because Wine is slow).
At 60 FPS, mouse jitter is still there but the game is almost perfectly playable. At 70+ FPS, the jitter is pretty much gone.

Installed the usualy d3dx9_43, d3dcompiler_43 and corefonts. I was able to download, start, and even deploy. But when I'm in-game, all I see is the hud. This includes waypoints that move as I move my mouse around. But the rest of the world is just black.

I've tried the settings Very Low, Low, Medium and Ultra. On the lowest settings, the hud would sort of 'stick' to the background, cluttering up the screen with images of waypoints, icons and the like when I turn my character.

Still doesn't work with 1.7.18
by subraizada3 on Monday May 12th 2014, 21:14

I upgraded to Wine 1.7.18 on my Arch 64-bit installation (new 64-bit wineprefix).
As mentioned on the WineHQ page, I winetricks'd corefonts, d3dx9_43, and d3dcompiler_43.
Launchpad downloaded the game, and it works as long as the Wine Windows version is set to XP (if set to Win7, Launchpad crashes on launch).
However, when I click the play button to launch PS2, it gives this error:
[code]
err:module:import_dll Loading library XINPUT1_3.dll (which is needed by L"Z:\\home\\sub\\ps2\\drive_c\\ps2\\PlanetSide2_x64.exe") failed (error c000007b).
err:module:import_dll Library d3dx9_43.dll (which is needed by L"Z:\\home\\sub\\ps2\\drive_c\\ps2\\PlanetSide2_x64.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\sub\\ps2\\drive_c\\ps2\\PlanetSide2_x64.exe" failed, status c0000135
[/code]
After this, I tried winetricking directx9.
That didn't help, it still gives the same errors.

I don't know why you're saying that the game works with wine 1.7.1/1.7.3 - for me it's exactly the same as last year, game runs and everything "works" but the mouse jitter is still there. Completely unplayable. If you actually managed to get it to run without any mouse jitter you need to give more information than you did, because I've tried pretty much everything imaginable. I've tried over 10 different wine versions (1.7.1, 1.7.3 and 1.7.4 included) plus bunch of random patches and whatnot. Nothing fixes the mouse jitter.

The only thing that reduces mouse jitter is lowering GFX settings by a lot so you get higher fps. The lower the fps the more severe the mouse jitter is. At 60+ fps it is only noticable if you move your mouse fast (and for some reason it seems to get a lot worse if you move your mouse while strafing.) but it's still pretty much unplayable since your aim will be terrible even if it isn't directly noticable, you can't get your muscle memory to work since quick movements will move the crosshair different distances every time.

I should add that I'm using the latest nvidia diviers, running 3.9.2-gentoo.

This game runs fairly well now in 1.7.3. Just like 1.7.1, It needs imm32 and corefonts. Wine 1.7.2 breaks this game.

However the game no longer crashes on exit now, which to be honest didn't make a difference in the first place...

The only bugs left in the game that I can find are:
1) The magriders making the framerate do a nosedive when you try to drive one with the HUD on (gunner seat is fine).
2) Using a graphics setting above 'Low' causes the screen to go strange colours.
3) Imm32 from windows xp + override for the in-game menu/map to work.
4) Corefonts for that awesomethingy process crash.
5) After playing for around 2.5 hours straight, the game *might* go silent for a few seconds then crash.

One more, this isn't application specific, but the ALT key gets stuck when you alt+tab. It's fixed by just pressing alt after change focus back to the game.

This game nearly deserves a silver rating, As I said in the test results it's fun shooting everyone not purple. I do hope "Operation make game faster" works in our favour though.

Works well but cannot exit cursor mode
by Ben on Friday September 13th 2013, 19:10

The latest Planetside 2 with Wine 1.4.1 (Debian) loads fine and I can get into a game and it appears to be running well but it is stuck in "cursor mode" (I think switching modes is done with left-alt).

I can use the cursor to interact with the game (e.g. set waypoints on minimap) but can't get it out of this mode. So no mouselook and no keyboard movement. I can type in the chat Window though! :-P

I tried the imm32.dll but it didn't work. Though I did download it from a random website so...

Not sure the current state of things for others, I'm getting a completely different problem to everyone else.

First I had the "awesomium" process crash. This is fixed by "winetricks corefonts".

From a fresh wineprefix, Using "imm32.dll" from windows 7 and not using it gives me the same result. I spawn in at the warp gate, I can walk around / look around normally including zooming, but as soon as I hit either "M" or "ESC" it hangs in that menu. Does anyone else have this bug?

I read that the steam/standalone versions are identical, Should this bug be attached here too?, It suggest the corefonts workaround for the process crash.
bugs.winehq.org/show_bug.cgi?id=32342

Precisely that many times. This occurs with both the wine 1.6 stable from Arch repos, and latest git. Patchlog for wine 1.6 says that they've switched from openssl to gnutls for https networking. Is there a fix, or am I going to need to rollback the git version? Because that's messy.

Installed fine, but can't run launcher now
by Alexander Nigol on Tuesday April 9th 2013, 22:11

Hey guys,

Following the instructions/guides on the internet, I managed to install the game without a hitch (using Q4Wine).

I used winetricks vcrun2008 corefonts, and did the imm32.dll over ride.

Instead of clicking play, I closed the window to ensure I had the correct settings/override on the planetside.exe and launcher. Now I can't get the launcher to run or the exe.

The Q4Wine log shows this:
App STDOUT and STDERR output:
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
Direct3D9 is not available without OpenGL.
Direct3D9 is not available without OpenGL.

The game update yesterday causes my game to crash on player select with PS2 code G12 and "ResetDisplay failed". -- Sounds like this is the same thing that crashes when changing settings in the options menu. The game is now broken for me. Please take a look at this

Hello all, I am very interested in better support for PS2. I would like to offer a bounty to the Wine Development team of $100 for fixing the Mouse Jitter Bug ( bugs.winehq.org/show_bug.cgi?id=32913 ) and getting PS2 to Gold status for Ubuntu. If these goals are reached, I will donate the bounty to the Wine Development Fund: www.winehq.org/donate/

PS2 players, I ask you to contribute your own bounty to this goal! Even a pledge of $1 will show your solidarity and help promote PS2 with the Wine Development team! I would like to one day see PS2 in the Platinum list, and today we can make a first step: Pledge $1 or more to a bounty for fixing the Mouse Jitter Bug and reaching Gold status.

I've been playing with the Graphic Setting of Low ever since I started playing PS2 and everything seems to be displayed properly.

When I set the setting to Medium my character on the selection screen is turned completely grey. If I set it to High my character turns completely black. If I start the game then the game world is mostly grey and I cannot make out any objects except for the sky. When I change back to Low I can see everything just fine.

Has anyone else seen this? Google hasn't turned up anything and I don't see any other comments. The How-To even says Medium and High works for them. I have the D3D DLLs loaded and the latest NVIDIA driver.

Major fps-drop since Ubuntu 13.04
by Geriain on Tuesday March 12th 2013, 17:17

Well I encountered a major fps-drop since I upgraded to the new ( actually quite in development ) release...leading me to just get a small win-partition to play ps2 and script a grub-reboot directly to windows if I want to play ... since there is almost no progress ( if it's not even get worse ) for this game or the mouse jittering at the moment.

But would be interested if someone also encountered the fps-drop lately? I'm now at all-low-settings and with a reduced render-quality but still won't get more then ~10 fps ingame

Most times, the launcher just spins the aqua circle for a few seconds and then freezes. However, sometimes it actually loads the login page, but I'm usually only able to type one or two characters before it freezes again.

Here's what I've done so far:
- Extracted imm32.dll from the Windows XP SP3 download as per this post and placed it in ~/.wine/drive_c, ~/.wine/drive_c/windows/system, ~/.wine/drive_c/system32, and ~/.wine/drive_c/syswow64
- Added imm32 to the Library Overrides (native) in winecfg
- Used winetricks to install d3dx9_43, d3dcompiler_43, corefonts, and a bunch of other packages
- Installed a few lib32 SSL libraries

I'm running Arch Linux with wine-1.5.25. I'm also using an NVidia GTX-660 with the proprietary nvidia drivers (both native and lib32-nvidia-utils 313.26-1). Any ideas or questions would be appreciated.

Fedora 18 64 bit wine i686 1.5.18 Directx is not up to date
by JUTUL on Thursday February 7th 2013, 12:12

Hi,

I tried all your tips, but allways when i try to install the game the setup is broken by an directx error. "Please install a newer Version of direct3d"

In Fedora 17 i could play the game but with many lags. So i try to tweak the game. Then there was a new Patch and i cant start the game anymore because of an hdd space error (not enough free hdd space, but i have 180 GB free). So i install fedora 18 and now im here :-)

Some turned out to be quite successful while several others did not... Here are my results:

I had a very successful run of PS2 in CrossOver. CrossOver is another 3rd Party Wine application that has an improed directory of supported applications, but sadly it is paid. I have tried to run PS2 in Wineskin, PlayOnMac/PlayOnLinux, etc. and yet while in some cases it did run... The best result was from the free trial of CrossOver through Steam. There is only one bug in the game in CrossOver and it is that the graphics settings of the game are not editable, so they are stuck at default which can have lower FPS for people that have graphics cards with video memory under 1 GB or built in graphics. Additionally, CrossOver is paid, although there is a 14-day free trial. The game must also be downloaded through the windows version of Steam - It will not run via the normal launcher, just FYI. I have searched far and wide through different wine-based applications and this is the best i've got. I most likely will buy CrossOver if a mac client isn't released before my trial is up (which is likely).

I'm using a GeForce 9800GTX+ with the 310.19 driver and a 3ghz Core 2 Quad and I only get about 10 FPS on any graphical setting. I can set things on High, which does make the game look pretty good, but FPS doesn't change. It's always slow.

I was interested in buying a GeForce 670 to help bump up the FPS, but I want to see if anyone else has any faster performance.

With the Game Update #1 a couple days ago, I now always have the 'mouse jitter'. The game is relatively smooth (10-20 FPS in a window) when moving around with the arrow keys, but whenever I move the mouse, the screen jumps/lags badly.

Previously, this would happen after about 30-40 minutes of gameplay, and a restart would fix it. Now, this happens all the time. I also noticed in the recent update that I no longer need to have Raw Mouse Input enabled. Neither setting works for me, though previously I had to have Raw enabled. Looks like something mouse-related changed.

I have been able to install and start the game. Everything seem to be working fine exempt when I load into the world I have a mouse pointer. I can click on the chat box and type what ever i want, but I can't toggle the mouse back to move around. Esc does not work either. I tried change the key-bindings but nothing works.

Hi all,
I'm fairly new to running games under WINE (not new to GNU/Linux though ;-) ), and I am currently having this issue where when I start up the game all the menu text is not appearing, but rather some kind of variable names like UI.Next instead of "next" and UI.Exit instead of "exit".

I'm at my wits end trying to figure out if it was a misplaced step or an overlooked step. I'm half wondering if it's something I HAD installed in my previous distro - and with it being gone now - could that be the reason?

- which is then followed by "fixme:time:GetSystemTimes..." for as long as I leave the window open

- complaints of "preloader: Warning: failed to reserve range 00010000-00110000" occured in the previous distro version, and after reading pat's comments on why it's occuring, I'm leary about making the adjustment to silence the complaints. PLUS, the game installed, connected, and ran before, with those same complaints.

What am I missing? Any ideas? Is this wine or something amiss in Slackware? A setting? An override? Help?

Game runs fine, but...
by Exodus111 on Saturday December 1st 2012, 6:33

After the latest patch the game now runs perfectly stable.
I've been playing for hours, and I'm not experiencing any crashes, all menu's work fine, I've been in the fray with tons of other players, taking bases, riding vehicles, planes tanks etc etc etc.

I've tested out every class in the game, all the starter weapons and vehicles, and I've engaged in massive battles, its stable, I'm not crashing, it works.

But... its still just a little too low on the FPS during fighting.
Holding a weapon steady is a chore, sniping is pretty much impossible, and this makes certain vehicles hard to control.

Its not game breaking, shotguns and carbines/assault rifles still work fine, though obviously if your opponent gets the drop on you there is pretty much nothing you can do, as aiming properly simply takes too long.

I've not tried any of the tweaks yet, can anyone tell me if they work? Does the game get smooth enough to enjoyable gameplay with them? If so, which tweaks should I go for? Should I try them all? or jsut a few first?

The game seems to run fine. Not the best framerates, but it's playable. For some reason the game crashes a few minutes (Maybe 5-10) after I get in-game. I have imm32.dll successfully installed, menus are no problem. vcrun2000, corefonts, d3dx9_43 and d3dcompiler_43 all register as installed. I'm on a 32-bit prefix.

I'm not very experienced, so if I need more information, please tell me how I wold acquire it.

Something I found to increase fps dramatically for me was to go into the UserOptions.ini and set the RenderDistance from 99999 to 1000. You can try and see if it's working for you in case of smoother gameplay.

Has someone found a solution for this jittering? Even when I play with virtual desktop and windowed after aprox. 30 to 60 minutes the mouse start to flick around and ruining the aim...I have to relog and wait in queue to fix it at the moment...

I already tried different solutions I found on the internet like installing corefonts and vcrun2008 didn't help. I also tried a new clean Wine prefix. I'm using the newest Wine version from git. Anyone got an idea how to fix this?

Actually you can play long, but only if you avoiding battles. Looks like it's somehow related to battle activity, some sound effects maybe. I've managed to play around 20 minutes on empty server.
Wine is trowing something like this at me every time, before crashing:
Code: