• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
hilkiah

Issues entering route

Recommended Posts

Hi all,

Trying to enter the following route (from PRO-ATC):

ESSA DCT NOSLI DCT VSN DCT JX DCT NEXIL N851 MAKEL DCT RARUP DCT ULSEN T155 ALOSI DCT KEMAD UN851 MASEK DCT KERAX EDDF

When I get to the N851 airway (VIA) I can't enter MAKEL in the to section (RSK-1).  i am getting a NOT IN DATA BASE message.  As a matter of fact, no matter what I try to enter in the TO field, it isn't accepting it.  I'm suspecting the N851 airway isn't available in the route database?  if so, anyway I can confirm this?  Note I have navigraph 1709 rev1 installed on the 717 as well as Pro ATC.

Share this post


Link to post
Share on other sites

I tried entering a bogus airway and immediately got the NOT IN DATABASE message, so it appears that N851 is in fact valid (since it does allow me to enter it)....its just that its not allowing me to enter the next waypoint after the airway.

Share this post


Link to post
Share on other sites

Strange.....cause when I enter the route in PFPX, it accepts it as valid.  It also shows the airway as N851

Professional Flight Planner X 8_22_2017 9_28_32 PM.png

Share this post


Link to post
Share on other sites

When I enter UN851 in PFPX, it deletes the airway completely and sets up a direct connection between 

PELUP and MAKEL 

Thus I am suggesting that UN851 isn't a valid airway for this route.   Also even if when I enter UN851 in the via field, I still can't enter MAKEL in the To field.

Share this post


Link to post
Share on other sites
Quote

ESSA DCT NOSLI DCT VSN DCT JX DCT NEXIL N851 MAKEL DCT RARUP DCT ULSEN T155 ALOSI DCT KEMAD UN851 MASEK DCT KERAX EDDF

Try to validate your route with the Eurocontrol IFPS validator but I'm pretty sure this route is not valid :)

Share this post


Link to post
Share on other sites

It didn't validate ;)....but I think its because of the format entered:

ESSA DCT NOSLI DCT PELUP N851 MAKEL DCT LUB UP605 KEMAD DCT ERNEP DCT EMGOD T729 NOSPA DCT BETEX EDDF

Response: 

SYN112: INCORRECT USAGE OF BRACKETS '(' AND ')' AT ROW= 1, COL= 1 (TITLE)

I then tried letting PFPX find a route from ESSA to EDDF, instead of Pro-ATC.  This is what it found: 

ESSA DCT NOSLI N850 ABAMA DCT SALLO DCT HLZ T157 KERAX EDDF

I tried to validate that through Eurocontrol but that didn't validate either :( (similar syntax looking error).

I will try the new PFPX route and see if the 717 likes it and report.

Share this post


Link to post
Share on other sites

Hi all,

I copied and pasted the above route into Pilot2ATC, with no problem.

 

I have attached a 'company route'  for this FP (ESSA > EDDF)

 

Could someone let me know if that works

thanks

 

 

ESSAEDDF.xml

Share this post


Link to post
Share on other sites
33 minutes ago, hilkiah said:

It didn't validate ;)....but I think its because of the format entered:

ESSA DCT NOSLI DCT PELUP N851 MAKEL DCT LUB UP605 KEMAD DCT ERNEP DCT EMGOD T729 NOSPA DCT BETEX EDDF

Response: 

SYN112: INCORRECT USAGE OF BRACKETS '(' AND ')' AT ROW= 1, COL= 1 (TITLE)

I then tried letting PFPX find a route from ESSA to EDDF, instead of Pro-ATC.  This is what it found: 

ESSA DCT NOSLI N850 ABAMA DCT SALLO DCT HLZ T157 KERAX EDDF

I tried to validate that through Eurocontrol but that didn't validate either :( (similar syntax looking error).

I will try the new PFPX route and see if the 717 likes it and report.

You have to validate a full flightplan, eg :

(FPL-XXX000-IS
-B712/M-SDFGHRWY/C
-ESSA1125
-N0454F360 DCT NOSLI DCT PELUP N851 MAKEL DCT LUB/N0457F350 UP605
 KEMAD/N0459F360 DCT ERNEP DCT EMGOD T729 NOSPA DCT BETEX DCT
-EDDF0159 ETAR
-PBN/A1B2 RVR/075)

But remember that DCT are limited in a flight plan, in most case (in europe) it can exceed 50nm.
Try something like that : SID NOSLI N850 BAGOS UN850 MIC T155 ALOSI T157 KERAX STAR

ps: I don t check it

Edited by foobar

Share this post


Link to post
Share on other sites

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