GoldenEye: Source Forums
Debriefing => Bug Reports & Fixes => Topic started by: StupidMarioBros1Fan[1138] on February 03, 2014, 11:28:52 pm
-
I keep getting this when trying to connect to a server, I can create a LAN server just fine, but I'm sick of playing against bots now that my internet connection is no longer shitty and I can play matches online without lagging. :P
Apparently someone had gotten this error back in September according to the FaceBook post, but other than that I keep getting the situation happening with CounterStrike: Source, and isn't actually in the same situations as me. :-\
Any ideas on what to do?
-
I had the same problem, opting out of the Steam beta fixed it.
-
I'll try that when I get home, I hope it works.
-
I just remove all my steam content except SteamApps folder and Steam.exe and it's work fine now :)
-
I have this same exact problem. I want a fix to where I wont have to delete everything :-\
-
Opt out of steam client beta. That's all you have to do.
-
What if you are not in the steam beta and it still does it? (I've already tried the delete trick)
-
Maybe Opt into a beta? I don't know, it's a valve error. A blind monkeys guess is sufficient when troubleshooting valve errors.
-
Maybe Opt into a beta? I don't know, it's a valve error. A blind monkeys guess is sufficient when troubleshooting valve errors.
Well i already tried that... why does this always happen.
-
I've had that issue too while not beeing in the beta.
But it was gone the next day.
-
Glad to know I'm not the only one. This just happened to me while I was not opting in any current betas, I attempted to opt into a beta with no luck. I reinstalled Steam, but to no avail. I tried running GE:S vanilla, assuming it could've been a problem with my reskins, gamemodes, or sprays, but that didn't do anything (luckily I backed them all up). I even tried reinstalling GoldenEye: Source but I hadn't struck any gold.
I connected to a Counter-Strike: Source server to see if this problem was throughout Source MP, but CS:S worked like a charm. This is especially annoying since I was just about to test my custom sprays and rent out a GE:S server. This is the first time this has ever happened to me, and I could easily believe this is on Valve's end which makes me hope they fix this soon.
EDIT: Rediscovered this old post while conducting a routine security check-up. Yes, it is important to fix typos 7 years after the fact. No, I will not fix the sense of uncertainty implied by my expression ("I could easily believe") with respect to who was at fault with this when it was obviously a Valve Software issue – to that extent I feel it wouldn't be proper to alter my previous statements.
-
Same prob for me here since yesterday... currently updating steam...
-
I just got it today. I wasn't participating in Steam Beta.
(http://cloud-2.steampowered.com/ugc/577888948812588587/0BECFF90972ACEE416DE68F9BB3344B8FC1A6CBC/)
I tried doing this:
http://forums.steampowered.com/forums/showthread.php?p=26454448
No go
-
Servers will have to be updated to the latest version of the SDK 2007 DS from SteamCMD before they will work with the latest version of the client.
-
Man, Valve really seems to hate mods nowadays! Hopefully the SDK 2013 update will help out a bit by bringing us up to speed on the latest tech...
-
STEAM certificate length error! 0/2048 here too... Since the Steam update that was automatically downloaded today. I get annoyed enough by the DAILY Steam updates, but even more so when the update breaks the game. :(
-
I just tested; with an old server install, I got the error. After updating it, I was able to connect locally, plus had someone connected remotely.
Valve didn't break anything. Servers just need to be updated. It's not rocket science.
-
Good to know. I'm setting up a new server now.
-
Servers will have to be updated to the latest version of the SDK 2007 DS from SteamCMD before they will work with the latest version of the client.
Does this work? Nothing seems to work currently.
Switched from HLDS to SteamCMD and it didn't work. Going to ask my host about it.
-
Does this work? Nothing seems to work currently.
It works. If you have the problem, you're not on the latest version. Right now there's multiple working servers. (That I know of, Troy's, 1138 and TG's)
-
I just tested; with an old server install, I got the error. After updating it, I was able to connect locally, plus had someone connected remotely.
Valve didn't break anything. Servers just need to be updated. It's not rocket science.
EDIT: Updated SDK and it works perfectly.
Cheers,