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

Company Route Format

Recommended Posts

Please Note that flight plans generated (for free) at SimBrief can now be exported for the TFDiDesign 717 (and they work).

Great to see that they've acknowledged this fantastic model.

  • Like 1

Share this post

Link to post
Share on other sites

You couldn't tell me exactly how you got the Company Route into the MCDU via SimBrief.

I created the flightplan in SimBrief, and i believe this flightplan needs to be placed into a folder within

the aircraft folder under documents/company routes.

If this is the case this folder didn't exist, i had to create the documents/company routes folder.

Anyhow within the MCDU itself, i typed the name of the flightplan and clicked the LSK next to the company routes, yet nothing appeared.

Am i way off here?

Any help would be appreciated.




Share this post

Link to post
Share on other sites

@vhufo If you're using the Community Opt-in Beta, it's under Documents\TFDi Design\717\Company Routes\, if not, it's in SimObjects\Airplanes\TFDi_Design_717\ (there should be a Company Routes folder in there - I can't remember if it's under Documents\Company Routes or just Company Routes in the aircraft folder). 

Share this post

Link to post
Share on other sites

Is it by any chance you guys can send it to PFPX so we can export our CO RTE from PFPX to the B717? 

Such as PMDG, WILCO and so on?

Our make a small export tool connected to the newest airac?

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