On 26/01/2013 18:51, Claudio Beretta wrote:
You can't really blame him for asking this:
-no announcement available at release
-client updates almost always make the server download the updated files,
even if it's optional for them
-tf2 history of forgetting to update steam.inf / master servers no
You can't really blame him for asking this:
-no announcement available at release
-client updates almost always make the server download the updated files,
even if it's optional for them
-tf2 history of forgetting to update steam.inf / master servers not sending
out the update notification
-tf2 his
The main question that I asked was "did servers even get it at all?" (not
"was this a mandatory update?"). Documentation was merely a secondary
question.
On Sat, Jan 26, 2013 at 7:03 AM, dan wrote:
> On 26/01/2013 01:49, wickedplayer494 . wrote:
>
>> Thing is, they weren't available for close to
On 26/01/2013 12:48, Essay Tew Phaun wrote:
I am positive that that is not the case and that walls are see through for
everyone.
Fair enough, but everyone uses the server and the client though :)
Is it specific maps?
FPS 385? Are you all using Billy's Buggy config or something like that?
--
On 26/01/2013 12:58, Essay Tew Phaun wrote:
Forgot to mention. Valve responded to me directly that it could be related
to "rdtsc discrepancies"
Yeah, that's the timer thing. Presumably they think it may be going
forwards and backwards
on different cores?
Do they always use it though? There's
On 26/01/2013 01:49, wickedplayer494 . wrote:
Thing is, they weren't available for close to 45 minutes before now. There
was more than enough reason to inquire during then.
If your client updated and you connect to your non updated server it can't
be mandatory.
The tf2 wiki usually has an entr
Forgot to mention. Valve responded to me directly that it could be related
to "rdtsc discrepancies" and suggested I set each server to use a single
core. So I'm going to do that and see if it resolves the problem.
On Sat, Jan 26, 2013 at 7:51 AM, dan wrote:
> On 25/01/2013 22:46, Essay Tew Phau
Yeah I posted here as a last resort after Googling for ages.
I did manage to find a shotgun limiter[1] but I'm still stumped on the
2v2/3v3 + spectator thing. Thought I'd ask here before writing my own.
[1] https://forums.alliedmods.net/showthread.php?p=746026
On 26/01/2013 11:18 PM, Erik-ja
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 se
I am positive that that is not the case and that walls are see through for
everyone. If I hadn't seen it happen to an entire server on multiple
occasions I would have probably thought the same thing.
http://cloud.steampowered.com/ugc/596977147797869396/DD97BD0D26B24D5EE167F0E7DC7FD471A1F9F767/http
On 25/01/2013 22:05, Essay Tew Phaun wrote:
Doorways will turn to flat colors that allow you to see through walls.
Everyone experiences this and it's not clientside.
I can't see how this can be anything other than clientside, the
server doesn't render walls or colours.
Randomly you won't be
Visit forums.alliedmods.net (google what you want) it surely has limiter +
weapon restriction plugins (sourcemod)
-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Yun Huang
Yong
Sent: zaterdag 26 januari 2013
12 matches
Mail list logo
