GNS 530 still crashing to desktop when entering waypoints in FPL or Direct To

[fabs79 1]

Hi guys,

 

 

I know there are other threads concerning my problem, but I haven`t found and answer yet so I thought I´d create another one.

 

I still can`t get the Mindstar GNS 530 to work properly in P3D V3.3. I have an Emuteq GNS 530 hardware  unit and use it in conjunction with your GNS 530 software. I set up the Emuteq hardware buttons to their according GNS functions using FSUIPC offsets in the GNS.ini, and I installed the Mindstar GNS 530 unit into my Lancair Legacy panel.cfg (and some other planes, too). The buttons work as expected, however whenever I try to enter a waypoint on the FPL page of the GNS 530, Prepar3D freezes for a few seconds and then crashes to desktop without any error message as soon as I push the "ENT" button. The same happens when trying to use Direct-To-NAV. I can use the rotaries to enter an ICAO code, but as soon as I push ENT to activate the Direct-To-NAV - freeze and CTD. I tried re-downloading and reinstalling the GNS software a few time now, updated the Prepar3D client to the latest version (3.3.5) but still no luck. My panel.cfg for the Lancair Legacy looks like this (note that I only use a 2D window, no virtual cockpit unit):

// RealAir Legacy 2012

[Window Titles]
Window00=Main
Window01=GPS
Window02=Blank

[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]
size_mm=456,331
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL
gauge00=MPI_GNS!GNS530_nobezel, 0, 0, 456, 331, 1:1:225




//--------------------------------------------------------
[Window02]
size_mm=1,1
position=0
visible=0
ident=15600
BACKGROUND_COLOR=0,0,0
gauge00=RASLegacy!Blank, 0, 0, 1, 1




//--------------------------------------------------------
[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=fs9gps!RAS_gps_500, 1, 607, 502, 416
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

BTW it doesn`t matter which plane I try to install the GNS 530 into, the issue is always the same.

 

 

I´d appreciate any help you could provide.

 

Thanks,

 

Fabian

[WarpD 824]

First, I'll ask to ensure you are running the current version or has it been a while since you downloaded the installer?

Second, you have something on your system that is interfering with the gauge.  Simple as that.

 

Contact via our support email as someone is going to have to go over your system.

[fabs79 1]

OK thanks, I´ll write you an email then. Any way to narrow down the problem beforehand? As I said, no error message is displayed when the crash occurs, but maybe there`s some kind of log file I don`t know about so I could provide additional information.

[WarpD 824]

Our support team will review things as needed.