99% of the time, this is easy: I've done it hundreds of times. I set the following options for the window in question in the panel cfg:

 

window_size=
window_pos=

 

and the window sits exactly where I want it.  Just a few windows (e.g. a couple in the Project Tupolev Tu154M) refuse to 'behave' however, as if they are set to snap to a grid (??). I keep changing size and position and nothing happens, until one particular minute change, when the window moves a couple of dozen pixels.

 

For instance, from this

 

window_size=0.123, 0.234
window_pos=0.345, 456

 

to this:

 

window_size=0.123, 0.234
window_pos=0.345, 476

 

makes no difference to where the window sits in the a/c. But change to this:

 

window_size=0.123, 0.234
window_pos=0.345, 477

 

and the window jumps down the screen by a centimetre or so.

 

Does this make any sense to anyone? How to fix it?

Thanks,

 

Martin

window_pos entries are valid only in the range from 0.0 to 1.0

 

They are not "absolute values" but rather "percentage values."

Overrides the position and windowsize_ratio variables. Provide at least an x value, the y value is optional. 

Yes, thanks, I know that. I calculate the values as percentage of the full window size. 

Yes, thanks, I know that. I calculate the values as percentage of the full window size. 

The entries in your OP show no decimal points for the 'y' values.

From this:

window_pos=0.345, 456

 

To this:

window_pos=0.345, 0.456

That's my typo here! Sorry. They are in the correct format in the cfg file.

I use FS Panel Studio just so that I don't have to concern myself with trying to calculate parameter values, much less try to make any sense out of 'em! :LMAO:

I have Panel Studio, but it takes me less than a minute to calculate the parameters myself, so that's not really a problem

Fair enough, but just out of curiosity, just how many minutes has it taken to solve this one value? :Just Kidding:

:rolleyes:   This is rare: 99% of the time windows sit where you place them; these two won't (though all the other windows in the 2D panel do). Yes, I should try Panel Studio on this one...

OK, I knew there had to be an 'external' reason why this wasn't working!! I have just found that the aircraft has a line in an ini file (gauge folder)...

 

panel_auto=1

 

set this to ..

 

panel_auto=0

 

and the windows behave normally!

 

Martin

OK, I knew there had to be an 'external' reason why this wasn't working!! I have just found that the aircraft has a line in an ini file (gauge folder)...

 

panel_auto=1

Odd... There must be something within the gauge itself that makes use of that setting, as it is not documented at all in the SDK.

Aircraft don't use .ini files unless they're third-party.

Yes, this is of course a third party aircraft - it's the Project Tupolev Tu154M. Pretty complex machine. The cfg entry is to help save and reload the panel states (not that it works all that well).