Open zeflap opened 8 years ago
I wouldn't know. I haven't had actual interaction or any progress in months. Today was literally the first thing I knew when my issue was closed today and that it was "fixed". I've yet to even catch up or even attempt.
This was way more documented between me and @danielmm8888 in chats and I've forgotten what we achieved.
In regards to your issue. Something happened during your install. By default it's always secure mode unless -insecure is stated in launch.
The issues with #68 are unrelated to the issue. The Insecure error is (as far as we're aware) a Valve (source engine) issue.
I've contacted some folks at Valve and a patch is pending for the engine, It may or may not fix the issue. If not some further digging will be required. VAC works serverside (and only serverside) and this is why I've not publicly announced Linux Binaries on the site yet.
I'll keep you posted and post a public announcement once they work.
If you're still having issues @Kiwi-1995 I'll re-open your issue but compiling it with an earlier copy of libraries and GCC on a 32bit install seemed to solve the segfault problems on my end.
Alright, thanks for the info.
How about adding this to your Launch Options for Team Fortress 2 Classic for the time being?
-steam
Sometimes this workaround works for quite a few VAC related issues...
If that fixes it I'll make sure to inform Valve and our players of the fix.
They think it may be fixed next Source SDK Base patch which is several months late.
Actually the -steam hack is also use by Valve themselves as you can see from the TF2 default launch option there at SteamDB https://steamdb.info/app/440/config/
which is added automatically if the game is launched from Steam according to Valve's wiki https://developer.valvesoftware.com/wiki/Command_Line_Options#Command-line_parameters
But it seems mods launched from Steam don't have -steam option added... So yeah, finger crossed if VAC issues fixed since I am no Source Engine developer just a net wanderer...
Edit: Ok ok so Source SDK Base 2013 do have -steam -game sourcetest added, but for whatever reasons it does not honour that -steam option for mods thus VAC issues inside mods on Linux and Mac versions. Additional -steam seems to fix it. Valve please fix!
-steam parameter is not a hack and Source SDK Base mods are normally always launched with that option as well otherwise you'll get same insecure mode error even in Windows version.
Well on Linux version it needs double -steam for now (at least for me)... :(
Wait, so adding -steam parameter does fix the issue with TF2C?
I don't know if it fixes 100%. I merely just sharing what it works for me and what I know so far. It can act as a workaround until the patch come along. I hope someone can confirm it.
Simply adding -steam to the TF2 Classic launch parameters did not work for me. After lots of fiddling I figured out a work around.
Be advised, launch parameters in Library stopped working for Source mods after the latest Steam update.
Simply adding -steam to the TF2 Classic launch parameters did not work for me. After lots of fiddling I figured out a work around.
- Either copy or symlink the tf2classic directory to the Source SDK Base 2013 Multiplayer directory.
- Set the launch parameters of Source SDK Base 2013 Multiplayer to "-steam -game tf2classic" (NOTE: it must be in that order. "-game tf2classic -steam" did NOT work for me.)
- Launch Source SDK Base 2013 Multiplayer.
Your solution worked like a charm!
The symlink solution seems to have been broken at some point, sadly. It worked for me before but on a new installation today I still can't reach servers.
GH isn't letting me edit at the moment, but there's another workaround available: if you do the symlink method and then manually launch from the terminal then it works.
Getting "You are in insecure mode. You must restart before you can connect to secure servers" on trying to connect to servers. Fetched the binaries 6h ago (from http://services.0x13.io/TF2C_2_0_0b1.7z), so if @Th13teen's fix to #68 affects this at all, it should be in what I have.
Furthermore, do the linux binaries @Kiwi-1995 mentions is #68 exist as a separate thing or is this a case of "build them"?
Running on Debian 8.2, if that has any effect.