On 25/01/2013 22:46, Essay Tew Phaun wrote:
Any idea what specifically about CentOS causes this? I'd prefer not to
switch the distro if at all possible. Could Valve possibly comment on this?
It'll presumably be the kernel or the libraries. Not very specific though.
If you have more than one server, I would switch one (I'd make it
vanilla too), because finding the cause,
assuming there even is one, will be far more effort than the half an
hour it takes to install debian -
and if it turns out there isn't one you'll have wasted a lot more time.
Plus, if running one Debian machine fixes it you can either switch them
all or, if you care, find what
specifically causes it yourself by comparing things on the good and bad
machines.
My bet is, it won't, as the issues sound a bit too specific.
Unless the payload thing is caused by whatever the engine uses to time
things
being different (which is no doubt a kernel config thing)
I can't see how the game rules would be affected in the way described.
I'd think it far more likely to be a plugin or a game bug.
I've not really played any payload to say anything about those bugs though.
I've certainly never seen through walls. 2fort's spawn door can have a
glitch
and refuse to open and let people out if there's a cloaked spy knocking
around occasionally
(at least I've attributed it to the presence of the spy, that could be
coincidence)
I've never had a problem picking up the intel in hundreds of hours of
CTF - but perhaps the
rule change to sticky and rocket jumper isn't well known and that
explains it. Are we talking
intel that is in the enemy base or that has been dropped somewhere along
the way?
Intel that is run into a spawn takes a tad longer to pick up as you exit.
--
Dan
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
