Forums » General
Cannot create character
I downloaded the game but it will not let me create a character. Is the free trial still in effect?
Yep. The only reason you couldn't create a character is the name you picked is taken, or you haven't chosen a name for your character.
I don't think that is my problem as I hvae tried several names, also my beta account does not work and I have tried craeting a new account.
ARRRGHHH
Finally was able to create a character, had to reinstall, but now I cannot select that character. It will not let me play, it just teases me.
Finally was able to create a character, had to reinstall, but now I cannot select that character. It will not let me play, it just teases me.
Hmmmmm. It works fine with this beta account. Actually I think I understand the problem now - there's a bug in the connection establishment code on the server. From the server's logs you're logging in and logging out in the same instant.
I don't really understand why your client is triggering this... Are you getting an extremely low framerate in the main menu with the rotating space station?
One thing I can suggest for right now is to log into the game, accept the EULA, hit 'disconnect', and then hit 'login' again. That -might- work but I'm still uncertain what the root cause is.
I don't really understand why your client is triggering this... Are you getting an extremely low framerate in the main menu with the rotating space station?
One thing I can suggest for right now is to log into the game, accept the EULA, hit 'disconnect', and then hit 'login' again. That -might- work but I'm still uncertain what the root cause is.
That doesn't work either. Bummer, am I the only windows user suffering this problem?
This is what shows up in the winsock.log
[11/02/04 03:31:06] event.cpp:(84): WSAENOTSOCK: One of the descriptor sets contains an entry that is not a socket.
[11/02/04 03:31:12] udpx.cpp:(469): WSAEWOULDBLOCK: Uh yeah. this operation would block.
[11/02/04 03:31:06] event.cpp:(84): WSAENOTSOCK: One of the descriptor sets contains an entry that is not a socket.
[11/02/04 03:31:12] udpx.cpp:(469): WSAEWOULDBLOCK: Uh yeah. this operation would block.
Are you by chance using Windows XP SP2?
If so, could you run the game, hit Alt-Enter (to bring the game into a window instead of being full-screen), and then try to connect, and see if Windows pops up a dialog asking you to Unblock the application?
If so, could you run the game, hit Alt-Enter (to bring the game into a window instead of being full-screen), and then try to connect, and see if Windows pops up a dialog asking you to Unblock the application?
I am using xp2 but the firewall is disabled.
Funny thing, I took my computer to work and can connect there.
it seems to be either my router or my cable connection. It would be odd if it were my router as I even tried setting my pc as the dmz host.
What ports does vendetta use? maybe something is being blocked.
Funny thing, I took my computer to work and can connect there.
it seems to be either my router or my cable connection. It would be odd if it were my router as I even tried setting my pc as the dmz host.
What ports does vendetta use? maybe something is being blocked.
It connects to server.vendetta-online.com UDP port 21141.
Your initial login packets are getting through okay, but then the connection is being lost right away.
Your initial login packets are getting through okay, but then the connection is being lost right away.
I will try updating the firmware on my router (Linksys BEFSR41)
I'll keep you informed.
The fact that I can get into the game from work means it is definitely something on my end. Maybe an issue with this aging router.
I'll keep you informed.
The fact that I can get into the game from work means it is definitely something on my end. Maybe an issue with this aging router.
I've played through 4 or 5 different Linksys routers. It works fine with the default config, and VO even works through my fancy schmancy config at home (wireless repeaters and all that jazz).
Well I had a lot of fancy port forwarding rules set up so maybe that had something to do with it.