Planetside 2

Just as an FYI. Test data already submitted

More info: -Used wine64,
-Did not create a brand new wine prefix for this version test; did not have time to re-download the game from LaunchPad.
-I was anxious to try 3.4-devel because of the BattlEye fixes indicated in the release notes.

If anyone wants to try out a fix please see this thread:

bugs.winehq.org/show_bug.cgi?id=37355#c2

Feel free to submit a test result if you make any progress.

Does anyone know of a way to fix the bug where as soon as you press play on planetside 2, a pop up saying "Starting BattleEye Service..." comes up and the game never launches. I am on MacOS running Wine 2.0.

Please see Bug #41670

Hi,

There is a new potential fix if you are interested in trying.

please see the following thread:
bugs.winehq.org/show_bug.cgi?id=37355#c2

Hi,
one of the most needed games for Linux (Mint 64 bit) is Planetside 2.

I tried a lot of ways to Play it and found the following sollutions.

My System;
Mint 17.03
18 GB RAM
12x Cores (6xTH)
NVidia GTX 760 4 GB
Wine 1.9.10

#1
I installed the Game like above in the instruction.
It worked but with some bugs, first I had a fully red-Screen In-Game.
FIX: Install DirectX 9 and add the dll's.

#2
Black Screen In-Game and in_Menu on the Models
FIX: Set the Graphic Settings to Middle, Low or Very Low (high settings cause the blackscreen problem)

#3
F***ing low FPS
My usual game FPS in Planetside on Win7 is 200 - 300 FPS
In Wine it was 13 - 37 FPS
To fix the FPS, I simply enabled in my Wine-Prefix (64bit) -winecfg, under the category graphics (CSMT, VAAPI, EAX and GTK3 [whyever]).
Not I play with ULTRA Settings (Graphic-Quality on Mid) and Anistropic Filter 16x + Antialiasing 32x(8xMS,24xCS) with Stable 80 FPS. It looks amazing!

By the way use 1.9.10

Hey, thanks for the information.
But, how do you get 200-300 FPS on Widows?
You mean you have that on low settings?

I have i5 3570K and Geforce 970, and I get under 100 FPS on Windows. (1920x1080 resolution)
In big fights it drops down to 30-40. Settings are on ultra, but shadows and fog shadows are turned off.

On Linux mint 17.03 I get 60-70 FPS, with drops to 20-30.
I did install DX via offline installer. And then installed Planetside, and enabled CSMT and EAX in winecfg staging settings.
I could not enable VAAPI though, that checkbox is grayed for me.
Any ideas, how FPS can be increased without hurting graphic settings too much?
Thanks.

Note: This is my opinion, it is subjective and could be false in eyes of programmers and geeks, but I would make it this way!

Make sure you have enough time!
Have a look at my Components;

GTX 470 (Boosted) // GTX 760 STICKER
i7 X 980 3.33 Ghz
12 GB RAM
500 GB Hard-Drive

Now compare it with yours and estimate the +/- performance, so you can comprehend the frames you should have.

If you do not want to damage the visualization of the game, there are just a few methods to get more fps;
Make a Clean 32bit Staging Wine Prefix & Install only the necessary stuff, do not run any other program in this prefix!
Also Run the Prefix in full-screen, this affects sometime the performance.
Than you could try older/newer wine-versions. (The newest are mostly the best optimized)
Try different wine-settings, even if you think that those can't affect your performance (sometimes it do, but nobody know why :D)

By the way, a short story!

I've played Skyrim (ultra-settings) in win7 using the GTX470 with around 30- 40 FPS (with Ultra Graphic-Mods). It worked not always well, but it worked!

Than I build in the newer and (better) GTX 760 STIKER, Every Game works well, but just one, Skyrim do not run at all, or just runs after several minutes. In addition there haven't been better performance than ~ 10 - 15 frames. So I stopped playing Skyrim in win7.

I thought in wine there should be a difference, but NOPE!
Wine+Skyrim+GTX470 = 60 - 70 frames and fluently loading-screens.
Wine+Skyrim+GTX760 = 5 - 20 frames, AND F***ing 10 minutes launching-time + endless loading screens. WTF This graphic-card is 3 till 4 times better in all stats. You can imagine that the game you want to play is not allways optimized for your gpu, sometimes it is not even compatible (e.g. old games).

Thanks for the reply!
I ll try to mess with my Wine settings. Maybe I'll be able to squeeze a bit more.
By the way, I do believe 32bit prefix is not viable now, since PS2 have only 64bit client.

Oh, yeah, ma mistake.

My winecfg;
WinXP, CSMT, VAAPI, EAX.
Still sometimes do not start properly, but sometimes it works. Just restart the prefix.

Have Luck!

I also got a copy of xinput1_3.dll and moved it to drive_c/windows/systemwow64.

The 64 bit version is 81.8 kB.

I don't remember whether I copied it from the planetside 2 directory or from a windows installation.

This should be below in the xinput1_3 response.

Can you try to use this to specify which one? The site has multiple specific dll versions, as well as multiple hash checks. It should clear up some issues.

www.dll-files.com/

How did you get around the error:

err:module:import_dll Loading library XINPUT1_3.dll

Any help is appreciated.

In winecfg, in libraries tab, I have the xinput_3 entries overridden to builtin. Having said that, even if you get past that point, the 64 bit client (which is all that is left now) is not likely to run. I have not found anyone who has been able to run it. See the discussions near the top of this page discussing the end of the 32 bit client and issues with page faults with 64 bit client.

I also got a copy of xinput1_3.dll and moved it to drive_c/windows/systemwow64.

The 64 bit version is 81.8 kB.

I don't remember whether I copied it from the planetside 2 directory or from a windows installation.

I've made best experienvce with installing dependecies with winetricks (wiki.winehq.org/winetricks). Doing it by hand is possible, but some libs have dependecies on other libs (which you can debug with WINEDEBUG="loaddll").

The winetricks verb is "xinput" so you install it with:
WINEPREFIX= winetricks xinput

Thank you Joseph and Felix. I got rid of the XInput error. Many thanks.

If you are able to get the game to run now that it is only 64 bit please post back with information about what linux distro you are running, what wine version and what you had to do, if anything, to get it to work.

There are are numerous people who would be very interested in knowing of anyone who is able to get it working.

I meant that I fixed the XInput1_3 error, The game doesn't work. Sorry.

I have reported the bug that crashes the game on launch in the game's bug tracker:

dgcissuetracker.com/browse/PS-1550

Please vote on it to bring it to developers' attention.

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.

Whenever I start the game with the latest patch I get the error:

Err:ntdll:RtlpWaitForCriticalSection 0x7dc109a0 "wine3d_main.cwine3d_cs" wait timed out in thread 0063 blocked by 0060, retrying (60 sec)

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

Gallium Nine (wiki.ixit.cz/d3d9) works fine for this game with my HD 6870. I had

- to patch wine used for GalliumNine using the well known patch (mouse jiter bugs.winehq.org/attachment.cgi?id=50096&action=diff&context=patch&collapsed=&headers=1&format=raw)

- to set settings to lowest level.

Here is a Youtube Video: youtu.be/yZHRmdsDnBU.

I will try to add more tests in January, 2015 for another graphic card.

Updated link: youtu.be/yZHRmdsDnBU

FYI the fix for "mouse jittering" was applied in Wine-Staging 1.7.6 (www.wine-staging.com). I tested it and it is quite useful.

Here my second test for GalliumNine with a HD 7970 card www.youtube.com/watch?feature=player_detailpage&list=PLhmTqTnY5Ke_wQ771BiiJaye0K9j-738p&v=23Xk1XC4GwQ

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.

wine 1.7.21
ubuntu 14.04
GTX 550 ti
i7
8gb

heres a video

www.youtube.com/watch?v=ehi5Jjo3hQY

Same here. 1.7.23

I got this problem aswell but installing wine-csmt from aur fixed it for me. The only problem with that is that with the csmt the nvidia driver crashes at random (sometimes i can play for hours, sometimes it crashes instantly).

I found a way to suppress the effects of mouse jittering. I overrid dinput from the winecfg.

wine.1045685.n5.nabble.com/Bug-32913-New-Planetside-2-Mouse-Jittering-td5744559.html

There also seems to be someone who is actually working on a patch to fix this issue. So hold out, my friends.

Fantastic!

What did you do? I have tried but it doesn't seem to work.

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.

Its nice to know your an ex-game developer; I have developed games as well, studied VR and Computer Graphics in Graduate school, its nice to pull our own weight around isn't it?

Given that you and I know how about translations, rotations, matrix multiplications, and etc doesn't give us any incite into how PS2 is programmed nor how mouse input is handled in wine.

Basically, your background nor mine doesn't improve the legitimacy of our claims (well your claims as I am not making any claims as to what the problem is but you are).

Michael, I hope then that you can see that our opinions carry the same weight. I saw your inappropriate response to subraizada, whom I agree with, and I wanted to make sure if a developer cam to solve this issue after nearly two years, he was not led down the wrong path. Regards.

Chase, in what why was my response inappropriate?

"he was not led down the wrong path."
And what path is the right path? As you don't have access to the source code of PS2, how can you determine what the "right" path is?

Its nice to know your an ex-game developer; I have developed games as well, studied VR and Computer Graphics in Graduate school, its nice to pull our own weight around isn't it?

Given that you and I know how about translations, rotations, matrix multiplications, and etc doesn't give us any incite into how PS2 is programmed nor how mouse input is handled in wine.

Basically, your background nor mine doesn't improve the legitimacy of our claims (well your claims as I am not making any claims as to what the problem is but you are).

Michael, he was just alluding to his background as a way of explaining his theory - maybe it's not *perfectly* worded, nothing on the internet ever is. Your statements, for example, lacked some punctuation in order to be readable in any way, but pronouncing it to myself a few times.

That said, I think you're being overly prickly - his substantiation lay in previous experience *and* observed behaviour in-game, both in length (extensive play) and when the variable crucial to his theory, the FPS, changes (airplane steering in low- and high-FPS situations) - it's nothing more than a hypothesis, which is valuable in itself.

Had you been less perturbed by him mentioning his former occupation, perhaps you'd stop to recognize the value in that - a hypothesis gives you a testable theory which through disproval can be rejected and then we all learnt something - namely that it isn't tied to FPS - or we can come up short in our efforts to disprove it, and by doing so, place increasing belief in its validity.

What you're indirectly suggesting is the absence of thought - unless we magically get a P2 developer to "spill the beans", NDA be damned, we can only treat it all as a big black box -- that's just not workable - taken to its extreme; we'd be equally well served patching font-rendering in wine as we'd be working on the input subsystems or dinput - would you honestly, as a developer, truly encourage such a "we know nothing!!!!111" approach, or did you just have a bad day ?

His hypothesis is incorrect. You may now step off your soap box.
wine.1045685.n5.nabble.com/Bug-32913-New-Planetside-2-Mouse-Jittering-td5744559.html

Hi, I noticed your reply today while reviewing PS2's status here. My analysis was correct. The problem was mouse coordinates being reported at a pixel level instead of a sub-pixel level. The jitter was caused by the lack of reported mouse movement while the buffer accumulated enough sub-pixel units to report a pixel of movement. Thank you have a nice day.

--Start copy pasta--

Brief problem description:
* XInput2 is only enable under special circumstandes.
* XInput isn't very accurate (It notices sub-pixel mouse movement, but reports
only pixel coordinates)
* Even with XInput2 enabled it might drop events because they are from a
different "serial"
* XInput and XInput2 events are both sent to the same low level message
function which expects pixel coordinates but XInput2 reports relative sub pixel
movement

* Planetside2 expectes "unproccessed" sub pixel coordinates like the ones
reported from XInput2

--End copy pasta--

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.

Also, when walking, crouching, jumping, and sprinting without moving the mouse produces correct animation (in human form).

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.

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.

One pretty important thing I forgot to say in the first post is that though the FPSs can get pretty low, graphics are pretty smooth - with the exception of the mouse, the game always looks like its running at a very high FPS.

CPU usage actually hovers around 20% in-game, going up to 30% and 2 cores in large battles - the previous comment about 60% was wrong, because Gkrellm scales the graphs on the fly. All the other CPU cores stay almost idle, occasionally spiking to 50-70% for a second or two.

In conclusion, the mouse jitter is caused by a low FPS. The FPS counter in the game reports that the GPU is the bottleneck. In reality, the GPU is running nowhere near its maximum, and the bottleneck for FPS is actually the CPU. However, the CPU is also not being fully utilized for some reason.

Hopefully this helps narrow down the specific cause of the jitter or helps fix it.

In addition, I did not have PhysX installed - winetricks physx failed.
I am using a 32-bit wineprefix on 64-bit Arch Linux with wine 1.7.18.
My CPU is the Intel i7-3930k and GPU is the nVidia GTX 680.

So the situation is unchaged since the Beta.

Also I think you draw a causation that's not there:
High FPS reduce the mouse jitter, but even at 30 FPS there shouldn't be any.

It seems more like Planetside is measuring the frame time to calculate mouse movement, but wine is reporting that wrong. That would explain why higher fps reduce the effect, the absolute error is reduced.

My phrasing wasn't the best, but that is what I meant in the second comment when I said that though everything else runs smoothly, the mouse jitters a lot at a low or even normal FPS.

I don't think the bug has to do with low frame rates or frame rates at all. As I can move forward, backward, side left, and side right without any issues. Its only when I rotate my mouse do I get a huge weapon jitter.

As I mentioned before, the graphics run smoothly at low FPS in Wine and on Windows, but for some reason in Wine the rate at which the game moves the mouse is tied to the FPS, causing huge jitter at low FPS.

It stops jittering at about 80 FPS, and is playable at about 65-70.

In Windows, the mouse movement is not tied to the graphics FPS so it is always smooth.

To test this, there is an area in the warpgate where I got 70-80 FPS compared to about 30 normally, and in that area you will find the mouse jitter is almost gone. I haven't played in a while so I don't remember exactly, but I believe that it's on the second floor of the warpgate, to the left of the stairs if you're facing the first floor. Just stand in the corner between the stair's railings and the wall, and face the wall. It was in the Indar TR warpgate.

Its not tied to the frames per second as the jitter doesn't happen when using a tank for instance.

The mouse jitter is caused either by a bug in Wine or a bug in PS2 that only happens when running on Wine.
I have spent lots of time experimenting on multiple computers with Wine and based on the data I collected the end result of the bug is that the mouse refresh rate is tied to the FPS.
When you are using a tank, the mouse moves smoothly, and everything works perfectly, and in that situation *the bug is not present*; so yes, the bug is tied to the FPS, however the bug is only present in certain conditions (not using a vehicle, for example).
"I don't think the bug has to do with low frame rates or frame rates at all." - Again, the bug is that the mouse is updated at the same rate as FPS. In this scenario, you are not moving the mouse so it does not affect the game.

My conclusion that the bug is based on the mouse input being tied to the FPS is based on playing PS2 in Wine for a couple of hours and observing the jitter/FPS/other variables.
You clearly do not have any evidence to back up your hypothesis that the bug is not tied to FPS, and until you or someone else collects some data and analyzes it to come up with some other conclusion, all the testing I have seen points to the conclusion that the bug is based on mouse input being tied to FPS under certain conditions in-game.

In brief, no, the bug *does* have to do with low frame rates, and you are just wasting everyone's time by making baseless arguments.

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.

Should have mentioned. I'm using Arch Linux x86_64 with a 32-bit Wine prefix. Video card is an Nvidia GeForce GTX 560 Ti.

I have this exact same problem, Arch 64bit, 32bit wineprefix, GT 650.

GTX 760 4GB Nvidia Driver v.361 / v.352 also.

I've got it to work.
I can Play on Ultra with 35 FPS.
To fix the Red-Screen or Black-Screen you need;
1. Add all necessary binaries to the winecfg, than install directx9 and than you can install Planetside 2.

Worked for me!

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.

Also, I have not done anything with the imm32 dll. All the Wine options are set to the defaults.

I don't get this problem with a 32 bit prefix. It might just not be playable with 64-bit.

Yup, switching to a new 32-bit wineprefix made the game launch. I haven't actually played yet, but the character model in the server select screen is black - I have a feeling the bug from my first test/report is still there.
Will post new test results soon.

GU01 (the big update from Nov 12) broke the game for me. Crashes on startup from Wine versions 1.5.27 to 1.7.7.

Same problem here, I'm not able to start the game. When I click start, the launcher crashes after a few seconds.

tRY SWITCHING TO WINE 1.7.18.

Launcher works but when you load the game up with a black screen with a white lane at the bottom.
And 0 errors from the wine just worth a black screen and a white lane.
What to do ?

This is also what I experience (Wine 1.7.1 CSMT)

not happening for me, using CSMT as well (steam version)

You don't have the mouse jitter?
What DE/WM do you use?

no nothing is wrong with mouse only issue for me is performance (get lag when near lots of players)

what is DE/WM?

Desktop Environment (Unity,Gome,KDE,...)/Window Manager (GDM,KDM,i3,...)

uhhhhh i have no idea what those are. i think that you are thinking that I am using linux? im using mac osx

Ha ok then this is a whole different story.

Mac haven't hat this problem in the first place.

oh ok. i think that we both have performance problems though right?

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.

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...

I tried it with the win 7 one, but it didn't work.

with the Win XP-dll it works fine!

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

Have you maybe forgotten to st the imm32 to native in winecfg?
Also if you prefix is 64bit it needs to go to system32 not system.
Lastly I'm not completely shure a win7 imm32 will work, I only tested it with win xp ones.

Thanks for getting back to me so quickly. You are correct, A 32-bit Win7 imm32.dll did not work for me. I found a WinXP version, set it to "native", and now the map/escape screen works without hanging (not crashing).

It might be worth pointing out that corefonts fixes "awesomium_process" from crashing and imm32 fixes the menus from hanging the game.

Maybe change "Pulled from a real windows install" to "Pulled from a real windows xp install" (This is the part I read, somehow skipped over the imm32 override instructions because I already knew how to add an override :-/)

My fault though, Many thanks for helping me get it working.

Yes, wine 1.7 gets the game working again for me too.

Now... no one break anything!

Use the imm32.dll from Windows XP

I first tried a win7 one, but then I downloaded the XP-dll, and it worked!


But there are many graphicbugs, so it is not verry playable...

I heard that the network bug was fixed, so I updated wine and tried it again. When the launcher tries to connect, I get:

GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304
GnuTLS error: Decryption has failed.
err:secur32:schan_DecryptMessage Returning 80090304

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.

I have tried rolling the git repo back to 1.5.31, and 1.5.25, same error :( It doesn't seem to be a wine version problem, since I ran older versions of Planetside on lots of wine versions between 25 and 31. It must be a Planetside problem, maybe they switched from SSL to TLS for better security?

With WINEDEBUG="+secur32", it gives massive amounts of text (past my 5000 line scrollback, till I changed it), but I think I got something useful. bpaste.net/show/117906/
It looks like things start going wrong around line 151. These lines(151-174) repeat a few times every so often. The number of bytes is always different, but it seems to always be expecting more than it gets. Either something is mismatched between client and server, or packets are getting chopped short somehow. In between these, there appears to be a sucessful keepalive or handshake of some kind. (lines 129-143) Note that it says:

trace:secur32:schan_gnutls_log REC[0xf3e017e0]: Expected Packet Handshake(22)
trace:secur32:schan_gnutls_log REC[0xf3e017e0]: Received Packet Handshake(22) with length: 81

So for once it is getting the correct packet length. But then it goes right back to getting pieces of packets. This process repeats a bunch of times, but then it does stop, it doesn't retry forever. For that matter, it doesn't say "Error" or "Retrying" or anything that actually says anything is wrong, other than

"Expected at least 3395 bytes, but buffer only contains 938 bytes."

Sort of thing. Can someone with more knowledge of networking/SSL/TLS try to explain this behaviour? And more importantly, how to fix it so I can play PS2 already? Thanks.

I have gotten the game to open the installer, updates, starts the game. Can create character and navigate menus with no fractals or errors.

Once in game I can move around all day long using the keyboard. Within seconds of moving the mouse however the client crashes.

Ubuntu 13.04
Wine 1.5.27 planetside 2 through PoL
No overrides
AMD 6600 with catalyst 13.4

I'm having the same problem both in POL and elsewhere. Everything is fine until I move the mouse ingame and crash to desktop.
I also have almost the same error just before the crash as mentioned in the conversation below this:
err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0890.

Interestingly enough, I am able to look all over. When the red hud designators inter my FOV however, the client locks and crashes.

The client also freezes as I strafe down the hallway within 5m and -1m of the crouch phase objective.

These are the two specific ingame aspects where my client freezes. For what it's worth.

Can you two add you findings to Bug 33529 ?

Sure, I'll do it when I get back to my rig

Is everyone crashing or just some people?

As far as I've seen everyone is crashing after some patch in April. I haven't heard anyone reporting playable since whatever changed during that patch.

Still crashing...

I dont know the reason but the bug is fixed, game is running fine now.
Unbuntu 13.04 and wine 1.6

game update or did you put some dll or change any config?

I can confirm that the game dose not crash when I move the mouse any more. Only thing I can think of that has changed is gameupdate and update to nvidia driver.
The mouse is now however very jittery again.
Checking/unchecking use raw mouse imput makes no diffrence.

OK then something is wrong here, what is your wine version, distro, etc..
I just tried it out with crossover and hapens the same thing, crash on mouse movement.

Game now crashes within a second of spawning into Warpgate. I think the relevant output is this:

err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0884.

This is the only different input I've noticed, also I've run the game 3 times now, its always the same socket.

yep, but now no need patches to change settings
any know how solve the new problem...?

Jep also noticed it.
First thought it would be due some test I did with compiling with clang but it also happens with a normal build.
I'll attach some log to your bug.

Oh aparently it doesn't like me anymore. Now the awesomium.exe crashes everytime... Well ok... maybe tomorrow.

I confirm this error. err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0848.

When running debug in PoL I also receive a continuous
fixme:d3d:query_init Unhandled query type 0xc or oxa. they alternate back and forth. fyi.
d3d9 override makes it so his message doesn't show up all the time, though it's always there when running dubug in PoL.

ultimatly client shuts down after fixme:dbghelp:elf_search_auxv can't find symbol in module. I've seen this warning related to a font error but all corefonts are installed in this bottle.

fixme:d3d:query_init , etc, has been spamming since I started playing PS2 in Wine, I don't think its a problem. I suppose it might be affecting performance. Thanks for pointing out that error msg on crash, I thought it was the network error that was crashing it. Now that we have some idea of the problem, maybe we can get this working again!
A quick search tells me that "elf_search_auxv" is about ELF Auxiliary Vectors, something about how ELF executables are loaded into the CPU. That low-level stuff is over my head. Perhaps some problem wrapping the .exe into an ELF executable? something the wrapper can't convert to ELF? If someone with more knowledge could pipe up that would be great.

The socket output cleared up for me by opening port forwarding for PS2 on my router.
I don't think it'll fix your crash but it cleared that socket string for me.

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.


Any help please?

Ok so I decided to give it one more try, and I changed the imm32.dll from Native, to Native/Built-in.

Now I can get the launcher working again, and get into the game menu, however it crashes before getting into the game.

The game is broken with the latest update; there is no fix for now. However you should be able to at least get to the character select screen.

I played fine before path today...
With bugs.winehq.org/attachment.cgi?id=44211 path

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

Wine 1.5.26 (working prior to update)

Dump:

fixme:win:RegisterDeviceNotificationA (hwnd=0x2008e, filter=0x2f46e970,flags=0x00000000) returns a fake device notification handle!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d:query_init Unhandled query type 0xa.
fixme:d3d:query_init Unhandled query type 0xc.
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
wine: Unhandled page fault on read access to 0x00000724 at address 0x128b718 (thread 000b), starting debugger...
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
Created new window in existing browser session.
Unhandled exception: page fault on read access to 0x00000724 in 32-bit code (0x0128b718).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:0128b718 ESP:0033d6ac EBP:0033d6d0 EFLAGS:00010202( R- -- I - - - )
EAX:00000000 EBX:00000000 ECX:25f57380 EDX:00000000
ESI:25f57380 EDI:04c72850
Stack dump:
0x0033d6ac: 25f57380 0128cce1 50f800fd 04c72850
0x0033d6bc: 25f57380 25f57380 0033d720 02702023
0x0033d6cc: 00000001 0033d6dc 0128cfdb 25f57380
0x0033d6dc: 0033d6f0 01191c83 00000000 2a13a894
0x0033d6ec: 25f57380 0033d72c 00cdbf5b 25f57380
0x0033d6fc: 2bb09f80 2a13a894 00000000 00dbcefd
Backtrace:
=>0 0x0128b718 in planetside2 (+0xe8b718) (0x0033d6d0)
1 0x0128cfdb in planetside2 (+0xe8cfda) (0x0033d6dc)
2 0x01191c83 in planetside2 (+0xd91c82) (0x0033d6f0)
3 0x00cdbf5b in planetside2 (+0x8dbf5a) (0x0033d72c)
4 0x00e780c8 in planetside2 (+0xa780c7) (0x0033d758)
5 0x00d535c0 in planetside2 (+0x9535bf) (0x0033d780)
6 0x00cef666 in planetside2 (+0x8ef665) (0x0033d7bc)
7 0x00d366b0 in planetside2 (+0x9366af) (0x0033d7e4)
8 0x00d03289 in planetside2 (+0x903288) (0x0033d814)
9 0x00d547e8 in planetside2 (+0x9547e7) (0x0033dc60)
10 0x00d613a5 in planetside2 (+0x9613a4) (0x0033e018)
11 0x032a88d0 in planetside2 (+0x2ea88cf) (0x0033fdd0)
12 0x013fb0c7 in planetside2 (+0xffb0c6) (0x0033fe60)
13 0x7b8610fc call_process_entry+0xb() in kernel32 (0x0033fe78)
14 0x7b864c0b in kernel32 (+0x54c0a) (0x0033feb8)
15 0x7bc75a50 call_thread_func_wrapper+0xb() in ntdll (0x0033fed8)
16 0x7bc75cad call_thread_func+0x7c() in ntdll (0x0033ffa8)
17 0x7bc75a2e RtlRaiseException+0x21() in ntdll (0x0033ffc8)
18 0x7bc4dc7e in ntdll (+0x3dc7d) (0x0033ffe8)
0x0128b718: movl 0x724(%eax),%ecx
Modules:
Module Address Debug info Name (165 modules)
PE 350000- 3a9000 Deferred physx3characterkinematic_x86
PE 400000- 3875000 Export planetside2
PE 3880000- 3a48000 Deferred physx3common_x86
PE 3a50000- 3ace000 Deferred physx3cooking_x86
PE 3ad0000- 3db8000 Deferred physx3_x86
PE 3dc0000- 3fbf000 Deferred d3dx9_43
PE 10000000-10129000 Deferred apexframework_x86
PE 1ec30000-1fff0000 Deferred awesomium
PE 25670000-256f0000 Deferred apex_common_legacy_x86
PE 25800000-2584a000 Deferred apex_framework_legacy_x86
PE 25960000-25ac2000 Deferred apex_dynamicsystem_x86
PE 2b2f0000-2b344000 Deferred ortp
PE 2d940000-2d99c000 Deferred vivoxoal
PE 2ea50000-2f16c000 Deferred vivoxsdk
PE 3b400000-3b41e000 Deferred steam_api
PE 4ad00000-4b67f000 Deferred icudt
PE 6f140000-6f199000 Deferred libsndfile-1
PE 76390000-763ad000 Deferred imm32
ELF 7b800000-7b904000 Dwarf kernel32
\-PE 7b810000-7b904000 \ kernel32
ELF 7bc00000-7bcc7000 Dwarf ntdll
\-PE 7bc10000-7bcc7000 \ ntdll
ELF 7bf00000-7bf03000 Deferred
ELF 7dc15000-7dc48000 Deferred uxtheme
\-PE 7dc20000-7dc48000 \ uxtheme
ELF 7dc48000-7dc4e000 Deferred libxfixes.so.3
ELF 7dc4e000-7dc59000 Deferred libxcursor.so.1
ELF 7dc59000-7dc69000 Deferred libxi.so.6
ELF 7dc69000-7dc6d000 Deferred libxcomposite.so.1
ELF 7dc6d000-7dc76000 Deferred libxrandr.so.2
ELF 7dc76000-7dc80000 Deferred libxrender.so.1
ELF 7dc80000-7dc86000 Deferred libxxf86vm.so.1
ELF 7dc86000-7dcab000 Deferred libxcb.so.1
ELF 7dcab000-7dddf000 Deferred libx11.so.6
ELF 7dddf000-7ddf1000 Deferred libxext.so.6
ELF 7ddf1000-7de0b000 Deferred libice.so.6
ELF 7de0b000-7de14000 Deferred libsm.so.6
ELF 7de33000-7debe000 Deferred winex11
\-PE 7de40000-7debe000 \ winex11
ELF 7df1a000-7df44000 Deferred libexpat.so.1
ELF 7df44000-7df78000 Deferred libfontconfig.so.1
ELF 7df78000-7df8c000 Deferred libz.so.1
ELF 7df8c000-7e026000 Deferred libfreetype.so.6
ELF 7e028000-7e02c000 Deferred libxinerama.so.1
ELF 7e02c000-7e032000 Deferred libuuid.so.1
ELF 7e045000-7e058000 Deferred psapi
\-PE 7e050000-7e058000 \ psapi
ELF 7e058000-7e12e000 Deferred opengl32
\-PE 7e070000-7e12e000 \ opengl32
ELF 7e12e000-7e25b000 Deferred wined3d
\-PE 7e140000-7e25b000 \ wined3d
ELF 7e25b000-7e291000 Deferred d3d9
\-PE 7e260000-7e291000 \ d3d9
ELF 7e291000-7e329000 Deferred msvcrt
\-PE 7e2b0000-7e329000 \ msvcrt
ELF 7e329000-7e343000 Deferred wsock32
\-PE 7e330000-7e343000 \ wsock32
ELF 7e343000-7e45e000 Deferred oleaut32
\-PE 7e360000-7e45e000 \ oleaut32
ELF 7e45e000-7e675000 Deferred shell32
\-PE 7e470000-7e675000 \ shell32
ELF 7e675000-7e6e4000 Deferred shlwapi
\-PE 7e680000-7e6e4000 \ shlwapi
ELF 7e6e4000-7e70c000 Deferred msacm32
\-PE 7e6f0000-7e70c000 \ msacm32
ELF 7e70c000-7e784000 Deferred rpcrt4
\-PE 7e720000-7e784000 \ rpcrt4
ELF 7e784000-7e898000 Deferred ole32
\-PE 7e7a0000-7e898000 \ ole32
ELF 7e898000-7e948000 Deferred winmm
\-PE 7e8a0000-7e948000 \ winmm
ELF 7e948000-7ea3e000 Deferred comctl32
\-PE 7e950000-7ea3e000 \ comctl32
ELF 7ea3e000-7ea56000 Deferred libresolv.so.2
ELF 7ea56000-7ea5a000 Deferred libxau.so.6
ELF 7ea5a000-7ea75000 Deferred dinput8
\-PE 7ea60000-7ea75000 \ dinput8
ELF 7ea75000-7ea98000 Deferred iphlpapi
\-PE 7ea80000-7ea98000 \ iphlpapi
ELF 7ea98000-7eac8000 Deferred ws2_32
\-PE 7eaa0000-7eac8000 \ ws2_32
ELF 7eac8000-7eb2e000 Deferred advapi32
\-PE 7ead0000-7eb2e000 \ advapi32
ELF 7eb2e000-7ec34000 Deferred gdi32
\-PE 7eb40000-7ec34000 \ gdi32
ELF 7ec34000-7ed79000 Deferred user32
\-PE 7ec50000-7ed79000 \ user32
ELF 7ed79000-7ed86000 Deferred libnss_files.so.2
ELF 7ed86000-7ed92000 Deferred libnss_nis.so.2
ELF 7ed92000-7edac000 Deferred libnsl.so.1
ELF 7efac000-7efd8000 Deferred libm.so.6
ELF 7efd8000-7efe1000 Deferred librt.so.1
ELF 7efe8000-7f000000 Deferred version
\-PE 7eff0000-7f000000 \ version
ELF f3af7000-f3afb000 Deferred libgpg-error.so.0
ELF f3afb000-f3b44000 Deferred libdbus-1.so.3
ELF f3b44000-f3bb8000 Deferred libgcrypt.so.11
ELF f3bb8000-f3bc8000 Deferred libtasn1.so.3
ELF f3bc8000-f3bd1000 Deferred libkrb5support.so.0
ELF f3bd1000-f3bf9000 Deferred libk5crypto.so.3
ELF f3bf9000-f3cc8000 Deferred libkrb5.so.3
ELF f3cc8000-f3cda000 Deferred libavahi-client.so.3
ELF f3cda000-f3ce8000 Deferred libavahi-common.so.3
ELF f3ce8000-f3d80000 Deferred libgnutls.so.26
ELF f3d80000-f3dbe000 Deferred libgssapi_krb5.so.2
ELF f3dbe000-f3e11000 Deferred libcups.so.2
ELF f3e30000-f3eed000 Deferred crypt32
\-PE f3e40000-f3eed000 \ crypt32
ELF f3eed000-f3f17000 Deferred netapi32
\-PE f3ef0000-f3f17000 \ netapi32
ELF f3f17000-f3f45000 Deferred secur32
\-PE f3f20000-f3f45000 \ secur32
ELF f3f45000-f3f84000 Deferred usp10
\-PE f3f50000-f3f84000 \ usp10
ELF f3f84000-f3f97000 Deferred msimg32
\-PE f3f90000-f3f97000 \ msimg32
ELF f3f97000-f4000000 Deferred setupapi
\-PE f3fa0000-f4000000 \ setupapi
ELF f4100000-f413d000 Deferred winspool
\-PE f4110000-f413d000 \ winspool
ELF f413d000-f4175000 Deferred winhttp
\-PE f4140000-f4175000 \ winhttp
ELF f4175000-f418c000 Deferred userenv
\-PE f4180000-f418c000 \ userenv
ELF f4314000-f431c000 Deferred libogg.so.0
ELF f431c000-f4347000 Deferred libvorbis.so.0
ELF f4347000-f44bf000 Deferred libvorbisenc.so.2
ELF f44bf000-f450d000 Deferred libflac.so.8
ELF f450d000-f457f000 Deferred libsndfile.so.1
ELF f457f000-f45e4000 Deferred libpulsecommon-1.1.so
ELF f45e4000-f4632000 Deferred libpulse.so.0
ELF f464a000-f4651000 Deferred libasound_module_pcm_pulse.so
ELF f4651000-f4743000 Deferred libasound.so.2
ELF f4746000-f474d000 Deferred libasyncns.so.0
ELF f474d000-f4757000 Deferred libwrap.so.0
ELF f4757000-f475f000 Deferred libjson.so.0
ELF f4762000-f478f000 Deferred winealsa
\-PE f4770000-f478f000 \ winealsa
ELF f478f000-f47af000 Deferred mmdevapi
\-PE f4790000-f47af000 \ mmdevapi
ELF f5395000-f70b8000 Deferred libnvidia-glcore.so.310.14
ELF f70b8000-f7198000 Deferred libgl.so.1
ELF f71f5000-f723a000 Deferred dsound
\-PE f7200000-f723a000 \ dsound
ELF f723a000-f7241000 Deferred libnss_dns.so.2
ELF f7241000-f7245000 Deferred libnss_mdns4_minimal.so.2
ELF f7245000-f7263000 Deferred libgcc_s.so.1
ELF f7264000-f7282000 Deferred dnsapi
\-PE f7270000-f7282000 \ dnsapi
ELF f7282000-f7287000 Deferred libcom_err.so.2
ELF f7287000-f729b000 Deferred dhcpcsvc
\-PE f7290000-f729b000 \ dhcpcsvc
ELF f72a8000-f72bb000 Deferred sensapi
\-PE f72b0000-f72bb000 \ sensapi
ELF f72bb000-f7300000 Deferred dinput
\-PE f72c0000-f7300000 \ dinput
ELF f7400000-f7404000 Deferred libkeyutils.so.1
ELF f7445000-f744e000 Deferred libnss_compat.so.2
ELF f744f000-f7454000 Deferred libdl.so.2
ELF f7454000-f75fe000 Deferred libc.so.6
ELF f75fe000-f7619000 Deferred libpthread.so.0
ELF f762c000-f7630000 Deferred libnvidia-tls.so.310.14
ELF f7639000-f777a000 Dwarf libwine.so.1
ELF f777c000-f779e000 Deferred ld-linux.so.2
ELF f779e000-f779f000 Deferred [vdso].so
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
0000001f 0
0000001e 0
00000015 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001c 0
00000019 0
00000014 0
00000013 0
0000001a plugplay.exe
00000020 0
0000001d 0
0000001b 0
00000021 explorer.exe
00000022 0
0000000c (D) C:\Program Files\Sony Online Entertainment\Installed Games\PlanetSide 2\PlanetSide2.exe
00000035 0
00000034 15
00000032 0
00000030 0
00000023 0
00000027 0
00000067 0
00000066 0
00000065 0
00000064 2
00000063 2
00000062 0
00000061 0
00000060 0
0000005e 0
0000005d 0
0000005c 0
0000005b 0
0000005a 0
00000059 0
00000058 0
00000057 0
00000056 0
00000055 0
00000054 0
00000053 0
00000052 0
00000051 0
00000050 1
0000004f 0
0000004e 0
0000004d 0
0000004c 0
0000004b 0
0000004a 0
00000049 0
00000048 0
0000000d 0
00000037 0
00000038 0
0000003d 0
0000003e 0
0000002b 0
0000002a 0
0000000b 0

Confirmed -- AFAIK the new update seems to break Wine compatibility for everyone, which is no fun. I can get to the character select screen, but when I click "Play" from there the game quits.

You seem to be right in that it's the same error that you get when changing graphical settings in the options menu.

I find that clicking "Reset to defaults" in the options menu crashes the game -- Did it used to do that before? Perhaps this indicates a change in default graphics settings?

Hmm I'm currently not at home, but could you try to delete the Useroptions.ini file? that should reset to the (new?) defaults.

I tried that, but when I relaunched, after hitting the "Play" button in the launcher (before the character select screen), I got a popup saying, "Failed to create D3D object" and Game Error G2 in the browser.

I foolishly didn't back up that file; can you post yours when you get home?

I sure can but that will be another day of waiting ;). But you may want to try to re-validate the game assets (or something along that lines) in the options of the launcher. That should help.

I tired it, and it still crashes on me as well.

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 am also trying to explain the benefits of wine compatibility to SOE as well. You can help by telling SOE how much money you spent on Linux gaming last year. Post a reply here:

forums.station.sony.com/ps2/index.php?threads/usersupportthread-ps2-on-linux-with-wine.47255/page-6#post-1418635

Agreed. The latest update breaks compatibility with every Wine user; fix that and the mouse jitter bug, and I'll pledge $15 with you to the Wine Foundation. Perhaps we should post this somewhere where more Wine developers can see it.

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.

OMG SAME HERE! I have struggled with this and it is so sad. I am looking now to see maybe if a certain setting that low disables couldbe it. I reccomend looking at the Useroptions.ini file and changing some numbers to see if you can pinpoint the problem. Hope this helps!

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

I can't seem to be able to start Planetside 2 (or, more importantly, its launcher) on my Linux box. I installed it via Steam, and here's the error I get when I try to run LaunchPad.exe:

habs.name/planetside/error.txt

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.

Oh jeez; seems like WineHQ comments strip links if they're enclosed in HTML brackets. Well the SP3 download is here:

www.microsoft.com/en-us/download/details.aspx?id=24

And the post that I got the idea from was here:

forums.station.sony.com/ps2/index.php?threads/usersupportthread-ps2-on-linux-with-wine.47255/page-6#post-1213564

Thanks again.

First of all I find this amusing :

p11-kit: couldn't load module: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

thought that this is only a problem in ubuntu at the moment ...

could you list the "bunch of other packages" you'v installed via winetricks?

Here's the output of "winetricks list-intalled":

corefonts
d3dcompiler_43
d3dx10
d3dx11_42
d3dx11_43
d3dx9_26
d3dx9_28
d3dx9_31
d3dx9_35
d3dx9_36
d3dx9_39
d3dx9_42
d3dx9_43
d3dx9
directx9
vcrun2008
xact_jun2010
xact
xinput

Thanks for your help.

Sry for the late answer, was a bit busy lately...okay here we go:

First of all you shouldn't use steam, as mentioned in the steam-section for this game it won't give you benefits, just download the installer for planetside 2, steam also only uses the same launcher as the installed version.

Secondly, don't copy the imm32 to all these folders, if you have an 32 bit prefix ( set with 'export WINEARCH=win32' before creating the prefix ) then copy it to the system32 folder, otherwise if you use a 64bit prefix ( WINEARCH=win64 | or standard if you use a 64 bit linux ) then copy the dll to the syswow64 folder.

Thirdly I would highly recommend to only use the winetricks mentioned here for the beginning.

d3dx9 ( or you install directx via the installer )
d3dx9_43
d3dcompiler_43

and maybe the vcrun2008 if the installer won't run, but I haven't installed it so far.

Maybe you should test it again in a clean prefix.


Greetings and good luck to you

Actually it should also work if you throw the imm32 in the same diretory as the PS2 executeable. I havn't tested it but it should be no different to SweetFX or ENB Series.

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 :-)

Does anybody can help me?

Sorry for my english.

For the DX-Error, sometimes it helps me to install it with the official ms-installer think it's called directx-june web installer.

32 bit driver for my geforce gtx 260 works for me, no can play but often many lags in BigBattle

My FPS are nearly doubled after last patch. 35-45 on low with geforce 460.
Unfortunately jittering is still there, making it unplayable.

I did quite a few tests on my MacBook Pro with a few of the third party applications listed here: wiki.winehq.org/ThirdPartyApplications

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).

For more info click here: www.codeweave...e/?app_id=10782

Hope this helps,

Ethan

Thx for the test results. Have you actually encountered the same wierd problems with the steam-version? Like the mouse-jittering and the imm32-override?

No imm32 overrides, but the mouse jitter is off and on, most noticeable when scoped or zoomed in. I found that widening the field of view has been quite effective in diminishing this although I can say it is much less compared to using strait up wine to run it so there must have been some kind of patch from the third party to try and fix it. Overall the game is very easily playable. In the end, it is usually quite smooth in comparison. The gun itself will jitter in your hand a bit when you turn your view usually while sprinting but that doesn't affect anything too much and you get used to it after a while anyway.

Hope this helped,

Ethan

Benchmarks indicate that threaded GL in the NVIDIA driver actually slows down performance.

www.phoronix.com/scan.php?page=article&item=nvidia_threaded_opts

The recommendation to enable this for Planetside 2 should be removed. Just because an option looks like it should help performance does not guarantee that it will.

Can you confirm the slowdown when setting WINEDEBUG=-all?

Winedebug by default calls GetError that completely defeat the purpose of Multithreading (Read bugs.winehq.org/show_bug.cgi?id=11674#c274 that bug comments contain many more indepth info starting about comment 260)

Please understand that threaded GL only benefits very specific applications. Enabling GL threading is not a cure-all for every OpenGL application and in this case it can actually decrease performance.

If you bothered to click on the link I provided you would have found that the benchmarks are for native Linux applications.

People get ideas in their head about video driver tweaks and believe enabling any option will speed up their application when it is only a placebo effect.

Why should I remove a tweak that works perfectly fine for this game? We have reports from several systems that experience a steep increase in Performance.

This Game profits just fine from that tweak. Its listed under optional tweaks for this game (and some others like GW2 and SC2). Why should I held back on a vaiable tweak that has NO impact on other applications (like some wine patches would have).

If people get wrong ideas they will soon discover that the threading is not a wonder-cure for everything, not even for every wine game.

On the other hand the possible gains (I read on several places about 10-30% depending on game) justifies to test every game with it, hey it's free performance.

Could I see a few replies from people with the following info:

Video card
Video driver
CPU

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.

GTX 680
313.09
i7 3770k

mdium fps about 25-30 spread from 20-60. FPS wise it is playable but the mouse jittering make it unplayable.

GTS 450 GLH
313.09
i5 Quad 2.8 Ghz


average 30 fps on medium settings and in kinda crowded battles

Well just tested the daily Ubuntu 13.04 build and fps got increased for me doing so, even the mouse jitter isn't as bad as before.

Just saying ^^

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.

Does anyone have any luck with mouse jitter issues?

Nope, same problem here so far and no solution at the moment :/

I must also confirm this.
This sucks... Just like in beta: Get it to run, patch, start over...

Yeah, I'm seeing the same exact thing.

So, does someone has any new progress ?

Has anyone figured out yet how to cope with that problem?

It doesn't seem like it, but what I've noticed so far is that doesn't happens in a few places.

Where I have not noticed it:
Driving a lightning or any MBT w/primary gun (but did notice it in 3rd person view with a lightning and the MBTs; except for the Magrider, possibly due to how the Mag is controled).
Flying any ESF, Liberator or Galaxy.
In a fixed base turret (any type, but the WG outposts didn't have an AI turret to verify).

I've observed jitter in these circumstances:
On Foot as infantry or MAX (a little right at login, but it gets significantly worse after a loading screen or two)
Driving a Sunderer or Flash (Mouse look while driving)
Any turret on any vehicle that you're not also driving (ie: Sundy turrets, Galaxy turrets, MBT secondary, etc).
Deployed Engineer Turret


When doing my testing, I noticed that the jitter felt FPS bound to some degree. If I was getting an indicated FPS of more than 35-40 FPS (I saw some spikes of up to 90 FPS in an empty WG on Miller), the jitter on foot wasn't there or noticeable. But if it dropped to 30 or below, the jitter was there but the rest of the game still seemed smooth. However, when I did the MBT tests I was getting an indicated 20-30FPS in game and the control was still smooth.

I think it is time to put up a propper bugreport in wine about this, maybe someone of the Devs/Debuggers has some idear how to get to it.

So do you'v already done that? Just tried today with a separate x-server...fps increased but jitter is still there. Testing all day long but nothing seems to work just decrease the problem a bit...

Ah I forgot. I'm currently swamped with the upcoming Exams so I haven't had time to aquire some data to help the report.

Well it's okay, I would do it but I realy have no idea what I have to do / add as logs. Can't see trough that weird stuff on the bug-wikipage...

With the latest patch (from around 10 jan), my FPS is nearly doubled (from 10-20 up to 20-35 in the WG) and feels much smoother. I still get some mouse jitter, but it isn't as bad as before, and during some low-intensity scenes, it is gone. I even saw 40 FPS at one point.

Another thing that helps is to direct the stdout and stderr of wine to /dev/null. Just add: " > /dev/null 2>&1 " after your wine command. This suppresses a never-ending stream of "fixme:d3d:query_init Unhandled query type 0xa." messages, which seem to add some overhead to my terminal. Running with the messages, I got 10fps, without, 20-25 in the warpgate. (Only did one or two trials, so this might not be conclusive).

I'm running 64 bit gentoo, 3.7.1 kernel, 1.5.21 wine, on an AMD Phenom II 4 core 965, with an ATI HD4850 with fglrx ati-drivers-12.6_beta_pre897. I currently play in a window, around 1400x1050 (might increase that), with the settings on Low or Off (set values to 0 in Useroptions, especially shadows).

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.

Try hitting Alt. It is supposed to toggle from the blue mouse pointer on and off.

I did, that is what I'm talking about. The game acts like there is no keyboard

try to upgrade wine to 1.5.20
cause i had the same problem before (with wine 1.4.x of ubuntu 12.10)
i upgraded to wine 1.5.20 (look at wine hq site how to do it)and this problem is resolved.

ubuntu 12.10 (with wine 1.5.20 now)

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".

example here: imagebin.org/238564

it's as though I am missing some kind of localisation or font package??

I am on opensuse 12.2 BTW.

Thanks

On further investigation this was actually a bug in PS2 itself, sorry to have brought it up

Alright, I'm at a total loss.

Game used to run decently enough, but I upgraded to the latest stable version of my distro, now, the game will install but the launcher refuses to connect.

Launchpad Error Message:
LaunchPad was unable to connect. Please check the network connection or try again later. If the problem persists, please visit www.soe.com/help for assistance.
(4-404)

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?

PREVIOUS distro version: Slackware64 13.37 (multi-lib)
CURRENT distro version: Slackware64 14.0 (multi-lib)

Attempts done with wine versions (all packaged up, gotten from winehq's links):
i486-1.5.15; i486-1.5.18; x86_64-1.5.15; x86_64-1.5.18 (this is currently used)

recent attempt's order of steps done (NOTE, backed up .wine-ps2 after each major step):

1. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 wineboot
> gecko made it in
> imm32.dll moved in, as well being set to "native"

2. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 winecfg
> set virtual desktop size;
> redirected some save-to folders;
> adjusted drive D to point to games directory.

3. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 winetricks directx9
> previously tried just d3dx9_43 & d3dcompiler_43

4. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 winetricks vcrun2008

5. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 wine "D:\Installer\PS2_setup.exe"
> installer installs fine, begins to enter "connect phase" and never connects.

TERMINAL OUTPUT:
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
err:shell:SHGetFileInfoW pidl is null!
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
preloader: Warning: failed to reserve range 00010000-00110000
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
err:setupapi:do_file_copyW Unsupported style(s) 0x144
preloader: Warning: failed to reserve range 00010000-00110000
bash-4.2$ fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:time:GetSystemTimes (0x33f4b4,0x33f4a4,0x33f4ac): Stub!
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x333a40,0x00000000), stub!
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:time:GetSystemTimes (0x33a4fc,0x33a4ec,0x33a4f4): Stub!
wwsCrashReportCreate: could not find uploader
fixme:browseui:ProgressDialog_SetAnimation (0x132900, 0xf7120000, 161) - stub
fixme:browseui:ProgressDialog_StartProgressDialog Flags PROGDLG_AUTOTIME not supported
Parsing digest
Iterating through digest
00.04%: Installed LaunchPad.libs/Web/images/install-bar-bg.jpg (13,521 bytes)
00.35%: Installed LaunchPad.libs/locales/en-US.dll (110,592 bytes)
00.36%: Installed LaunchPad.libs/Web/css/img/soe-logo.png (2,986 bytes)
00.36%: Installed LaunchPad.libs/Web/css/img/waiting-loading.gif (845 bytes)
00.37%: Installed LaunchPad.libs/Web/images/carousel/carosuel-nav.png (2,377 bytes)
00.37%: Installed LaunchPad.libs/Web/images/carousel/carousel_left_btn-1.png (2,252 bytes)
00.38%: Installed LaunchPad.libs/Web/images/carousel/carousel_left_btn.png (3,464 bytes)
00.39%: Installed LaunchPad.libs/Web/images/login-box-error.png (3,410 bytes)
00.40%: Installed LaunchPad.libs/Web/images/wrapper/topnav-arrow-open.png (1,370 bytes)
00.40%: Installed LaunchPad.libs/Web/images/wrapper/topnav-arrow.png (1,280 bytes)
00.41%: Installed LaunchPad.libs/Web/images/login-box.png (5,135 bytes)
00.44%: Installed LaunchPad.libs/Web/images/login-button-green.png (7,652 bytes)
00.44%: Installed LaunchPad.libs/Web/images/carousel/carousel_right_btn-1.png (2,392 bytes)
00.45%: Installed LaunchPad.libs/Web/images/carousel/carousel_right_btn.png (3,551 bytes)
00.47%: Installed LaunchPad.libs/Web/images/installButton/2.png (5,994 bytes)
00.49%: Installed LaunchPad.libs/Web/images/installButton/3.png (9,099 bytes)
00.50%: Installed LaunchPad.libs/Web/images/progress/install2.png (3,029 bytes)
00.51%: Installed LaunchPad.libs/Web/images/progress/preload.png (1,122 bytes)
00.51%: Installed LaunchPad.libs/Web/images/scrollbar/arrow-down.png (1,368 bytes)
00.51%: Installed LaunchPad.libs/Web/images/scrollbar/arrow-up.png (1,348 bytes)
00.53%: Installed LaunchPad.libs/Web/images/installButton/btn-play (2).png (6,283 bytes)
00.54%: Installed LaunchPad.libs/Web/images/scrollbar/bg-scrollbar-thumb-y.png (1,457 bytes)
00.54%: Installed LaunchPad.libs/Web/images/scrollbar/bg-scrollbar-trackend.png (938 bytes)
00.54%: Installed LaunchPad.libs/Web/images/scrollbar/bg-scrollbar-track-y.png (989 bytes)
00.57%: Installed LaunchPad.libs/Web/images/wrapper/border-bg.png (9,418 bytes)
00.57%: Installed LaunchPad.libs/Web/images/wrapper/button-language.png (2,339 bytes)
00.67%: Installed LaunchPad.libs/Web/images/wrapper/waiting-loading.gif (34,997 bytes)
00.68%: Installed LaunchPad.libs/Web/images/wrapper/window-controls.png (2,111 bytes)
00.78%: Installed LaunchPad.libs/Web/images/installButton/btn-play.png (35,556 bytes)
00.81%: Installed LaunchPad.libs/Web/images/progress/cover.png (11,000 bytes)
00.82%: Installed LaunchPad.libs/Web/images/progress/download.png (2,783 bytes)
00.82%: Installed LaunchPad.libs/Web/images/progress/file-check.png (996 bytes)
00.82%: Installed LaunchPad.libs/Web/images/progress/install.png (1,137 bytes)
00.90%: Installed LaunchPad.libs/Web/images/wrapper/content-bg-1.jpg (26,544 bytes)
00.90%: Installed LaunchPad.libs/Web/js/loading.js (939 bytes)
00.90%: Installed LaunchPad.libs/Web/js/window-controls.js (1,491 bytes)
00.91%: Installed LaunchPad.libs/Web/error-connection.html (2,656 bytes)
00.95%: Installed LaunchPad.libs/Web/loading.css (13,205 bytes)
01.19%: Installed LaunchPad.libs/Web/images/action-menu-bg.png (85,311 bytes)
01.19%: Installed LaunchPad.libs/Web/loading.html (1,672 bytes)
01.20%: Installed LaunchPad.libs/Web/images/advanced-menu-back.jpg (1,719 bytes)
01.29%: Installed LaunchPad.libs/Web/images/wrapper/content-bg-2.jpg (32,213 bytes)
01.29%: Installed LaunchPad.libs/Web/images/wrapper/footer-bg.png (1,334 bytes)
01.31%: Installed LaunchPad.libs/Web/images/advanced-settings.jpg (6,626 bytes)
01.33%: Installed LaunchPad.libs/Web/images/btn-action-menu.png (5,888 bytes)
01.33%: Installed LaunchPad.libs/Web/images/close-button.png (2,814 bytes)
01.34%: Installed LaunchPad.libs/Web/images/create-account-icon.png (1,651 bytes)
01.36%: Installed LaunchPad.libs/Web/images/default-button-green.png (6,087 bytes)
01.37%: Installed LaunchPad.libs/Web/images/default-button-red.png (6,159 bytes)
01.39%: Installed LaunchPad.libs/Web/images/dropdown-menu.png (6,508 bytes)
01.40%: Installed LaunchPad.libs/Web/images/error-header.png (1,140 bytes)
01.55%: Installed LaunchPad.libs/Web/images/wrapper/header.jpg (53,972 bytes)
01.55%: Installed LaunchPad.libs/Web/images/wrapper/letter.png (1,985 bytes)
01.71%: Installed LaunchPad.libs/Web/images/wrapper/PS2_Logo.png (54,621 bytes)
01.71%: Installed LaunchPad.libs/Web/images/wrapper/soe-logo.png (2,986 bytes)
02.00%: Installed LaunchPad.libs/Web/images/get-started-bg.png (101,248 bytes)
02.05%: Installed LaunchPad.libs/Web/images/get-started-new.png (17,863 bytes)
02.77%: Installed LaunchPad.libs/Web/images/mask-bg.jpg (258,416 bytes)
02.78%: Installed LaunchPad.libs/Web/images/menu-back.png (2,877 bytes)
04.48%: Installed Uninstaller.exe (602,568 bytes)
05.73%: Installed LaunchPad.libs/AwesomiumProcess.exe (448,000 bytes)
05.83%: Installed LaunchPad.libs/SOELogo.bmp (32,734 bytes)
06.33%: Installed LaunchPad.libs/Web/images/modal-error-bg.png (178,008 bytes)
07.15%: Installed LaunchPad.libs/wws_crashreport_uploader.exe (293,888 bytes)
07.75%: Installed LaunchPad.libs/Web/images/modal-login-bg.png (213,942 bytes)
08.52%: Installed LaunchPad.libs/Web/images/modal-reg-bg.png (275,075 bytes)
08.81%: Installed LaunchPad.libs/Web/images/news-bg.png (101,578 bytes)
08.82%: Installed LaunchPad.libs/Web/images/news-hover.png (2,881 bytes)
08.83%: Installed LaunchPad.libs/Web/images/reg-state-failed.png (3,237 bytes)
08.84%: Installed LaunchPad.libs/Web/images/reg-state-passed.png (3,144 bytes)
08.84%: Installed LaunchPad.libs/Web/images/select-object.png (1,064 bytes)
08.85%: Installed LaunchPad.libs/Web/images/star.png (4,009 bytes)
08.85%: Installed LaunchPad.libs/Web/js/error.js (787 bytes)
39.58%: Installed LaunchPad.libs/icudt42.dll (10,941,440 bytes)
100.00%: Installed LaunchPad.libs/Awesomium.dll (21,510,144 bytes)
Installed 36,573,910 bytes
fixme:browseui:ProgressDialog_SetAnimation (0x137f40, 0xf7120000, 161) - stub
fixme:browseui:ProgressDialog_StartProgressDialog Flags PROGDLG_AUTOTIME not supported
Parsing digest
Iterating through digest
35.76%: Installed Uninstaller.exe (602,568 bytes)
35.76%: Installed ApplicationUpdater.ini (25 bytes)
82.53%: Installed ApplicationUpdaterService.exe (787,936 bytes)
100.00%: Installed wws_crashreport_uploader.exe (294,400 bytes)
Installed 1,684,929 bytes
fixme:browseui:ProgressDialog_SetAnimation (0x137f18, 0xf7120000, 161) - stub
fixme:browseui:ProgressDialog_StartProgressDialog Flags PROGDLG_AUTOTIME not supported
preloader: Warning: failed to reserve range 00010000-00110000
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:time:GetSystemTimes (0x33f4b4,0x33f4a4,0x33f4ac): Stub!
fixme:browseui:ProgressDialog_SetAnimation (0x132ed0, 0xf7180000, 161) - stub
fixme:browseui:ProgressDialog_StartProgressDialog Flags PROGDLG_AUTOTIME not supported
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
Parsing digest
Iterating through digest
Installed 36,573,910 bytes
preloader: Warning: failed to reserve range 00010000-00110000
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:time:GetSystemTimes (0x33f4b4,0x33f4a4,0x33f4ac): Stub!
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x333a40,0x00000000), stub!
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:time:GetSystemTimes (0x33a4fc,0x33a4ec,0x33a4f4): Stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:iphlpapi:NotifyAddrChange (Handle 0x388e7cc, overlapped 0x31fd070): stub
preloader: Warning: failed to reserve range 00010000-00110000
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
preloader: Warning: failed to reserve range 00010000-00110000
fixme:file:ReplaceFileW Ignoring flags 2
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
fixme:file:ReplaceFileW Ignoring flags 2
preloader: Warning: failed to reserve range 00010000-00110000
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
fixme:time:GetSystemTimes (0x33f474,0x33f464,0x33f46c): Stub!
fixme:time:GetSystemTimes (0x33f3ec,0x33f3dc,0x33f3e4): Stub!
preloader: Warning: failed to reserve range 00010000-00110000

6. WINEARCH=win32 WINEPREFIX=/home/user/.wine-ps2 wine "D:\SOE\ps2\LaunchPad.exe"
> Vain attempt to connect via launchpad instead.

TERMINAL OUTPUT:
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:time:GetSystemTimes (0x32f4b4,0x32f4a4,0x32f4ac): Stub!
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x323a40,0x00000000), stub!
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0)
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:time:GetSystemTimes (0x32a4fc,0x32a4ec,0x32a4f4): Stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:iphlpapi:NotifyAddrChange (Handle 0x386e7cc, overlapped 0x31d7070): stub
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
fixme:file:ReplaceFileW Ignoring flags 2
preloader: Warning: failed to reserve range 00010000-00110000
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:gdi:GdiInitializeLanguagePack stub
preloader: Warning: failed to reserve range 00010000-00110000

______________

- 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?

I have a sneaking suspicion that this time around (slack14) that Awesomium isn't getting through for *some reason*.

LINE EXCERPT of terminal output, using debug +snoop:

0009:CALL Awesomium.?? 0JSValue@Awesomium@@QAE@PB_W@Z(00707d0c L"LaunchPad was unable to connect. Please check the network connection or try agai") ret=0041e6ca

If I understand that, it's Awesomium throwing the connection complaint?

First of all you don't have to do WINEARCH everytime, same for WINEPREFIX.

Just USE "export WINEARCH=win32/64" and "export WINEPREFIX=your/path" followed by "winecfg" to create your new prefix in the environment you want ( 32bit or 64bit ) that's enough. If used in a shell the variable for the WINEPREFIX ( called by using $WINEPREFIX ) will be set to your given path. Means that furthermore in a new shell you just have to reuse "export WINEPREFIX=your/path" again and no more WINEARCH, cause it's set in the prefix.

Just wanted to add that, will look through the log tomorrow, allready late here.

Ah, okay. I was using a script originally, using some exports (not winearch, as originally I used the 32bit only wine package), so thought I needed them still. Not terribly familiar with the various prefix methods, as I use to just use the main .wine prefix for everything, before I tried ps2 on/in anything.

Question:
with custom prefixes, by using WINEARCH & WINEPREFIX in the same command line, am I causing any damage? Or is this more of a "good practice"?

Well I never heard about that this could cause damage to your prefix, but you should use a new wineprefix for each program you want to install. Because the dependencies can vary hugely and you are able to use 64bit prefixes for many games and get improvements.

So that makes me wonder:

fixme:win:User32InitializeImmEntryTable (0x19650412): stub

Have you copied a native imm32 into your prefix like the guide above has told you to do?

That fixme appears also with a native imm32.dll

The fixme is caused from user32.dll not imm32.dll (no a native user.dll doesn't work well). As far as I see it this fixme does not impact functionality.

Correct, pulled it over from my native XP folder. winecfg was set to assume it's windows Xp, as it was pre-upgrade.

the stock wine imm32.dll was just renamed to imm32.dll.bak, then the native one dropped in.

I can now be certain, that the preloader warnings have nothing to do with this issue. Over in www.linuxquestions.org/questions/slackware-14/dos-support-unavailable-855667/ Pat explained how to correct such warnings, I tried that, no change, and have now reverted back to the way it was.

As another test, I've tried to just get the game to launch with zero adjustments, and still, same error.

Tried winetricks sandbox, no change. ie8, vcrun2010, vcrun2008, nothing seems to be working.

Poking on the forums, has revealed this MIGHT not be just me, but windows users as well. forums.station.sony.com/ps2/index.php?threads/launchpad-was-unable-to-connect.47556/

Deleting /soe/ps2/LaunchPad.libs to force Launchpad to redownload the rest of itself, same result.

I've started receiving this as well. I checked the launchpad log files located in $PLANETSIDEDIR/LaunchPad.libs/Logs. I believe I've found what the launcher is attempting to load.

I see several instances where the launcher attempts to load this URL - lp.soe.com/ps2/live/?t=42949

2013-01-05 02:14:12 1357373649 367 4 4294971633 (Main) onBeginNavigation, url=lp.soe.com/ps2/live/?t=42949, frameName=.

It ultimately ends up failing with -
2013-01-05 02:14:12 1357373649 416 4 4294971851 (Recovery) SetExternalObjectProperty - objectName=LauncherViewport, propertyName=LastErrorMessage, value=LaunchPad was unable to connect. Please check the network connection or try again later. If the problem persists, please visit www.soe.com/help for assistance..
2013-01-05 02:14:12 1357373649 417 4 4294971851 (Recovery) SetExternalObjectProperty - completed, objectName=LauncherViewport, propertyName=LastErrorMessage, value=L, totalTimeMs=0.
2013-01-05 02:14:12 1357373649 418 4 4294971851 (Recovery) SetExternalObjectProperty - objectName=LauncherViewport, propertyName=LastErrorCode, value=4-404.
2013-01-05 02:14:12 1357373649 419 4 4294971851 (Recovery) SetExternalObjectProperty - completed, objectName=LauncherViewport, propertyName=LastErrorCode, value=4, totalTimeMs=0.
2013-01-05 02:14:12 1357373649 421 4 4294971852 (Recovery) LoadUrl - url=local:error-connection.html

When I put "lp.soe.com/ps2/live/?t=42949" into my web browser. I'm able to load the page just fine. This leads me to believe that something within Wine isn't allowing this page to load. Perhaps the fact that it's using SSL? Granted I'm spit balling here but somethings better than nothing.

As Featherbane hints to below, this has to do with Wine not finding some libs needed for SSL.

On Arch Linux, the issue can be fixed by installing lib32-gnutls (and its deps: lib32-gmp lib32-libtasn1 lib32-nettle lib32-p11-kit).

Could someone test if these libs are still needed with the new 1.5.23 version? They seem to chaned the HTTPS implementation to no longer depend on OpenSSL

They seem to still be needed (tested on Arch).

Alrighty, between slackware64_13 to slackware64_14, there were at least two files that needed to be made 32bit compatible, n/nettle and n/p11-kit.

For those of us who are either lazy or well rested, Alienbob has "refreshed the multilib compat32 package set for Slackware 14 and -current." (nettle, p11-kit, and gmp are new, it looks).

Now that I've added in those three compat32 packages, Launchpad successfully connects.

Now to resume testing.

www.omgubuntu.co.uk/2012/12/planetside-2-dev-gives-hope-for-linux-port

Support it so that we maybe can get rid of wine for ps2 :)

Unlikely, but I gave my +1.)

Hi there,

I'm trying to run Planetside 2 on my mid 2012 MBP but i'm a fcking noob.

First I tried to understand something by reading this page but... I need skills.

Then I tryed with Wine and wineskin, creating my wrapper etc etc.. and get problems with "config.ini" when trying to run the game.

Because of that, I use wine bottler in order to make my life easier (I hope it could have been) but i have a problem when creating the app with DirectX 9.

I have a message from xquatz "DirectX 9.0 web setup --> command line option syntax error" and... I don't understand.

May you be able to help me ? :S

So I try to write a step by step guide with all the commands you possibly need to type in shell:

1. export WINEARCH=win32 or
export WINEARCH=win64 | depends on you which environment you want to use

2. export WINEPREFIX=$HOME/.wine-planetside2 | creates the prefix for installation in your Home-Folder, hidden.

3. winecfg | in winecfg go to graphic tab and choose virtual desktop and capture mouse in fullscreen

4. winetricks -q d3dx9

5. winetricks -q vcrun2008

6. cd to the folder in which you have the ps2-install-file for example cd $HOME/Downloads

7. wine ps2-install-file

6. install planetside 2 using express-installation

7. cd into the wineprefix for example cd $WINEPREFIX/drive_c/path/to/game-folder

8. wine launcher.exe


Now the launcher should start in a separate wine desktop and start downloading the game. These steps don't contain any tweaks or the imm32-override ( you can find the steps above )


Hope it may be helpfull, for scripts to optimize the process or start the game you can look into the posted scripts above too.


Greetings

missed one step ... between 5 and 6 you need d3dcompiler_43 to run the game so:

winetricks -q d3dcompiler_43

Thanks for help !

The game starts, check it DL, but before it reach the menu the game crashes with an error : "Unhandled exception : page fault on read access to 0x000000000 in 32bit code (0x016bf432)"

Any idea ?

Did you tried the imm32.dll fix before? You need a native imm32 in order to use the ingame menus. You can read the guide just above.

I found one DL on dll-files, I put the new imm32"dll in cdrive/windows/system32

You did WINEARCH=win32 or win64?

I think I don't understand what you mean with WINEARCH=win32

I will quote myself:

"1. export WINEARCH=win32 or
export WINEARCH=win64 | depends on you which environment you want to use "

this defines which sort of windows is used, 32bit or 64bit. If u use a 64bit Linux and just create a new prefix it will be 64bit, you can create a 32bit environment if u use "export WINEARCH=win32" before you create a new prefix.

The step to step guide was meant to be used in a shell without any wine-bottler-programm

But where (or how) do I use this "export WINEARCH=win32" ? Here is my problem...

(I'm working with OSX 10.8)

You start in a clean shell.

type:

export WINEARCH=win32

/ or

export WINEARCH=win64


#that will set the 32 or 64bit environment for the next created prefix

export WINEPREFIX=$HOME/.wine-planetside2

#set the variable $WINEPREFIX to the given path, it will be saved by wine for the next commands as your home prefix

winecfg

#will create the new prefix with the choosen environment ( can check it up in the prefix, 32bit only have the folder "Programm Files" where 64bit also contains "Programm Files(x86) )


That's how you should start creating a new prefix, after these 3 steps you'v created a clean new prefix for further usage, like winetricks and installing programms into that prefix.

But remember, you have to set the WINEPREFIX again in a new shell or when u use a script, so if u close your shell and want to reuse the created prefix just type:

export WINEPREFIX=$HOME/.wine-planetside2

before going on

Maybe after all I forgot about the OSX fact, don't think that OSX use the "export" command. Just looked up the Archwiki Wine-Page maybe that could help you to understand the WINEARCH-thingy a bit better then my explanations :)

wiki.archlinux.org/index.php/Wine

I discovered a alternative workaround for the mouse jittering:
When playing on a separate X screen I can use Fullscreen mode and have no mouse stuttering (and 5+ FPS boost).

This also gives a hint what is causing the jittering in the first place: The Window manager/compositor (maybe even only gnome/mutter?)

For playing on a different X screen add the following to the beginning of your PS2 Start-up script: (Beware Nvidia version)
X :1 -ac -terminate & nvidia-settings --load-config-only;
sleep 10;
export DISPLAY=:1;

Would love to try that but comes up with "Can't open Display" after loading all the modules.

maybe your screen :1 is already in use.
Try replacung all occurences of :1 with :2

Okay well I started a new xserver with

xinit -- :1

and then run my start script, first thing was that I couldn't swap the cpu-governor in the new x-server...saddest thing was that in fullscreen the jittering just began on start

does it work with
xinit /usr/bin/wine game.exe -- :1
or
xinit /path/to/your/script -- :1

So I got it working with google and a second script:

x.ps2.sh

#!/bin/bash

xauth add :1 . $(mcookie)

ps2task &

DISPLAY=1

xinit $HOME/Documents/Scripts/PlanetSide2 $* -- :1

read foo



but samething, jittering starts right after logging in fullscreen.

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?

Well I use

my multicore-script,

the GL_Threading Optimisation for nvidia 310.14+ driver from Guild Wars 2 ( mentioned in tweak-section above )

and the 3 winetricks tweaks vsm=hardware multisampling=enabled psm=enabled

playing at mostly all low settings except for graphic and texture settings to medium and getting almost stable 30+ fps even in big battles around the crown. So it will be depending basically on your hardware. But I would try those 3 things at least before saying it's nearly unplayable.


Greetings so far

Any chance of a step by step guide for the scripts?
Creating a script with the openGL commands, and exactly what to do with the other script...

Sorry Im still new to Linux.

Mabe its clearer when I post my take (I leave out the CPU governor things)
My planetside.sh:
pastebin.com/hxi9V3sN
This is the script I run when I start the game (take note of the paths you'll have to adjust them.
My ps2opt.sh:
pastebin.com/Eg19Etx2
this one does not to be modifyed by you, but to set the numbers behind taskset fiting for your cpu (0-7 for 8 cores, 0-3 for 4 cores etc.)

So the Planetside.sh sets the eviroment variables and runs the ps2opt.sh. The ps2opt.sh lingers in the background until it finds a running Planetside2.exe, this and the running wineserver and winedevice then get a treatment with taskset.

Alright, that sounds easy enough, ill try this out.
Thanks for spelling it all out.

I'm getting these errors:

planetside.sh: line 6: winefps: command not found
planetside.sh: line 4: /home/MyName/optscripts/ps2opt.sh: Permission denied

Let me do a step by step of what I did incase there are other Linux Noobs like me here.

1. Take the text from the two scripts posted and paste it int two new txt files named planetside.sh and ps2opt.sh.

2. Adjust the directories in planetside.sh(both the CD line and the WINEPREFIX line)

3. Place the ps2opt.sh in a new folder called /optscripts in /home/MyName/

4. run planetside.sh by typing: bash planetside.sh or: sudo bash planetside.sh

(both gave me the permission denied message)

You have to make the script executionable:

sudo chmod +x /home/MyName/optscripts/ps2opt.sh


And what the command winefps stands for I can't say, I bet it's not a basic wine-command. Just use "wine" instead.

Forgot that: Don't ever run wine or scripts for wine with sudo / root

oh replace winefps with wine. That one is another script I wrote to to put the output of WINEDEBUG=+fps onto a osd.

don't want to start another topic ... could you change the command

"export __GL_THREADED_OPTIMISATIONS=1;"

to

"export __GL_THREADED_OPTIMIZATIONS=1;" ?

Someone mentioned at GuildWars2 that this would be the correct one, referring to the nvidia documentation. Or can u confirm that "S" is working too? Cause I use it with "Z" all the time.


appdb.winehq.org/objectManager.php?sClass=version&iId=26558

-first comment on the site


Greetings

You're right it has to be written with a "Z"...
But doing so hurts performance extreme (30 vs 10 fps at warpgate).

But
"export __GL_THREADED_OPTIMISATIONS=1;" and
"export __GL_THREADED_OPTIMIZATIONS=0;"
give the same 30 fps so the version with a "S" is useless.

I cross tested with World of Warcraft, there the right "Z" version is giving me 10-15 Fps boost.

Something in Planetside is strange, maybe I have some time Tomorrow to run some tests (it could be graphics options related)

Well I tested it today with "S" and "Z" and can'T confirm the fps-decrease, with "Z" the fps felt more stable after all. We could need some more testing on that.

So the game runs but has someone managed to use the ingame function to buy sc-cash yet?

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.

Seems it was something graphic related. Lowering all of the graphic settings has fixed it from crashing, though the framerate makes it rather difficult to play.

Please see the "issues" section in the consolidated findings above.

Think I'm bored at the moment...

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.

good point. Tis is also a good tip for Windows. (hence I forgot to mention it)

Did completely nothing for me, even on 300. I guess it is more about RAM and video memory. I have 8GB RAM and 1gb video card, maybe it is enough as it is...

That is possible, it seems that the results differ also with windows users. Currently can't test it myself, but my system is even more beefy the yours (16GB ram, 2GB Vram) so I may also don't get any improvements.

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 also encountered this.
When I was playing without the vsm=hardware multisampling=enabled psm=enabled, without opengl threaded, whíthout multicore script and without SweetFX. The jittering appeared about 45 mins into a playsesion.

With all those changes there still was a change in mouse sensitivity after 30mins but it didn't began to jitter (only a litle bit, like turning with low FPS). I just readjusted mouse sensitivity ingame to compensate.

Could you explain the points of OpenGL threading and SweetFX, cause that are changes I haven't done yet, maybe it will fix the jittering so we could take this as a fix.

OpenGL treading helps to multithread GL rendering, wich helps rendering performance on multicore systems. It works in a limited way with not optimized apps (like PS2/Wine) but for full power a program needs to utilize it actively (Like the Linux version of TF2). There have been reports of 50-100% with TF2 (Nvidia driver 304 vs 310).

SweetFX is a Post-Prcessing injector (uses d3d9.dll to add post-processing Filters to games that don't support them natively). I use it for MSAA injection, Color correction and Gamma adjustment.
Gamma adjustment is needed since the ingame "Brightness" slider doesn't work in windowed mode and the Game is to bright for me without it.
MSAA needs aditional performance (3-5 FPS for me), so you may leave it off.

Could you add the way to add those options for further testing?

Added infos for SweetFX on top.
__GL_THREADED_OPTIMISATIONS is already there. Or is it to unclear written?

Nvm about GL allready have it in my script tho ^^

As I saw that I'm mentioned in the guide ( what an honour ^^ ) I put the link to mentioned script ( original by Danilo Riffo aka. DanAlucard so most credits to him ) in here:

pastebin.com/uKQ1RSJE

Greetings, may it be helpfull

hm missing edit-function, the link above has my old script, here's the new one:

pastebin.com/3PikpU8v

Thanka. iu updated the link in the guide.

also.. when it says above to lower the graphic settings, does that mean in-game? or setting something in wine to low graphics? and how..?

It means ingame settings. But I will update it sibnce I isolated the guilty setting. You can put everything on high (if your PC is beefy enought) but leave Particles on low.
Best to adjust these settings in the server selection screen (settings button on the bottom right of your screen)

Btw. you should edit your guide:

Virtual desktop
when playng fullscreen, this prevents crashes when momentarily switching to other applications, it may also help with mouse jittering issues.


when playing fullscreen you get the mouse-issues it should be windowed, or ? At least for me it'S that way ^^

Jep i see what you mean. I'll edit it when I add my new findings with graphics options (see PS2 forums).

Does anyone else seem to have the issue where the launcher freezes 90% of the time with the little spinny icon?

I have the same problem with Wine 1.5.18.

Do you also have this in your wine output?

*** glibc detected *** C:\Program Files\Steam\steamapps\common\PlanetSide 2\LaunchPad.exe: malloc(): memory corruption: 0x00050008 ***
======= Backtrace: =========
/usr/bin/../lib32/libc.so.6(+0x75932)[0xf749e932]
/usr/bin/../lib32/libc.so.6(+0x773aa)[0xf74a03aa]

/usr/bin/../lib32/wine/secur32.dll.so(InitializeSecurityContextW+0x120)[0xf6f8e730]
[0x10caafbe]
======= Memory map: ========

So I tried the latest git version and this problem in particular seems fixed.

I still get the slowness and freeze problems described by other people though.

Ah, sounds good I shall upgrade soon and try again :P

It appears I still get this issue with the latest version of wine :(

Every time i try to run the game the launcher windows opens and then AwesomiumProcess.exe crashes and the login page does not show up.

wine: Unhandled page fault on read access to 0x00000000 at address 0x10a44d31 (thread 002a), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x10a44d31).

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?

Same exact issue here. I did not play in Beta, but downloaded the install file 7.7 megs. And I have been unable to run it ofr installation. AwesomiumProcess.exe crashes about 3 times, and whole thing hangs.

Ok I figured that issue out.
U cant install it through the installer on the webpage, u gotta install it in Steam.

Still free though so no issue.

couls you please specyfy your configuration a bit more?
I get this crash without corefonts or when I set the prefix for any newer than winxp.
Normaly the Installer from the website works fine.

I spoke too soon before, im getting the same crash with trying to run the steam version.

So im running 64bit Distro, but 32 bit wine, windows XP.
Installing Corefronts, Vcrun2008, d3dx9_43 and d3dcompiler_43.

Im doing all this in Play on Linux through the install process, when I first installed Steam in a new Virtual drive. (I installed steam through the POL steam installation)

Also through the wine configuration button, I found Imm32.dll under the dll overrides window, and installed that.

Since Steam had been installed through POL I noticed it had defaulted to Wine 1.5.10 (which gave me another error).
So then I tried with both 1.5.18 and 1.5.17 and now im getting the same AwesomiumProcess.exe crash I did before.


So i dunno. Should I install it through steam in another way perhaps?
Im still new to Linux.

I installed the game using Steam, so I didn't use the installer. The launcher of the game crashes, not the installer.

I think Steam doesn't really matter, it just replaces the installer. After it is installed you can run the game from the PlanetSide 2 folder in the steamapps folder without Steam.

Alright i tried running Launcher.exe and Planetside2.exe with the same settings directly.
With the Launcher im getting the same Awsioumprocess crash, and running the planetside2.exe file it crashed in another way, giving me a POL error.

Ok so the issue is PlayonLinux.
Installing it through regular wine worked, and now I get access to the game. But im still new at this so any step by step instruction would be great. like thew whole imm32.dll thing, installing the one in wine doesnt work i take it? what do I do with the file once i have it?

I wonder If someone would post a confirmed working imm32 somewhere?

Look at post #15 in the thread in the Planetside forum.

Yeah, I was referred to that before and it didn't work (see the elongated thread -_-). I may very well have done it incorrectly, but I did try many combinations of files and locations, and it is indicated later in that forum that the linked file is no good. I'm just wondering if there is a confirmed dll somewhere or if I'll have to install xp to get it.

Strange since that file is exactly the one I used.
but you need to rename it from IMM32.DLL to imm32.dll (windows is not case-sensitive)

ok this is new as of this moment (or maybe not?) I can open wine config, but now when I add imm32 override and close, it isn't there the next time i start wine config.

I seem to be able to retain settings by lauching config with sudo. I renamed imm32.dll as typed and placed in system32, but I still get the menu crash and cursor problem. Is there some additional information I can provide that would explain this?

nope never mind, it seems to be randomly saving the changes i make in config and randomly forgetting them...

sounds like a ownership problem myou may run
chown username -R $WINEPREFIX

I almost exclaimed fixed! It isn't fixed though. config still wont remember changes??

Thanks for the help btw guys!

I'll write one in the how-to section above.

Tat would be great, Ive got a 64bit distro, how do I run a 32bit wine on it?
(Without POL)

the main thing is that you create a 32bit wineprefix, which you to by supplying WINEARCH=win32 when running the first command inside the new prefix.
Inside a 32bit prefix the 32bit wine will alsways be run.

I get invalid directory with that command.

Im guessing im supposed to supplement WINEPREFIX with a directory of some kind? Which one? The one to wine? The one to an existing prefix? A new prefix? Is it the same directory in every instance of WINEPERFIX you wrote up?

Could u give me an example line?
My wineprefix folder is: /home/myname/.local/share/wineprefixes

WINEARCH=win32 WINEPREFIX=/home/myname/.local/share/wineprefixes/planetside wineboot

every other instance of $WINEPREFIX is to be replaced with /home/myname/.local/share/wineprefixes/planetside

Ah alright.
Thank you so much. Sorry for stupid questions, I just started using Linux a few weeks ago.

Ok im gonna ask another stupi8d question.

So ive installed a 32 bit prefix of Wine.

But not Winetricks only installs to the default 64bit prefix.

Is there something I can do to get winetricks to point to the new prefix, or do I have to install steam manually now?

Im trying that, but:

WINEPREFIX=/home/myname/.local/share/wine32 wine c:\steaminstall.msi
wine: Bad EXE format for c:\steaminstall.msi.

And thats what im getting. What am I doing wrong?
(again sorry if this is stupid, this is my first time with Wine)

Run winetricks with with WINEARCH=win32:
WINEARCH=win32 winetricks steam

alternative:
WINEARCH=win32 WINEPREFIX=/home/myname/.local/share/wineprefixes/steam wine msiexec /i /path/to/steam.msi

Also: Istall every game in its own prefix, helps to rule out conflicts and helps to minimize use of native files.
so you use /home/myname/.local/share/wineprefixes/steam for steam and /home/myname/.local/share/wineprefixes/planetside for PS2.

Yeah that sounds like a good idea, but i need steam to install PS2. How do I get it installed in another prefix?

If you have no problem with it delete your complete prefix and start anew.
Think of a folder scheme you can easily remember. In my case I use ~/.wine_gamename so I have ~/.wine_steam for steam and ~/.wine_planetside for PS2. You could use pretty mouch any filder you want, but best to keep it inside your ~/ (it's an shortcut for /home/username/) to prevent rights problems.

If you don't want to delete you complete prefix, uninstall PS2 as you would in windows (there should be a uninstaller somewhere) and reinstall in a new prefix (hold to the how-to above).

Yeah, but how do I install Planetside 2 to its own prefix if im using steam to install Planetside 2?

You don't install it via steam.
The steam overlay would be the only reason to have it on steam, but the overlay is in general a source of errors and performance hogs, so you disable it in most cases.

Fair enough. So how do I install it?

Use the installer that is linked under "Free Download" on the top of this page.
It'll install exactly the same game as Steam does (there is no special Steam version). The steps for installation are easy enough.
Just follow the how to above, then "winetricks d3dx9_43 d3dcompiler_43", then "WINEPREFIX=$WINEPREFIX wine PS2_setup.exe".

ah dammit. That doesnt work for me. The installer never starts, it crashes with annals of awesiumprocess.exe errors.

The only version ive been able to run is the steam one.

Well, ill keep trying.

try "winetricks corefonts vcrun2008" before starting the installer.

Could you please stop spamming my LaunchPad crash question with your installer wine prefix stuff?

Sure. Ive got the same issue though.
Well not anymore. It worked with vcrun2008 installed before running the installer.
(Thanks for that)

Now I need to make the game playable...

WINEPREFIX=/home/myname/.local/share/wine32 winetricks
Choose the "default prefix" that will be it.

As for installing .msi manualy:
www.winehq.org/pipermail/wine-users/2005-December/020055.html

Thanks, that did set the default prefix to the win32 folder.
But the issue is that installing steam through winetricks runs a script that installs right into the regular default 64bit folder.

So ive got to install steam manually, or try to install PS2 without steam i guess.

Is anyone getting graphics issues like this?

oi45.tinypic.com/5mmvpd.jpg
oi46.tinypic.com/9qz505.jpg

Also, sometimes the launcher freezes with the little spinny icon getting stuck.

If I press insert to spawn on the squad leader the game crashes.
Opening the game menu freezes (I'm not sure what to do with the imm32 dll, 64bit prefix)

I have the similar problem to the first one.
Character model on selection screen is blacked out, on high graphics settings.

lower the "Grapics Quality" setting to make it visible again in the menu.

But OPs pick looks like something else, may it helps to lower that setting anyway?

I set it to low and now things show. Unfortunately the framerate is pretty bad :\

On 64bit prefix you should put it in syswow64 folder, and check imm32 in winecfg for this prefix.

That worked for me, menus don't freeze :D

Where did you get the .dll exactly, did you download it or do you have a windows install?

What version of windows is it?

I think you can take from a windows install or from here www.dll-files.com/dllindex/dll-files.shtml?imm32

I tried that already, so I must have done something wrong, or it doesn't work...

You also have to go in to winecfg and set imm32 to "native, builtin"

did you have to remove the imm32 already there?

I just renamed it incase to imm32.dll-builtin and copied the new one in as imm32.dll

to be clear, you renamed the downloaded "IMM32.dll" to "imm32.dll-builtin"?

I renamed the EXISTING one that wine created to imm32.dll-builtin, and the NEW one to imm32.dll in the same folder

right - sorry misread

anyway i did that, and it doesn't work but now i can't open wine config

err:module:import_dll Loading library imm32.dll (which is needed by L"C:\\windows\\system32\\winex11.drv") failed (error c000007b)

I got this message when I put it in Windows/system32, the correct way was to put it in Windows/syswow64 folder

Yeah, the first thing i did was rename the original imm32.dll back from -builtin to it's real name, in both folders, but i still can;t open wine config. Ps2 still has the menu problem, though it is set to native, not native,built-in

Check this tread, first post.
forums.station.sony.com/ps2/index.php?threads/usersupportthread-ps2-on-linux-with-wine.47255/

I can't - wine config and regedit won't open, they both yield the previously posted error requiring imm32, even though I have restored the originals to their correct places and names.

That's why you have to uncheck this dll manually in .cfg file, or recreate prefix.

there is no imm32 file in any of the .reg files there - I know for a fact that I added imm32 as an override, and that this started not even after trying the imm32 from the link, but after trying ps2 after a rename.

I figured it out; looks like some things got moved around somewhow - thanks

so.. I was following your posts because of similar problems.. and now I can't get regedit or cfg to work.. where did you end up finding things/fixing that problem.. I am not an advanced user, and probably shouldnt even be trying this.. also, where is the folder i'm supposed to put the img32? how do I get to it? I really want to play this, so any help to get wineskin back to working properly would be super helpful. oh and do I need to make all these adjustments before I install PS2? or when using the cfg does it affect all my wrappers? mostly just curiosity because I already have a wrapper with ps2 installed in it, just trying to work out the bugs.. well, i was, and now it's not opening at all and as I said I can't get the cfg to open.. thanks

For resetting the overwrite see my how-to for imm32 overites above.

You may want to find out where wineskin created your prefix (or wrapper). Also another player found that using POL created problems with the launcher for him so you may want to use bare wine (without a gui) for it.

You don't need to make it before installing the game, you can make it anytime you want, when the game is not running.

The dll replacement only affects the prefix (wrapper) you make it in, its one of the reasons this system exists, and you should a own prefix for every game.

In my experience I only got the imm32.dll working in a 32bit wine prefix.

Have 64 and 32 working, using my own dll from WinXP installation. In case of 32bit prefix it should be put into system32 folder, for 64bit - syswow64.

If you still have this glitches, I think it is related to rendering. Setting it to zero leaves me just with that blank gray screen with tickets and signs everywhere.
And I got the same issue with full rendering once, when I switched to another workspace, and then returned to the one with game on it.

do you know if it have to be from xp? also could the dll be modified when ps2 is installed?

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:

fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x1b11eed8): stub
wine: Unhandled page fault on execute access to 0x80000000 at address 0x7fffffff (thread 004d), starting debugger...
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
Unhandled exception: page fault on execute access to 0x80000000 in 32-bit code (0x7fffffff).

I also noticed that it seems to be linked to activity.
One outstanding recuring error I managed to get from the games is:

err:ntdll:RtlpWaitForCriticalSection section 0x2e284f0 "?" wait timed out in thread 0057, blocked by 0059, retrying (60 sec)

which leads me to the suspection that it may be linked to a problem with multi threading.

I have to conduct some extended testing but it seems to be stable if I use a 32bit prefix.
I created a fresh prefix with
WINEARCH=win32 WINEPREFIX=~/.wine_planetside winetricks corefonts vcrun2008 d3dx9_43 d3dcompiler_43
and it was stable for 5 minutes, Later today I will conduct a longer test to see if is stable.

Actually I don't think you need vcrun2008, have no installing issues if I don't install it.

could be, haven't cross tested vcrun, since I have the winetricks line in a script to comfortable redo the prefix.
In the 64bit prefix it was needed.

Well could be, anyways I think I'v to redo my test-data ... I'm able to jump right into the battle but some effect will create a critical error and quit the game ...

pastebin.com/WTuAMukU

32bit-prefix with all needed dll's including imm32 ... sad thing ... beta worked so well

could it be the graphic-settings? Playing at medium with 310.19 nvidia drivers...

any thoughts will be welcome on that ^^

Hm... Actually lowering graphical settings to medium worked for me, played for 2 hours so far. Using 32-bit prefix...

Well I get bumped to the G21 Error-Page, SOE mentions to reinstall the game to easily get rid of it ... reinstalled almost 10 times ...

I can second that. Playing on low graphics works, on medium (and higher, I guess) the crashes start happening.
Maybe we can narrow it down further to see which specific setting is causing it.

Oh, just noticed you said "lowering to medium". I seem to have to play on "low". "medium" crashes.

Tried low settings first, no crashes for 1 hour, changed to medium - the same - 1 hour, but I'm having quite poor fps even on low in big fights. Maybe I should try 310 drivers...

Well we aren't alone, some other players mention the same problem in the official forum. It's kind of corrupted files, which should be done if you reinstall but they already had reinstalled the game several times ^^

Good to know that it seems to not be a linux-only problem. At least they mention the same what I see, Droppod close to the ground-battle and then error...

will try the low settings now. Thanks for that hint