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
if you tried that post pc specs inc windows 10 or 11 as their have been issues with both over last couple months
a endless loadingscreen points to a problem in the system this can be caused by a lot of additional stuff, specific if it happens during invasions it could also be caused by the other end but normally if something goes wrong during connect there is a death timer that would close the game process, there are situations where it could ends in a endless loop but this should be rare.
primary a third party antivirus, firewall or other security software can cause such problems, additional to this windows internal malfuctions can cause this (a check of the time it happens and analysis of the event viewer logs could show a connection between a windows internal thing and the problem).
sometimes instable drivers cause this (a check of the device manager by show hidden devices would show if something is wrong).
it is also possible that the EAC installation in windows is not updated correctly (it is now reported multiple times for windows 11 that the registry keys are not updated or only partly updated causing a lot of different problems) and a clean reinstall with delete the registry keys is needed.
powermanagement can cause strange behavior (usb selective powersaving, CPU powersaving and some others are known for causing delays in the system that can break the netcode flow).
finally other background apps can cause a short delay window that cause that the netcode runs into a response timeout.
just to add at windows 10 was a silent windows update that has caused strange processing behavior at some systems, lagging and stuttering, freezes and some input reading changing behavior, for some it got resolved by set the start_protected_game.exe (sorry wrong file previous) in taskmanager to realtime but at some systems this is not possible and you have to use a registry change (looks like since the last EAC update it no longer works), what points to a cpu time order change in the process management. i have this problem since 3 weeks now with my testsystem and for older games at my newer systems, also for elden ring random (depends on how long the system did not got a restart of windows).
Happens to me sometimes in both invasions AND co-op, though it's significantly less often in co-op.
This is always due to the host having trash-tier internet. When connecting to the host, the loading progress bar doesn't just indicate loading assets into memory, but also how much world-state data has been sent from the host. Stuff like their build, equipment loadout, cosmetics, which enemies / bosses are still alive, etc. If the host's PC isn't sending this data, then you'll be staring at a slowly moving or completely unmoving progress bar until the connection times out. Would be great to have a way to manually cancel being summoned while in the loading screen.
I play offline so it has nothing to do with invasions or co-op and i havent run any third party security software since the most recent download, my drivers are all fine and like i said ive done a clean reinstall
I just know that not all proton versions work and for elden ring a specific Version has to be set.
Nfinite.recursion is far better for troubleshooting in Linux.
Proton 7.0-6 is the most stable Version, i can see from posts of infinite.recursion.
Finally the game is made for Windows and i have no idea how to troubleshoot it at Linux, there are no logs i could analyse and i also do not know if some form of driver conflict could appear that cause this problem.