PDA

View Full Version : Weird Resolution problem with Maximizer



FunkStar
03-03-2008, 05:53 PM
When I set up my maximizer regions, things seem fine untill regions start overlapping.

This is exactly what I do in order:

name: 1
x,y: 0,0
w,h: 1920,1200

name: 2
x,y: 1920,0
w,h: 1920,1200

name: a
x,y: 1920,0
w,h: 960,600

// The next few are irrelevant, but might help understand my setup

name: b
x,y: 2880,0
w,h: 960,600

name: c
x,y: 1920,600
w,h: 960,600

name: d
x,y: 2880,600
w,h: 960,600


Now making region 1, and 2 works fine. I can start them up properly etc, no problem. To clarify, 1 is a fullscreen of my left screen, and 2 is a fullscreen of my right screen.

Anyhow, as soon as i add region a, which is 1/4th of my 2nd screen, and then I try to launch 1, my resolution will change to 1919x1199 (i found this in the WTF config file)
If I go back in the settings, and i remove region a again, the resolution will be the proper 1920x1200 again.
Now you'd say such a little difference is no biggy, true, but this change seems to clutter up all the text, making it look extremely fuzzy and ugly.

Is it known that overlapping is bad? or has it got nothing to do with that?

If i make region 1, a, b, c, d it works fine
if i make region 1 and 2 it works fine
but if i make region, 1,2, a,b,c,d it fucks up region 1 (region 2 still works fine with proper resolution, didnt test a,b,c,d)

keyclone
03-03-2008, 06:02 PM
no, overlapping shouldn't be a problem.

please PM me your keyclone.ini file (edit out user/account names please) and i'll check it out.

keyclone
03-04-2008, 02:07 PM
i think i see the issue. i believe i will have to add 1 to the dimensions i set within the gxResolution.

it's on the list

FunkStar
03-04-2008, 02:54 PM
if thats the issue, then how is it possible that if i only make:

1: left fullscreen
2: right fullscreen

it works fine? on the right resolution 1920x1200

keyclone
03-04-2008, 02:59 PM
because you are using multiple directories and i believe you are looking at the wrong config.wtf file
(i don't have the code here to look at.. but i believe it modifies the config.wtf in the directory specified in the command)

FunkStar
03-04-2008, 04:03 PM
Nope, both 1 and 2 are launched from the same folder
a,b,c,d are all launched from a 2nd folder (on other HD)

and its the folder on C (which holds 1 and 2) that has the wrong config resolution

and the problem is there even if i don't 'launch' a, i just have to add it in maximizer, and then '1' stops working on 1920x1200.

So to sum it up:

1 and 2 made, both launch from folder 1 on HD 1, both work fine
1, 2 and a made, i launch 1 (ONLY 1) and it already makes it 1919x1199. As soon as i remove region 'a' from maximizer 1 works again. Don't have to actually launch anything else than '1' to get the resolution 'bug'