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
Just keep trying and you'll be summoned. Unless the differences are too high.
Either way... There's something like TTL (Time To Live) in the networking. It works like that:
1. Send a request (peer1) - ping
2. Decide whether to send a response or not (peer2) - pong
3. Receive the response (peer1). If not received by a certain time, send the request again.
Yet! If the request and/or response from peer1 to peer2 exceeds its limit of routes based on the TTL, then the request/response is lost. A single route you may interpret as a computer that ping-ponging the request/response on the network path from peer1 to peer2.
The message in the game itself means nothing from the technical perspective, so I just may speculate how this server-client connection infrastructure works.
You may try any of my following suggestions:
- turn off any background programs that may using the Internet during the play (i.e. browser)
- change the DNS's to be closer to the DS servers
- try to connect with DS servers using VPN with shorter network routes
- boost OS Internet settings to fit the highest performance for the poorest connections
- try to play with someone from your place of belonging, like in your country; if you cannot play with that person comfortably then you have just poor Internet connection and you cannot do anything special with that
There's no really a one universal answer for that.
For better understanding of summon sign appearings in other worlds (so I may assume):
1. Summon sign is placed
2. Player request is queued to the asynchronous list
3. Player is summoning to the other world
4. Trying to create session (asynchronously) - connecting phantom with the host
5. Refusing at any errors
6. Loading phantom side area, statistics nerfing and scaling etc.
7. Refusing at any errors at any time for too long duration
The problem is that nearly at any of this points there need to be a network connection. See 7. Also there's still some problems when your game get stuck because of your hardware. How you can interpret that in phantoms worlds?
Dark Souls have no network compensation (if there are problems then the players character won't be animated - lack of data; in games like Battlefield moves are actually predicted and mapped, so you don't see this microlags and desyncs), but has sort of a network time compensation (waiting for a while after summon may give you some profit with synchronisity between phantoms and the host).
few exceptions. the only time it happened to me, I hard-rebooted my modem and it got fixed.
normally, that message appears when you were about to enter a world in which there was someone that had blocked your steam profile, so the invasion/summon fails.
I know, I said that it usually only happens when someone had blocked you, but very rarely you get that error almost every single time for some reason, and the fix for me was to hard-reboot the modem.
https://support.bandainamcoent.com/index.php?/Knowledgebase/Article/View/512/458/dark-souls-iii---connection-tips-for-dark-souls-iii
I had to both open (port forward) the TCP and UDP ports (my router also had a specific format which must be used to get all the ports in),
- reboot the router, _and_ also totally
- quit and restart Steam, but afterwards I was summoned as Blue Sentinel automatically and in my own summon signs right away.
* I still have issues sometimes, but I notice they go away on their own (usually within a few hours to a day), so I can only assume it's just network congestion, because without changing anything it starts working again, but definitely improved with these ports.
Hope it helps someone else.