[Bug] FPS Issue

Question

[Bug] FPS Issue

voozul opened this issue 2 months ago · 17 comments

Describe the bug
Hi, I am running on Ryzen 5600x and Nvidia 3080ti (I've set all graphics settings in game and in nvidia to basically the lowest 1/10).

Idk if this is a plexus issue. I am having big fps issues in the new raid (I run default blizz ui with a few mass used addons like details, plater - I have set their refresh timer to the lowest).

I ran an addon that measures addon cpu usage during raid combat and it says Plexus was using nearly 50% of my cpu does this sound right? (this was in LFR 25 man testing, in raid when we do hc we go 30 man and i'm on like 16 fps which is basically unplayable). Details and plater etc were using v tiny amounts according to the cpu usage addon.

I've cleared out all the debuffs I tracked from previous raid tiers from plexus but didn't notice any difference.

Desktop (please complete the following information):

OS: [e.g. Windows] windows 10 pro
Version [e.g. v1.5.6] 22h2
Game Version - retail

Additional context
Add any other context about the problem here.

voozul · Answer 1 · 2024-09-30T14:57:50.000Z

Idk if this is to be expected but after testing the same LFR fight with default blizz healing frames v plexus I'm losing about 20 fps with Pleux.

doadin · Answer 2 · 2024-09-30T18:34:10.000Z

hmmm, not sure, would have to disable some modules in plexus maybe to narrow it down to which part of plexus is using so much cpu. what addon do you use to get this info?

voozul · Answer 3 · 2024-09-30T18:54:55.000Z

its from curse and called "addons-cpu-usage" (was recommended by a guildie when I was having issues)

…

On Mon, 30 Sept 2024 at 19:34, doadin ***@***.***> wrote: hmmm, not sure, would have to disable some modules in plexus maybe to narrow it down to which part of plexus is using so much cpu. what addon do you use to get this info? — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4NH7EQLZCBESGA2XE26ZTZZGKTRAVCNFSM6AAAAABPC6OWSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBTHA4TSNRYHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

doadin · Answer 4 · 2024-09-30T19:00:18.000Z

Thanks, I will try and reporduce this issue and narrow it down, if you could do the same by disableing some modules of plexus till the fps issue goes away, I would appreciate it, if not no problem, thanks for reporting I will try my best to fix this.

xaos-org · Answer 5 · 2024-10-20T18:24:17.000Z

I experienced this problem as well and have been tracking this issue. I've disabled the two related addons (PlexusStatusRaidDebuff and PlexusStatusDungeonDebuff) that I had installed with no change. Last night I reverted to version 3.3.5 from 2024-08-28 and the "unplayable" issue disappeared for me, so I suspect that changes from 3.3.5->3.4.1 introduced the significant FPS issue -- or at least magnified any issue that might have already existed.

Asherak · Answer 6 · 2024-10-30T19:43:08.000Z

It seems that people joining and leaving causes a significant stutter and people joining and leaving quickly tends to bog the game down.

Hey, just wanted to mirror this comment as this is the exact issue I'm facing currently. Cycling people out during mythic reclears 100% leads to issues as people leave/join the raid group. Typically will get a few frames of my game freezing as people join/leave and game performance steadily drops until I restart my game.

Unsure if related but I've had a separate issue where Plexus seems to give up and will reset into a random position/layout with the following error in Bugsack (other addons mentioned as well, not sure which is the cause):

4x Plexus/Layout.lua:1074: script ran too long
[string "@Plexus/Layout.lua"]:1074: in function LoadLayout' [string "@Plexus/Layout.lua"]:992: in function ReloadLayout'
[string "@Plexus/Layouts.lua"]:359: in function ?' [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...ons/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:109> [string "=[C]"]: ? [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...ons/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15> [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function SendMessage'
[string "@Plexus/Roster.lua"]:251: in function ?' [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...ons/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:109> [string "=[C]"]: ? [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...ons/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15> [string "@AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function Fire'
[string "@Bartender4/libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <Bartender4/libs/AceEvent-3.0/AceEvent-3.0.lua:119>

Locals:
self =
{
layoutSettings =
{
}
modules =
{
}
defaultModuleState = true
db =
{
}
enabledState = true
frame = PlexusLayoutFrame {
}
LayoutList =
{
}
defaultModuleLibraries =
{
}
options =
{
}
prototype =
{
}
forceRaid = false
name = "Plexus_PlexusLayout"
orderedModules =
{
}
layoutGroups =
{
}
baseName = "Plexus"
defaultDB =
{
}
super =
{
}
layoutPetGroups =
{
}
moduleName = "PlexusLayout"
}
layoutName = "ByRole"
p =
{
hideTab = false
backgroundTexture = "None"
layouts =
{
}
ScaleSize = 1.200000
FrameLock = true
borderSize = 16
lock = true
anchor = "TOPLEFT"
backgroundColor =
{
}
showOffline = true
showWrongZone = "ALL"
PosY = -623
groupAnchor = "TOPLEFT"
unitSpacing = 0
layout = "ByRole"
Spacing = 0
anchorRel = "TOPLEFT"
Padding = 8
borderInset = 8
layoutPadding = 0
scale = 1.350000
borderTexture = "None"
horizontal = true
borderColor =
{
}
PosX = 539
}
layout =
{
1 =
{
}
defaults =
{
}
name = "By Role"
}
groupsNeeded = 1
petGroupsNeeded = 0
groupsAvailable = 1
petGroupsAvailable = 0
defaults =
{
unitsPerColumn = 5
groupBy = "ASSIGNEDROLE"
groupingOrder = "TANK,HEALER,DAMAGER,NONE"
sortMethod = "NAME"
}
groupSpacing = nil
iGroup = 2
iPetGroup = 1
(for index) = 1
(for limit) = 1
(for step) = 1
(*temporary) = 1
(*temporary) =
{
groupFilter = "1,2,3,4"
maxColumns = 4
}
(*temporary) = PlexusLayoutHeader1 {
1 = PlexusLayoutHeader1UnitButton1 {
}
2 = PlexusLayoutHeader1UnitButton2 {
}
3 = PlexusLayoutHeader1UnitButton3 {
}
4 = PlexusLayoutHeader1UnitButton4 {
}
5 = PlexusLayoutHeader1UnitButton5 {
}
6 = PlexusLayoutHeader1UnitButton6 {
}
7 = PlexusLayoutHeader1UnitButton7 {
}
8 = PlexusLayoutHeader1UnitButton8 {
}
9 = PlexusLayoutHeader1UnitButton9 {
}
10 = PlexusLayoutHeader1UnitButton10 {
}
11 = PlexusLayoutHeader1UnitButton11 {
}
12 = PlexusLayoutHeader1UnitButton12 {
}
13 = PlexusLayoutHeader1UnitButton13 {
}
14 = PlexusLayoutHeader1UnitButton14 {
}
15 = PlexusLayoutHeader1UnitButton15 {
}
16 = PlexusLayoutHeader1UnitButton16 {
}
17 = PlexusLayoutHeader1UnitButton17 {
}
18 = PlexusLayoutHeader1UnitButton18 {
}
19 = PlexusLayoutHeader1UnitButton19 {
}
20 = PlexusLayoutHeader1UnitButton20 {
}
21 = PlexusLayoutHeader1UnitButton21 {
}
22 = PlexusLayoutHeader1UnitButton22 {
}
23 = PlexusLayoutHeader1UnitButton23 {
}
24 = PlexusLayoutHeader1UnitButton24 {
}
25 = PlexusLayoutHeader1UnitButton25 {
}
UnitFramesCreated = 25
}
(*temporary) = PlexusLayoutHeader1 {
1 = PlexusLayoutHeader1UnitButton1 {
}
2 = PlexusLayoutHeader1UnitButton2 {
}
3 = PlexusLayoutHeader1UnitButton3 {
}
4 = PlexusLayoutHeader1UnitButton4 {
}
5 = PlexusLayoutHeader1UnitButton5 {
}
6 = PlexusLayoutHeader1UnitButton6 {
}
7 = PlexusLayoutHeader1UnitButton7 {
}
8 = PlexusLayoutHeader1UnitButton8 {
}
9 = PlexusLayoutHeader1UnitButton9 {
}
10 = PlexusLayoutHeader1UnitButton10 {
}
11 = PlexusLayoutHeader1UnitButton11 {
}
12 = PlexusLayoutHeader1UnitButton12 {
}
13 = PlexusLayoutHeader1UnitButton13 {
}
14 = PlexusLayoutHeader1UnitButton14 {
}
15 = PlexusLayoutHeader1UnitButton15 {
}
16 = PlexusLayoutHeader1UnitButton16 {
}
17 = PlexusLayoutHeader1UnitButton17 {
}
18 = PlexusLayoutHeader1UnitButton18 {
}
19 = PlexusLayoutHeader1UnitButton19 {
}
20 = PlexusLayoutHeader1UnitButton20 {
}
21 = PlexusLayoutHeader1UnitButton21 {
}
22 = PlexusLayoutHeader1UnitButton22 {
}
23 = PlexusLayoutHeader1UnitButton23 {
}
24 = PlexusLayoutHeader1UnitButton24 {
}
25 = PlexusLayoutHeader1UnitButton25 {
}
UnitFramesCreated = 25
}
(*temporary) = PlexusLayoutHeader1 {
1 = PlexusLayoutHeader1UnitButton1 {
}
2 = PlexusLayoutHeader1UnitButton2 {
}
3 = PlexusLayoutHeader1UnitButton3 {
}
4 = PlexusLayoutHeader1UnitButton4 {
}
5 = PlexusLayoutHeader1UnitButton5 {
}
6 = PlexusLayoutHeader1UnitButton6 {
}
7 = PlexusLayoutHeader1UnitButton7 {
}

doadin · Answer 7 · 2024-10-26T10:00:06.000Z

@voozul @xaos-org
can you guys test v3.4.3, let me know how it works?

voozul · Answer 8 · 2024-10-26T11:38:58.000Z

HiYeah I rolled back to 3.4.3.I did gain fps but there are other factors in play so I can’t say for sure it was the roll back.My guild had been doing queen hc 25 man and after upgrading my cpu to 5700x3d I got 12 fps with graphics on 1 which I found unplayable. I was ready to chuck my pc out of the window so I rolled back plexus and tried to find 25 man queen pugs to test but there were none (only smaller groups).We went on 23 man this week in guild and the lowest fps I got was like 22 so gained a solid 10 on the worst bits fps wise of the fightOn 20 man queen pug I had 40fps so could just be some awful group scaling issue on blizz end.I also heard some big addon devs had been digging into the fps issue in raid and found that blizz has some check/call on group to check ppl entering and leaving group and blizz was calling this way more than it should which in turn made addons that use that call and it was tanking fps getting worse with group size.Sorry I can’t be of more help im not very technical. Just glad the raid is semi playable again I hope some of the above info helps!I love plexus! <3Sent from my iPhoneOn 26 Oct 2024, at 11:00, doadin ***@***.***> wrote: @voozul @xaos-org can you guys test v3.4.3, let me know how it works? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

Adardrae · Answer 9 · 2024-10-26T19:24:28.000Z

I'm having issues with plexus dragging my framerate way down as well. Joining groups from premade group finder for world bosses drops my FPS by a signficant amount. Disabled PlexusAutoFrame size and issue persisted. Disabled all plugins. It seems that people joining and leaving causes a significant stutter and people joining and leaving quickly tends to bog the game down.

I'm playing on ultrawide 7680x2160 with an RTX4080 and modern CPU, and generally stay above 60 FPS, but plexus brings me down to 5-10.

doadin · Answer 10 · 2024-10-26T19:37:38.000Z

The only significant change since v3.3.5 was private auras, can you maybe try disableing them in plexus settings and test?

doadin · Answer 11 · 2024-10-26T19:38:15.000Z

I am trying to narrow it down but im not sure yet which module/status the fps drop is coming from.

Adardrae · Answer 12 · 2024-10-27T17:17:45.000Z

I tested it again today and after trying alternative grid2, i'm not sure the issue is related to plexus. As with most WoW FPS issues i'm having a hard time figuring out exactly what the deal is, but i'll explain what I did and give you the information I have and let it be a data point for you. I did azuregos twice more today and recorded a vod. The first time is disabling plexus completely and running grid2 for unit frames. It seems on average to perform worse than plexus, but the group size might have been a factor. There are too many variables for me to tell for sure. With plexus (with no plugins, and private auras disabled) it seems that I had a higher average framerate, so maybe it's one of the plugins I had installed (plexusautogroupsize, plexussmoothhealth, plexusstatusdungeondebuff, plexusstatusraiddebuff). I would say I did still notice a stutter when people would join and leave, but not always. Maybe it was during combat. Anyway, sorry my troubleshooting isn't more helpful, but I'll provide the vod for you to review if you want. https://youtube.com/live/7IbStnt87PE?feature=share

…

On Sat, Oct 26, 2024 at 2:38 PM doadin ***@***.***> wrote: I am trying to narrow it down but im not sure yet which module/status the fps drop is coming from. — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMOJEVJV7JZTIV2A7LXXYODZ5PVT3AVCNFSM6AAAAABPC6OWSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZG4YTINZSGY> . You are receiving this because you commented.Message ID: ***@***.***>

xaos-org · Answer 13 · 2024-10-27T19:46:36.000Z

<3Sent from my iPhoneOn 26 Oct 2024, at 11:00, doadin @.> wrote: @voozul @xaos-org can you guys test v3.4.3, let me know how it works? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

i tried it in a theater lfg raid group that was 100% full. in the past, just joining this -- and throughout the event -- i would basically be at single-digit fps. with this latest version, i barely noticed any issues. i will try it in our "real raid" tuesday evening and report back. [i had also re-enabled the two companion addons, PSraiddebuff and PSdungeondebuff]

[edit: i also have private auras disabled, from earlier in my troubleshooting. i'll try to remember to re-enable that for science on tuesday night too]

voozul · Answer 14 · 2024-10-27T20:00:59.000Z

sorry i am in the middle of a big house move, unlikely to be able to test soon

…

On Sun, 27 Oct 2024 at 19:46, xaos-org ***@***.***> wrote: <3Sent from my iPhoneOn 26 Oct 2024, at 11:00, doadin *@*.*> wrote: @voozul <https://github.com/voozul> @xaos-org <https://github.com/xaos-org> can you guys test v3.4.3, let me know how it works? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.*> i tried it in a theater lfg raid group that was 100% full. in the past, just joining this -- and throughout the event -- i would basically be at single-digit fps. with this latest version, i barely noticed any issues. i will try it in our "real raid" tuesday evening and report back. [i had also re-enabled the two companion addons, PSraiddebuff and PSdungeondebuff] — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4NH7E3NYJPKO5VAGKCP3DZ5U7LFAVCNFSM6AAAAABPC6OWSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGE2TEMBZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

doadin · Answer 15 · 2024-10-27T20:52:32.000Z

with all built-in statuses seperated out sems like the core still has high usage, I wonder if its the function that recieves the status from statuses/modules or something else.

xaos-org · Answer 16 · 2024-10-30T02:15:40.000Z

for me, in a 30-person raid at nerub-ar tonight, it was significantly better than it had been. i didn't remember to re-enable private auras until just now, so i was running without it enabled still sorry. i had PSRaidDebuff enabled.

Share to