Generally speaking the event itself isn’t the problem. The problem is that every addon creates its own listener and then calls a function to receive the information, which includes the actual event name that addons use to even see if they need to do anything. But in order to get that info, you need to get all info, just to check if it’s the event you want to listen to. It’s expensive in terms of CPU.
Note that this isn’t the (lead) cause of FPS issues, but it’s certainly one of those things that doesn’t help. Splitting the event into multiple events, or even just passing the sub event would probably already make a difference.
I’m pretty sure that all the passive effects causing aura changes don’t help either. Pressing a spell doesn’t just do damage, it usually also applies debuffs, buffs, heals other targets etc.
Compared to a even just a Legion 5 Pro they are.
(I am talking about the old series which had the 3060 ones; some of the newer nitros are a bit better but still nowhere near as good as the legion pros).
simple, it’s just unoptimized, I had a look at their minimal requirements and I almost coughed up my breakfast because my PC outpaces that several times over and I still had sub 1 fps (around 1 fps every 4 seconds) at the start of the week anywhere in khaz algar during the flame radiance event
Which one? I don’t have fps issues on any of the bosses and I’m running a 3060. I’m also not running ElvUI or a trillion weakauras that are constantly loaded although they shouldnt be or 0.25interval details however.
Also the issue in WoW isnt the GPU in most cases. Its the CPU combined with it getting bombarded by a trillion calculations a second because of how Blizzard designed classes because they are defacto incapable of remembering the past.
We had this already in BFA with the game no longer being able to handle the amount of calculations and the game flat out going down on its knees during Nyalotha because it was overwhelmed with the sheer amount it had to do calculate each second. They just switched Azerite Traits and Corruptions with our current Talent design.
The playerbase is also partly to blame for this because people wanted classic tree design while still feeling the impact with each talent point spent. The game can’t handle it.
Sabotage level optimization since dragonflight, class designs bloated with cpu heavy tasks on this engine, like attending formula 1 race with an 20 year old regular car
COMBAT_LOG_EVENT_UNFILTERED does not have a payload, so you look at the 2nd parameter called “subevent”. So if you want to listen to say _CAST_START, you will have to listen to every single COMBAT_LOG_EVENT_UNFILTERED event, call CombatLogGetCurrentEventInfo() to get the payload, then check the 2nd parameter and ignore it of it’s not the cast start subevent.
