June 23, 201213 yr Has anyone came across a good explanation on understanding the parameters of the panel.cfg file. Having gone to a widescreen Nvidia surround display across 3 23" monitors, I have been forced to edit my panel config files to avoid the 2D panel "bug" than plagues these types of configurations. (http://www.wsgf.org/forum/11008/problem-triplehead2go-and-fsx-2d-view?page=2) Although this helped to some extent in resolving the most detrimental aspect of the bug, flashing active cursor with dramatically reduced framerate effect, 2D panels are still inconvenient to use. Although I do prefer the VC cockpit, I do depend on 2D specific panels for some options, not to mention some of my older aircraft don't even have virtual cockpits. Some of the challenges I have with the 2D panels are, i) showing up off screen, requiring window minimization to find it ii) grotesquely sized panels requiring manual resizing. I am grateful I can do that, it's just simply an annoyance. I've searched and came up with no real clear explanation. Microsoft has provided documentation in it's SDK documents, but well ... yeah ... not an easy read. Trial and error of panel.cfg parameters is agonizingly slow, and there are so many different paramaters, it's hard to say how combinations of changes will affect the overall impact. Can anyone explain the which parameters are used that determine where a window is placed on a display, and it's size. Their is the "position" and "window_pos" parameters. What are their differences? Does one provide something the other doesn't? Are they dependent on each other? When it comes to size, their is the "size_mm" parameter, the "window_size" parameter and the "window_size_ratio" parameter. Similarly, how do these differ? Are they independent of each other? With one, in not the combination, would allow me to default the preferred size on my display when they are opened? Sorry for all the questions, but I find it an complicated topic for a relatively basic concept? RM Killins
June 23, 201213 yr Have you looked at Flightline gauges? I don't know if they would solve your problems, but maybe. They also have DL manuals for modifying the config files. http://www.reality-xp.com/flightsim/flt/features/index.html
June 23, 201213 yr I guess you will find a comprehensive set of explanations here, right from the devs of FSX. This should help with all the size and position matters. http://msdn.microsof...y/cc526956.aspx
June 23, 201213 yr Author Hi folks, thanks for your comments. Toedv, I checked out your suggestion. My issues aren't so much with the actual gauges or the panels, but more with the windows that host them. Again, they are all related to each other, but the question is how. CoolP ... yes ... as mentioned in my initial post ("Microsoft has provided documentation in it's SDK documents, but well ... yeah ... not an easy read."), I have reviewed that many times and attempted to deciphre it. Using that as a basis, I tried to do some trial and error experiments but they were disasterous. Again ... I think the different parameters have some relationship to each other, and simply changing one and not the other perhaps, doesn't net good results. RM Killins
June 23, 201213 yr I have to apologize to you, I was obviously missing the line where it says that you've already looked at the SDK docs. Well, perhaps there's a Wiki out there, giving more examples and descriptions. FSDeveloper maybe?
June 23, 201213 yr Can anyone explain the which parameters are used that determine where a window is placed on a display, and it's size. Their is the "position" and "window_pos" parameters. What are their differences? Does one provide something the other doesn't? Are they dependent on each other? 'Position=' is a fixed position relative to the main window (ie [window00]) from 0 to 8. 1 being the upper left corner of the main panel, 8 being the lower right corner. 'Window_pos' is a x,y location relative to the upper left corner of the main window in percentage. Example: window_pos=0.50, 0.75,0.25,0.25 This means from the upper left corner, left 50% of the main window, down 75% of the main window. Width 25% of the main window, height, 25% of the main window. note: this position is the upper left corner of your new window. you cannot use both position, and window_pos. the window_pos setting will override any position setting. When it comes to size, their is the "size_mm" parameter, the "window_size" parameter and the "window_size_ratio" parameter. Similarly, how do these differ? Are they independent of each other? With one, in not the combination, would allow me to default the preferred size on my display when they are opened? Sorry for all the questions, but I find it an complicated topic for a relatively basic concept? 'size_mm' is the size of the window in pixels. 'window_size' is a percentage of your display screen. example: window_size=1.00 - is 100% of the screen. window_size=0.50 - is 50% or half of the screen. An fairly easy way to set the size of your window is to set the window position and sizes you desire, then save the the flight. The window positions, and sizes are saved in the .FLT file. You can use that info to then permanently set the position and sizes exactly in your panel.cfg Example: .FLT file [Panel.1] ScreenUniCoords=0, 0, 8192, 6144 .. Panel.1 equates to [Window00] in the panel.cfg file. [Panel.6] ScreenUniCoords=81, 2027, 2375, 4018 ID=5004 ... Panel.6 equates to [Window05] in the panel.cfg file, ID= equates to the 'ident=' param in the panel.cfg file. divide the panel.6 coordinates into the panel.1 coordinates to get the window_pos, and window_size values. Window_pos is the first 2 parameters and window_size the last two. Example: window_pos = 81 / 8192 = 0.010 2027 / 6144 = 0.330 window_size= 2375 / 8192 = 0.290 4018 / 6144 = 0.654 window_pos=0.010, 0.330 window_size=0.290,0.654 An even easier way to do all this is with FSPanel Studio. It has a visual drag and drop interface for easy panel editing. Regards. Ernie.
June 23, 201213 yr The SDK docs describe it in detail - you just have to read it carefully. The Position parameter gets overridden by the Window_pos parameter if it is present. Bert
June 24, 201213 yr Author Thank you Ernie for taking the time to provide an understandable and relevant reply. It was most helpful. What is the pu Bert, yes ... the SDK is a thorough document, I never said it wasn't. If I fully understood the explanations as they related to complexities of the panel.cfg file, I wouldn't have wasted my time posting here. For those with a good understanding of development and programming, this is likely easily understndstoood. Some, just need layman's explanation to be able to digest it. I find things aren't as straight forward when your working with a resolution of 6053x1080. FSX in most part was not developed, and as such it's documentation, for such panoramic resolutions. The use of "window" and "panel" can be easily misunderstood, and there is a vital relationship between secondary panels and the "main" panel, which may or may not play a role in the desired outcome. RM Killins
July 2, 201213 yr Author Hi Ernie, I've been tinkering around with your suggestion on maintaining window sizes and positions, but haven't been having much success. Despite following the instructions you gave, my adjusted panels still are not sized or positioned the way I orginally saved them in my .flt. An fairly easy way to set the size of your window is to set the window position and sizes you desire, then save the the flight. The window positions, and sizes are saved in the .FLT file. You can use that info to then permanently set the position and sizes exactly in your panel.cfg Example: .FLT file [Panel.1] ScreenUniCoords=0, 0, 8192, 6144 .. Panel.1 equates to [Window00] in the panel.cfg file. [Panel.6] ScreenUniCoords=81, 2027, 2375, 4018 ID=5004 ... From my saved flight file, here are the first two panel entries for a DA Fokker 100. [Panel.1] ScreenUniCoords=0, 0, 2727, 6144 UndocCoords=0, 0, 0, 0 Visible=False Undocked=False HiddenOn=False ID=0 ViewsOn=0 [Panel.2] ScreenUniCoords=7389, 213, 677, 2985 UndocCoords=5421, 78, 516, 958 Visible=False Undocked=False HiddenOn=False ID=5051 ViewsOn=0 Example: window_pos = 81 / 8192 = 0.010 2027 / 6144 = 0.330 window_size= 2375 / 8192 = 0.290 4018 / 6144 = 0.654 window_pos=0.010, 0.330 window_size=0.290,0.654 In my case, to reposition window01 (panel.2) - in panel.cfg , 7389 / 2727 = 2.709 213 / 6144 = 0.0346 and to resize it ... 677 / 2727 = 0.248 2985 / 6144 = 0.485 windows_pos = 2.709 , 0.0346 windows_size = 0.248 , 0.485 So ... here are my panel.cfg entries for windows 00 (main) and 01 (radio stack), [Window00] file=MM_F70100_MPNL.bmp size_mm=1280 window_size_ratio=1.000 position=0 visible=1 //no_luminous=1 ident=MAIN_PANEL window_size= 0.333, 1.000 //window_pos= 0.000, 0.000 zorder=0 [Window01] //Radio Stack file=MM_F70100_RDST.bmp size_mm=221,645 windows_pos=2.709,0.0346 windows_size=0.248,0.485 //window_size= 0.333, 1.000 //position=0 visible=0 ident=5051 zorder=1 This results in a bloated window01, centred in the bottom centre of the centre monitor. I had resized and repositioned it to provide better resolution (shrunk it) and placed it in the centre of my right monitor. Any obvious errors? Suggestions for improvements? RM Killins
July 4, 201213 yr An fairly easy way to set the size of your window is to set the window position and sizes you desire, then save the the flight. The window positions, and sizes are saved in the .FLT file. You can use that info to then permanently set the position and sizes exactly in your panel.cfg <snip> Regards. Ernie. Wow!! Thanks Ernie. This is a great technique. It allowed me to set up my GPS, Autopilot, & Radio Stack popup gauges the exact size and placement I wanted. I have made a master text file and I copy & paste it into my favorite planes. Very useful suggestion. Obie311
July 9, 201213 yr windows_pos = 2.709 , 0.0346 windows_size = 0.248 , 0.485 So ... here are my panel.cfg entries for windows 00 (main) and 01 (radio stack), [Window00] file=MM_F70100_MPNL.bmp size_mm=1280 window_size_ratio=1.000 position=0 visible=1 //no_luminous=1 ident=MAIN_PANEL window_size= 0.333, 1.000 //window_pos= 0.000, 0.000 zorder=0 [Window01] //Radio Stack file=MM_F70100_RDST.bmp size_mm=221,645 windows_pos=2.709,0.0346 windows_size=0.248,0.485 //window_size= 0.333, 1.000 //position=0 visible=0 ident=5051 zorder=1 This results in a bloated window01, centred in the bottom centre of the centre monitor. I had resized and repositioned it to provide better resolution (shrunk it) and placed it in the centre of my right monitor. Any obvious errors? Suggestions for improvements? I think your flight saved the window as a docked window. A docked window can go beyond the boundaries of the panel. Try undocking the window and trying again. The window_pos should be no greater than 1.0. Regards. Ernie.
July 11, 201213 yr I think your flight saved the window as a docked window. A docked window can go beyond the boundaries of the panel. Try undocking the window and trying again. Hi and thanks for your suggestion. I do use undocked windows on a second monitor, is there a way to save undocked windows and positions too?
May 21, 201610 yr Im also running 5040x1050 in three monitors and want to add other 2d panels in another two monitors with independent resolutions.
Create an account or sign in to comment