I will try to keep tabs on when this happens to me as well. It happens a lot (to the point where I only turn on GW when I want something to update, or before I leave the house to go to work).
I have always run windower, that is the only constant in my data at the moment. My variables are use xi-util or no, dual box or no.
I can try it w/o windower and see if it makes a difference? I'll also post the data I find and see if I can't help pinpoint it.
I sent out an update last night which I believe might fix the problem.
As a side note do most of you notice the high CPU usage when POL/FFXI is open but a character is not logged in? Or does it persist even when POL/FFXI are fully turned off?
I have this problem from time to time as well but mine sits at ~45-50% CPU usage on a AMD Phenom II X2 560 (3.3 GHz). I do dual box at times but I'm not sure if this is the cause. I'll try to pinpoint the exact circumstances of the problem but it definitely causes major performance issues when playing.
Every person who this issue before has now confirmed that it is in fact fixed as of Feb 17, so if you have another issue I would appreciate more details.
That said we are working on porting Guildwork Client to a Windower plugin which should resolve these issues.
I logged my 2nd character in today with the main still running and GW running, as soon as the 2nd ffxi started up GW started using ~12% of my cpu and said it couldn't attach itself to it
Melanie replied
65 weeks ago