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
Got 12 certs on logging in.
Warped from Indar to VR Training to Esamir back to Indar.
Swapping classes and resupplying at terminal works.
Could move around with WASD and turn/ADS/fire with mouse
(Everything done in VR)
Killed a NC combat medic target with HA / T9-CARV
Blew up a tank with HA rocket launcher
Tested all abilities of all classes (cloak/heal/shield/jetpacks)
Spawned a Sundy and drove/deployed, used 2nd seat gun.
I could redeploy at Sunderes.
Spawned a Mosquito and flew for a few seconds, mouse controls, W/S, and up thrust work (will test more soon), shot a few rounds at an enemy tank but not enough to destroy it.
I could not heal anyone in VR (friendly fire off), but the animation shows and it shows me the health.
In VR, I spawned a stock Engi turret but it said I did not have permission to get in the vehicle.
Threw a grenade in VR.
Got a outfit join request on signing in, clicked accept button but did not test any more than that.
Could look around map.
Redeploy button on map.
Changing any settings except graphics settings and brightness.
Players and vehicles showed up on minimap.
Laser sight laser shows up
Iron sights of the TR default rocket launcher and one other RL.
Reflex sight works.
TR combat medic default weapon iron sights work.
Game runs in fullscreen.
What does not
On Very Low/Low/Medium settings (which I will call low settings), class/vehicle terminals render as black rectangles, with fancy particle effects on very low or low (or as a plain black rectangle on medium). Warpgate boundaries and the glowing ammo dispenser stuff does not render on low settings.
On High/Ultra, when choosing a class/resupplying, the player renders as a black shape, though this works on low settings. However, the stuff that doesnt show up correctly on low settings works. Other players/MAXes render correctly, and I can still switch classes/resupply.
On ultra settings, I got about 20 FPS in VR and a few less in the Indar warpgate, which is similar to what I get on my Windows 7 laptop. Though the game is very playable on the laptop, on Linux, even with the same FPS (and also on Very Low settings where I get a lot more FPS), it is very choppy, and probably would not be good for much other than sniping.
There might e some very minor graphical effects that shouldn't be there, or it might just be the choppiness making everything look different.
What was not tested
Going outside the Indar warpgate
Redeploying in a real continent (not VR)
Battling a real player (though VR dummies work)
VS or NC stuff
Any vehicle except the Mossy and the Sundy
Healing someone that doesn't have full health
Taking damage (though when my mossy crashed I got a suicide)
Using the engi turret (outside of VR, where it failed)
Ammo packs, mines, C4
Buying stuff with certs or station cash
Customizing classes in the 3rd tab of the ESC menu (though I can look through options in the upgrades tab)
Minimap didnt work in VR, though it usually doesnt work in VR on my Windows computer. I did not look at it outside of VR.
I did not spawn as MAX.
Battling, capping/losing a facility, getting exp/certs, anything to do with station cash.
I did not try to get out of fullscreen.
The choppiness is the only real problem. Not being able to see the character when changing classes does not really affect gameplay. However, if the computer can only run the game on Medium or lower settings, then there is a bunch of stuff that can not be seen, which would give a disadvantage. I will do more testing tomorrow and try to narrow down which specific graphics settings causes the issues with stuff rendering wrong. The only things I had to do to make the game run was the imm32 workaround and winetricks corefonts. I installed in a clean 64 bit wineprefix. Emulate a virtual desktop was turned off. Windows version was set to XP. imm32 was placed in C/windows/syswow64 and set to native, then builtin. Window manager could decorate and control the windows.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Arch Linux x86_64||Apr 15 2019||4.6-staging||Yes||Yes||Yes||Garbage||timawesomeness|
|Show||Arch Linux x86_64||Apr 10 2019||4.5-staging||Yes||Yes||Yes||Garbage||timawesomeness|
|Show||Arch Linux x86_64||Apr 10 2019||4.5-staging||Yes||No||No||Garbage||timawesomeness|
|Show||Linux Mint 18.1 "Serena" x86_64||Apr 15 2018||3.6||Yes||No||Yes||Garbage||Xuara Ars|
|Show||Linux Mint 18.1 "Serena" x86_64||Mar 23 2018||3.4||Yes||No||No||Garbage||Xuara Ars|
|Bug #||Description||Status||Resolution||Other apps affected|
|32342||Multiple applications and games using 'Webkit' or 'Blink' web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation)||STAGED||View|
|37355||Multiple software protection schemes need ntoskrnl 'MmMapLockedPagesSpecifyCache' implementation (Tages Protection v5.x, BattleEye's 'bedaisy.sys', MRAC Anti-Cheat)||NEW||View|
available via winetricks
must be manually installed
imm32.dll - see note below
The following are required if you abort the DirectX redistributable installer:
available via winetricks
I start with a new prefix you may adapt it to your situation.
$WINEPREFIX will always be your path for you Planetside2 wine folder. The first step will create that folder.
example with step 1:
WINEARCH=win32 WINEPREFIX=~/.wine_planetside wineboot
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.
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 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.
- pulled from a real windows install, solves menu crashing issue; also solves some disappearing cursor issues.
- winetricks corefonts
- for the launcher.
- Loader (LaunchPad):
- possible crash after updating (I need to verify this)
- file check may hang at "0 files" or the last file (usually saying "4854 files")
- if at "0 files" - you need to restart
- if at the end - just wait it out
- when clicking on links, you get an "Invalid parameter" warning but it does not crash.
- manually triggered "Validate" often slows down between ~2800 to ~3100 files
- just wait it out or restart
- will crash with error G12 when altering the following graphical settings:
- Game Resolution Mode
- Window/Fullscreen Mode
- Render Quality
- Crashes when "Particles" setting is on medium or higher
- every other setting works up to high (ultra untested). Set according to System Performance.
- (only Nvidia driver version 310.x+) Enable OpenGL threaded optimisations, execute before launching (best to write a script for launching PS2):
- export __GL_THREADED_OPTIMIZATIONS=1;
- export LD_PRELOAD="libpthread.so.0 libGL.so.1";
- export WINEDEBUG=-all;
- Use the Multicore Optimisation script posted by Geriain in the Beta Comments (you may need to adapt it for your own needs)
- Use winetricks vsm=hardware multisampling=enabled and psm=enabled
- confirmed to give up to 15 FPS on low settings.
- in UseOptions.ini set RenderDistance to 1000
- You can try to use SweetFX
- Place all extracted files in your PS2 directory.
- Set d3d9 and dxgi to native,builtin in winecfg
- use this config for a startpoint. (you may disable SMAA for performance).
- Read the readme of SweetFX for further infos.
adopted from PS2 forums.