Jump to content

[SOLVED] XPX Route data discrepancy


Muskoka

Recommended Posts

Hi Philipp, still have a issue with the destination distance on the MFD. Here's screen shots of the actual route and the distance between the wayoints. If you add them all up they don't equal what the MFD is displaying for distance to destination.

The math :15+12+14+8+25+53+38+69+35=269..........not 290. Where is the extra 21NM coming from?

Here's the route from SimRoutes: YXU V98 YYZ J586 YCF LANRK......No arrival procedure entered.

post-7708-0-42890900-1327412034_thumb.jp

They list the route with a CAPTL9 arrival, and it's still only 275NM.

post-7708-0-14989000-1327410380_thumb.jppost-7708-0-12353900-1327410388_thumb.jppost-7708-0-64108000-1327410395_thumb.jp

I still have the oddity with the Saitek yoke, engines shut down everytime I touch the hat switch after initial load of XPX. I do start XPX with the engines running as apposed to cold and dark, that may be obvious.

Also, now when I input a temperature on the Perf Page, there's no values for TO, CLB, CRZ, and MCT, there used to be? Screen shot included.

post-7708-0-81002400-1327410370_thumb.jp

I started my usual flight, and gave up, well had no choice as the engines shut down around 16,000ft. It has happened before, just didn't say anything. The odd thing is, the engines all of a sudden shut off (start to spool down), you can hear it, but the gauges don't indicate the the engines have shut off. There are no warnings on the display, they just shut off. Always carry an extra hour of fuel, so it's not the problem. Similar things have happened in another aircraft I fly on a regular basis, starting to think it may be a XPX thing, not the CRJ.

Haven't tried XP 9.7 yet.

Glen

Link to comment
Share on other sites

The point is, the route is PHYSICALLY only 275NM, not 290NM. From waypoint , to waypoint , to waypoint, only equals 275NM. The whole route is not 290NM, where is that figure coming from.

I don't like doing this but it seems to be the only way to get the point across. Here is the same route in the LDS 767 in FSX, and it has the correct distance of 275NM.

post-7708-0-68555000-1327413380_thumb.jppost-7708-0-27117500-1327413390_thumb.jppost-7708-0-70337500-1327413402_thumb.jp

Glen

Edit: Here's the same route from another flight plan service. Notice the distance to destination.

post-7708-0-62347100-1327413801_thumb.jp

Here's some other screen shots, showing the remaining waypoints and the distance to destination. Guys, I'm 38NM from LANRK. LANRK to CYOW is roughly 35NM, so I'm 38 from LANRK, and LANRK is 35 to CYOW, so the total should be around 73NM, not 143NM that's on the MFD.

post-7708-0-65688700-1327414613_thumb.jppost-7708-0-85941100-1327414623_thumb.jp

Edit: Sorry, forgot to say, this is the latest version, downloaded last night, and was XP 10.03 rc2.

Edited by Muskoka
Link to comment
Share on other sites

Also, now when I input a temperature on the Perf Page, there's no values for TO, CLB, CRZ, and MCT, there used to be? Screen shot included.

Did you enter the flightplan before? The FMS must know the destination aiport (actually, the elevation of the departure runway) to calculate the performance figures.

As for the others, I will take a closer look once I'm back at my development computer.

Philipp

Link to comment
Share on other sites

Hi guys, just got back from the tooth fairy (dentist).

Ok, as usual, fired up XPX, CRJ is sitting at the terminal at CYXU with engines running, move the hat switch on my Saitek yoke so I can look around the cockpit and the engines stop. No biggie, just reload the aircraft, just letting you know it still happens. Maybe I should delete my prefs, although this is a new install of everything, XPX and CRJ..geeeez.

Ok, here's some more screen shots. First, I entered the flight plan, actually loaded from a save, loads fine. You can see the route on the MFD. Notice the last waypoint is CYOW, nothing after. There's no SID, no STAR, no Destination runway selected, and hence, no Missed approach waypoints.

Then I proceed to put the current temperature in the OAT on the Thrust Limit Page, 2 deg celsius, no N1 Percentages.

post-7708-0-28056700-1327437958_thumb.jp

Second screen shot is again of the MFD showing CYOW as the Destination waypoint, and the distance to that waypoint is 290NM, it should be around 275NM. It's not a big deal on this flight, I can almost do it with my eyes closed. Because I have done it so many times I know what my TOD is, but if it were a flight I was unfamiliar with, and the Destination Distance on the MFD was not correct, your starting you descent at the wrong time / distance. That distance figure has to be accurate, or you could be in trouble. Saying things you already know, I'll be quiet now.

post-7708-0-03326200-1327437970_thumb.jp

Glen

Link to comment
Share on other sites

Notice the last waypoint is CYOW, nothing after. There's no SID, no STAR, no Destination runway selected, and hence, no Missed approach waypoints.

Then I proceed to put the current temperature in the OAT on the Thrust Limit Page, 2 deg celsius, no N1 Percentages.

post-7708-0-28056700-1327437958_thumb.jp

No departure runway selected = no threshold elevation altitude for the departure runway = no performance calculation :)

Link to comment
Share on other sites

Ah, now I remember putting that in before, pilot error, cut in my pay, thanks Philipp, one down.

Glen

**Edit**: Philipp, just sorted out the issue with the engines shutting down when using the hat switch, deleted my prefs. A few days ago I reinstalled XPX and updated to 10.03r2. Then did the installs / reinstalls of the CRJ updates. So, XPX didn't like something after doing the updates. I even tried assigning the different 3d views to different toggles and buttons on my Saitek stuff, didn't make a difference. Anyways it's working properly now, that's all that matters.

Glen

Edited by Muskoka
Link to comment
Share on other sites

Philipp, it's fixed, you fixed it.....

Just by putting the Departure runway in, all is well in the world again. You can see in the screen shot, I put in the departure runway "9", and now the distance to destination says 275NM, whoooo. You can also see the whole flight plan with CYOW still as the destination. Why it works this way, I don't know, one for you to figure out :P . Most FMS / FMC's I've used will calculate the distance to destination without putting in a departure runway, but if that's the way this one works, fine with me, it works.

post-7708-0-27909500-1327443388_thumb.jp

Thanks to all for the help.

Glen

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...