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

Flight plan deleting.

Recommended Posts

I had problem several times earlier this week. 
Good import of flight plan from SIMBRIEF. EGPH to EGBB. 
Added SID TLA6C no problem. 
Added STAR C4C. 
All of plan deleted before STAR. 

Dean

Edited by Dean33

Share this post


Link to post
Share on other sites
Posted (edited)

Same issue: after selecting and inserting STAR, everything except this STAR is deleted from the flight plan. I'm using the latest beta.

My route: ENBR (RWY 17) TUXI3C TUXIL P603 ZOL AMSEV L621 AAL P622 TOMGU (RWY 27 via ODNEV, tried both ILS Z and ILS Y) EKBI

EDIT: I'm aware that there is no actual STARs in EKBI. It seems that FMC cannot connect my last waypoint (TOMGU) with IAF (ODNEV).

Edited by dimkzr
correction

Share this post


Link to post
Share on other sites

This happened to me also.
Usually I don't set the arrival procedure before the flight when atc is online, I only put the altitude restriction of the first star wpt in order to have a correct tod.
Sometimes atc gives me the current star after i reached the tod and there when I enter the star all the flightplan disapears.

Share this post


Link to post
Share on other sites

I'm trying to get my aircraft to do it so I can debug, however, I'm not having this issue (though I'm not denying that it is happening). What are you experiencing this? (Ground, in flight, etc.?)

Share this post


Link to post
Share on other sites

Happened once again before ENBR-ENBO flight.

Aligned IRS, finished with F-PLN INIT and WEIGHT INIT pages.

Entered flight plan (INTUM STM) - OK

Selected SID (INTU2D, rwy 35) - OK

Selected STAR (STM6D via ADREL, ILS 25) - and boom, everything except STAR is gone:

5a5160c123a69_Screenshot-07_01.20182_50_20.png.fec435791668323ac53b0b02ae7ec38c.png

P3Dv4.1, 1.0.9.19, AIRAC1801

I've tried to fly this bird three times since my purchase. First time it was this STAR problem. Second time FMC decided to insert TOD in the middle of a STAR. And now this STAR issue again. I want to fly it so badly, but it simply won't let me :D

Share this post


Link to post
Share on other sites
Posted (edited)

It seems that this is happening when you are not entering Cost Index. Tried without CI: FP deleted. Tried with CI: no problems. Recorded both attempts:

 

Edited by dimkzr

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