Out of curiosity, will this upcomming release also herald the passing of the VSM aka VAC1? The King is dead, long live the King and all?
- Ben On 02/07/05, Alfred Reynolds <[EMAIL PROTECTED]> wrote: > This is just another nudge, make sure to use "-vacbeta" on your HL1 > servers. There will be a release in the next few weeks to enable VAC2 by > default on servers (with the same command line options as VAC1). > > - Alfred > > ----Original Message---- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Alfred > Reynolds Sent: Thursday, June 16, 2005 3:05 PM To: > hlds_linux@list.valvesoftware.com; hlds@list.valvesoftware.com; > [EMAIL PROTECTED] Subject: [hlds_linux] VAC2 Beta > information > > > As most of you know, VAC2 has been in beta for a few weeks. We're > > nearing release, but we need lots of servers to run the beta right > > now in order to complete our testing. > > > > VAC2 is a significant overhaul of the Valve Anti-Cheat system. Its > > release is going to be a major event in the community, so your help > > during the beta will be much appreciated. > > > > From experience, we know that the members of this mailing list will > > provide us with better feedback than we'll be able to get elsewhere. > > We need as many of you as possible to start running your servers with > > the > > VAC2 beta code turned on. Once you've started doing so, please send > > us any and all trouble reports by reporting them to this list. > > > > Instructions: > > The VAC2 beta functionality is already included in both the Source > > and > > HL1 dedicated server, just ensure you have the most recent update by > > running the hldsupdatetool. > > > > In order to turn it on, simply restart your server and add " -vacbeta" > > to your the command line. > > > > We're primarily dealing with connection issues at this point. This > > means that if you choose to run your server using the VAC2 beta, a > > small number of users could have trouble connecting to your server. > > We are particularly interested in hearing about any issues regarding > > connection problems. > > > > Things to watch for: > > - "No Steam Logon" errors reported by clients. If a user gets this > > consistently across a couple day period then get them to go to our > > support site for help. > > - "steamclient.dll not found, server communication disabled." printed > > out on startup. For linux users make sure you have at least GLIBC > > 2.3.2 or above. You also need to allow outbound UDP traffic on port > > 27014 from your server. If you do have the correct GLIBC version or > > run under win32 then contact me to debug the problem. > > > > Thanks for your help. > > > > - Alfred > > > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list > > archives, please visit: > > 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 > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
