Fpl Page Goes Blue After Adding Star

[mas618 17]

This is in P3d v2.2 using the RA duke V2. Navdata updated via Realnav tool.

 

Route was ENCN-ENHD, with routing N0219F220 SUBUX (VIA SUBUX6B) EVRUS ZOL. I copied the FP to route # 2.

 

All good, and around EVRUS, I added the ZOL8V arrival via pressing PROC and selecting the STAR, and pressing ENT to load.

 

When I returned to the FPL page, it was just blue (both pages). Pressing the Menu key made the background faded (like normal), but the menu itself never came up.

 

 

As I was unable to reload any FPL, I tried a DCT TO ENHD, but the GNS was unable to find the airfield. It just came up with nothing but was suggesting Russia (!?) as the country of search? I tried ZOL VOR and KRM VOR, but I couldn't find those either and suggested Estonia!?

 

If I tuned the VORs in the GNS, I was unable to use the CRS on the NAV to get a DCT-to BRG, like the GNS could not feed the analog instrument with any info - both on GPS and VLOC.

 

I tried to turn off and on the GNS but withsame result. It was like the GNS had totally lost it's database both over stored FP and navdata...

 

Going to the NRST page over VOR stations, both ZOL and KRM was listed with appropriate DIS and BRG?

 

I wish I had taken some screenshots, and in fact I tried using the v-key as I used to in FSX, but forgot that I had not set that up correctly in P3D.

 

In then tried to acces the Flightplanning menu in P3D, which then of coursed crashed the sim (known bug, so stupid of me).

 

Can you (or anyone reproduce this?), perhaps guide me to what I did wrong, if anything?

 

Yesterday on route ENCN-EKRK, I was able to load an arrival without hassle...? Only thing I might have done differently yesterday (IIRC), was that I might have added the approach first, and then the arrival. Today I started with the arrival, and of course never got to the approach...?

 

Regards

 

Mas

[mas618 17]

 

Regards

 

Mas

Update:

 

(short summary: I think the ZOL8V coding is faulty and causing the GNS to screw up).

 

I was able to reproduce the issue. I loaded up at ENCN on ground, and loaded the FP used before from storage. Added the departure as before, removed double entry SUBUX, and then added the arrival ZOL8V - and the exact same issuse as before.

See screenshots here: http://s354.photobucket.com/user/mas618/library/Mindstar%20GNS

 

Tried same procedure, but loading the approach first, same result,

pics here: http://s354.photobucket.com/user/mas618/library/Mindstar%20GNS%20set%202

 

Loading another arrival is without issues,

pics here: http://s354.photobucket.com/user/mas618/library/Mindstar%20GNS%20set%202/Mindstar%20GNS%20set%203

 

It could seem that the coding of the arrival ZOL8V is giving some issues. The big trouble is, that once you've selected a "faulty" arrival, the GNS and the flight seems to be unrecoverable...

 

Further more, as pr. official charts, there are two ZOL arrivals into ENHD, ZOL8V and ZOL8U. The listed arrival ZOL8 in the GNS corresponds to ZOL8U (rwy 14), and the faulty ZOL8V is for rwy 32.

 

Hope you can solve this - this may be applicable to other arrivals globally... (hope not )

 

Mas

[WarpD 824]

Ok... the only thing I can offer is that you talk about removing a double entry. There is no such thing in a 430 flight plan and you really shouldn't be deleting waypoints like that. If you see a waypoint twice, it should be there twice.

 

Aside from that... I have been able to load this without issue.

[mas618 17]

Hi Ed. Thx for your response!

 

When you are able to load the procedure, is this under the same circumstances as me - eg same airport, route and such? I'm able to reproduce every time, so I guess it could be my setup?

 

Could it be my panel.cfg entries?

 

I'll try and uninstall and then reinstall with the latest installer and report back.

 

Mas

[mas618 17]

So I re-installed the unit using the link (but still version 1.0.0.5 - same as before). I re-installed the latest update to the navdatabase.

 

Unfortunately I can reproduce the issue - selecting ZOL8V will "balnk" both FP pages and leave the unit as described earlier. Curious to know if your situation setup is different from mine - if yes, then something must be "messing" with the gns, since you are not able to reproduce.

 

I've attached my panel.cfg here, maybe something is wrong with it?

 

I'd appreciate if anyone could assist, or perhaps could try and reproduce the issue?

 

thx again

 

Mas

[WarpD 824]

Ok... delete the flight plan in storage. Do it without a stored flight plan. I can load that arrival without issue so it's something on your end that's the source.

 

I see no panel.cfg file.

 

Based on the images you've provided... it appears your 530 has a different flight plan than your 430... is this correct?

[mas618 17]

Hi Ed.

 

I did start a fresh FPL, simply ENCN-SUBUX-ZOL-ENHD. And also I deleted the stored one.

 

My Cfg is inserted below.

 

I only manipulate the GNS530 throughout the simsession, so I've not inserted a different FPL on the 430 on purpose. The 430 FPL pages also "blanks" when adding the procedure, and it seems that the 430 suffers from the same issues as the 530 described above.

 

If you find nothing in the .cfg below, I'm out of ideas, and from the sound of it, so are you guys

 

Mas

 

// Panel Configuration file
// RealAir Simulations Beechcraft Duke B60 2013 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright © 2013 RealAir Simulations

[Window Titles]
Window00=Main Panel
Window01=GNS


[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=RASDuke!InitVars, 1022, 1023, 1, 1
gauge04=RASDuke!1hzCode, 1023, 1023, 1, 1
gauge05=RASDuke!2hzCode, 1024, 1023, 1, 1
gauge06=RASDuke!18hzCode, 1025, 1023, 1, 1
gauge07=Config!AdfDip, 1026, 1023, 1, 1

gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!Annunciator, 886,131,137,262
gauge15=RASDuke!KA285_Annun, 512,2,337,108

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' 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=RASDuke!Blank, 0, 0, 1, 1

gauge21=RASDuke_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke B60 V2/Panel/Sound/RASDuke_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1



Day=255,255,255
Night=225,117,89
Luminous=200,200,101

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

[Window01]
size_mm=456,520
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL
gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225
gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225
 

[WarpD 824]

Where did that window entry come from? Did you hand write it?

 

It shouldn't be listed AFTER the VC window entries.

 

Also... this entry in VCockpit01 window:

 

gauge19=fs9gps!RAS_gps_500, 1, 607, 502, 416

 

Not allowed. You can't run default GPS gauge code with our GNS units. You just can't.

[mas618 17]

Well I took that window section from your website (an example of how to run 430/530), I figured it would go for any aircraft?

 

But let me try and move it pre VC, and I'll get rid of the default gps entry also - was not aware that this was a no go, and given my very limited knowledge on these things, I didn't want to mess around to much in the .cfg.

 

I'll test again tonight and report back - thank you for your dedicated support!

 

Mas

[mas618 17]

Unfortunately the issue persists.

 

This is my current panel.cfg

 

// Panel Configuration file
// RealAir Simulations Beechcraft Duke B60 2013 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright © 2013 RealAir Simulations

[Window Titles]
Window00=Main Panel
Window01=GNS


[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[Window01]
size_mm=456,520
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL
gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225
gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=RASDuke!InitVars, 1022, 1023, 1, 1
gauge04=RASDuke!1hzCode, 1023, 1023, 1, 1
gauge05=RASDuke!2hzCode, 1024, 1023, 1, 1
gauge06=RASDuke!18hzCode, 1025, 1023, 1, 1
gauge07=Config!AdfDip, 1026, 1023, 1, 1

gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!Annunciator, 886,131,137,262
gauge15=RASDuke!KA285_Annun, 512,2,337,108

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' 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=RASDuke!Blank, 0, 0, 1, 1

gauge21=RASDuke_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke B60 V2/Panel/Sound/RASDuke_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1



Day=255,255,255
Night=225,117,89
Luminous=200,200,101

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

 

 

I wish I knew what was going on, but i'm totally blank now... Did something maybe go wrong during installation? Are there any key files I could check for being in the proper location or anything?

 

Mas

[mas618 17]

Assuming it's my setup that causes this, I'll be doing a full re-install of P3d v2.3.

 

Ed, can you advise which Mindstar folders to look for, to ensure a complete wipe of the Mindstar product (assuming the uninstaller will leave some folders and files) , before re-installing the package to a vanilla p3d?

 

Thx

 

Mas

[WarpD 824]

We still haven't gotten past the waypoint deletion issue.

 

You stated you removed the double entry SUBUX. Since there's no such thing as a double entry in the 430... what are you talking about?

[mas618 17]

I must have explained my self wrong. What I meant was that if I first enter the route SUBUX EVRUS ZOL ENHD, and then afterwards select the departure SUBUX 6B, I'll have a departure segment in the gns that ends with subux, and following this an Enroute segment that starts with SUBUX. Approaching SUBUX I get the message "Approaching waypoint" and if I do nothing, the gns will try to return to SUBUX after having overflow it, resulting in a 360 turn. I then have to select the next leg in the Enroute segment - SUBUX-EVRUS. I'm sure this is also something I'm doing wrong, but nonetheless I wanted to make sure my install was good.

 

Mas