You are not logged in.
They've disabled keyhashes in v1.612. Keyhash shows an empty field with game.listPlayers command and in the "status" Gamespy packet there is no keyhash associated with any player, that's why BFServerManager doesn't work normally with the v1.612. BFServerManager should restart the server in case of a crash, though. I tested it and it restarts.
They've disabled keyhashes in v1.612. Keyhash shows an empty field with game.listPlayers command and in the "status" Gamespy packet there is no keyhash associated with any player, that's why BFServerManager doesn't work normally with the v1.612. BFServerManager should restart the server in case of a crash, though. I tested it and it restarts.
so that means that !commands are messed up too
to test, i just joined some random (empty) server with bfsm and issued !runnext
and it worked
(they probably have bfsm users with empty keyhashes and that now matches mine. and yours. and everyone's)
bah, why they have to mess up stuff that works instead of fixing real problems
few bytes changed here, few bytes changed there and 1.612 origin clients can connect to what used to be a 1.61 linux dedicated server (and now probably first 1.612 linux server)
BFServerManager should restart the server in case of a crash, though. I tested it and it restarts.
You are right tuia, i may have spoke too soon, the microsoft send error reports was active so its probably why it did not restart for me.
few bytes changed here, few bytes changed there and 1.612 origin clients can connect to what used to be a 1.61 linux dedicated server (and now probably first 1.612 linux server)
That is sweet! It would save me and others a lot of trouble if we were able to use a linux environment to host.
few bytes changed here, few bytes changed there and 1.612 origin clients can connect to what used to be a 1.61 linux dedicated server (and now probably first 1.612 linux server)
That's great news! Can you please share what bytes did you change to accomplish it?
That's great news! Can you please share what bytes did you change to accomplish it?
i'll test it tonight with more players than just myself and if i don't find any other problems, i'll share it
can people with origin client try to connect to my test linux server?
you don't have to play, i just need to know if here's no problem with joining the game
109.71.69.254:14567
thanks
1942 Origin peaking at 2000 players today vs. 2500 last four days .....
Is the population declining already ? Let's hope not ....
it'd surprise me if there wasn't a sharp decline
most of the people just try it because it's free
some won't like it, some will be discouraged by the massive number of teamkilling noobs
Joined with origin, worked fine. Around 30 other players there too.
can people with origin client try to connect to my test linux server?
you don't have to play, i just need to know if here's no problem with joining the game109.71.69.254:14567
thanks
X=X=X=X=X=X=X=X wrote:1942 Origin peaking at 2000 players today vs. 2500 last four days .....
Is the population declining already ? Let's hope not ....
it'd surprise me if there wasn't a sharp decline
most of the people just try it because it's free
some won't like it, some will be discouraged by the massive number of teamkilling noobs
I just hope they will buy the retail version.
why should they? they can do everything the same in origin
X=X=X=X=X=X=X=X wrote:1942 Origin peaking at 2000 players today vs. 2500 last four days .....
Is the population declining already ? Let's hope not ....
it'd surprise me if there wasn't a sharp decline
most of the people just try it because it's free
some won't like it, some will be discouraged by the massive number of teamkilling noobs
I think there will be a slow decline, not a sharp one, mainly because of teamkillers/disrupters and cheaters.
EA could have made a good move with this, but they rushed the BF1942 free release on Origin, not worrying about fixing any bugs and glitches, server crashes, or having something simple added as native widescreen support and basic PunkBuster support. It seems they only solved the Windows Vista/7 compatibility problem and focused their attention in getting Origin integrated with BF1942. They also disabled keyhashes, probably due to technical reasons, which makes admining almost impossible. Basically, they used BF1942, not caring about the game, to get some people to sign up an Origin account. That was, and is, their main purpose, to get more numbers in Origin.
why should they? they can do everything the same in origin
Pretty much what Tuia just said.
-Punkbuster support
-bugs and glitches
-server crashes
-server isn't run professionally
etc
Does anybody know how to make a server restart after a crash ?
I run mine in Win XP, using :
Battlefield 1942 v1.612 server up to 128 players
http://team-simple.org/download/BF1942_ … layers.zip
and
BFServerManager v2.01 for Windows patched
http://team-simple.org/download/BFServe … atched.zip
I've enabled "Restart the server automatically" in "Options"
But the server doesn't restart after crashes. Solution ?
As bud wrote:
the microsoft send error reports was active so its probably why it did not restart for me.
You'll probably have to disable Windows Error Reporting service.
so in almost 24 hours of running, there were 4 crashes, i suspect them being the usual 1.61 crashes
haven't spotted any other problem so here are the patched binaries
http://ax.sadman.net/files/bf1942_lnxde … 612.tar.gz
enjoy
Thank you s[sk]! I'm going to see what you changed from the original code.
actually it wasn't that hard
- patch function that returns version as string (used in gamespy replies)
- patch version that's used in netcode when client is connecting
- kill cd key check (these empty keyhashes don't have chance to pass)
- kill client checksum check (was lazy to patch it properly to recognize origin client, with it in place you get data differs error when connecting)
that's probably all
- Be compatible with 1.61
this is not true, it's not compatible
i think you'd have to patch client aswell to be compatible (if you try to connect with 1.61 client, server says it's 1.612 and client will ask to upgrade)
Impressive work. Looked at the code, and it's not some small changes. In the client checksum, however, I think from what you changed a client with version 1.6 could connect to the server.
Impressive work. Looked at the code, and it's not some small changes. In the client checksum, however, I think from what you changed a client with version 1.6 could connect to the server.
but there's still version check in client
so it won't join the game but instead tells player to update (WRONG VERSION! DO YOU WANT TO UPDATE?) - because server version > client version
Yes, you're right, it has to pass the version check first, although the client checksum passes, because it's invalid. I'm really impressed with your work. I will try to understand better what you changed. Very well done.
so is it possible to make patch switcher to 1.612 just like we have now?
so is it possible to make patch switcher to 1.612 just like we have now?
It is possible, I guess. The biggest hurdle is to send the correct client checksum to the server, to accept the connection.
EA wouldnt be pleased if that was released. You wouldn't need to sign up an account on Origin to play BF1942 v1.612.
Is it possible to patch the BF1942.exe to 1.612 ? I mean just to change the number, nothing else. Then i hope this error message will not appear.
I mean just to change the number, nothing else. Then i hope this error message will not appear.
That's cosmetic stuff. I've just played with a v1.6 client in a v1.612 Linux server. I changed the netcode version, only one byte change. Now the difficult part is to patch the client checksum. Any suggestion, s[sk]?
It would be nice to have a patch, especially for mac users, so they can play on origin servers. But its not done by that, you would also need a patch switcher 1.6 to 1.61 to 1.612