• 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.
Sign in to follow this  
N99WB

OK, I surrender. . .

Recommended Posts

The MFC is beyond me.  Maybe, just maybe I can fly

KOKC ---> KAUS using VOR's and ILS RWY 17L.

Can I get some tips on how to:

Tune the NAV's.

Set the courses

Engage Autopilot to follow the radio/nav

 

Thanks,

N99WB

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, N99WB said:

The MFC is beyond me.  Maybe, just maybe I can fly

KOKC ---> KAUS using VOR's and ILS RWY 17L.

Can I get some tips on how to:

Tune the NAV's.

Set the courses

Engage Autopilot to follow the radio/nav

 

Thanks,

N99WB

Click on NAV/RAD on the MCDU. There you can enter VOR frequency and Course...Ex : 113.30/120 or ILS 108.90/177 or NDB frequency.

Instead enter a frequency, you can enter directly a VOR name like Ex : SWR...and so...

You have also a good MCDU tutorial there :

Hope this help.

Regards,

Edited by Richard Portier

Share this post


Link to post
Share on other sites

Normally we just use the MCDU to do a VOR approach on the 717, like on an Airbus or a Boeing 757/767.
We don't need to catch a radial from a VOR beacon but simply select the appropriate approach on the MCDU and that it :)

The problem is the DIR-TO function is not yet implemented on the 717 so if you fly online the ATC will guide you to intercept a course and you currently can't do a DIR-TO with an intercept course on this addon.

So you have to switch to HDG mode, enter the VOR frequency / intcp crs on the RAD NAV page then when your heading crosses the course click on the VOR ARM key and ARM the AP nav mode. 

Once the plane intercepted the course, you can continue on the track and manage manually the descent or done a DIR-TO to the next waypoint and keep the MCDU manages the descent (but be carreful: a lot of approaches are not correctly interpreted and will not work (incorrect altitude, missing waypoints...)

 

Share this post


Link to post
Share on other sites
On 1/7/2018 at 6:16 AM, foobar said:

Normally we just use the MCDU to do a VOR approach on the 717, like on an Airbus or a Boeing 757/767.
We don't need to catch a radial from a VOR beacon but simply select the appropriate approach on the MCDU and that it :)

The problem is the DIR-TO function is not yet implemented on the 717 so if you fly online the ATC will guide you to intercept a course and you currently can't do a DIR-TO with an intercept course on this addon.

So you have to switch to HDG mode, enter the VOR frequency / intcp crs on the RAD NAV page then when your heading crosses the course click on the VOR ARM key and ARM the AP nav mode. 

Once the plane intercepted the course, you can continue on the track and manage manually the descent or done a DIR-TO to the next waypoint and keep the MCDU manages the descent (but be carreful: a lot of approaches are not correctly interpreted and will not work (incorrect altitude, missing waypoints...)

 

That "select the appropriate approach" part seems to be one of my problems.

That and what buttons set the AP to what state :)

I'll keep trying. . .

 

Thanks,

N99WB

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

Sign in to follow this