I have been using the GNS 530 for a while now with no issues. I have not entered a flight plan until now. When I go to FPL and start entering a waypoint the gauge freezes. The timing varies. Sometimes it happens as I'm scrolling though the letters other times when I'm confirming entry of waypoint. It even let me enter the first waypoint once, and then it became unresponsive.

The aircraft is a Carenado 210, with only Mindstar 530/430 stack installed. I use it in VC mode, popping up the unit to enter data. When it becomes unresponsive none of the buttons work, and if I hide the pop-up, the VC version screen remains black. I try using the 430 and it is also unresponsive. Everything else in the aircraft works.

Another time, I got an error "Debug Assertion Failed! Program H:\SteamLibrary\steamapps\FSX\fsx.exe File F:\dd\vctools\crt_blt\self_x86\crt\src\vsprint.c Line: 280 Expression: ("Buffer too small",0)" just by scrolling though the pages and chapters on the screen.

Using FSUIPC version 4.969 registered.

The panel.cfg is below. Thanks for your help.

[Window Titles]
Window00=GPS
Window01=Manual
Window02=Control Windows
Window03=INFO

//--------------------------------------------------------
[Window00]
Background_color=255,255,255 
size_mm=520,378
window_size_ratio=1.000  
position=0
visible=0
ident=794
window_size= 0.360, 0.438
window_pos= 0.015, 0.530
zorder=15

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

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=1000,1000
window_size_ratio=1.000  
position=0
visible=0
ident=793
window_size= 0.440, 0.773
window_pos= 0.520, 0.040
zorder=0

gauge00=T210MManual!manual,  0,0,1000,1000

//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=581,153
window_size_ratio=1.000  
position=0
visible=0
ident=796
window_size= 0.321, 0.150
window_pos= 0.020, 0.170
zorder=5

gauge00=CCTC!Control_windows,  0,0,581,153

//--------------------------------------------------------
[Window03]
file=info.bmp 
size_mm=345,157
window_size_ratio=1.000  
position=0
visible=1
ident=142
window_size= 0.161, 0.116
window_pos= 0.020, 0.040

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$C340_GPS

gauge00=MPI_GNS!GNS530,  0,0,256,186,1:1:-1
gauge01=MPI_GNS!GNS430,  0,186,130,71,2:1:-1

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=1024,1024
texture=$RadiosC114

gauge00=RadioC210!RadioAudio,  0,0,297,57
gauge01=RadioC210!RadioAdf,  0,321,300,75
gauge02=DigTrans!transponder,  0,166,297,74
gauge03=APBK!Autopilot,  0,242,297,78
gauge04=DME!DME_screen,  302,212,210,82
gauge05=CCTC!Temp,  334,338,150,150
gauge06=CCTC!Oxygen,  3,398,115,114
gauge07=CCTC!Gear_light_red,  124,463,40,40
gauge08=CCTC!Gear_light_green,  124,419,40,40
gauge09=CCTC!Panel_annunciator,  301,114,207,93
gauge10=CCTC!Test_Light,  181,461,40,40
gauge11=CCTC!ELT_Light,  181,416,40,40
gauge12=CCTC2!ALTqnh,  490,0,20,20

Day=255,255,255
Night=255,255,255
Luminous=201,64,64

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=3500
 

OK, I think I fixed it by reinstalling the Carenado bird. Now everything seems fine. A plus is that in researching I found that one can use the keyboard to enter waypoints when in data entry mode. Nice!

Hope this helps someone else.

Thanks!

Any ideas why reinstalling the aircraft would help the panel config?  I have two 530's installed in the PC12.  Everything works until I hit activate on the direct to or the FPL>AG

Most of the time I have seen this behavior is when someone has installed a scenery that updates navigational data in the core sim files.

The issue is back, and just as bad if not worse. I thought it had gone away, but it persists.

I even bought RealNavData to ensure the GPS was using good data and it now crashes to desktop when loading a flight plan, adding any waypoints or anything in flight planning.

Screen shows it is using RealNav and it is up to date. I do not have any sceneries that update nav data. I only have ORBX stuff. Strange, it takes the waypoint, then there is a breif interruption in the sound, a few seconds, another interruption, and it crashes to desktop.

I even tried using the default Cessna C172 with the panel and it also crashes. Any support would be appreciated.

 

I also just tried disabling ALL add-on sceneries that I own, same result.

You have something on your system that's not quite right.  Contact our support via email and they'll get someone in touch with you to work it.

Checked event log and it seems the API.DLL is causing the crash. I removed FSUIPC completely and it seems to be working again. Will report more after a few flights. Thanks!

Ah... FSUIPC.... first, ensure you are using the very latest version of it... then try adding these lines to the FSUIPC.INI file:

ProvideAIdata=Yes
ProvideAIairports=No

On 8/2/2017 at 6:19 PM, WarpD said:

Ah... FSUIPC.... first, ensure you are using the very latest version of it... then try adding these lines to the FSUIPC.INI file:

ProvideAIdata=Yes
ProvideAIairports=No

These additions to my FSUIPC4.ini file solved the same crashing issue I encountered with my Mindstar GNS 530/430 after installing FSUIPC4. I would like 

 to know how and why they solve the problem.

 

Because it bypasses a function call that FSUIPC is making in the sim that causes a crash when our software is running.  It's something in the core sim that isn't correct and FSUIPC doesn't like it.  It only shows it's ugly head when our software is running.  While I really don't remember the details it's something like this:  FSUIPC asked for a piece of information, the sim didn't have said information, but instead of returning nothing it returns junk and that causes a crash.

Thank you for your explanation. It sure caught me by surprise because I have been running the Mindstar GNS 530/430 in my A2A aircraft for about a year with no problem until I recently installed FSUIPC4 to support a new switch panel. I was very happy to find this post with the fix. Now looking back at the GNS product web page I see there is note for FSUIPC users that includes the additions to the FSUIPC.ini file.