Does anybody here have a belkin router?

Wonder if my vent crashing programs I found would work on it :p

Me.

It wouldn't because it wouldn't be a ventrilo server.

UN's Current Playercount: 69
Has UDP option checked: 39 (57%)
Has UDP option unchecked: 30 (43%)

:confused:

Zodiac's Current: 48 - RCs (6) = 42
No UDP: 39
Using UDP: 3

Seems pretty minuscule to me, I guess UN has just used the mic feature more than others.

It's mostly for sparring, not for mic.

I'm actually surprised more people on Zodiac don't use the mic since it would actually make sense there in party play. Saying "buff please" over mic is much quicker and easier than stopping what you're doing and typing "buff please"

Except no one keeps Graal sounds on :P Also, can anyone understand anything said over Graal mic?

i remember there being dance parties on graal where people would stream music over the mics, and it sounded good


in relation to the thread, i've found that prior to logging on graal, using the "PFPortChecker by PortForward dot com" and checking to see if port 14899 for UDP is open and then logging on makes UDP work, assuming you can get the port open

I just ****ing said try sparring. Graal's default movement/fighting system is effected by UDP/TCP. When using TCP players will appear more jumpy and thus be harder to hit, while two clients using UDP will be silky smooth to eachother. This doesn't really matter on Zodiac so it's no wonder no one cares. Also probably why everyone there is so skippy compared to players on UN, makes melee fighting worse.

Didn't notice the movement thing when I used it but thats cool I guess.

Actually, it should have relatively the same effect no matter what movement system a server is using. It happens because of network lag with TCP, so the players location might not get sent until microseconds (or even seconds) later.

UDP honestly should be the default, it's generally the standard in online games. Though it doesn't guarantee a packet will make it to it's destination, it is plenty faster than TCP. The issues between two users who are using different protocols (sometimes a TCP user may not see a UDP user) is probably in how that's handled in the client, which, to be fair, is probably difficult because you wouldn't generally have users using different protocols (nor should you).