[cod] CoD:WW patch news

[James Landi]

Quote by Voodoo Extreme regarding the "Treyarch Patch Process":

    Two to three months is ridiculous. Many developers take far less 
time, and as a result save a lot more money, so please refine your 
process, if only to increase your bottom line.

Could'nt have said it better......

-Jim Landi
Rudedog
FPSadmin.com


=TG=McRag wrote:
> No word on the bins, and no /record.
> No /record means no competitive gaming in leagues.
>
> Reaching the point, bye bye WW
>
> -----Oorspronkelijk bericht-----
> Van: |T-OC|Morpheus|:.Web [mailto:morpheus at clantoc.org] 
> Verzonden: zondag 18 januari 2009 1:51
> Aan: cod at icculus.org
> Onderwerp: Re: [cod] CoD:WW patch news
>
> What does make nearly no sense is the redundance in QA testing from both 
> developer and then publisher, that add more time in an already long 
> waiting for availability.
>
> But it's a reality : with no "centralization" for updating the game with 
> hotfixes (I think Ubisoft has some sort of it already running, seen in 
> Farcry 2), it take too much time to update the game... And I think that 
> if they want to "announce" linux support (don't talk about 
> availability), they can't implement the "Game for Windows Live" platform...
>
> What is so sad is that many of things that worked in cod4 and, from my 
> point of view, did not need to be modified, becomes screwed (record, 
> cg_drawfps, redirect, to say the least).
>
> IMO much more time was needed to even release the game, but I don't 
> think we have to throw all of our fire to Treyarch in this situation...
>
> Marco Padovan a écrit :
>   
>> nah, they might be holding the patch till the binary is ready... but 
>> they have not yet realized that the binary cannot be done untill the 
>> patch is out... so they are just waiting each other LOL
>>
>> Geoff Goas ha scritto:
>>     
>>> i really have a difficult time believing they are holding back the 
>>> linux binary just to release a patch. doesn't really make sense.
>>>
>>> On Sat, Jan 17, 2009 at 6:25 PM, Tyson 
>>> <twisted at twistedgamingservice.com 
>>> <mailto:twisted at twistedgamingservice.com>> wrote:
>>>
>>>     We wouln't ever see Linux bins for this game nor the record
>>>     function which shouldn't have been stripped to begin with since
>>>     COD5 is based off the COD4 code anyway.
>>>
>>>      
>>>
>>>     More bullshit is all that post from JD was.
>>>
>>>      
>>>
>>>      
>>>
>>>      
>>>
>>>     *From:* John Kennington [mailto:jwkennington at gmail.com
>>>     <mailto:jwkennington at gmail.com>]
>>>     *Sent:* Saturday, January 17, 2009 3:01 PM
>>>     *To:* cod at icculus.org <mailto:cod at icculus.org>
>>>     *Subject:* Re: [cod] CoD:WW patch news
>>>
>>>      
>>>
>>>     8 weeks for phase two.  I wouldn't hold my breath.
>>>
>>>     On Sat, Jan 17, 2009 at 12:42 PM, Mike <mike at reidesign.com
>>>     <mailto:mike at reidesign.com>> wrote:
>>>
>>>     JD posted on the callofduty site:
>>>
>>>     "I know many of you may feel a bit left out seeing the console
>>>     updates that keep getting pushed through, which is why I am
>>>     making this post.
>>>     I want to explain why the PC community cannot receive updates
>>>     quite as frequently as the console world.
>>>
>>>     For that, please read the PC Patching Process sticky here:
>>>     http://www.callofduty.com/board/view...p?f=29&t=91072
>>>     <http://www.callofduty.com/board/viewtopic.php?f=29&t=91072>
>>>
>>>     After having read that, I want to update you with where we are at
>>>     in that process. Presently, we are smack dab in the middle of*
>>>     Phase 2*.
>>>     We have a comprehensive list of what the community has been
>>>     reporting, and we are reproducing & fixing some the issues for
>>>     Patch 1.2.
>>>
>>>     Now we understand that some issues are more urgent than others.
>>>     For this reason, we are aiming to release Patch 1.2 as quickly as
>>>     possible - sometime towards the end of this month, beginning of
>>>     next month (February).
>>>     We want to move quickly on some of the more pertinent and more
>>>     easily isolated issues, rather than waiting to release a more
>>>     comprehensive patch that attempts to address them all.
>>>
>>>     Below is a list of some of the issues we are trying to fix for
>>>     Patch 1.2. In order to get this patch out at the beginning of
>>>     February at the latest,
>>>     there may be an issue or two we intended to fix that gets pushed
>>>     to Patch 1.3.
>>>
>>>               o All relevant console hot fixes & TU fixes (mostly MP
>>>                 map fixes).
>>>               o HTTP Redirect.
>>>               o Dedicated server reconnecting to master server index
>>>                 w/out reboot.
>>>               o Fast-XP "Power Servers" exploit.
>>>               o Server authentication errors.
>>>               o Cg_drawFPS in Multiplayer.
>>>               o Cg_fov defaulting back to 65 after death.
>>>               o +connect command line argument.
>>>               o Preventing altering clan tag colors (used to appear
>>>                 as friendly instead of an enemy).
>>>
>>>     Patch 1.2 will not address every problem in the game. Patch 1.3
>>>     will encompass many more of the outstanding issues,
>>>     and will start at Phase 2 again once patch 1.2 passes through
>>>     Phase 5.
>>>
>>>     Additional support for the game will be available by way of
>>>     patches as necessary in the future.
>>>     And before you ask, one of the items still on our list is*
>>>     /record* (this is unfortunately a bigger task which cannot be
>>>     completed in time for 1.2).
>>>     More info regarding future patches will be made available after
>>>     Patch 1.2 is released.
>>>
>>>     Hope that clears up some of the questions. In the meantime, enjoy
>>>     double-XP this weekend!
>>>
>>>     Regards,
>>>     -JD
>>>     "
>>>
>>>     /Villan
>>>
>>>
>>>
>>>
>>>     -- 
>>>     "Some people are like a Slinky .. Not really good for anything,
>>>     but you still can't help but smile when you shove them down the
>>>     stairs."
>>>
>>>
>>>
>>>
>>> -- 
>>> Geoff Goas
>>> Network Engineer
>>>       
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
>
>
>