Exception Access Violations during loading

[angstrom]

As well as the ol' EAV 009543A2, I get the following EAV's during loading :

008A9E15
00565234
008A69E5

I've managed to log in twice (by luck, obviously), so I know it can do it....

Anyone out there got a magic solution for me?

 

[thorgrin]

I believe it's known, some cache problem. Most players have suffered this too.
Waiting a few minutes seems to help a bit.

[LigH]

I get address 009543A2 often too, since there was an update to the vfs.cfg file; now the "shadercache" will be created in the "Local Settings" area of the user account, instead of the root of the partition where the game is installed.

It is a matter of patience and repetitions. You may have to restart the crashing game about 20 times until all shaders are rebuilt, then the game will work again. The reason seems to be a multithreading issue (I believe shader definitions get used before they are precalculated and created on disk).

[angstrom]

009543A2 is when I launch.

The rest happen during the loading (when the brown bar is inching it's way across the screen)

[Mouli]

Here are the log errors I got when I login... I can choose my character but got an Exception Access Violations after loading


Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/top_left_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/top_right_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/bottom_left_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/bottom_right_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/left_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/right_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/top_1.png<
Sun Dec 13 21:43:53 2009, <..\..\src\common\paws\pawsimagedrawable.cpp:66 pawsImageDrawable::PreparePixmap SEVERE>
Sun Dec 13 21:43:53 2009, Could not open image: >/paws/base/maps/leather/bottom_1.png<

[Glaciusor]

I've had this exact same issue. Wait for a few minutes on the character selection screen before doing anything. You might need to select your character and then wait a few minutes before entering the game if you have multiple characters.

[LigH]

@ Glaciusor: The first crash (address 009543A2) happens in the first second after trying to start the client. Already long before you even see the game window. I found that chances are better when the CPU is rather busy while starting the game, so chances are less that several threads of the game client are able to run "at the same time".

@ Mouli: Unfortunately, those messages are not really related to the reasons of the crashes.

[angstrom]

Some good news 

I've managed to get the client to load - regularly!

I've got a dual core AMD processor. When psclient.exe starts running, I only allow it to use a single core and it's loaded every time.
(It also keeps crashing during play however, especially when loading new areas)

[Siteri Kidachi]

I often get EAV at 696DA174 after the progress bar reaches the end, and various other errors at the start. I've managed to get to the login screen ONCE (by opening the game about eight times consecutively) and never gotten past that.

I guess I'll just have to wait for the patch... not that I play much anyway.

[weltall]

add to your config file
ThreadManager.AlwaysRunNow = true

[LigH]

Just repeating verbosely, because it really seems to work (just tested on a QuadCore)!

Add the following line to either %ProgramFiles%\PlaneShift\psclient.cfg or %APPDATA%\PlaneShift\planeshift.cfg
(locations for Windows, assuming default installation):

ThreadManager.AlwaysRunNow = true

  Hail teh weltall!

[angstrom]

Hail to weltall indeed 

This seems to be the line that'll save my sanity. 

[Tuathanach]

 
Thank you Weltall

[Siteri Kidachi]

I tried that and still get the error upon full progress bar.

[LigH]

Then you have another reason, Siteri. And maybe a different address than 009543A2 ?