using maximizer through keyclone my main loads fine with a widescreen resoltion on the left side of my spanned desktop... but my clones are loading with a 3:4 res and then being streched to 16:9 x4 on the right half
any thoughts?
Printable View
using maximizer through keyclone my main loads fine with a widescreen resoltion on the left side of my spanned desktop... but my clones are loading with a 3:4 res and then being streched to 16:9 x4 on the right half
any thoughts?
are you trying this on 1 monitor or 2?
2 monitors, spanned... I have no problems with just using a bat file and loading the copies up with maximizer, but using them automatically with keyclone has this issue
you will need to set their width to height ratio to be the same as your main area.
so, if your main is 1600x1200... then make your alts 800x600 .. same ratio
makes sense?
I'm pretty sure I'm reading that clearly... but in the gui for maximizer in the setup options I have everything divided up evenly... my desktop is 2880 x 900 and I have the 4 extra windows at 720x450 and the main at 1440x900... I noticed keyclone was adjusting the resolutions by 1 or 2 pixels like 721 x 449 so I just cleaned up the numbers so so there was no overlapping but the problem persists
Before running each instance of WoW, Keyclone modifies each config.wtf to set the WoW client window size to the same size as the maximizer region it will reside in.
But, if config.wtf contains a window size smaller than 800 horizontally or 600 vertically, WoW will reject this and default back to 800x600 when the game runs. 720x450 in config.wtf isn't allowed.
What you need is some way to prevent Keyclone from modifying your config.wtf files, perhaps make them read-only, and manually set them to 1440x900 yourself. When the windows get resized, they'll retain the correct aspect.
I don't know how keyclone will handle being unable to write to the config.wtf files.
@Bravo
very odd. i was running 1280x1024 x 2 in horizontal span last night.. my main full screen @ 1280x1024 and my alts were in a 2x2 on the right screen... 640x512 each. my fps wasn't great, but i attribute this to my single core 2.2GHz AMD (was only able to do maxfpsbk of 10, maxfps 20)
the pip swap was taking time.. 2-4 seconds... again, i attribute this to my single core as wow tries to reset its graphics engine (keyclone is only moving a window.. there isn't much to do otherwise)
if you can drop me a screenshot, maybe that'd help
Rob, I'm seeing this same behavior on mine...Quote:
Originally Posted by 'keyclone',index.php?page=Thread&postID=56339#post 56339
I run one copy at 1680x1050 and the other 4 at a much smaller size that matches the 1.6:1 ratio. The smaller windows load skewed.
Two possible solutions I can see...
A: If keyclone is asked to launch a window smaller than 800x600, it calculates the ratio and resizes to be LARGER than 800x600, puts that data int eh config.wtf, launches WOW then resizes it.
B: Allow the user to set a "Master zone size"... this would be particularly useful for people using PIP. I honestly don't care if the aspect ratio looks good on the 1/4th size windows, I care however that it looks good on the 1680x1050 window for when I take control. If you let each command have a master size, the user could set that to match their biggest window, put that value in the config.wtf and then resize to the region it's scoped to. Even if the window loses aspect ratio in the resize, once you PIP it to your primary region it's back to normal.
hmmm
So can we look for a solution tot he sub 800x600 resolution issue? :)Quote:
Originally Posted by 'keyclone',index.php?page=Thread&postID=56427#post 56427
/grovel.
For some reason the script I used to open my copies with isn't working any more
REM batch file to launch 5 evenly spaced wows
REM Left monitor
c:\wow1\maximizer.exe --margin 0,0,0,1440
REM top of right monitor
c:\wow2\maximizer.exe --margin 0,450,1440,720
REM bottom of right monitor
c:\wow3\maximizer.exe --margin 450,0,1440,720
REM bottom right, right screen
c:\wow3\maximizer.exe --margin 450,0,2160,0
REM Top right, right screen
c:\wow3\maximizer.exe --margin 0,450,2160,0
I haven't been able to pin point the problem, but it has to be because I've switched over to using junctions to share data. I'm gonna troubleshoot this some more tonight, but I can only assume keyclone isn't the problem.
Ok ran into a bit of a snag which conflicts with my previous reasoning....
Maximizer script launching main + adds on 2 folders + junction = resolution issue on adds
Keyclone script launching Main + adds on 2 folders + junction = resolution issues on adds
Maximizer launching Main + adds from 1 folder = no resolution problems
Keyclone launching from 1 folder = resolution issues on adds
the problem with 'Maximizer launching Main + adds from 1 folder' is they share the same video properties, and I like to keep my main fairly high so I can keep things pretty, and my adds have low video propertys so everything runs fairly quickly . and the script that doesn't pose any problems right now loads everything at a high res because I'm using my main folder
*UPDATE*
in this thread there seems to be a solution to my script problem... if I go into config.wtf and set the resolution to 1440x900 and then launch my script there is NO resololution problems even though my adds are 720x 450 when I run 'Maximizer script launching main + adds on 2 folders' ... is it possible to get keyclone to use a higher resolution on the config file if a widescreen resolution is used?
@Ozbert I just re read and your last paragraph and you already had that solution, I think I may have skipped it the first time I read it though.
Blocking the config.wtf file will still have issues with the user name though which is a nice feature if your launching from 1 or 2 folders.
@Keyclone is it possible not to write gxResolution when modifying the Config.wtf or add a toggle to choose not to?
@Bravo
i have a solution to your issue in the upcoming release, v1.8h
you should be fairly happy with it then