[cod] Cassino

todd at simops.com todd at simops.com
Mon Jan 24 06:46:14 EST 2005


Use it and pay.
Remove it and benefit.

Only 2 choices at this time.

TLP
  ----- Original Message ----- 
  From: Andre Lorbach 
  To: cod at icculus.org 
  Sent: Monday, January 24, 2005 5:00 AM
  Subject: RE: [cod] Cassino


  You mean a "workaround", this is no solution to me ;)

  regards,
  deltaray



----------------------------------------------------------------------------
    From: Nemeth [mailto:nemeth at jolt.co.uk] 
    Sent: Montag, 24. Januar 2005 09:09
    To: cod at icculus.org
    Subject: RE: [cod] Cassino


    The solution is to remove it from your map rotations. A lot of people have done.

     

    Nemeth

     

    Jolt Call of Duty Head Admin

    cod.jolt.co.uk - #cod.jolt


----------------------------------------------------------------------------

    From: Armageddon [mailto:armageddon21 at sympatico.ca] 
    Sent: 24 January 2005 04:31
    To: cod at icculus.org
    Subject: [cod] Cassino

     

    This is the second time I bring up the cassino CPU Usage problem.. But this is getting realllllly annoying,  16 player cassino on a dual opteron 242 2 gig ram  spike over 80% cpu uage .... normal map never go over 40-45 ....  this is cutting in half the numbers of server we can put on a box... 

    Anyone know a solution? Or the reason ?

     

    Thanks!!!!

     


----------------------------------------------------------------------------

    From: Mark J. DeFilippis [mailto:defilm at acm.org] 
    Sent: Sunday, January 23, 2005 10:35 AM
    To: cod at icculus.org
    Subject: Re: [cod] COD 1.5b / COD:UO 1.51b patches the facts

     


    It appears the mirrors are not up to date, the link provided by John is:

      http://download.activision.com/callofduty/CodUO_Patch_151b.exe

    For Windows CLient with the updated game_mp_x86.dll

    Md

    At 10:25 AM 1/23/2005, you wrote:

    Steve,

    Thanks, this is clear. I can also concur that indeed the uo_game_mp_x86.dll was
    changed, and produces tons of MD5 Mismatch's in your logs.  So....

    1. There is NO Linux patch at this time.  Ryan said there is one coming
    shortly, but has not said when.

    2. Have your Windows users update their client to the new OFFICIAL 1.5.1
    release of UO.

    3. Your Linux server should be the original release, plus the add on
    in December from Ryan. However, I strongly recommend you apply
    "Bits" code fix that fixes the "Jeep crash" and "UO:TDM" problems.
    (Just add the pk3 file a few messages back)...

    We wait for Ryan to announce that "upcoming" Linux patch...

    BTW:  Punkbuster was updated last night. Your servers should
    update automagically, but the fix was reasonably important. I would
    go to your pb directory on your servers and force the update by
    executing  ./pbweb.x86

    MD

    S3-------------------------------------------------------------------------------
    Mark J. DeFilippis                    defilm at acm.org
                                          defilm at ieee.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20050124/b8c8b032/attachment.htm>


More information about the Cod mailing list