FMC progress page not showing data

[Capt.Stanford]

Hello all

Recently purchased the IXEG 737 classic since I'm a real life pilot (PPL, working towards my ATP) and because of this I'm a massive hardcore systems simmer. I do checklists according to the real FCOM & the 737 by IXEG is my PMDG for me for X-Plane.

Now the IXEG 737 isn't perfect (nothing ever really is) the FMC does not have full functionality and I can live with that for now, hoping IXEG will release an update in the future which I believe they will after reading previous threads.

The problem I have now is that I program the FMC according to real world procedures, inserting the coroute & completing the PERF INIT & TAKEOFF page, however it shows the LEGS on the PROGRESS PAGE but does not show the destination AIRPORT & the fuel remaining. I followed procedures from the FCOM & memory and I haven't had this issue with other aircraft either in X-Plane or P3D.

Now I know the FMC is not complete (hopefully, Yet) but there must be something I missed? I don't have much experience with the 737 classic especially in X-Plane so can anyone recommend any ideas?

[mmerelles]

PROGress page is WIP not ready yet.

 

 

[Capt.Stanford]

Hmmm I know it is still a WIP but I forgot to mention in the previous post that I was able to get it to work by adding the STAR to the route during preflight, tried it again and it still didn't work.

I want to know if other people have the same issue & if they did how they fixed it.

[Capt.Stanford]

Ok I managed to pull it off again, what I did was insert the departure runway, then the route itself, then before activating & executing I inserted the STAR & an arrival runway, the end result is the progress page displayed the destination. I'm not sure if you need to enter the STAR before route activation to get the DEST airport showing but it seems to work for me.

Hopefully waiting for the news of a V1.3 release that will complete the FMC soon she really is a fine bird it's just the FMC that kills me.

 

[Luiz Giorgi]

On 3/1/2018 at 12:09 AM, Capt.Stanford said:

Ok I managed to pull it off again, what I did was insert the departure runway, then the route itself, then before activating & executing I inserted the STAR & an arrival runway, the end result is the progress page displayed the destination. I'm not sure if you need to enter the STAR before route activation to get the DEST airport showing but it seems to work for me.

Hopefully waiting for the news of a V1.3 release that will complete the FMC soon she really is a fine bird it's just the FMC that kills me.

 

Hello! I'm new to ixeg aircraft and the question I have about prog is the ETA to waypoints and destination. It seems that the ETA to your destination is incorrect due to your ETA to TOD (more than 1 hour between tod and destination). The same happens here. Is that a way to check the correct estimated times in our navigation? 

Thank you

 

Best regards

[Litjan]

Hi Luiz,

Yes, the PROG page is not working correctly. We try to be upfront as much as possible about things that are not done (yet) and posted them in this thread, so that prospective buyers can form a picture about the state of the aircraft before making the purchase:

https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/

While modern pilots (and especially layman simulator users)  do rely heavily on the FMS to do the necessary aviation calculations for them, it IS entirely possible to do all of them in a conventional way.

If you want to know your ETA at a certain point, just use the formula velocity = distance / time. Solve for time: time = distance/velocity. Insert distance (NM) and average groundspeed (KTS) and you will get the time in hours. Multiply by 60 and you get the estimated time enroute in minutes. Add those to your current time and you have the ETA.

Cheers, Jan

 

[AngelOfAttack]

On 8/4/2024 at 1:57 PM, Litjan said:

If you want to know your ETA at a certain point, just use the formula velocity = distance / time. Solve for time: time = distance/velocity. Insert distance (NM) and average groundspeed (KTS) and you will get the time in hours. Multiply by 60 and you get the estimated time enroute in minutes. Add those to your current time and you have the ETA.

 

Nah, at least we have Fuel and Time table in PI