Been a while since I've posted on here but I'm having a problem and I'm at a loss. I'm running a cod4 server in FreeBSD. I have run many o game server on this box without problems until now. My problem, in a nutshell, is that anything involving the clock in cod4 seems to be going way too fast. Okay, that probably doesn't make any sense, I will try to elaborate.
When sitting in warmup, the numbers for the timer countdown as expected, every second. However, the beep that is heard client side happens approximately twice per second. Somewhere about halfway through the countdown, the match will start. The same thing happens when you plant a bomb in search and destroy. The countdown will say 35 seconds, the bomb will blow up at 15. I'm suspecting the visual timer is done client side, which would explain why the numbers decrement as expected. What I can't figure out is what's going on server side causing this problem.
I'm wondering if this is a problem others are having. Also wondering if it is specific to FreeBSD or if it exists on Linux machines as well (since I'm just using the linux binaries). Unfortunately cod isn't like rtcw or et, it doesn't give you the build name other people are running so I have not been able to track down a linux server to check out.
If this post doesn't make any sense or you'd like to see for yourself, PM me and I will send you the IP.
Full Version: cod4 question for *nix users
QUOTE (divzero @ Jan 30 2008, 07:30 PM) 
Been a while since I've posted on here but I'm having a problem and I'm at a loss. I'm running a cod4 server in FreeBSD. I have run many o game server on this box without problems until now. My problem, in a nutshell, is that anything involving the clock in cod4 seems to be going way too fast. Okay, that probably doesn't make any sense, I will try to elaborate.
When sitting in warmup, the numbers for the timer countdown as expected, every second. However, the beep that is heard client side happens approximately twice per second. Somewhere about halfway through the countdown, the match will start. The same thing happens when you plant a bomb in search and destroy. The countdown will say 35 seconds, the bomb will blow up at 15. I'm suspecting the visual timer is done client side, which would explain why the numbers decrement as expected. What I can't figure out is what's going on server side causing this problem.
I'm wondering if this is a problem others are having. Also wondering if it is specific to FreeBSD or if it exists on Linux machines as well (since I'm just using the linux binaries). Unfortunately cod isn't like rtcw or et, it doesn't give you the build name other people are running so I have not been able to track down a linux server to check out.
If this post doesn't make any sense or you'd like to see for yourself, PM me and I will send you the IP.
When sitting in warmup, the numbers for the timer countdown as expected, every second. However, the beep that is heard client side happens approximately twice per second. Somewhere about halfway through the countdown, the match will start. The same thing happens when you plant a bomb in search and destroy. The countdown will say 35 seconds, the bomb will blow up at 15. I'm suspecting the visual timer is done client side, which would explain why the numbers decrement as expected. What I can't figure out is what's going on server side causing this problem.
I'm wondering if this is a problem others are having. Also wondering if it is specific to FreeBSD or if it exists on Linux machines as well (since I'm just using the linux binaries). Unfortunately cod isn't like rtcw or et, it doesn't give you the build name other people are running so I have not been able to track down a linux server to check out.
If this post doesn't make any sense or you'd like to see for yourself, PM me and I will send you the IP.
I may be completely wrong here, as I've never run FreeBSD or any type of BSD, but I think I remember reading somewhere that BSD calculates clock cycles differently than *nix or windows does...I can't remember though where I read that or what it involved.
I'll see if I can find that article.
I've wondered if it had something to do with HZ in the kernel or something else similar. It is odd because I have not had this problem with any other games that I have run: rtcw, et, quake 4, doom 3, css. Of course cod is its own beast, from what I hear they have changed a lot under the hood in the engine.
Oh figure this one out. The actual round time limit is fine. For example, setting scr_sd_timelimit 5 works and counts down correctly. However, when planting a bomb with scr_sd_bombtimer 45, the bomb blows up somewhere around 15 seconds left.
Oh figure this one out. The actual round time limit is fine. For example, setting scr_sd_timelimit 5 works and counts down correctly. However, when planting a bomb with scr_sd_bombtimer 45, the bomb blows up somewhere around 15 seconds left.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.