to move the default FPS counter frame. I use a variety of add-ons and have a pretty custom UI. Currently my bar add-on is over the FPS counter. I've tried moving it with "MoveAnything" but the frame is not listed.
The "FPS:" is named FramerateLabel and the actual fps number is FramerateText. They're not actual frames (they're FontStrings), so I'm not sure MoveAnything can move them.
If you don't mind dedicating a macro you can macro this to toggle the fps meter:
/run FramerateLabel:ClearAllPoints() FramerateText:ClearAllPoints() FramerateLabel:SetPoint("RIGHT",UIParent,"CENTER",-200,0) FramerateText:SetPoint("LEFT",FramerateLabel,"RIGHT") ToggleFramerate()
Change -200,0 to the x,y coordinates you want to display the fps meter, relative to the center of the screen.
A negative x value goes left from center.
A negative y value goes down from center.
If you don't mind dedicating a macro you can macro this to toggle the fps meter:
/run FramerateLabel:ClearAllPoints() FramerateText:ClearAllPoints() FramerateLabel:SetPoint("RIGHT",UIParent,"CENTER",-200,0) FramerateText:SetPoint("LEFT",FramerateLabel,"RIGHT") ToggleFramerate()
Change -200,0 to the x,y coordinates you want to display the fps meter, relative to the center of the screen.
A negative x value goes left from center.
A negative y value goes down from center.
2 Likes
Thanks for this, just wanted to confirm this works, my UI is pretty tightly put together as well and I thought there was no way to move this. You do want it on a macro though because I don't believe it saves it's place, even if you just reload your UI.
FYI the coordinates I ended up using were:
/run FramerateLabel:ClearAllPoints() FramerateText:ClearAllPoints() FramerateLabel:SetPoint("RIGHT",UIParent,"CENTER",-630,-375) FramerateText:SetPoint("LEFT",FramerateLabel,"RIGHT") ToggleFramerate()
which puts it right in the lower left corner of my screen.
FYI the coordinates I ended up using were:
/run FramerateLabel:ClearAllPoints() FramerateText:ClearAllPoints() FramerateLabel:SetPoint("RIGHT",UIParent,"CENTER",-630,-375) FramerateText:SetPoint("LEFT",FramerateLabel,"RIGHT") ToggleFramerate()
which puts it right in the lower left corner of my screen.
1 Like
Thank you Checkers and also the person who suggested it. (I used your macro numbers works fine on my screen!)
thanks worked great!
Moveanything.. type framerate that should let you move it
Yes, Teresa, and I'm certain they've been waiting four years for you to answer them.
Please don't necro post.
I know, Google. . . .
Google isn't an AI, it's a search engine.
It isn't aware of the Forum Posting Guidelines.
https://us.battle.net/forums/en/wow/topic/20752671773
You're supposed to be.
Please don't necro post.
I know, Google. . . .
Google isn't an AI, it's a search engine.
It isn't aware of the Forum Posting Guidelines.
https://us.battle.net/forums/en/wow/topic/20752671773
You're supposed to be.
well, after 4 years it's the top google search for "how to move fps in wow" and i merely needed to know what it was called in move anything, because "Frame" returns just about everything.
so this was immensely useful, even if it was necro'd :)
be less toxic pls
so this was immensely useful, even if it was necro'd :)
be less toxic pls
To repeat, Google isn't an AI, it's a search engine.
Google isn't aware of the posting guidelines.
Posters here are supposed to be.
There's nothing toxic about pointing that out.
The guidelines (see the link I provided above) aren't really "optional" so much as "the rules of this community" and particularly on this forum, necros are a bad, bad idea.
The UI and API changes with such frequency that I've seen Blue posts in this forum advising that any post over a month old is pushing necro territory.
Me, personally, that's a little more extreme than I'd use for a threshold, but a six year old thread last meaningfully replied to four years ago? There is just no reasonable reason to post a "helpful" reply to something like that.
If you have something to contribute, start a new thread.
Google isn't aware of the posting guidelines.
Posters here are supposed to be.
There's nothing toxic about pointing that out.
The guidelines (see the link I provided above) aren't really "optional" so much as "the rules of this community" and particularly on this forum, necros are a bad, bad idea.
The UI and API changes with such frequency that I've seen Blue posts in this forum advising that any post over a month old is pushing necro territory.
Me, personally, that's a little more extreme than I'd use for a threshold, but a six year old thread last meaningfully replied to four years ago? There is just no reasonable reason to post a "helpful" reply to something like that.
If you have something to contribute, start a new thread.
Good meme 10/10
04/12/2018 09:27 PMPosted by EhiztariTo repeat, Google isn't an AI, it's a search engine.
Google isn't aware of the posting guidelines.
Posters here are supposed to be.
There's nothing toxic about pointing that out.
The guidelines (see the link I provided above) aren't really "optional" so much as "the rules of this community" and particularly on this forum, necros are a bad, bad idea.
The UI and API changes with such frequency that I've seen Blue posts in this forum advising that any post over a month old is pushing necro territory.
Me, personally, that's a little more extreme than I'd use for a threshold, but a six year old thread last meaningfully replied to four years ago? There is just no reasonable reason to post a "helpful" reply to something like that.
If you have something to contribute, start a new thread.
This actually helped me today, October 7th 2018.
So, actually, you're wrong, kid.
So, actually, you're wrong, kid.
It isn't a question of whether or not it helped you.10/07/2018 06:09 AMPosted by StealthThis actually helped me today, October 7th 2018.
So, actually, you're wrong, kid.
And it's entirely possible to read a forum post without replying to it.
Do not pollute the forum by necroing old posts. Period.
Thanks for the info. 10/10
big help
big help. Thanks for the resurrection.
Thanks for this. I realize this is old as hell, but it worked perfectly.