ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler How are those fixes coming? We're now in the 6th week since you said this would be fixed "next week".
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler How are those fixes coming? We're now in the 6th week since you said this would be fixed "next week".
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler How are those fixes coming? We're now in the 6th week since you said this would be fixed "next week".
There have been multiple tweaks and adjustments since the issue rose its head, they're just not listed in the patch notes. It's not something they can fix right away without breaking other stuff, and apparently they're constantly making changes each patch to make it better. So far it's worked for some and not others.
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler How are those fixes coming? We're now in the 6th week since you said this would be fixed "next week".
There have been multiple tweaks and adjustments since the issue rose its head, they're just not listed in the patch notes. It's not something they can fix right away without breaking other stuff, and apparently they're constantly making changes each patch to make it better. So far it's worked for some and not others.
Could you direct me to where I can find some corroboration?
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler How are those fixes coming? We're now in the 6th week since you said this would be fixed "next week".
There have been multiple tweaks and adjustments since the issue rose its head, they're just not listed in the patch notes. It's not something they can fix right away without breaking other stuff, and apparently they're constantly making changes each patch to make it better. So far it's worked for some and not others.
Could you direct me to where I can find some corroboration?
Cillion3117 wrote: »It only does it on my main who is VR15. All my lower level toons never have any problems.
When this game was in beta and then released, we had no lag in Cyrodil, even in huge fights, and quick loading screens. Now, almost two years later, even 1/3-sized fights in Cyro are lagfests, and loading screens take forever. And you think they are fixing things, lol?
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler Still not fixed?
b92303008rwb17_ESO wrote: »ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
@ZOS_BrianWheeler Still not fixed?
I guess he is going to reply soon, like Cubs are going to win world series.
ZOS_BrianWheeler wrote: »This is an issue we're tracking and have some fixes in the works for next weeks patch.
https://www.youtube.com/watch?v=dQw4w9WgXcQ