Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
No, my buddies didn't re-install and I reckon they shouldn't have to, seeing how they can connect to any other server with no issues. Also, it doesn't crash with any error message, it just stops responding.
sv_pure 0 gives me 'this command is write protected', so can't change that. As for the other commands...that's basically Chinese to me. And none of it sounds like something I or any of my friends should HAVE to do, considering we all otherwise easily connect to other servers. But in any case, how can I check those values?
I am still perplexed by the fact they were able to join that one time after I freshly re-installed the game. As if sv_pure 0 was there by default, and changed to 1 after re-running the game?
In any case, thanks for all suggestions!
You can launch a listen server then check the values in your console. Here's what I see on my end, for instance :
You can type the first part, like sv_pak, then hit TAB for a list of cvars starting like that.
For reference on what these cvars are for, you can CTRL-F them there :
http://www.regurge.at/ql/
I wrote with the Bethesda support and one of their instructions has fixed the problem for me: Performing a clean Windows boot. Here are the instructions: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
Make sure to NOT disable the service "Steam Client Services". This is the only service that you have to keep enabled.
With a clean Windows boot I was finally able to join my friend's server. It get's better: Even after returning to a normal Windows boot, the problem has now disappeared magically. The error is gone.