[ Converted text/html to text/plain ] Ok I though I wouldn't have to deal with the kind of attitude i got from some of you people. Seriously, shame on you! 1. We are not going to be able to use 66 tick. It's just NOT an option. I'm not going into A discussion about it. 2. I am NOT from England or USA and therefor do not use english as my language of choice. Try to think outside your little box you call your life. 3. This was primarily directed to the plug-in writerst, and other who know some coding or have any other knowledge that would be of use. It was not directed to people who only wan't to make fun of me or trying to boost their ego, just don't press the "SEND" button if your one of them. Anyhow, the fix that some servers have, that one of you said they had, may be phys_timescale 1.5. This does indeed fix the door issue but has MANY drawbacks that one may not think about when playing on a fun-server or general public server. It would be good if anyone who knows a server that has this "fix" could check if phys_timescale is the case. Check this by jumping up boxes for example. You will feel the difference.
>Use a 66 tickrate server. :) >Seriously, I haven't heard a single good reason to use anything higher >that >stands up to serious scrutiny. On 12/5/06, jonatan sandberg <[EMAIL PROTECTED]> wrote: > > [ Converted text/html to text/plain ] > Hello Friends. > I am a server administrator for my competetive team. I try to get our > matches > as fair and smooth as possible. We have to play our matches in tick100, > league > rules. Because of this the doors in all maps that our league plays are > really > hard to use and kind of unpredictable at times. A couple of days ago > someone > posted a "quickfix" for the doors, adjusting phys_timescale. This is not > any > kind of fix that can be used in serious matches. Phys_timescale also > affects > jumping, if only a little its still to much, and other things. > Because of this I am here asking if there is possible to create a plug-in > to > fix this problem. It's a longshot but is it possible to create a plug-in > that > only changes the phys_timescale value for the doors, or ANYTHING to fix > the > problem. Lets face it, Valve is not going to touch this, ever! And because > of > this we at r60.org, and possibly every other Cs:s league out there, asks > you > plug-in creators to take a look at this. We would really be in dept to > you, we > already are! > Thank you in advance, if for nothing else than for trying. /Jonatan > Sandberg > Forsgren > > > > ------------------------------------------------------------------------------ > Get Your Own .NU Web Address Now! ---> http://WWW.NUNAMES.NU[1] > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux[2] > -- ------------------------------------------------------------------------------ Get Your Own .NU Web Address Now! ---> http://WWW.NUNAMES.NU ===References:=== 1. http://www.nunames.nu/ 2. http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
