Jump to content

Davidb777

Members
  • Content Count

    23
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. Glad it worked for you. I found out by finally trying to eliminate the variables I thought were creating the problem, since I had spent so many hours trying to find out in the Internet if anyone had similar issues, but to no avail. Since these files were created for FS2004, but are reported to work for FSX (you can find many posts relating to this, and they do "work"), my first trial was to eliminate the possibility that some part of the original code for FS2004 was not transferring well in Lesson 4 to FSX. I've read so much about the VNAV function, that I knew something was not right in my tutorial flight - it's supposed to do things in a certain way. So, decided to fly an original flight from scratch, and doing everything myself instead of using the tutorial files. Gladly, that did it! I imagine the first lessons, because they are "easy" in terms of what you are doing (and not using the autopilot), work perfectly, but as you progress into Lesson 4 and VNAV, which is a mathematical intensive application, something does not write well into FSX, hence the faulty VNAV.David
  2. The problem is the "old" files of the tutorial, which were written for FS2004, but work for FSX. Somehow, the VNAV function acts quirky with FSX (at least in my setup.) I did a flight created from scratch (up to FL250 only) from KMIA to KDFW, and VNAV works perfect. I get all the modes working flawlessly, so no need for anyone to try the tutorials as I asked in my previous post - thanks if you did anyway. In case anyone out there is doing the tutorials by step like I did and using FSX, this might help you if you encounter any issues like mine.ThanksDavid
  3. Yes. An example of the modes I get - a flight to FL340 with a "hold" initial altitude of 5000 set on the MCP alt window (not a hard altitude restriction, so no restrictions set on the FMC): just after takeoff, when LNAV and VNAV go active= THR REF | LNAV | VNAV SPD at about 1000 feet to go before reaching 5000, modes change to = SPD | LNAV | ALT (this doesn't look right, I should get VNAV ALT based on the tutorial) to go to say 18,000 given by ATC (as an example), I use FL CH (hitting the alt selector button and then VNAV will not work in my case as previously explained) and set 12,000 (arbitrary) on the alt window - plane changes to = THR | LNAV | FLCH SPD then I set 18000 on the alt window, hit on the alt selector button, then press VNAV, and voila, modes change to = THR REF | LNAV | VNAV SPD Because VNAV disengages before reaching 5000, and because I get modes SPD | LNAV | ALT at 5000, hitting on the alt selector knob and then VNAV will not activate VNAV (it's not engaged to begin with.) I should never have lost the VNAV mode; holding at 5000, I should get VNAV ALT and then I would be able to execute the selector knob to continue climbing under THR REF | LNAV | VNAV SPD When reaching FL340, VNAV changes to THR REF | LNAV | VNAV PTH, which is the correct mode What is not working is that I don't get a THR REF | LNAV | VNAV ALT at 5000 or any other hold altitudes I set in the alt window, as it's explained in the tutorials. Something is quirky with the VNAV function, in my opinion, at least with these tutorial files. If it's not too much to ask, can you or someone else try this tutorial (Lesson 4, Part 1 or 2) and see if you get the VNAV ALT modes at any point during the intermediate holds? It'll take 5 minutes at most, if you have the files ready to go. What I'll do as well is a totally different flight, made from scratch using FSX flight planner, and see if the modes behave the same (or different) and report back. If they act the same as I've been experiencing, then I'll know that the tutorial files that I copied are not the culprit.Thank you for your continuing support to get to the bottom of this.David Bolanos
  4. Thank you for trying to help me with this. Confirmed, it's set at FL210. Confirmed - when I press the ALT Selector Knob, the altitude restriction on the legs page and VNAV page of the FMC is cleared.I tried this flight again confirming the above, and same thing happens. I get no VNAV ALT mode at intermediate set altitudes. I did find the following:I'm established initially at 3000 (first altitude restriction) under VNAV PTH (correct), and upon passing it, VNAV SPD engages and takes me up to the new MCP ALT of 6000 (altitude restrictions have been cleared both on legs and VNAV pages on FMC.) Again, at 4000 feet, VNAV disengages, and SPD and ALT modes engage all the way up to 6000. So I have in the Autopilot Mode Anunciation in the PFD, modes: SPD, LNAV, and ALT, and the alt HOLD is lit. Once level at 6000, and going up to say 15,000, at least I've found a way to engage VNAV, as I was not successful before, until sometimes passing 10,000. I still can't get it to work by setting the new altitude in the MCP alt window, pressing the alt selector button, and clicking on VNAV. But, if I enter an arbitrary number below 15000 and higher than 6000, hit the ALT Selector Knob, use FL CH, and commence the pitch, and then change the altitude to its correct altitude of 15000, pressing the alt selector knob, and then pressing VNAV, it engages! Tried this several times at different mid level altitudes (below and above 10000), and it always worked. So, at this moment, I can't get VNAV to correctly display a VNAV ALT mode when holding at intermediate altitudes set in the MCP altitude window. I tried another flight, from KPHX to KLAX (also part of the tutorial), FL340, confirming the FMC (VNAV and perf pages) was properly setup, and that has an initial altitude "hold" at 7000 per the departure procedure, and same thing happens just before reaching 7000. VNAV disengages, and SPD and ALT modes engage. I then need to use FL CH, and do the short work around to engage back again VNAV to take me to FL340. In the end, I've found a way around it and if that's the way I need to fly this bird, then I'll live with it, but I'm still trying to figure out if this is: 1) a bug, or 2) something I still don't understand about the way VNAV specifically behaves on this plane, or 3) just something that is haywire on my install of the 747.Thanks.David Bolanos
  5. Hi there. I've been doing the tutorials for the 747-400X, and have reached tutorial 4 (Lesson 4, Part 2) - I'm having what I think is a problem or erratic behavior of the VNAV function while climbing. As a refresher, this lesson is to takeoff using the autopilot and autothrottle, reach several mid level altitudes (3000, 6000, and 18000), before reaching a cruise of FL210. First things first, before doing the tutorials, I read the PDF manuals that came with the DVD I purchased. I've had this plane for about a month. I have also searched this forum for the problem that I'm having, found a couple of entries relating to it, tried several of the methods found, but I'm still getting the issue.Now, onto the problem. The flight is a preloaded flight found in the tutorials I downloaded. I preload Lesson 4, Part 2, and the plane is already lined up with VNAV armed, ready to go. The altitude in the MCP is initially at 3000, but as instructed in one section of the lesson, I change it to 6000. There are two altitude restrictions in the FMC, both set at 3000 for two made up fixes - one at 5 miles from the airport, and the other at 15 miles. The lesson teaches the reader how VNAV works. What's supposed to happen is that VNAV will take me up to 3000 under VNAV SPD, reach 3000 (the first altitude restriction in the FMC) with VNAV PTH, and upon terminating the 3000 altitude restriction, VNAV SPD engages again to take me up to 6000 (which is set at the MCP), at which point VNAV ALT should engage. Then onto 18000 again with VNAV SPD, and finally reach FL210.When departing 3000 to 6000 (and ending the alt restriction), VNAV automatically pitches the plane up and changes correctly to VNAV SPD, but when reaching about 4000, the VNAV light disengages and the SPD and ALT modes are seen engage on the display (PFD.) The plane levels at 6000 and the ALT HOLD light turns on. VNAV is still "off", i.e., VNAV ALT is not engaged, as is depicted and explained in the instructions of the tutorial of what should happen. When leaving 6000 up to 18000 (changed in the ALT MCP), I press on the ALT MCP button, and hit VNAV, but nothing happens. I tried using the VS to 1000, and then hitting VNAV twice, but nothing happens (this was explained in a posting I read.) I used FL CH, which works perfectly, and then tried to change to VNAV while clicking it twice (sometimes more), but it doesn't change modes. It always stays at FL CH.The curious thing is that when reaching 10,000, the transition altitude, the airplane accelerates to the FMC speed of 323, but the mode is still at FL CH, not at VNAV. I was able to sometimes re-engage VNAV after passing this altitude of 10000 (after clicking VNAV several times), but it was not consistent. At 1000 feet from 18000, instead of VNAV changing to VNAV ALT, it again disengages, and the SPD and ALT modes are engaged. From 18000 to FL210 (after pressing the ALT HOLD button), I need to always use FL CH to initiate the climb, then I press VNAV and it finally engages and works as expected. It seems that at the initial alt restriction, VNAV operates as expected, and also works fine on the last altitude leg to FL210, but the intermediate levels is where the VNAV function acts differently (compared to how it's explained in the tutorial.)I have flown the specific scenario about 10 times, and I can repeat what I have explained above. In reading the tutorial, it doesn't mention anything about the SPD and ALT modes, and from what I understand, I should get a VNAV ALT when reaching the intermediate altitude holds. In other words, it should always use one of the VNAV modes, either PTH, SPD, or ALT. Maybe I'm going about this the wrong way or not understanding how VNAV really works, and sure would appreciate any feedback on this matter to manage the VNAV function correctly. I know the post was long, but needed to be specific. Here are my computer specs:FSX SP2, Windows XP Home SP3 32 bit, 4 gigs Ram, Geforce 9800 GTX+ 512 MB, several airplane addons, payware FSUIPC, ASX + XGraphics, GEX, RC4FSX is on its own dedicated hard-drive.Thank you,David Bolanos
×
×
  • Create New...