[cod] Laag with 1.7 Linux Servers? - possible Fix included!!!

Sh0rt sh0rty2k at gmx.de
Wed Jul 9 02:01:17 EDT 2008


removing the auto_ss will propably have the most noticeable effect

----- Original Message ----- 
From: "Thomas Toka / www.serverman.de" <webmaster at serverman.de>
To: <cod at icculus.org>
Sent: Wednesday, July 09, 2008 9:46 AM
Subject: Re: [cod] Laag with 1.7 Linux Servers? - possible Fix included!!!


> Hello again...
>
> Thank you all for your feedback.
>
> It think i have "buffered" the laags with some settings.
> I know what these settings do, so please dont tell me that
> there is no log or PB-Screens after this. *lol*
> As for now if you are affected by this issue please try to only
> change these parameters an check if there is less laag:
>
> server.cfg (changes)
> set g_logsync "0"
> set logfile "0"
>
> pbsv.cfg (change)
> pb_sv_AutoSs 0
>
> pbsv.cfg (add)
> pb_sv_cvar snaps IN 20 60 // prevents artificial lag
> pb_sv_cvar cl_timenudge IN -50 0 // prevents artificial lag
> pb_sv_cvar cg_bobup IN 0 0.005 // prevents bobup exploit
> pb_sv_cvar com_maxfps OUT 1 30 // prevents artificial lag
> pb_sv_cvar sv_padpackets IN 0 // prevents artificial lag
> pb_sv_cvar cg_shadows IN 0 1 // prevents shadows wallhack
> pb_sv_cvar r_znear IN 4 // prevents potential code hack
> pb_sv_cvar r_shownormals IN 0 // prevents potential code hack
> pb_sv_cvar r_nocurves IN 0 // prevents potential code hack
> pb_sv_cvar cm_oncurves IN 0 // prevents potential code hack
> pb_sv_cvar cm_noAreas IN 0 // prevents potential code hack
>
> Please give me a feedack.
>
> My Clan Mates said it works well!
>
> Regards
>
> Thomas Toka aka Tom-i
> www.serverman.de
>
>
>
> MaydaX schrieb:
>> http://www.pbbans.com/mbi-viewban-5ff15eb7-vb76958.html
>>
>> As you can see the maximum resolution allowed to be captured has been 
>> increased. I can not go into details at this time as PBBans have been 
>> asked by EB to keep the details of the changes we requested quiet while 
>> its tested for bugs.
>>
>> One downside of using larger resolutions at this time is it can take 
>> upwards of 5-7 minutes to receive a PBSS from the client.
>>
>> MaydaX
>> PBBans Developer
>>
>>
>> Tyson wrote:
>>> The max resolution has not changed. It is all about sample rates.
>>>
>>> The higher the sample rates the bigger the screen size with less details 
>>> you
>>> can achieve.
>>>
>>> My Opinion you people need to go back to the PsB cfg's recommended 
>>> settings
>>> and start moving the capture area around to get different areas of the 
>>> game
>>> screen. Alternatively, follow this guide to get the best shot at the 
>>> size
>>> you want.
>>> http://www.punksbusted.com/wiki/index.php/PB_Screenshot_Setup
>>>
>>> The max is still 8200 pixels divided evenly between your width and 
>>> height.
>>> If you use oddball sizes, you are going to get weird results.
>>>
>>> Tyson
>>> Twisted Gaming Service
>>> http://www.twistedgamingservice.com
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: MaydaX [mailto:maydaxone at gmail.com] Sent: Tuesday, July 08, 2008 
>>> 11:43 AM
>>> To: cod at icculus.org
>>> Subject: Re: [cod] Laag with 1.7 Linux Servers?
>>>
>>> The 1.7 patch had nothing to do with the higher PBSS resolutions, it was 
>>> a PB client update that enabled them. The transfer rate for sending the 
>>> PBSS from client to the server still remains the same.
>>>
>>> MaydaX
>>>
>>> Guðmundur Örn Ingvarsson wrote:
>>>
>>>> Could it be that pbss is now taking ss in the resolution we specify and
>>>>
>>> then compressing them?
>>>
>>>> I had this set
>>>> pb_sv_ssheight 768     //[Requested pixel height of remote screenshots]
>>>> pb_sv_sswidth 1024      //[Requested pixel width of remote screenshots]
>>>>
>>>> And after patch 1.7 I see more of the screen of players than before 
>>>> even
>>>>
>>> though the pictures is still 512x384
>>>
>>>> Bigger ss, bigger impact on network
>>>>
>>>>
>>>
>>>
>>> ---
>>> 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
>>>
>>>
>>>
>>>
>>
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>
> 




More information about the Cod mailing list