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
I've played like this before where I left Rust, played something else for a while and came back in the same session / without restarting Windows. When I submitted a ticket for this issue, the first thing they told me was to delete the EAC folder and verify the files, which I did and tried to enter a server normally after re-downloading it. NOPE! Repairing it did nothing, just like reinstalling Rust in its entirety.
Same situation as with 149.56.28.91:28016 - I can connect with it while I launch Rust without EAC, but nothing else. Deleted Rust and reinstalled it, same with EAC, updated my drivers and nothing was changed. About a day later now, and it's doing the same thing.
If it helps, the last frame on the screen before my computer instantly restarted displayed "SPAWNING WORLD (562/11721)". Maybe if others deal with the same thing at the same "stage" of loading, it could pinpoint the cause of the issue.
024-05-14T12:44:23.744Z|0x2bac|Generating procedural map of size 4500 with seed 267853072
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:Log(Object)
<InitCoroutine>d__19:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
Client:StartLoading(IEnumerator)
<StartPlayingDemoInternal>d__103:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
2024-05-14T12:44:24.760Z|0x2bac|NullReferenceException: Object reference not set to an instance of an object.
at GenerateHeight.Process (System.UInt32 seed) [0x00000] in <00000000000000000000000000000000>:0
at WorldSetup+<InitCoroutine>d__19.MoveNext () [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00000] in <00000000000000000000000000000000>:0
clan
How do I even check it? There's nothing in F1 while I'm loading other than info I already know, and I can't check in-game because I can't load a game.
Id put money its your power supply failing. Thats usually what happens.
The game is loading up, as soon as it starts pulling full power from the rail and the psu cant sustain that spike, itll cause your system to restart.
This is why I buy power supplys with about 150-200 more watts than what I need. If I only need 350 watts, id have a 500 watt psu. The psu will last much longer that way. If you do the bare minimum they only seem to last for 3-5 years.
650watt PSU.
Rust isn't crashing, the problem is it is freezing the PC, cannot alt tab, cannot move mouse. Rust works fine when EAC is disabled and I have played a lot of other games from Halo, Hell Let Loose, FIFA and even used Blender to render a scene. No spike in temps, absolutely nothing to say it's a hardware problem.
In my case, it literally force restarts the PC. It doesn't lack power, because my Lenovo Legion Go portable which is way weaker can run Rust no problem, and for some reason Rust does not crash there.
There's still time for it to start crashing, since it did not start crashing right away on this patch on my main/laptop, but rather after almost 2 weeks have passed where I've been playing no problem. The GPU is not going bad because I can play other, more demanding games without an issue.
And as I said in a previous reply, the last thing displayed in Rust before force restarting my laptop was "SPAWNING WORLD (562/11721)". Maybe this information is relevant and can lead to figuring out what's causing the issue, as I haven't changed ANYTHING on my PC in those couple hours while I've been absent.
Then explain how after the update we all had the same failing power supply but can join facepunches server without the easyanticheat
Its the easy anti cheat its as simple as that.