PiP == trashed FPS on main - need restart to recover - any idea ?

yes, my main window / wow becomes super slow; when it is the main one, but I can run 3 or 4, including the main as a small at 30fps (my max) for some reason the main which was fine gets messed up - sometimes I was able to recover it by changing the video settings (but that makes it gone from keyclone list (maybe that's why it fixes it ?) and after that even if I add the window back it can't be maximized back into place...)


I didn't mean to say pip is setting the fps low; I meant to say that pip screws up my main wow after a few switches... I'll try to get more recent video drivers maybe that'll help

is there anyway way to get a debug or something version of keyclone to track down what's happening at that point ?

before the main gets messed up... how many wows are you running and what is the size and fps for each one? (hit ctrl+R to show the fps)

ie:
wow1 800x600 40 fps
wow2 400x300 10 fps
wow3 400x300 10 fps
wow4 400x300 10 fps

then... after a few pip swaps and the fps seems messed up... do the same

Sizes and geometry are above


I starts at 30 fps on main, 10 fps on slaves (or 9.9 and 29.9 sometimes)

After swapping often more than 1 windows is at 30 (I have to click in extra windows and click back on main window to back the small ones go down back to 10 fps)

Then suddenly the main one (original window) lags horribly and drops to a few fps - surprisingly though switching that "bad" window to one of the small one; I can get *both* to be 30fps with no lag - just can't get the original window on the original "big" space to work ok after that and need to restart every wow and keyclone

Note that I upgraded the nvidia drivers to the most recent one and that made the problem less frequent and less bad - I suspect somewhat the PiP swapping triggers some sort of memory leaks in the 3d drivers or the card itself maybe

keep swapping through all your windows. i find if it happens ill do a swap going down the list of my alts until i find the one that is running smoothly. then swap back to your main. This usually fixes the problem. If not. repeat.
but ive never actually had to restart keyclone or wow using this method.

sounds like the wow window doesn't realize that it is no longer active... and is trying to maintain the maxfps (30 fps). the solution would be to force the wow window to understand that it has lost focus, which is what you are doing if you start flipping the windows around.

for me, when i notice that... i mouse into and out of those windows while having 'focus follows mouse' enabled. by moving the mouse over the problematic window, keyclone pushes focus to that window... forcing it into the foreground. upon mousing out of the window and into another, keyclone pushed focus to the new window... and away from the problematic one. as that happens, wow normally recognizes that it lost focus and dials down to maxfpsbk (or 10 fps in this case)

oh... and no amount of pip swapping would result in 'memory leaks in the 3d drivers'. memory leaks are memory leaks, regardless of the position or size of the window... or the number of times its moved around... afaik, of course. :D

hmm....in all this time its happened i dont think ive ever tried just mousing into each window. ill have to give that a go next time.
Im always using focus follows mouse now as well, forcing each window by clicking on it is just annoying after a while.

yea, same here. it's the one feature, besides the maximizer, that helps the most to smooth out game play while multi-boxing (well, besides normal key passing, of course :D)

i am working on a fix for the mouse getting stuck outside a side window for next release (there is a hold up... but i'm working through it now)

As I said a few times already, I'm able to get back to correct background fps settings by clicking in each window; but that's not the same problem as my main window becoming corrupt fps wise (way below even the low fps, all choppy and laggy) (and again that same window when put in place of small one can run at maxfps again; and the slaves ones can also run at maxfps in place of the main; just the main in the main spot runs at crawling speed)

so to clarify...

You have 5 sessions on one monitor,

ONEBIG
2345

When you swap back and forth eventually ONEBIG gets screwed up if it's in it's original PIP slot but 2 3 4 or 5 work fine in that slot and ONEBIG's FPS is correct in background but NOT in foreground?

Quote:

---

Originally Posted by 'keyclone',index.php?page=Thread&postID=164321#pos t164321

i am working on a fix for the mouse getting stuck outside a side window for next release (there is a hold up... but i'm working through it now)

---

/bow ....if i donate again does this come out faster :P