Forum

ahaha D:

Quoted from AnAkkk

because tickrate 100 fuck up the game door speeds and other things

How so?
I thought this only happened when the server doesn’t have the hardware to support it. Read that on the valve developer wiki site somewhere a while ago..

Quoted from AnAkkk

lol. That’s quite good. Unfortunately all the kids who don’t understand how the netcode works are whining, and that don’t know that the OB Engine hit registry is better.

And no, this is not breaking mods. This is more like fixing things, because tickrate 100 fuck up the game door speeds and other things.

Fixing the things which Zblock allready fixed without this change yes?

Also the engine is better yes, but whats the point in putting it onto the better engine then downgrading, hardware improvements have allowed servers and clients to get a pritty stable 100tick / fps theres no point lowering it now…

Also when your saying “blabla they know nothing about netcode” theres plenty of people in the css community who will probably know more about the netcode than you (to my knowledge) who are saying its screwed but we should wait and see anyway.

Quoted from AnAkkk

lol. That’s quite good. Unfortunately all the kids who don’t understand how the netcode works are whining, and that don’t know that the OB Engine hit registry is better.

Anakin, I know you’d like to think you know what you’re talking about but i’d like to explain publically why this is complete and utter pish.

Yes, The OB engine does have better hit registry, I’ll give you that. However you’re missing the fact that 100 tick should be in the OB engine anyway.

A lot of people are starting to get 120Hz monitors, and I don’t just mean hardcore gamers like nvc etc, I mean normal hardware fanatics, and higher refresh rates seem to be the logical way for LCD monitors to go in general anyway. It usually takes a few years but this always trickles down to what jim and bob have in their PC. On a 66 tick server, this means that on every 2nd frame, the computer is just guessing whats actually happening… (extrapolating the data). On a 100tick server, theres a lot more data, making the whole system a lot more accurate. I don’t see how that could possibly be a bad thing?

I know what your saying Anakin, but really, nobody wants any of the changes in the CSS beta, they just want fixed hit reg. Move it to orangebox, allow 100 tick and everyone will be happy.

Quoted from Skyride

[…]

Anakin, I know you’d like to think you know what you’re talking about but i’d like to explain publically why this is complete and utter pish.

Yes, The OB engine does have better hit registry, I’ll give you that. However you’re missing the fact that 100 tick should be in the OB engine anyway.

A lot of people are starting to get 120Hz monitors, and I don’t just mean hardcore gamers like nvc etc, I mean normal hardware fanatics, and higher refresh rates seem to be the logical way for LCD monitors to go in general anyway. It usually takes a few years but this always trickles down to what jim and bob have in their PC. On a 66 tick server, this means that on every 2nd frame, the computer is just guessing whats actually happening… (extrapolating the data). On a 100tick server, theres a lot more data, making the whole system a lot more accurate. I don’t see how that could possibly be a bad thing?

I know what your saying Anakin, but really, nobody wants any of the changes in the CSS beta, they just want fixed hit reg. Move it to orangebox, allow 100 tick and everyone will be happy.

This, I personaly didn’t think about the refresh rate issues actully, I play on a CRT and didnt think about this untill you said it

good, css is a dog game

Quoted from TucE

Thats must to do, when CSS has Orange Box engine. TF2 have way better netcode than CSS with 100 tickrate server now.

Did you even read the topic?