![]() Possibly a warning that when a certain log size is exceeded, it may cause FPS drops/Freezes in combat - making the user aware of why an issue may be happening, and that they can fix the issue themselves without room to blame incorrectly. I have set it to 5, and will report back if I see this issue arise again. It may be useful to have a slider that simply says "Max Log Size" which allows the user to set the size in megabytes (or kilobytes?) An exception to this is Kinessa's Oppressor Mine which will enter neither target nor Kinessa into combat. Using abilities that count as Weapon Shots. Activation To activate the Out of Combat mechanic, a player must spend 5 seconds without: Taking or dealing damage. I am unsure if the 'General Options > Data Segments to Keep' slider will mediate this issue. Out of Combat is a Gameplay Mechanic in Paladins. Perhaps consider implementing an automatic log cleanup, on by default, that deletes older data after a certain period of time.Ī fancier option might include deleting 'trash' fights before boss fights. The way I had to discover the cause, required tearing appart my addon list to find it.īecause many addons are involved with combat, it can be difficult to find which addon is causing the problem - and if Skada is found to be causing the problem, a user may not understand that their log is simply too large and instead blame Skada itself - and not the fact that they just haven't reset their logs recently. The character this occured on, is one that I mostly solo world content with - so I never hit any of the cases that Skada would suggest resetting the data. This happens with default addon settings, and causes frame drops to 'mysteriously arise'. Freeze continued when all addons were disabled, except for Skada.Freeze came back when Skada was re-enabled.Freeze went away when Skada was disabled.Disabled addons in sequence, until the freeze stopped happening on combat start.This lasts for a brief, but very noticeable period of time (long enough for an enemy to close to melee range from ~20 yards before the game unfreezes) I never need the DPS meter in the center of the UI like that, but I really want to see more (ten to twelve) rows of data in it.When Skada is using around 18MB it begins to cause brief framedrops/freezes when combat starts. I specifically don't want to have the DPS meter window and the threat meter window in the same place and switch mode: I only need a small threat meter (three rows) but it has to be highly visible during the fight because I need to watch my threat, or co-tank threat, closely. I would probably end up setting my DPS meter window to hide in combat, and my threat window to hide out of combat, so that I had the appropriate things shown at the appropriate time. I would most prefer a model where this worked on a per-window basis, fully configurable. ) Please provide any additional information below. I exclusively use threat in combat, for the obvious reasons. (In practice I rarely, if ever, use the DPS track in combat, but frequently outside it. I use Omen for that, because I want to be able to hide my threat window when not in combat, but I am happy with the regular damage/healing meters being visible all the time. Right now I use Skada for all my tracking except threat. What is the enhancement in mind? How should it look and feel? Regardless of the out of combat (hide) setting, you can always right click the arrow beneath the chat box to toggle the embedded addon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |