PlaneShift
Support => Technical Help: Problems BEFORE entering the game => Topic started by: lucius on June 04, 2004, 07:28:57 pm
-
I just started the gme , didn\'t knew what to do and so I went into the biggest structure I saw - Temple of some sort . There I falt in some well and got myself into some underground ruins . It\'s not just I don\'t know how to get out of there , it gives me \"SERVER DROPPED US(INVALID ERROR MESSAGE)\" mesages and throws me away sometims ...
-
Sometimes the server drops players. There isn\'t much to do against that. I don\'t really know about the invalid error message though.
Sad, when i saw your first post, i thought you didn\'t use caps. Looks i was wrong ... ;(
-
Maybe the error message came in caps and he wanted to quote it properly?
-
Can\'t be. That\'s my \"favourite\" way to quit PS. :( It\'s not in caps. My next favourite version is \"invalid operation\" or somesuch (I really don\'t pay attention to Windoze\'s error messages as they usually are wrong anyway).
I\'m looking forward to trying the Linux version of PS, if I can get it to compile.
-
Sorry !!! Geee ... I saw this error message only once and for a short time ... I thought it was capitalized :( ... Sorry ... Geee ... So many noise and only because of my capitalization of error message .
By the way , why do you guys hate caps so much ? :)
-
Because it looks really stupid if u type in caps.... and it makes it harder to read, which means people have to use something called \'effort\', which most people around here don\'t have much of. ;)
-
WTF ARE YOU TALKING ABOUT? THIS LOOKS SO PWN!!
I hereby decree the rule that all newbs to this forum must post at least one thread with CAPS, in order to get the old geezers around here out of bed :P
-
Lol
-
I upgraded to 300 MB of RAM recently. The continous swapping almost stopped and the constant reloading was also reduced.
Furthermore, I don\'t get this error anymore. Instead, PS simply crashes with \"illegal exception\" ore somesuch everytime.
Therefore, I believe that the mentioned error is an indirect result of the continous swapping / realoading that uses up the CPU power due to hdd activity and / or resource locks. Therefore, the client doesn\'t send a message to the server in time (keepalive). Because of this, the server thinks the client has crashed (as it\'ll do anyway, as the playability duration didn\'t exactly increase) and closes the connection. When the client finally sends it\'s message to the server, it gets the response that the server dropped the connection, which is exactly the case, due to (percieved by the server) inactivity.
The inevitable crash might be a result of my particular hardware or O\"S\", though.