Jump to content
Sign in to follow this  
dustin_usaf

GNS 430 in FSX Steam Edition (sim connect issues)

Recommended Posts

I'm getting multiple sim connect failure pop-ups when starting the sim/flight. I read that this was a potential known issue with FSXE, but couldn't find a solution posted.

 

Additionally, I have a panel .cfg question. I am trying to set the panel so that I have 1 430 in the VC, and a clickable pop-up for a separate screen (so only 1 GPS in the aircraft, just 2 ways of viewing/using it). As best I can tell, I have correctly set the .cfg entries, according to the instructions. However, whenever I use the pop-up, the screen goes blank in the VC, until I close the popup. Is this normal/the only way to do this without using 2 units? Thanks!

 

Please reference the panel entry below and the attached screen shots.

 

1_zpsjnfggugp.png

 

2_zpswegj7wer.png

 

// Panel Configuration file

 
[Window Titles]
 
 
Window01=Conf
Window02=GPS
Window03=Parking
Window04=Power
 
[Window01]
Background_color=0,0,0 
size_mm=600,380
position=7
visible=0
ident=Conf
window_size=0.5
 
gauge00=Config!Config,  0,0,600,380
window_pos=0.050,0.050
 
[Window02]
size_mm=456,378
window_size=0.5
position=8
Background_color=0,0,0 
visible=0
ident=GPS_PANEL
gauge00=MPI_GNS!GNS430, 0, 0, 456, 189, 1:2:225
 
 
[Window03]
size_mm=221,349
window_size=0.5
position=10
window_pos=0.58,0.185
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=150
zorder=4
 
gauge00=eclipse-da20 3!Parking,            0,0
 
 
[Window04]
size_mm=221,355
window_size=0.5
position=9
window_pos=0.58,0.54
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=10
zorder=4
 
gauge00=eclipse-da20 3!Power,            0,0
 
 
 
[VCockpit01]
size_mm=2048,2048
pixel_size=2048,2048
texture=$CZAW
background_color=0,0,1
no_luminous=1
 
gauge00=eclipse-da20 3!compass,            1890,373,146,152
gauge01=eclipse-da20 3!attitude,           190,0,324,340
gauge02=MPI_GNS!GNS430,           1188,4,850,356, 1:1:-1
gauge03=eclipse-da20 3!Flaps Switch,        478,1211,379,141
gauge04=eclipse-da20 3!Number Plate,        11,1532,370,70
gauge05=eclipse-da20 3!Turn,    32,272,445,530
gauge06=eclipse-da20 3!xpdr,                 600,0,536,135
gauge07=eclipse-da20 3!Directional gyro Knob,         854,304,52,51
gauge08=eclipse-da20 3!Audio,   600,142,472,97
gauge09=eclipse-da20 3!annunciator-gen,         455,514,100,200
gauge10=eclipse-da20 3!annunciator-canopy,          454,302,100,200
gauge11=eclipse-da20 3!annunciator-start,         563,308,200,200
gauge12=eclipse-da20 3!Pitch trim,         167,1211,155,155
gauge13=eclipse-da20 3!Clock,          6,1215,151,152
gauge14=eclipse-da20 3!GarminSl40,          6,934,1342,268
gauge15=eclipse-da20 3!Directional gyro,         893,525,400,400
gauge16=eclipse-da20 3!Altimeter Knob,         48,0,50,50
gauge17=eclipse-da20 3!Altimeter s,         1818,922,96,1044
gauge18=eclipse-da20 3!glideslope_VOR,         492,1383,528,530
gauge19=eclipse-da20 3!Panel Lights,         1,1947,100,100
 
 
[Views]
VIEW_FORWARD_ZOOM=8
VIEW_FORWARD_EYE=0.000, 0.040, 0.400
VIEW_FORWARD_DIR=1.000, 0.000, 0.000
 
[Color]
Day=255,255,255
Night=255,255,255
Luminous=201,64,64
 
[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143

Share this post


Link to post

You didn't state what the errors were, so I'm kinda guessing here... FSX:SE doesn't install SimConnect by default. You will have to do that yourself. I don't know exactly where they put the installers, but I know they're provided with the FSX:SE version.

 

As for the GNS only rendering on the popup, yes that's correct behavior. It's to keep performance up... and besides, you have no reason to look at the exact same display in two different locations at the same time... right?

  • Upvote 1

Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

Ed, you're right, I don't need it in both locations, it's just habit, all the previous ones I have used behaved where they showed in both locations simultaneously. I just wanted to make sure I hadn't done something wrong. Thanks for your help, really appreciated. My fault for not posting the specific error, but again, you were right, I had to actually install sim connect. Sorry if that was a rookie move, didn't even think to check for that. Everything is fixed and in working order, no error messages. Posting the below information for anybody else with this issue who happens upon the thread:

 

D:\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM\SimConnect.msi 

D:\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.msi

D:\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi

 

(click on the .msi files to install the files, accept the license, etc. and see the YouTube link below for a quick tutorial I found)

 

https://youtu.be/5jpJmJ4wfzA

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...