Super Speed Windower…

Ok wow, no crashes tonight. However another weird bug popped up. When I login and get to the screen before your character select, (and the camera is panning through the landscape with the final fantasy title up) my camera is moving at 100 miles an hour. Then also on the character select screen, the idle animations are moving super fast. Then when I login, for a few seconds my in game characters animations (tail wagging ect) are going super fast. When I’m scrolling through the menu as well, it’s so fast. Then if I logout and try to log onto a mule, I get the server connection has timed out or something. If I try it again, it says the character is already logged in. The only thing I’ve done since getting this bug is installing dgvoodoo. Which seems to have stopped my crashing.

Anyone had this before? It’s annoying, I can’t switch between characters without logging off fully or just praying lol…

Sounds like your FPS are uncapped and you don't have any limiter in place

FrameRateDivisor is uncapped it sounds like

Do a find in files pointed at your windower folder directory using notepad++usually this is presented in

config
Fastcs

Having it uncapped is uncapped frame rate
You may have the settings file wrapped with individual characters rather than global

What should it be at, 60? How do I recap it ;o

If you used Windower Config, then you would want to type in the console window

config FrameRateDivisor 1

1 is for 60fps, 2 will give you 30fps, and 0 is uncapped. Below is a link to the support page with way more detail.

Link to Windower Confit support

This just happened to me when I changed to Secure Boot for the BF6 beta. It unlocked my framerate for FFXI for some reason. I was able to use config to put it back to 30.

How did you do that?

I entered the command in game to set the rate to 1 as Drayco suggested. But when I returned to the character select screen it was sped up again.

You can set an upper limit in Nvidia Control Panel, Select POL and set it to whatever you're most comfortable with.
I have it set to 180 as otherwise it goes to 500fps on my PC and starts bugging out.

Manage 3D Settings -> Program Settings -> POL -> Max Frame Rate

Ok, got it sorted. Opened the config.xml for config. For some reason global was set on 0 for uncapped. Which is strange, because it's was fine yesterday. So somehow it got switched to upcapped. No idea how.
But a super thank you to everyone that chimed in, I wouldn't have known what to do without ur guys help.

Thank you, Thorny, Jinxs, Drayco, Hamburgerz, Noscrying.

Much appreciated.

I can finally go to bed now...4am, couldn't get it off my mind lol, now I know it's fixed I'll grab a couple hours zzz :D

if you use fastcs, make an alias or bind to toggle it on/off. you'll need it.

Yeah it's probably going to come back after the first interaction
It's also listed in fastcs

FrameRateDivisor
Is how it appears in both settings xml

If you utilize the findinfiles feature of notepad++
You can track down these issues and more pretty quickly

Now when FrameRateDivisor is undefined or set to 0 on global this happens

The settings file for both can be pointed at either global or per character
the great thing about findinfiles is it will bring up all of them for easy access c:/windower/

dangit, I really was hoping for a good Duck recipe.

Hey Jinxs, thanks for the info. I don’t know how to use that feature of notepad++ but I’ll look into it.

On a side note is there any reason to keep the guildwork plugin? Will removing it free up any resources ect?

Cheers!

It's right next to the standard find from control F

I hope people don't stop using the guild work plugin as unreliable as it might be sometimes I don't think it has a meaningful performance impact

You can see how much memory things are using via lua m in the console if you have a lot it will print more than you can see
You will need to use console_log 1 and 0 on and off to get it to print to a file.

Things that do make the game slow down typically occur after log periods of reading and writing tables and can be solved with an unload and reload of the addon(s)

But it's how we get bazaar data, I do a lot of my shopping via this sourced bazaar data