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

After finishing the SID the 717 likes to turn in circles


I have just bought the 717, because there isn't many aircraft working in V4, anyway I've set it all up as far as I know put in my flight plan chosen the SID etc, there were no DISCO that I noticed, I was flying out of TNCM at the end of the SID it went a bit funny because it just started turning back to the first waypoint which is the start of the sid, I tried DIR To between the end of the sid and the next WP of LARPP with the airway b520 but it wouldn't do it it just keeps turning, What am i doing wrong, there are 3 waypoints after the end of the Sid with the same airway so when I put in airway b520 to larpp it doesn't work either does b520 to b520:/


N0441F320 BOPAT2 JUICE B520 STT DCT UTAHS R507 SAPPO/M075F320 R507

          MRTEE/M075F340 R507 GTK Y587 DONEZ A555 ZQA FOWEE8


I think the SID was Bopat2, The plan was made by pfpx but i typed it in manually.

Share this post

Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Please submit this to the Autoflight section of the Bugs and Suggestions system - it will ask you for some specifics we can use to recreate and solve this. Thank you for letting us know!

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