Check you hard disk activity. There is probably some program or service running on the background that is using up all your disk. stop the service/exe after identifying it. For some reason ESO makes some windows services startup and go crazy on my laptop and it will only run smoothly after stopping them. Tip: Disabling shader cache did help me out a lot with loading screens and stutter.
Check you hard disk activity. There is probably some program or service running on the background that is using up all your disk. stop the service/exe after identifying it. For some reason ESO makes some windows services startup and go crazy on my laptop and it will only run smoothly after stopping them. Tip: Disabling shader cache did help me out a lot with loading screens and stutter.
thanks for the feedback, it just needs to be a bit more specific.
Please list those Windows services. Or do I just randomly stop (more) services?
Shader Cache: Are you still talking about Windows here? Or a game setting?
Shadowmaster wrote: »
TheRealPotoroo wrote: »[snip]Invincible wrote: »In the 90s you had to wait 20 minutes to load a jpeg [snip] you talking about bruh
[snip]
Vipstaakki wrote: »HAHAHAHA! Poor you for having to wait 5 minutes. People in the 90's had to wait 20 minutes to even get a game to start.
Telling someone to disable their Antivirus to make their game run better is perhaps one of the single worst bits of advice to give to anyone.
These are a couple of services I disable/stop (try stopping them first and see how it goes):
Windows Update (has big impact randomly mid-through game)
Superfetch
Windows Search
Anti-virus/windows defender (has big impact from time to time)
Background Intelligent Transfer Service
Nvidia Telemetry Container (if you have nvidia)
and one very important thing: disable windows telemetry and data collection. This may give you a big boost.
Merlin13KAGL wrote: »Telling someone to disable their Antivirus to make their game run better is perhaps one of the single worst bits of advice to give to anyone.
These are a couple of services I disable/stop (try stopping them first and see how it goes):
Windows Update (has big impact randomly mid-through game)
Superfetch
Windows Search
Anti-virus/windows defender (has big impact from time to time)
Background Intelligent Transfer Service
Nvidia Telemetry Container (if you have nvidia)
and one very important thing: disable windows telemetry and data collection. This may give you a big boost.
Windows Defender, maybe. Antivirus - hell no, not for any game, not for a minute, not ever.
If your AV is affecting your game:
- Add the game to the 'trusted' section of your AV
- Get a new/better AV
- Get a new/better PC.
Simply put, if you have to ask which services are ok to stop or temp disable, or if you are recommending someone disable AV to make their PC perform better, you have zero business mucking about with Windows services in the first place.
It ends badly.
I remember 2014 like it was just three years ago.This is 2017 not 2014
Also, loading screens were generally much shorter back then.
Putting the abysmal Client/Server implementation aside for a moment, ZOS has been continuously scaling down their Server hardware ever since launch.
It should be no surprise to anyone that this is getting worse instead of better.
I remember 2014 like it was just three years ago.This is 2017 not 2014
Also, loading screens were generally much shorter back then.
Putting the abysmal Client/Server implementation aside for a moment, ZOS has been continuously scaling down their Server hardware ever since launch.
It should be no surprise to anyone that this is getting worse instead of better.
Agreed. I and several of my friends all ran Traceroutes to the server IP address provided directly by ZOS support, and every test returned the same result. Our findings suggest (if not outright prove) that packets are being rejected by the endpoint, aka their server. I got their ISP involved after seeing this, and their engineers ran their own investigation and confirmed the same thing. Information is transmitted successfully all the way to the server, and for whatever reason (most likely they don't have the capacity for everything flowing in simultaneously) they reject it.
The takeaway here is that ZOS is not fixing it. A combination of too little or underperforming hardware and ZOS's iconic lack of caring about our performance despite hard evidence is likely the culprit here. No, we shouldn't be surprised. And yes, I did send all of my findings to ZOS and was ignored. The whole process was a constant, daily exchange between me and support trying to troubleshoot. The second I provided this data to them, my ticket was closed.