Pixelation

[Savage]

I run five WoWs on the same PC / Monitor. Sometimes when I start up the five windows, a few of them are very pixelated - You can tell mostly from the text. Comparing from the ones that arent like that, you can defenitely see a difference. When I close those windows and re open them via Keyclone, most of the time they're normal again! Anyone have any idea?

I took a picture here, maybe you guys can see what im talking about now.

http://i80.photobucket.com/albums/j187/thesavagetony/Untitled-2.jpg

Obviously, the top window is 1, then 2 3 4 5 on the bottom. Number 3 is the one, right now, that is "Pixelated"

[Savage]

Bumpity Boo to the top :D

[keyclone]

Heya Tony,

what are the exact sizes and positions of each region?
ie:
region1: ( 0,512 ) ( 640, 512 )

[Savage]

Region | X,Y | W,H
---------------------------------
Region 1 | 480,0 | 960,800
Region 2 | 0,800 | 480,400
Region 3 | 480,800 | 480,400
Region 4 | 960,800 | 480,400
Region 5 | 1440,800 | 480,400

[keyclone]

hmph... i was hoping for an odd boundary or one that was not on a multiple of 4 (byte alignment... you never know)

for grins, try this. get them into their starting position... where region3 is fuzzy... then go into keyclone/setup/maximizer .. left click region3 and add 1 to the x position (ie: 480,800 change to 481,800 or maybe 482,800).. then hit ok and see if that affects the fuzzy factor

[Savage]

Sorry that took so long - I did that and nothing :( It really isnt a big deal, I always just close that window and relaunch it from Keyclone.

[RadicalPi]

I'm not sure if it might help you to have a bit more data on the problem, but here's my setup.

Region | X,Y | W,H
---------------------------------
Region 1 | 320,256 | 640,512
Region 2 | 0,0 | 480,384
Region 3 | 5,605 | 480,383
Region 4 | 800,0 | 479,384
Region 5 | 801,605 | 479,383

I know there's a couple of non-divisible by 4 coords in there, but it was happening before I shifted those 2 windows. It's only Region 1 that messes up for me.

[Ifalna]

It happens with hotkey.nets maximiser too, something to do with resolution of the actual clients.

If you maximise them, then restore them to normal size, it instantly fixes it. Never noticed any kind of pattern in what client it affects, but only ever happens to me after I launch and size the windows for the first time.