Archived

This topic is now archived and is closed to further replies.

Bert Pieke

Fun with the default Cessna

Recommended Posts

If you like to occasionally fly the default Cessna, you may find it useful to re-arrange the minipanel gauges so that you can fly with the minipanel and still have your "sacred six" gauges in view.This gives you great frame rates since the rest of the panel does not have to be drawn and good situational awareness since the view out front is unobstructed.Here is what I added to the panel.cfg file... this is using the RXP gauges, but you can substitute whatever gauges you use. Also the window size is dimensioned for a 1680x1050 monitor which is what I use. If the gauges are not round, adjust the window_size line !{Window05}position=7size_mm=315,206 child_3d=1background_color=0,0,0window_size= 0.2813, 0.2942 // for 1680x1050 monitorno_luminous=1ident=MINIPANELgauge00=RXPFLT!Airspeed, 0,0,98,98gauge01=RXPFLT!Attitude, 104,0,98,98gauge02=RXPFLT!Altimeter, 206,0,98,98gauge03=RXPFLT!TurnCoordinator, 0,106,98,98gauge04=RXPFLT!Gyro, 104,106,98,98gauge05=RXPFLT!VerticalSpeed, 206,106,98,98Replace the { } brackets by square brackets and...Enjoy !

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Bert,Great info. One question...is there a "formula" for determining the values to adjust in the window_size line?I'm using a TripleHead2Go 3-wide monitor setup displaying at 3840 x 1024. Mini-panels have always been a problem at this resolution across the 3 monitors...most of the guages aren't anywhere near round. If you have a "ballpark" figure that I could use to start adjusting (or a formula that would work), I would much appreciate it.Rick

Share this post


Link to post
Share on other sites

Rick, I work it out with a calculator...The window_size parameters are the portion of the overall screen that you want the minipanel window to occupy.Example: 0.5 , 0.333 means one half of the screen in the horizontal direction and one third of the screen in the vertical direction.FSX is based on a standard screen resolution of 1024x768, aka 4 : 3.So, if your screen is 3840x1024... that means your screen is 3.75 x wider and 1.33 x taller than the standard FSX screen. 3.75 / 1.33 = 2.82 is the factor by which FSX will stretch your gauges horizontally.In my example, my screen is 1680x1050, aka as 16 : 9.1.64 x wider and 1.37 x taller that the FSX standard.FSX stretches my gauges by a factor of 1.20.For you to use my example in the original post, you should divide the first window_size parameter by 2.36. (2.82 / 1.20 = 2.36)So: 0.2813 becomes 0.119 and the line would bewindow_size= 0.119, 0.2942Another way of coming at it, is to look at the size_mm definition. Lets use the original FSX Cessna panel as an example.The size_mm=631,100 line means that this window is meant to be 631 pixels wide and 100 pixels tall on a standard 1024x768 screen.This gives you the well known Minipanel look where the gauges take up over half the width of the screen.If you want the same hight on your screen, you would take 100/768which is 0.130 as the window_size hight.For the width, you would take the adjusted 631/1024/2.82 which is 0.219.So for the standard Minipanel to look right, you would add a line to the panel.cfgwindow_size=0.291 , 0.130Hopefully I did my math right...Try it and see if it works !

Share this post


Link to post
Share on other sites

Bert,Thanks! I just tried it with the default C172 and it worked great!. I never knew you could manipulate the minipanel sizes this way, and I've been cussing out all minipanel views ever since I started using the TripleHead2Go. I'd usually just cycle the "W" key to get rid of the gauges and enjoy the view, then cycle back to the VC for "gauge info" when I needed it. Your info above just raised my flight simming experience a magnitude.Gotta go to work in a bit, but gonna be making a bunch of changes to all my panel.cfg files when I get home in the morning!Even us veteran simmers can learn something new here because of posts like yours. Thanks again for taking the time to expalin it all!Rick

Share this post


Link to post
Share on other sites

Hey Bert,I hope you are still around. I got frisky and downloaded a new minipanel file from the library (new_min_pan_80_5.zip). I tried using your math tutorial above, but something isn't working correctly (most likely my ol' brain!).When I installed the file with no math conversions, it spreads out over my entire 3840 x 1024 resolution as expected. When I apply the math conversion, it then appears as a small, elongated strip of guages at the top left of my 3 monitor setup. The width seems OK (stretches across the length of the top left monitor), but the height is very compacted...totally unreadable.There are "other settings" in the included copy/paste (that goes in the panel.cfg file) in the file's readme installation file. A window_size_ratio=1.000, and a couple others that aren't referenced in your tutorial above. I'm pretty sure these have something to do with my results, but I've tried numerous combinations ranging from changing those values, to just deleting them also. No go...I'm stuck on what to do to get this minipanel to display correctly (centered on the bottom of my middle monitor and stretching across that monitor only) on my 3840 x 1024 monitor setup.I've included a copy/paste below of the minipanel {WindowXX} entry included with the installation instructions that goes into the panel.cfg file. Can you help me sort this out? Thanks for any assistance!NOTE: "Brackets" changed here only so they will show up in this post.FalconAF --------------------------{Window06} // ---alter the number to the right one ---Background_color=0,0,0 size_mm=1024,768window_size_ratio=1.000 position=7visible=1ident=MiniPanelwindow_size= 1.000, 1.000window_pos= 0.000, 0.000child_3d=1gauge00=f4u1a_corsair!Icon_Map, 40,702,22,22gauge01=cessna182s!Autopilot_Switch, 10,673,22,22gauge02=SimIcons!Avionics Icon, 40,673,22,22gauge03=SimIcons!GPS Icon, 10,643,22,22gauge04=SimIcons!ECU Icon, 40,643,22,22gauge05=kingair!Land_Light, 866,647,30,30gauge06=kingair!Taxi_Light, 866,682,30,30gauge07=737-400!Airspeed, 68,655,110,97gauge08=737-400!Altimeter, 301,684,110,73gauge09=bell_206b!HSI, 416,657,110,95gauge10=CONCORDE!Engine1-Ignition-Switch, 965,686,20,38gauge11=CONCORDE!Engine2-Ignition-Switch, 991,686,20,38gauge12=CONCORDE!Autothrottle-Switch, 864,716,35,52gauge13=mooney_bravo!Attitude, 184,687,110,67gauge14=kingair!Vsi, 533, 644 ,110,109gauge15=Z_AB320KM!Autopilot Approach Switch, 10,730,22,22gauge16=airbus.mgear_320!Chronometer, 649,644,110,110gauge17=737-400!Gear Lever, 908,686,52,81gauge18=SimIcons1024!Kneeboard Icon, 40,730,22,22gauge19=RCB_Groundhandling5!Taxispeed, 905,646,60,38gauge20=RCB_Groundhandling5!Brakes, 964,646,48,38gauge21=CONCORDE!Engine3-Ignition-Switch, 965,729,20,38gauge22=CONCORDE!Engine4-Ignition-Switch, 991,729,20,38gauge23=737-400!Pitch Trim, 763,645,34,110gauge24=cpt.toggles.lear!NAV-GPS, 10,702,22,22gauge25=boeing737-71!Flap Gauge, 803,645,53,109gauge26=Mooney_Bravo!Altitude Alerter, 301,643,110,43gauge27=737-400!Nav 1, 184,643,110,30gauge28=737-400!Audio, 184,674,110,13gauge29=Boeing747-400!Autopilot Heading Window, 420,640,110,21gauge30=Boeing747-400!Autopilot IAS-Mach Window, 73,638,110,21------------------------------------------------------------

Share this post


Link to post
Share on other sites

Well... one step at a time...Window_pos overrides position =so put two slashes in front of the window_pos line.That should move the gauges to the bottom center.Let me know from there.. :-)

Share this post


Link to post
Share on other sites

Bert,OK, I got it working, but some of it was "hunt and peck" to get the final panel.cfg entries correct.I commented out the window_pos line, and that moved the panel to my lower center monitor. Was still the same size (very narrow vertically) as in the upper left hand corner.Rechecked my "math", and that all seemed OK yet, so I figured I'd just start experimenting with new values in the WINDOW_SIZE= line. This is what I ended up with to get the minipanel centered correctly and the right height:[Window05]Background_color=0,0,0 size_mm=1024,768window_size_ratio=1.000 position=7visible=1ident=MiniPanelWINDOW_SIZE=0.325,1.000//window_pos= 0.000, 0.000child_3d=1Note the VERTICAL entry for the WINDOW_SIZE= line had to be 1.000, which is strange as the default Cessna has the same vertical 768 entry ("size_mm=xxxx, 768") as this new minipanel does. But to get this one to work, I had to up the 768 parameter to 1.000 (whereas for the default minipanel, it came out to be 0.130). Could the line "window_size_ratio=1.000" have anything to do with this? That line isn't in any of the default panel.cfg files as far as I have seen.Anyhow, you got me pointed in the right direction with your help, and even though I used an "unorthodox" way to get the rest of it right, it worked. Thanks for your help!Rick

Share this post


Link to post
Share on other sites

Rick,Happy it worked for you.Yes, these things can take some fiddling to get right.One thing that confuses me in your example is the statement that the default Cessna has a Minipanel with size_mm=xxx, 768Mine has 631,100Maybe that is the reason that the math was not working.

Share this post


Link to post
Share on other sites