my favorite post from there:
"My guess is the 15th. The 8th makes more sense to most players, so naturally Blizzard will choose the 15th instead."
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
so I guess it is 15th, right?![]()
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
https://us.battle.net/forums/en/d3/topic/20770687480
(TL; DR : Nobody knows)
Supported version for all Resu plugins
Even though Blizz changed a lot of offsets, a few structure sizes, and some important keys (with no Enigma to fix things up... I'm still working on getting the framework working properly again.. so many sleepless nights.. just need to borrow a few extra braaaaiiiinnnnss.. I'm just can't seem to get ahold of the ContainerManager and ObjectManager (even though the guys at ROS-BO...uuuuuT) somehow figured it out right away! GRRRRRRRRRR.)
Anyway, I have my own overlay and I noticed that the latest version of D3 is using many more UI cycles (limited to one thread on Windows machines). I noticed my queued overlay/Dispatcher operations were being delayed. I'm pretty sure it is blizz that increased its hogg-age of the primary UI thread lately. I've been able to get almost equivalent performance, oddly enough, by turning off vertical sync but most importantly - adjusting the "Max Background FPS" in the game. I have no idea what blizz is smoking but it seems like if that number is too LOW they aren't yielding to the UI thread like they were before. It doesn't make much sense - that number is supposed to only affect framerate when D3 is not in the foreground, but I can demonstrably show that Blizz slows my overlay (and vice versa) unless I bump up the background FPS to at least 15.
Nothing else has changed with my overlay nor my system... I could be full of crap but seriously.. it won't hurt to try, and I think they may be yielding those "background frames" to other programs, whereas before they were being gentler with calculations happening directly on the UI thread... it's also possible it's a Blizz bug and it's not their intent to take into account the background FPS user setting at all when D3 is running in the foreground. An easy way to test is crank background DPS down to 2, then up to 5, then to 15 and compare results. GL... hopefully I'm wrong about this and it's just a bum video driver release, but I know you/I aren't the only ones noticing lag, especially when there are other competitors competing for the Windows UI thread/Dispatcher.
https://us.battle.net/forums/en/d3/t...0856885#post-3
This reasoning seems right and it seems that we will have to wait until the 15th, although with Blizzard we never know.
It is Blizzard's mess: Still no era end. Patch date wasn't announcemned, but era end was (8th January).
"As you may have noticed, the latest Era did not roll as originally communicated on January 8. We have updated the Era end date to January 14 in light of this issue.
We apologize for any inconvenience and misunderstandings that may have occurred as a result of this miscommunication, and look forward to seeing you in the next Season and Era when they begin next week"
Supported version for all Resu plugins
Blizz's screw-up. Era 14th, patch 14th/15th, S16 18th.
so next Tuesday/Wednesday is confirmed?
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
I read monday 14th (if you suppose New era and New patch will be at the same time)... But it's the well known Blizzagenda...
https://us.battle.net/forums/en/d3/topic/20770676889
Supported version for all Resu plugins
https://us.battle.net/forums/en/d3/topic/20770907028
Read the last post. Era ends 5 PM in respective time zones. Patch will be ~24 hours after that and S16 72 hours after patch. If not, the official forums will riot.