beta patch 3

looks like they are working on a new patch.
http://utforums.epicgames.com/showthread.php?t=590487

It has been released for beta testing, but we are not at liberty to let anyone download the beta patch.

any news about the official patch ?

Not yet. Beta patch 2 was a mess and hopefully 3 is going to get Epic closer to official release. Maybe two or three weeks...

Dude. Just Dude.

- Implemented a Favorites tab page in the server browser.

THIS should've been in the official release. This should have been a day one feature, not a patch. Good job rushing it out the door, guys.

- Fixed IP addresses being reported in host byte order instead of network byte order

OH MY GOD. SERIOUSLY?

... This makes me want to cry.

Originally Posted by Optimus_P-Fat

OH MY GOD. SERIOUSLY?

...
What's that bad about it? I mean, it makes it even funnier to ban IPs

By the time I can play it will be playable

I think redirect and webadmin are more important than favorites or history.

Originally Posted by ARsEnAl51

...
What's that bad about it? I mean, it makes it even funnier to ban IPs

What's that bad about reporting an IP in the wrong byte order? If you have to ask that, don't try writing any network programs anytime soon, because if you try to use that incorrectly reported IP to connect to, it wont work

Byte order is like RULE ONE when writing network apps. Convert to network byte order on the way out, convert to host byte order on the way in. If you are writing the code that serialized TO the network, you make sure to run it through the conversion to network byte order. Likewise, converting to host byte order, if you are writing any code that is deserializing data from the network. You have no way of guaranteeing that the the endian-ness of the machines on both ends is going to be the same, hence you convert to a common order (network) for the transfers, and let the hosts themselves convert into the byte order they need once they receive the data. htons() / htonl(), -> network -> ntohs() / ntohl(), etc. I'm actually very surprised they missed something like that.

That was why clients could see the servers but couldn't connect to them.

Originally Posted by Optimus_P-Fat

What's that bad about reporting an IP in the wrong byte order? If you have to ask that, don't try writing any network programs anytime soon, because if you try to use that incorrectly reported IP to connect to, it wont work

With the .NET Framework, I don't even need to worry about this ;p

Originally Posted by QettoE

I think redirect and webadmin are more important than favorites or history.

+1 although all of them should have been in the release IMO

Originally Posted by ARsEnAl51

With the .NET Framework, I don't even need to worry about this ;p

Does the framework provide serialize calls for DWORDs and things like that when you need to send to the network? How do you pack data for send through a socket? Or is it so abstractly high up that you just waste resources like mad by sending everything through variants or strings?

Originally Posted by Optimus_P-Fat

Does the framework provide serialize calls for DWORDs and things like that when you need to send to the network? How do you pack data for send through a socket? Or is it so abstractly high up that you just waste resources like mad by sending everything through variants or strings?

The .NFW provides a Socket class as well as easy-to-use wrappers for UDP, TCP and at an even higher level, HTTP.

In the .NFW, I/O operations are based on streams. The Stream class only accepts byte arrays. So if I need to send an integer, a string or an object to a stream, I use a specialized writer/serializer.

Btw, the Variant type doesn't exist in the CLR. You can specify an attribute to marshal a paramater as a Variant for PInvoke calls or marshal it 'manually' using a .NFW class that provides numerous functions for native&COM<->managed interaction, but that's all.

So you serialize your numeric types to the streams.

Most times this type of stuff is done in the same manner - a library interface to go through when sending that takes care of byte order stuff. That is why I am so surprised they missed this.

get a room you two FFS

It's like your having phone sex in Chinese or something

Heck I SHOULD move those posts over to "Programming"

Originally Posted by Optimus_P-Fat

I'm actually very surprised they missed something like that.

I dunno, I'm not surprised. The only clients released have been for Intel so everyone's got the same byte ordering.

these beta private patches are fucking useless! why are they teasing us!?!?!
Epic

Beta patches are supposed to be for testing by a minority. Wait a few weeks and there will be a proper patch aimed at you.