I was wondering if I could get some assistance with installing the Mindstar GNS430/530, I recently tried to set it up with the Carenado PC12, and it sort of worked the first time in one of the 2x GNS530 panels where I had the default running alongside the Mindstar version but it has been crashing my Prepar3D exe ever since I quit and tried to set up the second gauge as a secondary Mindstar GNS530. As in, P3D crashes before start up, even though the default scenario is loaded.

I've even tried reinstalling Prepar3D clean by itself with just the Mindstar GNS430/530, updated with the latest AIRAC and the program still crashes. Viewing the logged event in Event Viewer, it shows the following (mostly they are clr.dll module failures with different process IDs):
 

Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3
Faulting module name: clr.dll, version: 4.0.30319.34014, time stamp: 0x52e0b784
Exception code: 0xc00000fd
Fault offset: 0x0041c732
Faulting process ID: 0x136c
Faulting application start time: 0x01d01f91c4a33bba
Faulting application path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report ID: 035ac995-8b85-11e4-be80-d05099261977
Faulting package full name:
Faulting package-relative application ID:

 

 

Before I reinstalled P3D with just the Mindstar GNS430/530, one time when it crashed I got the following in event viewer:

 

Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3

Faulting module name: MPI_GNS.gau, version: 1.5.0.0, time stamp: 0x54750930

Exception code: 0xc0000005

Fault offset: 0x0028b3cb

Faulting process ID: 0x1310

Faulting application start time: 0x01d01f76980f47fd

Faulting application path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Faulting module path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\GAUGES\MPI_GNS.gau

Report ID: 63afe2aa-8b6a-11e4-be7f-d05099261977

Faulting package full name: 

Faulting package-relative application ID: 

 

 

And on two occasions, I got:

 

 

Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3

Faulting module name: DINPUT8.dll, version: 6.3.9600.16384, time stamp: 0x52158cf1

Exception code: 0xc0000005

Fault offset: 0x0001f21c

Faulting process ID: 0x1158

Faulting application start time: 0x01d01f76396ffd7e

Faulting application path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Faulting module path: C:\WINDOWS\SYSTEM32\DINPUT8.dll

Report ID: b9232fe6-8b69-11e4-be7f-d05099261977

Faulting package full name: 

Faulting package-relative application ID: 

 

I'm not personally sure what it all means but it seems I can't seem to get the Mindstar to work at all now.

 

Now if I delete the hypergauge entry in the DLL.xml file, i.e.:

 

 

 <Launch.Addon>

    <Name>HyperGauge</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\hypergauge.dll</Path>

  </Launch.Addon>

If I delete the above from the DLL.xml file then Prepar3D starts up normally, otherwise it will CTD prior to starting up if I add the line back in. I don't know what's causing the incompatibility. Any suggestions or ideas on what to do? Disabling the hypergauge will allow P3D to start up, but it seems that the gauges do not work and are black - should they work even with the hypergauge.dll file disabled?

 

In terms of the panel.cfg integration, I have used:

 

 

[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:1:225

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

 

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

 

 

 

and further down the panel.cfg file I have:

 

[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=MPI_GNS!GNS530,   512,  0, 510,372,1:2:-1

gauge04=MPI_GNS!GNS530,  512,373, 510,372,2:2:-1

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

//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

 

 

 

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

 

 

 

 

 

 

 

I've installed Microsoft Net Framework 4.0 (4.0.30319.34014) which I believe is the latest using the web download link from Microsoft. Redownloading the web installer, it says that mine is currently up to date and won't update further.

Ok... I'm going to give you a Christmas present... and see if this fixes the problem:

 

First... in your popup you have:

gauge00=MPI_GNS!GNS530, 0,0,520,378,1:1:225

It should be:

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

In your VC entry you have:

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

It should be:

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

Happy Holidays!

Ok so I tried completely uninstalling Prepar3D and Mindstar using geekuninstaller, and searched out any registry keys relating to either and deleted them (I would recommend only doing this if you know what you are doing - not that I really do but beware and be careful if you do).

 

Reinstalled Prepar3D into a different folder (not the same one I deleted previously), right click compatability and made sure to always start it in administrator mode. Started it up to make sure it worked and shut it down again, restarted computer.

 

Installed the Mindstar software into a new folder (not the same one I deleted from previously).

 

Installed the Carenado PC12, and added the corrected gauge lines to the panel.cfg file as per Ed's comments above. Checked and the DLL.xml file (located in your %appdata/roaming/lockheed martin/prepar3d v2 folder) and it shows it still is loading up the HyperGauge.dll file.

 

Fired up Prepar3D, didn't crash on start up, loaded up the Carenado PC12 and lo and behold, dual Mindstar GNS530s in action! Didn't comment out gauge05 which allows for the top right click spot on the top GNS530, though can only seem to use Shift+2 to close the popup window. No biggie, it seems to be working well though!

 

Ed, thank you so very much to spend some time helping me out during your Christmas break! A+++ for Mindstar support.

Great work Ed.  Thanks.

 

I've had one Mindstar working in PC12 for months but now two!  It is Christmas.

 

I wonder if you could accumulate a catalogue of these codings for various aircraft? 

I know the 'instructions' are correct on your website but frankly us normal people (most simmers) fail to understand or follow them properly.

We could all contiribute what we are using and you could check them?

The Mindstar is a great product especially for P3d and this sort of support (on Christmas Day even!) really help.

 

 

Autogyro - until Ed replies I just wonder if in reinstalling your Mindstar the Ident Number has changed? I had a problem with pop up activation a while ago and it was because the ident at the top didn't match the ident in the 5th parameter - in this case 10020.

 

Dean

Hi Dean,

 

No I believe that the PC12 is always 10020 as the required ident number, I simply didn't understand the requirement to match the ident in the 2D pop up coding. From what I gather the ident is set by the airplane modeller and shouldn't change, we just need to match it or otherwise adopt 225.

Both mine in Window 1 are 11013 and it works.

Please try. There was a thread which mentioned it. Not supposed to work but it does!

Hi Dean, sorry I might have misunderstood, what are you suggesting I change? Both the idents in window01? I'd imagine as long as they match it will work as a popup? So you could probably put anything there as long as it matches?

I don't want to step on Ed's toes.

But - yes that's what I thought when I had 225 and 10020 and both didn't work.

I set it at 11013 and it works.  Ident at the top 11013. 5th parameter 11013.

Let me know.

Dean

11013 is the correct value to simply open and shut the popup by clicking the unit's screen. The 225 value is for supporting the GPS icon that many panels have.