KI525 Gauge

[OrtegaS 1]

Hello,

 

I created a window popup using the included MPI_CDIgauge(s) so that I can have vertical guidance during a WAAS approach in aircraft where developers have not provided one.  I have found that of the three, GI106A; KI525; KI209, the KI525 gauge will not work for me.  So far I have tried the gauge in the RealAir Duke V 2 and LanceAir V1.  I am using the latest installer ver 1.08.0020 on a Windows 10 64bit platform.  The gauge MPI_CDIGauge.gau file in my FSX (non steam) shows 11/24/2014 10:30AM  10,904kb.  My panel entry looks like this:

 

[Window03]

size_mm=100,100

position=7

visible=0

ident=

window_pos= 0.000, 0.000

Background_color=0,0,0 

gauge00=MPI_CDIGauge!GI106A,  0,0,100,100,1:1:225

//gauge00=MPI_CDIGauge!KI525,  0,0,100,100,1:1:225

 

 

It could be that as I am still learning how to manipulate these file entries. 

 

Thank you.

 

Steve

[WarpD 824]

First, you didn't give your window an ident value... "ident=" isn't valid.

Second, I dunno what that 1:1:225 is for the 5th parameter of this gauge... doesn't use it.

Third, I double dog dare you to figure out what someone's problem is when all the info as to what is wrong is: "will not work for me".

Fourth, your panel.cfg shows you using the GI106A... did you mean to show me you're using that one??  With the KI525 commented out, I'm pretty certain it won't work for anyone.

[OrtegaS 1]

1- ok

2- ok. I dont see in your install guides how to install a gauge ie G106a Ki525 ki209.

3-. "I have found that of the three, GI106A; KI525; KI209, the KI525 gauge will not work for me." In other words with the syntax I posted below the Gi106a works. The Ki209 works. The Ki525 does not.

4- the ki525 is commented out. You are right it won't work for anyone.

I should have removed the working line and replaced with commented out line.

 

I am only trying to get the ki525 to work. The other two do with what I have shown.

[WarpD 824]

You still haven't explained what you mean by "win not work for me".  That doesn't explain absolutely anything.

 

WHAT doesn't work?  You need to be specific.

 

As for how to install the gauge... like absolutely any other gauge in a panel.

[OrtegaS 1]

I am asking for your assistance on how to create a pop up gauge of the KI525 from your MPI_CDIGAUGE file.

[WarpD 824]

It is considered appropriate to answer questions when they are asked.  It also makes my task easier.

[WarpD 824]

Sunday morning and more thought... post the content of your panel.cfg

[OrtegaS 1]

Unfortunately I won't be at my PC until tomorrow afternoon. I will post it then for us.

 

Thank you.

[OrtegaS 1]

// RealAir Legacy 2012

 

[Window Titles]

Window00=Main

Window01=Mindstar GNS

Window02=Blank

//Window03=Mindstar GI106A

Window03=Mindstar KI525

 

[VIEWS]

VIEW_FORWARD_DIR=0.000, 0.000, 0.000

 

//--------------------------------------------------------

[Window00]

size_mm=1024,1024

position=0

BACKGROUND_COLOR=0,0,0

visible=0

ident=15552

 

 

 

 

//--------------------------------------------------------

[Window01]

//window_pos=0.739583,0.000000

//window_size=0.260417,0.300000

//visible=0

//ident=15531

//zorder=99

//gauge00=rxpGNS!GNS530,0,0,100,100

 

size_mm=456,520

window_size=0.5

position=8

BACKGROUND_COLOR=0,0,0

VISIBLE=0

ident=11013

gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:2:11013

gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:11013

 

 

//--------------------------------------------------------

[Window02]

size_mm=1,1

position=0

visible=0

ident=15600

BACKGROUND_COLOR=0,0,0

gauge00=RASLegacy!Blank, 0, 0, 1, 1

 

//--------------------------------------------------------

[Window03]

size_mm=100,100

position=7

visible=0

ident=225

window_pos= 0.000, 0.000

Background_color=0,0,0 

//gauge00=MPI_CDIGauge!GI106A,  0,0,100,100,1:1:225

gauge00=MPI_CDIGauge!KI525,  0,0,100,100,1:1:225

 

 

 

//--------------------------------------------------------

[VCockpit01]

size_mm=1024,1024

pixel_size=1024,1024

texture=$RASLegacy_CFG

background_color=1,1,1

 

gauge01=Config!Options, 1020, 1023, 1, 1

gauge02=Config!RealView, 1021, 1023, 1, 1

gauge03=RASLegacy!InitVars, 1022, 1023, 1, 1

gauge04=RASLegacy!1hzCode, 1023, 1023, 1, 1

gauge05=RASLegacy!2hzCode, 1024, 1023, 1, 1

gauge06=RASLegacy!18hzCode, 1025, 1023, 1, 1

 

gauge08=RASLegacy!NavCom1, 1, 2, 509, 61

gauge09=RASLegacy!NavCom2, 1, 64, 509, 61

gauge10=RASLegacy!ADF, 4, 127, 332, 49

gauge11=RASLegacy!Xpndr, 7, 243, 305, 57

gauge12=RASLegacy!Autopilot, 5, 177, 292, 62

gauge13=RASLegacy!DME, 4, 305, 256, 46

gauge14=RASLegacy!VM1000C, 579, 0, 445, 446

gauge15=RASLegacy!Annunciator, 0, 379, 453, 68

gauge16=RASLegacy!AOA_Pro, 347, 204, 106, 63

gauge18=RASLegacy!Master_Warn, 346, 271, 108, 107

 

// ===============================================================================

// IMPORTANT - 'gauge19'. 'gauge20, 'gauge22', and 'gauge23' BELOW CAN BE OVERWRITTEN 

// BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE

// IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY 

// CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22'

// ===============================================================================

 

//gauge19=rxpGNS!GNS530, 1, 660, 504, 364

gauge24=MPI_GNS!GNS530, 1, 657, 504, 353, 1:1:-1

gauge20=RASLegacy!Blank, 0, 0, 1, 1

 

gauge21=Config!AdfDip, 1019, 1023, 1, 1

 

gauge22=RASLegacy_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Legacy/Panel/Sound/RASLegacy_Sound.ini

gauge23=RASLegacy!Sound_Manager, 1,1,3,3

 

 

 

 

[Default View]

X=0

Y=0

SIZE_X=8192

SIZE_Y=3500

 

[Color]

Day=255,255,255

Night=255,255,255

Luminous=201,64,64

[WarpD 824]

Now you need to explain "will not work for me".  Since the KI525 is a rather complex gauge compared to the other two... I need more information than what those five words offer.

[OrtegaS 1]

Thank you......

 

If I do this:

 

[Window03]
size_mm=100,100
position=7
visible=0
ident=225
window_pos= 0.000, 0.000
Background_color=0,0,0 
gauge00=MPI_CDIGauge!GI106A,  0,0,100,100,1:1:225
//gauge00=MPI_CDIGauge!KI525,  0,0,100,100,1:1:225

 

Then I am able to call up a 2d popup panel as shown here on the bottom left....

 

 

If I do this:

 

[Window03]
size_mm=100,100
position=7
visible=0
ident=225
window_pos= 0.000, 0.000
Background_color=0,0,0 
gauge00=MPI_CDIGauge!KI209,  0,0,100,100,1:1:225
//gauge00=MPI_CDIGauge!KI525,  0,0,100,100,1:1:225

 

I can get the KI209 to come up also as shown here:

 

 

 

But with my panel.cfg as shown in post 9 I can not get the KI525 to do the same.

 

Thanks.

[WarpD 824]

You need to remove the 5th parameter... I have no idea where you got information that it was needed for these gauges... it's not.  Remove it, see if that corrects things.

[OrtegaS 1]

Removed the 5th parameter.   No change.

[WarpD 824]

Show me a screen shot with the KI 525 in it.

[OrtegaS 1]