KB971033-- Description of the update for Windows Activation Technologies
KB2952664 -- Compatibility update for keeping Windows up-to-date in Windows 7
KB2976978 -- Compatibility update for keeping Windows up-to-date in Windows 8.1 and Windows 8
KB2990214 -- Update that enables you to upgrade from Windows 7 to a later version of Windows
KB3021917 -- Update to Windows 7 SP1 for performance improvements
KB3022345 -- Update for customer experience and diagnostic telemetry
KB3035583 -- Update installs Get Windows 10 app in Windows 8.1 and Windows 7 SP1
KB3044374 -- Update that enables you to upgrade from Windows 8.1 to Windows 10
KB3068708 -- Update for customer experience and diagnostic telemetry
KB3075249 -- Update that adds telemetry points to consent.exe in Windows 8.1 and Windows 7
KB3080149 -- Update for customer experience and diagnostic telemetry
KB3123862 -- Updated capabilities to upgrade Windows 8.1 and Windows 7
RinaldoGandolphi wrote: »The FPS drop over time can be "somewhat" alleviated by following the steps i put out in a video awhile back
https://www.youtube.com/watch?v=-pYJeanHHQ4
This will make the FPS drops over time on Windows 10 less noticeable and will buy you a bit more time before your forced to restart the client.
However the only "real" fix to the FPS drop over time issue in ESO is rolling back to Windows 8.1 or Windows 7 SP1 with the Platform Update for Windows 7 installed. This is because DirectX11 in Windows 10 is emulated though DirectX12 (by using feature levels) this means a Direct X11 application running on Windows 10 runs through DirectX12 but only calls the feature levels for DirectX 11.0, 11.1 or 11.2. This is how previous previous versions of DirectX worked on previous versions of Windows such as DX8 running though DX9 on XP, DX9 running though DX10 on Vista, and DX 10 running through DX11 on Win 7 and Win 8.
The issue is the implementation of piping DX11 though DX12 is bugged in Windows 10. I have reported this to Microsoft for the last year and a half. I have a support agreement though Microsoft where I work, and I was told by Tier 3 support that they are aware of this issue but have ZERO intentions to fix it.I was told this was left in place soley for enterprise users who use version of .Net and WPF and WPP applications mostly. They want to move away from DirectX11 completely when Windows 7 and Windows 8.1 support expires (2020 for Windows 7 extended and 2023 for Windows 8.1) their response was to port the application to DirectX12 or work around the Windows 10 DirectX11 implementation.
I guess this issue only happens in certain cases which is why many other games are not effected. I would guess something ESO does with lighting and particles causes this bug to crop up. The bug however does not exist in Windows 7 or 8.1 which have native implementations of DirectX11.0, 11.1 and 11.2.
I know folks don't want to hear this, but Microsoft isn't fixing this DirectX11 bug on Windows 10. At this point if ZOS wants to continue with DirectX11 than they need to find what part of their code(im guessing lighting and particles) is causing the bug and refactor that code to address it.
Also, don't forget the following updates are baked into Windows 10 and can not be removed:KB971033-- Description of the update for Windows Activation Technologies
KB2952664 -- Compatibility update for keeping Windows up-to-date in Windows 7
KB2976978 -- Compatibility update for keeping Windows up-to-date in Windows 8.1 and Windows 8
KB2990214 -- Update that enables you to upgrade from Windows 7 to a later version of Windows
KB3021917 -- Update to Windows 7 SP1 for performance improvements
KB3022345 -- Update for customer experience and diagnostic telemetry
KB3035583 -- Update installs Get Windows 10 app in Windows 8.1 and Windows 7 SP1
KB3044374 -- Update that enables you to upgrade from Windows 8.1 to Windows 10
KB3068708 -- Update for customer experience and diagnostic telemetry
KB3075249 -- Update that adds telemetry points to consent.exe in Windows 8.1 and Windows 7
KB3080149 -- Update for customer experience and diagnostic telemetry
KB3123862 -- Updated capabilities to upgrade Windows 8.1 and Windows 7
Those updates are constantly using CPU cycles in the background and are constantly reporting telemetry data to Microsoft and there is no way to shut them off unless your running Windows 10 enterprise which requires a Volume License Key which is only available to companies who purchase in large quantities or in some educational licensing.
Those updates were backported to Windows 7 and Windows 8.1 but they can be uninstalled and hidden on those OS and the Tracking Services disabed or deleted thus your computer isn't constantly using CPU cycles reporting telemetry. Yes, your PC faults every second, and every time it does that in the background telemetry goes to work.
honestly Windows 10 is a bear of an OS. It uses 15% more ram than Windows 8.1 does, its slower in everyday use on the same hardware, and its constantly collecting user data, and is just downright buggy. They had to pull the Windows 10 1809 update 3 times due to catastrophic bugs (Like deleting users files from My Documents on upgrade) among many others things.
If you can roll back to a previous version i would suggest it. If not than follow my video and it should give you some relief.
Only having 2 cores on a inside a CPU resulted in those PC's getting a massive FPS increase when multi-core support was added.
Only having 2 cores on a inside a CPU resulted in those PC's getting a massive FPS increase when multi-core support was added.
Have you tried to turn Hyperthreading off in Uefi/Bios and forcing ESO to work on 2 Cores? Im not sure if I understand you correct there but as we are able to have CPUs with 4,5+ Ghz and more per Core, why not trying that. Im interested to hear if that works.. If yes I would try the same with my i7 4790k.
I mean, sure its not our Job to do that as result of ZOS failing to programming their Game correctly but Im so tired of it and Im almost only playing ESO, that Im wanted to do anything to "Fix" this Drops over Time.
You also mensioned its triggered by Tab Out? Im sure that isnt the only reason as I get this as well in after a Restart in different Trials with Exclusive Fullscreen enabled and no Tab out till Raid End after more than a Hour.. After that Hour or sometimes less, many Wipes at Bosses later Fps Drops and Drops until theyre at a Point around 40 where the whole Game slows down, where 40 fps feeling like 20 or so, laggy, slow, dying. lol
I think of coming back. Has the problem been resolved?
Intel Core i7+ 8750H Coffee Lake 17.3" LED 1920x1080 IPS ComfyView 144Hz RAM 24GB DDR4 + 16GB Intel Optane NVIDIA GeForce GTX 1060 6GB HDD 1TB 7200still every time I use a skill in a 1v1 I get about 0.5s lag. Frames drop anytime by just traversing the likes of Murkmire with barely any NPC in sight, which hints to the game not being optimised.
With the upcoming Update 24 on Monday, there will also be significant Improvements concerning Memory Fragmentation/Management.
Unfortunately nobody talks about this in the last 4 Weeks for the PTS. Did anyone Test this out? Did it help?
Will I be able to Play Groupcontent longer than 20 minutes without being forced to Restart the whole Game because my Framerate got almost cut in half?
All my hopes for future Performance Improvements are based on this problem.
Alienoutlaw wrote: »you could try this, i went from a hard cap of 60fps to now running over 120fps pvp usually sits around 70-80 dropping to 40 in keeps
https://www.youtube.com/watch?v=JuD-n5zIXoQ