AW: [bf1942] sea bug (nr 288) fixed?

conciser conciser at gmx.ch
Mon Dec 30 14:16:04 EST 2002


sorry, I forgot to mention this.
I have done this testing in my LAN (100Mbit)


and here is also my ServerSettings.con:

game.serverName "Test BF1942 Server"
game.serverDedicated 1
game.serverGamePlayMode GPM_CQ
game.serverGameTime 0
game.serverMaxPlayers 16
game.serverScoreLimit 0
game.serverInternet 0
game.serverNumberOfRounds 3
game.serverSpawnTime 20
game.serverSpawnDelay 3
game.serverGameStartDelay 20
game.serverGameRoundStartDelay 10
game.serverSoldierFriendlyFire 100
game.serverVehicleFriendlyFire 100
game.serverTicketRatio 100
game.serverAlliedTeamRatio 1
game.serverAxisTeamRatio 1
game.serverCoopAiSkill 75
game.serverCoopCpu 20
game.serverPassword ""
game.ServerBandwidthChokeLimit 0
game.ServerMaxAllowedConnectionType CTLanT1
game.ServerAllowNoseCam 1
game.ServerFreeCamera 0
game.ServerExternalViews 1
game.ServerAutoBalanceTeams 0
game.ServerNameTagDistance 50
game.ServerNameTagDistanceScope 300
game.ServerKickBack 0.000000
game.ServerKickBackOnSplash 0.000000
game.setServerSoldierFriendlyFireOnSplash 100
game.setServerVehicleFriendlyFireOnSplash 100
game.setServerIP 192.168.0.10
game.setServerPort 14567


> -----Ursprüngliche Nachricht-----
> Von: sittnduck [mailto:sittnduck at bioclan.com] 
> Gesendet: Montag, 30. Dezember 2002 19:57
> An: bf1942 at icculus.org
> Betreff: Re: [bf1942] sea bug (nr 288) fixed?
> 
> 
> Whats your pipe bandwidth?
> ----- Original Message -----
> From: "conciser" <conciser at gmx.ch>
> To: <bf1942 at icculus.org>
> Sent: Monday, December 30, 2002 12:11 PM
> Subject: Re: [bf1942] sea bug (nr 288) fixed?
> 
> 
> I did some more detailed "research"...
> 
> 
> land maps (0 player connected)
> - cpu usage:     between 0 and 2%
>   (except El Alamein & Gazala use 30-40%)
> - gamespy ping:  about 30 ms
> 
> 
> land maps (1 player connected):
> - cpu usage:     between 25 and 35%
>   (this is for the most maps, El Alamein & Gazala use 40-70%)
> - gamespy ping:  about 40 ms
>   (for El Alamein & Gazla about 55 ms)
> - "ingame ping": 0 ms
> 
> 
> water maps (0 player connected):
> - cpu usage:     about 85%
> - gamespy ping:  between 150 and 300 ms
> 
> 
> water maps (1 player connected):
> - cpu usage:   between 85 and 90 %
> - gamespy ping: between 200 and 300 ms
> - "ingame ping": 0 ms
>   (getting constantly "connection problem warning"
>   and extremly "laggy")
> - Iwo Jima seems not do be affected, this map uses about
>   65% cpu and I get no "connection problem warning" at all.
> - Omaha Beach seems not do be affected - quite the reverse,
>   this map uses only between 10 and 30% cpu)
> 
> 
> 
> 
> bf1942-lnxded-betaupdate-build-1040889129
> Linux 2.4.18-4GB i686
> Pentium(R) III at 450 MHz
> Ram: 256 MB
> 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Bill Wood [mailto:wawoodtx at attbi.com]
> > Gesendet: Montag, 30. Dezember 2002 17:18
> > An: bf1942 at icculus.org
> > Betreff: RE: [bf1942] sea bug (nr 288) fixed?
> >
> >
> > Same situation here. But I'm currently using the same 
> processor(PIII 
> > 450). A land map such as El Alamein is much smoother, but 
> processor is 
> > still 95% and not likely to support more then one tester. 
> Previously 
> > was on an AMD XP 1800 and the problem was not apparent, but 
> cpu usage 
> > was still excessive with just a few players.
> >
> > -----Original Message-----
> > From: conciser [mailto:conciser at gmx.ch]
> > Sent: Monday, December 30, 2002 5:16 AM
> > To: bf1942 at icculus.org
> > Subject: [bf1942] sea bug (nr 288) fixed?
> >
> >
> > is this sea bug (#288) really fixed?
> > for me it's not.
> > as soon as I change to a sea map (eg midway) the only thing 
> I get is a 
> > flashing connection problem warning.
> >
> > cpu usage (only one player) climbs to about 95%
> > (I know, I'm underpowered with a PIII 450, but it's just 
> for testing - 
> > all land maps are working fine (again: only one player)
> >
> >
> > bf1942-lnxded-betaupdate-build-1040889129
> > Linux 2.4.18-4GB i686
> > Pentium(R) III at 450 MHz
> > Ram: 256 MB
> >
> >
> >
> >
> 
> 
> 
> 




More information about the Bf1942 mailing list