PlaneShift
Support => Technical Help: Problems BEFORE entering the game => Topic started by: Marko_______ on October 02, 2010, 10:27:42 pm
-
i create chr and when it starts loading it crashes, i dont see the error i only see window where i describe what happend....
EDIT: ok now i managed to enter and when i exited to make it fullscreen it didnt work again ...btw now i actually see the error it says :
"crashid=bp-c656dd52-d89e-4cae-9238-f63402101002
Thanks for submitting your report.
***NOTICE***
You are already running and old version of the client for wich this crash may already be fixed. Please update to 0.5.3 using the updater or download from www.planeshift.it "
this is the first time i downloaded this game and i dled it from torrent...
-
Please type up your system specifications, kinda hard to help without knowing that at first and that error happens more or less everytime ps either crashes or is closed you can safely ignore it if it always showes this as part of the error "Please update to 0.5.3".
-
Our usual recommendations for a first emergency reaction are:
1) Ensure that the sound is set to use OpenAL, and that an OpenAL driver is installed (for Windows you can find an oalinst.exe at Creative, the makers of e.g. SoundBlaster cards).
2) Delete the file "shadercache" once (it has been documented several times here where to find that).
3) Do not use "fullscreen". Instead, try to find a windowed mode which is quite close to it. Switching between the game in fullscreen and other applications often has strange side effects.
The game often crashes when you quit the game - especially in a crowded area like the city of Hydlaa. This is unfortunately "quite usual".
Also there are more bugs which may result in a sudden crash. This may especially happen when you see something that has now a different appearance compared to the content in the "shadercache".
And as Elvi mentioned: The message to update to 0.5.3 is wrong and outdated, the current version is 0.5.4(.10).
Thank you for submitting your crash ID. Could be that a developer may find out what the reason was in your specific case - if they read this thread at all...