I think ZOS should be starting to see a trend here - something is blatantly broken in the engine or game code.
@ZOS_AlexTardif Until the issue is solved, could we use a script command (or sort of) to avoid relogging?
I think of something able to temporary "clean" the memory, reboot the stucked process or such.
It would be extremely useful to mitigate our frustration.
GUYS? I found the solution.
I switched the sampling rate from my soundcard from 48KHz to 44.1KHz.
I guess it is some buffer problem of the DirectX sound library.
k4Ku.exGb16_ESO wrote: »Just gotta believe...
It would be interesting to know what else he did though. Since his issue seems to be fixed. Maybe he just quit the game already though and doesn't wanna admit that 'fix' didn't work.
He seems quite convinced that it did the job idk..
k4Ku.exGb16_ESO wrote: »Can you elaborate? Maybe just link something?
GUYS? I found the solution.
I switched the sampling rate from my soundcard from 48KHz to 44.1KHz.
I guess it is some buffer problem of the DirectX sound library.
Cambion2401 wrote: »k4Ku.exGb16_ESO wrote: »Just gotta believe...
It would be interesting to know what else he did though. Since his issue seems to be fixed. Maybe he just quit the game already though and doesn't wanna admit that 'fix' didn't work.
He seems quite convinced that it did the job idk..
Some time ago it helped for some people to install actual DirectX (as Windows10 emulates older DirectX versions trough DirectX12, and any emulation cost performance. Trying to directly call to files might also give problems). It's a bit tricky because Windows would tell you you have a newer DirectX already, but there is a version for developers that does work.
Now, this didn't work for everyone too, but there is a pattern.
Perhaps his solution was not the one, but perhaps it is indeed DirectX related. The issue (for me) has always changed with every patch. Right now it gone and thanks to a reinstall I am on "normal" DirectX. Or (if it's DirectX related) my issue isn't really gone but 8GB DDR5X vram makes it more doable. I've been able to play 7 hours strait this weekend tho (altrough I have a crafter on another character now so I relog to switch every now and then).
Cambion2401 wrote: »k4Ku.exGb16_ESO wrote: »Just gotta believe...
It would be interesting to know what else he did though. Since his issue seems to be fixed. Maybe he just quit the game already though and doesn't wanna admit that 'fix' didn't work.
He seems quite convinced that it did the job idk..
Some time ago it helped for some people to install actual DirectX (as Windows10 emulates older DirectX versions trough DirectX12, and any emulation cost performance. Trying to directly call to files might also give problems). It's a bit tricky because Windows would tell you you have a newer DirectX already, but there is a version for developers that does work.
Now, this didn't work for everyone too, but there is a pattern.
Perhaps his solution was not the one, but perhaps it is indeed DirectX related. The issue (for me) has always changed with every patch. Right now it gone and thanks to a reinstall I am on "normal" DirectX. Or (if it's DirectX related) my issue isn't really gone but 8GB DDR5X vram makes it more doable. I've been able to play 7 hours strait this weekend tho (altrough I have a crafter on another character now so I relog to switch every now and then).
I use Windows 7, so whatever voodoo tricks you think you found (but didn't share with us anyway) do not apply here.
k4Ku.exGb16_ESO wrote: »Well, I'm not quite sure if it's entirely fixed yet. But I'm quite positive it's at least a great improvement. After installing the runtimes from the sdk I've played a couple of hours now and it's not gone as bad as it was before. I still clearly loose performance after a while, about ~5 fps and more stutters when streaming in stuff, but it always goes back up to 60fps+ if I'm outside towns.
k4Ku.exGb16_ESO wrote: »And yea btw I tried Windows 7 & 8.1 on the weekend and I had the same issue. So it also has to be hardware related. On Windows 7 it took way longer for it to happen though. Maybe that was only the low pop on early Sunday morning though.
What happend with the DirectX SDK if i start a fresh new Steam or Gog game? Normally, DirectX is reinstalled there. Every game.
Cambion2401 wrote: »EDIT:
This is what is pre-installed (end-user Runtimes):
https://www.microsoft.com/en-us/download/details.aspx?id=8109
This is what you need to make sure it installs correctly (SDK):
https://www.microsoft.com/en-us/download/details.aspx?id=6812
Cambion2401 wrote: »EDIT:
This is what is pre-installed (end-user Runtimes):
https://www.microsoft.com/en-us/download/details.aspx?id=8109
This is what you need to make sure it installs correctly (SDK):
https://www.microsoft.com/en-us/download/details.aspx?id=6812
These are the links we wanted.