Hi

 

I'm no expert but I have installed Mindstar 530 in the PC12 virtual cockpit and also as a 'pop up'. 

 

However, the pop up only works by pressing 'shift 2'.  

 

It does not operate through the usual click hotspot on screen of the GPS VC unit.

 

Can you explain how to correct this please?

 

Thank you.  

 

Dean

 

 

[Window01]

Background_color=8,8,8 

size_mm=524,378

visible=0

ident=10020

window_size= 0.310,  0.370

window_pos=  0.650,  0.060

no_luminous=1

zorder=7

 

 

gauge00=MPI_GNS!GNS530,   0,0,520,378, 1:2:10020

gauge01=PC12CAR!ToggleCAR530,    64,0,384, 32

 

 

 

[Vcockpit01]

Background_color=0,0,0 

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$Panel_1

 

 

gauge00=GAUGEPC12EADI!Gauge_EFIS50_EADIVC,     0,  0,512,480

gauge01=GAUGEPC12EHSI!Gauge_EFIS50_EHSIVC,     0,481,512,480

gauge02=PC12CAR!ToggleEFIS,   0,  0,512,480

 

//gauge03=GPS530_3D_PC12!GPS_530_3D,   512,  0, 510,372

gauge03=MPI_GNS!GNS530,   512,  0, 510,372, 1:1:-1

gauge04=GPS530_3D_PC12!GPS_5302_3D,  512,373, 510,372

gauge05=PC12CAR!ToggleCAR530, 512,  0, 510, 32

 

gauge06=GAUGEPC12!Gauge_UPDATE,   0,  0,  1,  1

 

gauge07=CarSound_PC12!CarSound,  0,0,5,5

gauge08=PC12_EX500!EX500, 0,0,1,1

 

gauge09=PC12_Cabin_alt!C340_PRESS,         0,0,1,1

 

The window ID must be set to 225 for the clickspot to work.

Thank you for your prompt reply.

 

I have changed the window Ident from 10020 to 225. I have also changed the last code on the fifth parameter from 10020 to 225.

 

This has not worked. I still get a click spot saying zoom 530 but it does not open the extra PPP up window.

 

Could you please clarify if I am misunderstanding your guidance?

 

The window does still open using shift 2 though!

 

Thanks.

Dean.

Ok... stupid question from me... where is this click spot?

The whole of the glass screen in VC has a tip (or it clickspot) 'zoom 530'.

Dean

What is the second gauge you have in that window? It's not ours.

It came with the aircraft.

I've deleted it but still the same situation.

Shift 2 opens a window that has the GPS and of course the VC version goes blank.

Interestingly if I click on the pop up screen it now closes and reverts to the VC.

But clicking on the VC will still not open the pop up.

Not the end of the world but it would be nice to sort it.

Thanks.

Dean

Well, I know that our code is written and functions correctly. If the popup closes on clicking it's screen... and the VC will not open the window... then the click is probably not getting to our gauge and thus we don't try to open the window.

Hello,

With respect Ed, I don't believe that constitutes an adequate answer to Dean's problem. I share his frustration but I am getting the same symptoms with your installed GNS/Cessna 172 combination. I cannot get the pop-up to work by clicking on the 2d or VC GNS screens (I've put the GNS in the default panel and VC just for trial purposes). Clicking on the pop-up screen makes it disappear as it should. Shift+3 activates the pop-up as it should. I think I've tried all combinations of the 'Instance' number.

You're right.....it seems the click is probably not getting to the gauge......but why not? May we have a bit more expert assistance to help solve this problem please?

Only the individual with the 3D model can offer further assistance. The mouseclick itself is there and because you can use it to close the 2D window... it functions as expected. So, only the 3D modeler can assist in figuring out why clicking the screen of the gauge in the VC does nothing.

 

I'm curious, do you see the cursor change shape over the screen in the VC?

These marked in red must be commented out or removed. The gauge04 and gauge05 entries are interfering with the MPI_GNS gauge.

 

//gauge03=GPS530_3D_PC12!GPS_530_3D,   512,  0, 510,372

gauge03=MPI_GNS!GNS530,   512,  0, 510,372, 1:1:-1

//gauge04=GPS530_3D_PC12!GPS_5302_3D,  512,373, 510,372

//gauge05=PC12CAR!ToggleCAR530, 512,  0, 510, 32

 

The PC12CAR!ToggleCAR530 is an XML gauge that is used in the "default" to open/close the 2d popup of their GPS gauge. As such it is overwriting the built-in control of Mindstar's popup command.

 

The reason clicking on the 2d popup works is because the ToggleCAR530 gauge was commented out...

Thanks to both of you for the quick replies.

 

@Ed - Yes. In both the 2D and VC panels the cursor changes from a pointer to a hand and the tooltip 'Zoom 530' or 'Zoom 430' appears as appropriate.

 

@Fr.Bill - I hope this helps Dean but I do not have the PC12. As you know the default C172 does not have a GPS in either panel, only the pop-up from a Simicon, so there must be some other interference happening? And the problem is the same in the MilViz C310R which is installed as supplied as far as I can tell. :unsure:  I cannot see any suitable xml candidates in that panel.cfg to be removed. Over to you again.........and thanks.

I have no idea how you put a 430/530 in the default 172... since it doesn't have one.

 

Since you've shown absolutely no panel.cfg information I'll assume you have made a mistake there and leave you to solve it. Because I know the clickspot built into the gauge functions when everything is done correctly. When things aren't working, it is not the gauge.

 

And let us be crystal clear... Bill Leaming neither works for nor represents Mindstar and as such is simply being a nice guy with his information regarding an aircraft we don't own and aren't going to purchase.

... and unfortunately what Bill suggested didn't work for me as I already had those lines commented out. Thanks though.

Dean

I think the continued point-scoring behaviour between MindStar and developers who license the MindStar products is quite disgraceful, most unhelpful and is really shooting each other in the foot. A MindStar GNS for FSX or P3D is of little use without a vehicle to put it in, and even less use when it doesn't work as advertised. Similarly Milviz (because I've paid good money for their C310R and B/E-55 as well as to MindStar for their GNS530/430) have a vested interest in the combination of aircraft and avionics working together properly.

 

If you have no idea how to add a gauge to an FSX aircraft then perhaps you are in the wrong business! I will supply any amount of panel.cfg or other information if requested by someone who is trying to help me with my problem. Perhaps you or Bill Leaming can provide me with a configuration that DOES work properly?