Problems starting

wolfgang · Post by **wolfgang** » 31 May 2007, 16:49

Hi, i have been with problem since today, i can play TMW
First the update dont start adn say that is strongly recomend to do try later, then a cuple of hour later i tried agai and the same, so i decided to play whit out update, but i cant, i cant enter the server
Sorry for my inglish im a spanish talker

Post by **Crush** » 31 May 2007, 17:57

Our server got a different IP today and we forgot to update some dns entrys. But everything should work fine now. If not you got to wait a bit until the dns cache of your internet provider has refreshed.

wolfgang · Post by **wolfgang** » 31 May 2007, 18:18

ok thanks!

khandy · Post by **khandy** » 01 Jun 2007, 02:58

Anyone runnung Linux able to connect (debian test)? I compiled from current source 22.2, with current guichan 6.1. It was working yesterday. The new dns seems to have taken.
It will update correctly.
After clicking Ok on the "select server" screen, it locks up, leaving that screen on, and using 100% of the cpu (as seen by top). Dragging anothr screen over it leaves black area, which never refreshes. Nothinghappens after several minutes. I have to use a "kill -9" on it.
I also tried it on another Linux machine, and it does the same thing.

Post by **Bjørn** » 02 Jun 2007, 08:35

khandy wrote:Anyone runnung Linux able to connect (debian test)? I compiled from current source 22.2, with current guichan 6.1. It was working yesterday. The new dns seems to have taken.
It will update correctly.
After clicking Ok on the "select server" screen, it locks up, leaving that screen on, and using 100% of the cpu (as seen by top). Dragging anothr screen over it leaves black area, which never refreshes. Nothinghappens after several minutes. I have to use a "kill -9" on it.
I also tried it on another Linux machine, and it does the same thing.

Are you still having problems right now? Just asking since I see 7 people online at the moment, so it should work.

Client behaviour when connecting doesn't work should be a bit better with 0.0.23 (to be released soon), but it's still not optimal. You should always check the log (~/.tmw/tmw.log) and report which server and IP it's trying to connect to and whether there is any error related to it.