• 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.

Recommended Posts

I really love all that was done with the new update. It is such a huge improvement, but I know that you don't want to know what is right as much as you want to know any problems that we might have.

I'm sure that you still have a lot of work to do on the FMC, but I wanted to point out my experience.

It still does not seem to put the correct altitudes for SIDs and STARs.  I will see a waypoint that shows +16000 on a SID, then the next waypoint shows 15999, which wouldn't make much sense if you had to be above FS160 at the previous waypoint.

Also, I was decending via LEEHY4 STAR to KSLC Rwy 16L using autoflight NAV mode with VS decent, when they cleared me for RWY 16R.  I went into the FMC and selected 16R without changing the STAR (*Insert), and the autopilot completely lost the track on the STAR and didn't turn for the next waypoint.  I had to catch it and turn with HDG SEL and was asked by ATC if I thought I was still on LEEHY4.  i just acted innocent, but I was about five miles off track and they had to vector me to the runway.

 

TFDi 717 FMC.jpg

Share this post


Link to post
Share on other sites

It seems you've caught two things here - the first one may not actually be a bug. The 15999 is a prediction (this MCDU shows where it thinks you'll be the same way it shows AT restrictions). How far from PCKNS is FOOOT - if it's very close, it may think you're holding or beginning a descent slowly. The second issue, however, where it loses its place when an arrival is changed, however, is a good catch. I will correct this.

Share this post


Link to post
Share on other sites

Hello Collin,

PCKNS is 6 miles from FOOOT.  I didn't think that the numbers were a big deal. 

So the +16000 is the restriction, but because the other doesn't have a + or -, it is a prediction?

You have done simply amazing with this 717. I have wanted a 717 for so long and never expected one that is at this level of high realism. It is simply beautiful and a pleasure to fly.

I'm so glad if I can find something that would make it even better.  Changing runways from the one you expect is something that ATC is very good at doing.  I like to fly with real ATC on Pilotedge and sometimes it can be nerve racking. Especially if the aircraft does something that you don't expect and ATC is asking "What are you doing?" (which has happened to me more than once). ^_^

Thank you for responding,

 

Bob

 

Share this post


Link to post
Share on other sites

Not a problem! The tricky thing with the altitude display is that some restrictions that are not ABOVE or BELOW will display the same way as a prediction. If you click the right level select key associated with it, the VERT REV page will show it as an AT restriction if it is. If no restriction is shown, it's a prediction.

I'm really glad to hear you're enjoying it and I'm looking forward to making it more dependable, especially online.

  • Like 2

Share this post


Link to post
Share on other sites
1 hour ago, turbofandude said:

Not a problem! The tricky thing with the altitude display is that some restrictions that are not ABOVE or BELOW will display the same way as a prediction. If you click the right level select key associated with it, the VERT REV page will show it as an AT restriction if it is. If no restriction is shown, it's a prediction.

I'm really glad to hear you're enjoying it and I'm looking forward to making it more dependable, especially online.

Thank you Collin. That is good information. I will be looking for that.

I will let you know if I see anything else suspicious too. 

 

Bob

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