TECHNISCHER SERVICE / WEB APPs BUGS

Hi, I'm stuck on the "connecting" screen. I'm tethering my cellphone as my current internet connection. So far it hasn't failed me, patching and account set-up went seamlessly. Now this "connecting" screen is giving me issues. I turned off my firewall thinking that could be an issue, but still no movement. My phone's connection is better than the required 56k modem connection. Does anyone know what might be causing this issue? Maybe someone else is tethering a phone connection and ran into this same problem?

What OS are you on? Have you successfully played Ryzom on this computer with a different kind of connection?

Hi Sywindt, I'm running Windows XP. Yes I have successfully run Ryzom on this pc.

If you go to your Ryzom installation directory there should be a file called "client.log". The last lines of this file could shed light on the problem.

Can you copy/paste them here?

The last 4 lines:
2011/08/27 10:59:32 INF cc0 client_ryzom_rd.exe client.cpp 592 WinMain : Releasing of Ryzom...
2011/08/27 10:59:32 WRN cc0 client_ryzom_rd.exe editor.cpp 3928 R2::CEditor::release : *R2* release
2011/08/27 10:59:32 WRN cc0 client_ryzom_rd.exe game_context_menu.cpp 89 CGameContextMenu::init : gamecontextmenu:init: 'ui:interface:game_context_menu' window does not exist.
2011/08/27 10:59:32 WRN cc0 client_ryzom_rd.exe editor.cpp 3928 R2::CEditor::release : *R2* release
2011/08/27 10:59:32 WRN cc0 client_ryzom_rd.exe game_context_menu.cpp 89 CGameContextMenu::init : gamecontextmenu:init: 'ui:interface:game_context_menu' window does not exist.

Well that doesn't help much :) It seems that you are quitting Ryzom using the (X) button? If so, then please make a copy of the client.log *before* you quit (or use the task manager to force the application to stop), and give the last 10 lines of the copy.


Perhaps it has something to do with the fact that Ryzom uses UDP packets (as opposed to TCP), which your phone may not support. I suggest you look to your phone's documentation for this.

Another possibility is that you are just not waiting long enough; try to give give it a few minutes, if you haven't yet.

The last 10 lines, while the game is still on the connecting screen:

2011/08/27 11:19:58 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:19:58 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:19:58 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:19:59 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:19:59 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:19:59 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:20:00 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:20:00 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:20:00 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'
2011/08/27 11:20:01 INF 86c client_ryzom_rd.exe network_connection.cpp 1002 CNetworkConnection::sendSystemLogin : CNET[0142A710]: sent LOGIN cookie='E55A36D0|6E08A142|000500B8'

I'll check on the phone's connection type to see is UDP is supported.
With a 1.9mbps connection, what is the average connection times? It's been connecting for at least 10 minutes.

I love you long time, Swindt. The mention of UDP was the key. The issue was resolved by allowing UDP pass-through on the tether app on the phone. Thanks for the help :)

*blush* ;)