iFly 737NG

Nicholas Cavacini · « **Reply #15 on:** June 21, 2011, 07:34:03 AM »

I Know what your saying but it tells me it is complete and shows no other links. What is weird is I have had no problems with other Boeing aircraft.

Michael Freudeman · « **Reply #16 on:** June 21, 2011, 09:36:06 AM »

You need to have a point on the airport for it to know what the end of descent is. In your preflight or during cruise, select any arrival runway (not approach) from the DEP/ARR page then cross check the restrictions of the STAR with the chart and it should calculate ToD fine. Just remember to choose the correct runway or approach when you actually know what you'll be using. I also like to slow the descent speed to 280-300 M.78 or so since the VNAV has a really tough time keeping the speed down as it doesn't seem to calculate the descent path too accurately. Can't wait for the NGX

Nate Coffield · « **Reply #17 on:** June 21, 2011, 09:36:28 AM »

Quote from: Kyle Rodgers

Does anyone know why the FMC won't calculate T/D?? I'm serious, nothing else is wrong, it just doesn't calculate descents. It only calculated the desc maybe once.

I have had this same problem.....the only solution was to make sure you insert an arrival runway before you depart. Once the arrival runway is in and any discontinuities are removed it will calculate the TD. However, i have ran into issues if ATC give me a crossing restriction that is not planned. It seems like the FMC does not know how to handle it and will not descend. The FMC looks just like it should...but it will not descend. I then have to switch to V/S mode and put the plane in a dive to get back where I need to be. Sometimes the PATH descent mode will work but that seems to be hit and miss.

I can't imagine that this would be a programming error on IFLY's side...so I feel i am missing something....but I have never had this problem with the PMDG....you never had to input an arrival runway until you wanted. And you could set as many crossing restrictions as you needed and the plane would follow.

Maybe someone else has had this same issue and can help out.

Nicholas Cavacini · « **Reply #18 on:** June 21, 2011, 01:46:17 PM »

Thanks, seems to have worked for now. It is not an error on our part but almost certain it is an error on iFly's part.

Michael Freudeman · « **Reply #19 on:** June 22, 2011, 09:57:38 AM »

Quote from: Nicholas Cavacini

Thanks, seems to have worked for now. It is not an error on our part but almost certain it is an error on iFly's part.

There is also an issue with the RNAV SID/STAR route selection. On some of them, it doesn't select the route for the runway selected. The ILS frequency auto-tune sometimes doesn't change the course and frequency to the correct ones or changes it away from the auto selected ones. The vertical path doesn't calculate correctly and will descend either too soon or too late causing you to level out for a bit or descend at 5000ft/min. Really bad VC frame rates, especially with the EFIS/Map (Southwest style) option. I've had problems with the auto-brakes not engaging between 80-100 kts RTO. RNP approaches are impossible as VNAV doesn't follow the vertical path, it keeps descending, into buildings and radio towers (try the RNAV Y RWY29 into KEWR). It has on occasion blown through the MCP altitude using FLCH and kept descending, although I believe this to be partly an issue with FSX since it has happened to me once before (however it has happened twice on the iFly so far). You get GPWS warnings on short final while on the GS of the selected runway. That's enough nitpicking for now

Nicholas Cavacini · « **Reply #20 on:** June 22, 2011, 11:56:44 AM »

XD Yea it works for now but I'm more hopeful for the NGX. PMDG usually irons most the bugs out before release. What I like about the iFly is that it includes 600,700,800,900 and the BBJ. The HUD is also a nice feature in the BBJ though they forgot it in options for the others. I've been on an 800 or 900 and it had a HUD in it.

Michael Freudeman · « **Reply #21 on:** June 22, 2011, 12:25:57 PM »

Quote from: Nicholas Cavacini

XD Yea it works for now but I'm more hopeful for the NGX. PMDG usually irons most the bugs out before release. What I like about the iFly is that it includes 600,700,800,900 and the BBJ. The HUD is also a nice feature in the BBJ though they forgot it in options for the others. I've been on an 800 or 900 and it had a HUD in it.

It it would be nice if they had included the HUD on the commercial variations but, the iFly HUD is rather useless since it isn't focused in front of the plane,it is plastered on a flat surface in font of your face. This makes the FPV, among other spacial oriented elements of the HUD useless and only good for displaying airspeed and heading information. I find it more of an annoyance than a helpful tool since you can't click through it either.

Nicholas Cavacini · « **Reply #22 on:** June 22, 2011, 02:30:59 PM »

That is true.

Stephan Faessler · « **Reply #23 on:** August 03, 2011, 11:33:51 AM »

iFly is okay but has some issues, PMDG will be better and on sales tomorrow I hope ;-) cheers