Re: [hlds] Optional Team Fortress 2 update later today (toolchain update)

2017-03-14 Thread BOOM! Support
Without a doubt there's huge number of TF2 players down right now. It would
sure be great if Valve would take 30 seconds to post post an announcement
on their *http://www.teamfortress.com * page
telling players the update has broken MAC clients. Right now I'm certain
players everywhere are wasting their time and troubleshooting their own PCs
thinking something with their PC is screwed up having know idea the update
broke their client.

On Tue, Mar 14, 2017 at 6:52 PM, A Fearts  wrote:

> Here is a three page thread about it: http://steamcommunity.com/app/
> 440/discussions/0/135511655650120722/
>
> On Tue, Mar 14, 2017 at 9:36 PM, A Fearts  wrote:
>
>> I can confirm E. Olsen's reply. Some Mac users have reported to me also
>> they are getting that same disconnect message.
>>
>> With the Mac user I tested:
>>
>> 1. Having them try to connect to a server not using the optional update.
>>
>> 2. Having them try to connect to a server that is using the optional
>> update.
>>
>> 3. Having them try to connect to a Valve server.
>>
>>
>> None of the three tests allowed the user to connect.
>>
>> On Tue, Mar 14, 2017 at 9:14 PM, E. Olsen  wrote:
>>
>>> Hiya John,
>>>
>>> Just a heads-upa few of my users that are on Macs are getting the
>>> following message when trying to connect after their clients updated:
>>>
>>> *Disconnect: Server uses different class tables*
>>>
>>> On Tue, Mar 14, 2017 at 4:58 PM, John Schoenick >> > wrote:
>>>
 We're working on an optional update for Team Fortress 2. The notes for
 the update are below. We are tentatively aiming for 4PM PDT (23:00 UTC).

 This update will be making the toolchain beta branch live.  This update
 is known to break numerous server mods, many of which have updates
 available.  In order to reduce the pain with this transition, the update is
 optional for servers.  However, the next mandatory TF update will
 necessarily end support for the pre-toolchain-update builds, so server
 administrators should seek to update as soon as possible.

 See the "Updated system requirements for TF2 dedicated servers" thread
 for more information on the toolchain update.

 - John

 

 - Internal updates to support future development

 ___
 To unsubscribe, edit your list preferences, or view the list archives,
 please visit:
 https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


>>>
>>> ___
>>> To unsubscribe, edit your list preferences, or view the list archives,
>>> please visit:
>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>>
>>>
>>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Optional Team Fortress 2 update later today (toolchain update)

2017-03-14 Thread A Fearts
Here is a three page thread about it:
http://steamcommunity.com/app/440/discussions/0/135511655650120722/

On Tue, Mar 14, 2017 at 9:36 PM, A Fearts  wrote:

> I can confirm E. Olsen's reply. Some Mac users have reported to me also
> they are getting that same disconnect message.
>
> With the Mac user I tested:
>
> 1. Having them try to connect to a server not using the optional update.
>
> 2. Having them try to connect to a server that is using the optional
> update.
>
> 3. Having them try to connect to a Valve server.
>
>
> None of the three tests allowed the user to connect.
>
> On Tue, Mar 14, 2017 at 9:14 PM, E. Olsen  wrote:
>
>> Hiya John,
>>
>> Just a heads-upa few of my users that are on Macs are getting the
>> following message when trying to connect after their clients updated:
>>
>> *Disconnect: Server uses different class tables*
>>
>> On Tue, Mar 14, 2017 at 4:58 PM, John Schoenick 
>> wrote:
>>
>>> We're working on an optional update for Team Fortress 2. The notes for
>>> the update are below. We are tentatively aiming for 4PM PDT (23:00 UTC).
>>>
>>> This update will be making the toolchain beta branch live.  This update
>>> is known to break numerous server mods, many of which have updates
>>> available.  In order to reduce the pain with this transition, the update is
>>> optional for servers.  However, the next mandatory TF update will
>>> necessarily end support for the pre-toolchain-update builds, so server
>>> administrators should seek to update as soon as possible.
>>>
>>> See the "Updated system requirements for TF2 dedicated servers" thread
>>> for more information on the toolchain update.
>>>
>>> - John
>>>
>>> 
>>>
>>> - Internal updates to support future development
>>>
>>> ___
>>> To unsubscribe, edit your list preferences, or view the list archives,
>>> please visit:
>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>>
>>>
>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>
>>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Optional Team Fortress 2 update later today (toolchain update)

2017-03-14 Thread A Fearts
I can confirm E. Olsen's reply. Some Mac users have reported to me also
they are getting that same disconnect message.

With the Mac user I tested:

1. Having them try to connect to a server not using the optional update.

2. Having them try to connect to a server that is using the optional update.

3. Having them try to connect to a Valve server.


None of the three tests allowed the user to connect.

On Tue, Mar 14, 2017 at 9:14 PM, E. Olsen  wrote:

> Hiya John,
>
> Just a heads-upa few of my users that are on Macs are getting the
> following message when trying to connect after their clients updated:
>
> *Disconnect: Server uses different class tables*
>
> On Tue, Mar 14, 2017 at 4:58 PM, John Schoenick 
> wrote:
>
>> We're working on an optional update for Team Fortress 2. The notes for
>> the update are below. We are tentatively aiming for 4PM PDT (23:00 UTC).
>>
>> This update will be making the toolchain beta branch live.  This update
>> is known to break numerous server mods, many of which have updates
>> available.  In order to reduce the pain with this transition, the update is
>> optional for servers.  However, the next mandatory TF update will
>> necessarily end support for the pre-toolchain-update builds, so server
>> administrators should seek to update as soon as possible.
>>
>> See the "Updated system requirements for TF2 dedicated servers" thread
>> for more information on the toolchain update.
>>
>> - John
>>
>> 
>>
>> - Internal updates to support future development
>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>
>>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Optional Team Fortress 2 update later today (toolchain update)

2017-03-14 Thread E. Olsen
Hiya John,

Just a heads-upa few of my users that are on Macs are getting the
following message when trying to connect after their clients updated:

*Disconnect: Server uses different class tables*

On Tue, Mar 14, 2017 at 4:58 PM, John Schoenick 
wrote:

> We're working on an optional update for Team Fortress 2. The notes for the
> update are below. We are tentatively aiming for 4PM PDT (23:00 UTC).
>
> This update will be making the toolchain beta branch live.  This update is
> known to break numerous server mods, many of which have updates available.
> In order to reduce the pain with this transition, the update is optional
> for servers.  However, the next mandatory TF update will necessarily end
> support for the pre-toolchain-update builds, so server administrators
> should seek to update as soon as possible.
>
> See the "Updated system requirements for TF2 dedicated servers" thread for
> more information on the toolchain update.
>
> - John
>
> 
>
> - Internal updates to support future development
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Optional Team Fortress 2 update released (toolchain update)

2017-03-14 Thread John Schoenick
We've released an optional update for Team Fortress 2. The notes for the
update are below. The new version is 3842775.

This is the toolchain update discussed previously on this list.  The
update is optional to give server operators a final grace period to
ensure their setups are valid, but be warned that there will be no
fallback available whenever the next mandatory TF update ships.

See the "Updated system requirements for TF2 dedicated servers" thread
for more information on the internal changes in this update.

- John



- Internal updates to support future development


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Prerelease Update available for Counter-Strike: Source, Day of Defeat: Source, Half-Life Deathmatch: Source, Half-Life 2: Deathmatch, and the Source SDK 2013 Base

2017-03-14 Thread John Schoenick
A prerelease update is available for Counter-Strike: Source, Day of
Defeat: Source, Half-Life Deathmatch: Source, Half-Life 2: Deathmatch,
and the Source SDK 2013 Base. The update notes are below.

Prerelease branches can be accessed in Steam via the Properties -> Betas
tab. Dedicated servers can pass -beta prerelease to the app_update
command in SteamCMD.

If all goes well, this branch will be promoted to the current release in
the coming days, so please let us know if you encounter any issues.

Note that this is *not* the previously mentioned toolchain update for
these games, which is still slated for the near future.


 - John

-

- Improved Steam Voice support
  - Removed sv_use_steam_voice convar. Steam voice is now selected via
"sv_voicecodec steam"
  - Fixed demos not properly recording Steam Voice status, resulting in
potential corrupt voice in demos with differing default settings
  - Will now use the native Steam Voice sampling rate, instead of
clamping to 11kHz
  - Improved compatibility with Steam client beta
- Added CELT audio codec currently in use in TF2 and CS:GO
  - Server operators may enable use of this codec via "sv_voicecodec
vaudio_celt"
  - Steam voice remains the default voice codec in all SDK2013 games
- Updated spec_player command to match recent improvements in TF2
  - Now accepts partial player names, Steam IDs, etc.
- Fixed security issue reported by Amat Cama via GeekPwn
- Updated engine with recent stability and bug fixes from TF2
- Updated handling of game language setting to match Team Fortress 2
behavior:
  - Steam per-game language setting is now properly honored and syncs
with the in-game setting
  - In-game UI language now honors above language setting, rather than
improperly using the Steam client's UI language setting
- Users wishing to have separate UI and audio languages may pass
-audiolanguage on the command line
- Updated the localization files
- [DoD:S] Updated custom loading error dialog to include numerous tweaks
and fixes that have previously been applied to the base version


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Optional Team Fortress 2 update later today (toolchain update)

2017-03-14 Thread John Schoenick
We're working on an optional update for Team Fortress 2. The notes for
the update are below. We are tentatively aiming for 4PM PDT (23:00 UTC).

This update will be making the toolchain beta branch live.  This update
is known to break numerous server mods, many of which have updates
available.  In order to reduce the pain with this transition, the update
is optional for servers.  However, the next mandatory TF update will
necessarily end support for the pre-toolchain-update builds, so server
administrators should seek to update as soon as possible.

See the "Updated system requirements for TF2 dedicated servers" thread
for more information on the toolchain update.

- John



- Internal updates to support future development
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Heads up - Updated system requirements for TF2 dedicated servers, likely mod breakage - Beta available

2017-03-14 Thread Oscar
Is the steam runtime as buggy for servers as it is for clients? Never had
it work out the box for me, praise the AUR

On Tue, 14 Mar 2017, 00:41 Rowedahelicon, 
wrote:

> Do you have a rough day in mind this week? I'm worried about the winter
> storm taking down my power this week and need to know if I have to make
> accommodations
>
> On Mon, Mar 13, 2017 at 7:48 PM, Weasels Lair 
> wrote:
>
> Yep, sorry got that posted before trying disabling SMAC.  Disabled SMAC
> and it worked better!
> Will try Ryan's "smac_validate_auth 0"
>
> On Mon, Mar 13, 2017 at 4:41 PM, Ryan Stecker 
> wrote:
>
> smac_validate_auth 0
>
>
> On Mon, Mar 13, 2017 at 6:35 PM, Weasels Lair 
> wrote:
>
> PS: More specifically, on a non-BETA TF2 client, trying to connect to the
> current BETA TF2 server, the client connects, seems to work for a few
> seconds, then throws a dialog with the error:
>
> "Disconnected" (Title)
> "Disconnected: Your client has failed to authorized in time.
> Please reconnect or restart your game."
>
> Restarting the game does not help.  Playing on non-BETA TF2 servers seems
> to work fine.
>
>
> On Mon, Mar 13, 2017 at 4:26 PM, Weasels Lair 
> wrote:
>
> Lately I have not been able to successfully connect from a plain
> (non-Beta) TF2 client to my BETA TF2 server.  Has that functionality been
> broken by a non-beta TF2 client update?
>
> On Mon, Mar 13, 2017 at 3:36 PM, John Schoenick 
> wrote:
>
> There have been no significant changes after the few fixes mentioned here
> on Day 1 (namely, removing libstdc++ from the install)
>
> On 03/13/2017 02:58 PM, A Fearts wrote:
>
> Hey John quick question. Have there been any changes to the toolchainbeta
> since you first posted it that we might need to recheck stuff or it is all
> the same?
>
> On Mon, Mar 13, 2017 at 5:47 PM, John Schoenick 
> wrote:
>
> Reminder, we plan on releasing a normal update with this change this
> week.  Server operators are encouraged to double-check that their setup
> works against the toolchainbeta branch to avoid ugly surprises!
>
> - John
>
> On 02/20/2017 02:46 PM, John Schoenick wrote:
>
> Hey everyone,
>
> Following up on the warning email we sent a long while back, we're making
> good on our promise and changing our build toolchains for the TF2+SDK2013
> games' dedicated server.  TF2 is being updated first, with the other
> SDK2013 games to follow.
>
> There are two things that may affect server administrators that you should
> be aware of:
>
>
> *The Linux dedicated server now targets the Steam Runtime*
>
> The Steam Runtime is a common runtime target based on Ubuntu.  For srcds,
> this largely means linking against a more recent glibc than may be
> available in some server distributions.  Administrators should check that
> the provided beta still runs in their environment of choice.  Those who are
> on older or incompatible distributions have several options:
>
> - Switch to a distribution more compatible with the Steam Runtime, such as
> Ubuntu LTS
>
> - Make use of a chroot/container/VM environment to run srcds.  The tools
> linked below include a script for creating a chroot that can be used for
> bootstrapping Steam Runtime environments.
>
> - Use the Steam Runtime tools linked below combined with some dynamic
> linker magic to use the runtime libraries on an incompatible distribution,
> e.g.:
>
> steamrt=/path/to/runtime
> export LD_LIBRARY_PATH="bin:$steamrt/usr/lib32"
> LD="$steamrt/usr/lib32/ld-linux.so.2"
> "$LD" ./srcds_linux "$@"
>
> More information about the Steam Runtime and utilities for obtaining it
> can be found here: https://github.com/ValveSoftware/steam-runtime
>
>
> *The compiler toolchain used for all editions of srcds has changed*
>
> Along with the client builds, all server builds have been updated to a
> newer compiler.  Windows builds now use the MSVC2015 tools, while Linux
> builds now use a newer edition of GCC with differing command-line
> parameters that affect codegen.
>
> This is expected to break mods that expect certain ABI behaviors or look
> for certain signatures in order to hook functions (such as SourceMod).  We
> have separately spoken with the SourceMod team and they are working on
> supporting the new setup.  Maintainers of other mods should test them
> against the beta release below.
>
> Our previous warning also indicated that this would change the _srv naming
> of the linux binaries.  We have decided *not* to adjust this, and the
> separate _srv build and naming remains unchanged.
>
>
> *Beta*
>
> We've made a beta branch available for TF2 with these new changes.  The
> remaining SDK2013 games will be updated in the near future, and we will
> provide a beta for them at that time.
>
> The beta is compatible with the current TF2 public release - servers may
> safely convert to it and continue serving both