I have played this game for years and have seen this mentioned a few times. The problem is that whilst some people will get a little improvement from doing this, the game itself is poorly optimised and the servers (especially EU) are a shambles.
Worth trying, but do not expect miracles from this tip as there are real core problems with the game itself that I, after years of false promises, have given up on ZOS ever fixing.
If you think this is not the case, I would very much like to be corrected.
It's not just pointless, It's harmful.
The only time you'd want to do this is if you can't connect to the game at all, because your DNS cache has the wrong address for the server. And as stated above, the DNS lookup is only done when the numeric IP address is not known, so that's probably never for ESO.
For everything else you do, it's bad, and slows down making all subsequent internet connections.
Thevampirenight wrote: »So it does indeed speed up internet connection and sinse Eso launcher and the game itself does indeed interact with Dns through their website clearing the dns cache would likely help with Eso Latency. Because of this factor and explains why it works.
No, flushing your resolver cache does not speed anything up. At best it would fix a bad entry in said cache, something that rarely happens. The result (if necessary) would give the impression of a performance increase, when in reality, the device is now just properly resolving something.
There is (usually) nothing faster than resolving an IP with a locally cached result. After that, the next best step is whatever DNS server (not DNS resolver) is closest in your network's topology. Usually this is an external server to your LAN.
Thevampirenight wrote: »according to google
Google is hardly the authority on anything knowledgeable, their search engine peddles in advertising.
It is good however that you're indulging your curiosity on how things interconnect and operate. Don't be discouraged from it. Off the top of my head, when the DNS service on windows is stopped and restarted, the cached entries are dumped. So, essentially a reboot does the same thing as ipconfig/flushnds.
Just speculating here, but the servers in MD may be authoritative to all things DNS, but those entries are likely propagated to your ISP's servers. All governed by their TTL (probably no more than 24 hrs)
netsh int ip resetwhich will clear any potentially corrupted TCP/IP settings, and reboot.
vamp_emily wrote: »I heard that eating a handful of skittles before logging in to ESO reduces lag too.
I don't think /flushdns will help but I would buy "Make ESO work again" water at this point in hopes that ESO magically started working again.
I've used /flushdns when i updated a website IP Address. It never made my computer run faster.
It seems unlikely that flushing a DNS cache would be useful, especially when connecting to servers with static IP's, even if their TTL was misconfigured, it'd still be the same IP.
Resetting a router (thereby clearing its state table) would actually be more useful. Most big box store routers are junk. (I don't care how much it resembles a B2 bomber)
Okay
This is a WireShark showing the game and the patcher making DNS queries. Even supports IPv6. (color me shocked)
The #1 performance resolution I found was just delete the shader.cooked file under the documents eso directory, delete your settings.ini, boot the game but do not log in and close the game (this recooks the shader file), manually edit the settings.ini to 20 view distance (lower is better and 20 will get you objects appearing with that fun tessellated animation as you approach them). Set shaders to high or medium (ultra preloads shaders all around you, high just renders your visual field). Never adjust the view distance again, especially in game, or you will have to repeat this process.
The view distance is broken and it causes some sort problem with the way the shader file stores shaders. I'm *guessing* what is happening is the shader cache file is storing high quality or high distance shadows that are still being used even when the view distance is set low.
SET MaxCoresToUse.4 "8" //Altough I have 16 cores (in 2 processors), works better with 8...
SET RequestedNumJobThreads "8"
SET RequestedNumWorkerThreads "1"
And about ping perfomance after dns flushing, sorry but lol again XDDDDDDDD
@CathexisNetwork problems typically have to do with:
- Your geographic region
- Your bandwidth
- Network traffic
- Wifi
The farther you are from the server, the poorer the connection (information travels). Your bandwidth can also be too low or have too much traffic and this will compress your game's traffic. Some report varying degrees of success by using a VPN service that will bypass the public network load by making your computer more directly connect to the server. Most importantly, I cannot stress this enough, USE A HARD LINE NOT WIFI from PC > Router (ALWAYS for any game where possible). Flushing the DNS will only have an impact where the DNS being called and the DNS is not responding (so if the DNS isn't responding then flushing it might have a net benefit impact). If flushing the DNS is showing marked improvements for you, I recommend resetting your router to its default DNS settings, looking at DNS related settings, or a full factory reset (if it's not a lot of trouble), as a faulty configuration may be causing the DNS to fail.
Client side is the only real place you can make a performance impact.
The #1 performance resolution I found was just delete the shader.cooked file under the documents eso directory, delete your settings.ini, boot the game but do not log in and close the game (this recooks the shader file), manually edit the settings.ini to 20 view distance (lower is better and 20 will get you objects appearing with that fun tessellated animation as you approach them). Set shaders to high or medium (ultra preloads shaders all around you, high just renders your visual field). Never adjust the view distance again, especially in game, or you will have to repeat this process.
The view distance is broken and it causes some sort problem with the way the shader file stores shaders. I'm *guessing* what is happening is the shader cache file is storing high quality or high distance shadows that are still being used even when the view distance is set low.
Network problems typically have to do with:
- Your geographic region
- Your bandwidth
- Network traffic
- Wifi
The farther you are from the server, the poorer the connection (information travels). Your bandwidth can also be too low or have too much traffic and this will compress your game's traffic. Some report varying degrees of success by using a VPN service that will bypass the public network load by making your computer more directly connect to the server. Most importantly, I cannot stress this enough, USE A HARD LINE NOT WIFI from PC > Router (ALWAYS for any game where possible). Flushing the DNS will only have an impact where the DNS being called and the DNS is not responding (so if the DNS isn't responding then flushing it might have a net benefit impact). If flushing the DNS is showing marked improvements for you, I recommend resetting your router to its default DNS settings, looking at DNS related settings, or a full factory reset (if it's not a lot of trouble), as a faulty configuration may be causing the DNS to fail.
Client side is the only real place you can make a performance impact.
The #1 performance resolution I found was just delete the shader.cooked file under the documents eso directory, delete your settings.ini, boot the game but do not log in and close the game (this recooks the shader file), manually edit the settings.ini to 20 view distance (lower is better and 20 will get you objects appearing with that fun tessellated animation as you approach them). Set shaders to high or medium (ultra preloads shaders all around you, high just renders your visual field). Never adjust the view distance again, especially in game, or you will have to repeat this process.
The view distance is broken and it causes some sort problem with the way the shader file stores shaders. I'm *guessing* what is happening is the shader cache file is storing high quality or high distance shadows that are still being used even when the view distance is set low.
Absolutely true. I think I have tried everything possible in this game and that is by far the most useful. Delete usersettings.ini and mostly everything under documents. In my case, after last update, ESO went monocore again, and the only thing it returned to multicore was that, and setting up in usersettings.txt
SET MaxCoresToUse.4 "8" //Altough I have 16 cores (in 2 processors), works better with 8...
SET RequestedNumJobThreads "8"
SET RequestedNumWorkerThreads "1"
And about ping perfomance after dns flushing, sorry but lol again XDDDDDDDD
relentless_turnip wrote: »@Cathexis
I just tried this... My shader.cooked file never came backsorry to sound like an idiot... but is it meant to?
The game ran fine anyway...
Also when editing the user settings did you mean: usersettings.txt file?
gatekeeper13 wrote: »I dont think the problem is how fast the client communicates with the server. Its not a connection issue. Its mostly how fast the server does the calculations. Game engine is bugged, the server cant handle high load and sent data to your client fast enough. This is what I THINK the problem is. I am not a programmer and cant speak for certain. May be wrong.
I made these changes and got like +20 fps in cities and around +30/40 fps everywhere else.
SET MaxCoresToUse.4 "-1"
SET RequestedNumJobThreads "-1"
SET RequestedNumWorkerThreads "0"