This is the 2nd time I've experienced this situation. The first time in the original build. Now, it has happened again after upgrading SP1.The A/P is engaged and HDG mode allows you to guide the plane by setting the heading on the rotary knob. So far so good.Now, after (using the HDG knob) bringing the plane within LNAV capture range, the YELLOW part of the NAV button does not illuminate. When I push the NAV button, the button iluminates GREEN... BUT... the plane immediately makes a smooth turn to a North heading.The route is clearly defined on the EHSI... showing the next WPT and the markers for the next one thereafter and so on. The FMS/CDU behaves normally. As you approach a WPT, the distance correctly updates on the CDU.I am presently on a flight from Nancy, France back to Aberdeen-Dyce... online with Vatsim, FSPassengers and FSAcars, ASA, REX2. If I don't manually turn the HDG knob to follow the route line, I'd never get there via the LNAV/FMS.I made some FRAPS screen captures which I will upload after I get offline with this flight.This is a real 'buggy' situation.While on the list of personal bugs. I thought SP1 was supposed to address the SPOILER - not resetting - issue. Well, in SP1 - which I am now running - it still (every once in a while) doesn't reset. After shutting down the engines at the gate and stepping outside... there they are... sitting UP.I now expect the flood of wannabe developers to tell me to reinstall something... OR... something is wrong with my box... or... some other finger-pointing exercise.Just wait until I upload the photos... almighty gurus... you will see.Cheers,Keith Rocke

This is the 2nd time I've experienced this situation. The first time in the original build. Now, it has happened again after upgrading SP1.The A/P is engaged and HDG mode allows you to guide the plane by setting the heading on the rotary knob. So far so good.Now, after (using the HDG knob) bringing the plane within LNAV capture range, the YELLOW part of the NAV button does not illuminate. When I push the NAV button, the button iluminates GREEN... BUT... the plane immediately makes a smooth turn to a North heading.The route is clearly defined on the EHSI... showing the next WPT and the markers for the next one thereafter and so on. The FMS/CDU behaves normally. As you approach a WPT, the distance correctly updates on the CDU.I am presently on a flight from Nancy, France back to Aberdeen-Dyce... online with Vatsim, FSPassengers and FSAcars, ASA, REX2. If I don't manually turn the HDG knob to follow the route line, I'd never get there via the LNAV/FMS.I made some FRAPS screen captures which I will upload after I get offline with this flight.This is a real 'buggy' situation.While on the list of personal bugs. I thought SP1 was supposed to address the SPOILER - not resetting - issue. Well, in SP1 - which I am now running - it still (every once in a while) doesn't reset. After shutting down the engines at the gate and stepping outside... there they are... sitting UP.I now expect the flood of wannabe developers to tell me to reinstall something... OR... something is wrong with my box... or... some other finger-pointing exercise.Just wait until I upload the photos... almighty gurus... you will see.Cheers,Keith Rocke

Alright,I landed at Aberdeen-Dyce after (basically) manually directing the JS41 from Nancy-Essey in France. Here is the vataware flight info... http://vataware.com/flight.cfm?id=4401120. Disregard the fact that the original company-provided route was incorrect.Here are the screen caps I made to shot LNAV not working on this flight.============================================Climb using VS. LNAV button lit. 4.8nm to GOPAS intxhttp://www.keithrocke.com/j41/lnav-01.jpg============================================ Using HDG wheel to intercept the route http://www.keithrocke.com/j41/lnav-02.jpg============================================ Notice. A/P is engaged. Soft Ride is also engaged. YAW control is OFF http://www.keithrocke.com/j41/lnav-03.jpg============================================ The next five (5) shots - in sequence - will show how LNAV turns the plane to a North heading http://www.keithrocke.com/j41/lnav-05.jpg http:// www.keithrocke.com/j41/lnav-06.jpghttp://www.keithrocke.com/j41/lnav-07.jpg http:// www.keithrocke.com/j41/lnav-08.jpghttp:// www.keithrocke.com/j41/lnav-08.jpg====================================================Would someone from the Development team respond?ALSO NOTE:In all the shots above, you will notice that the spoilers ARE armed. Upon landing at Aberdeen-Dyce, they did NOT deploy.Thanks in advance,Keith

I've noticed his as well. I loaded default cessna, the loaded saved flight with cold and dark js41. took off and had exaclty the same problem. Then tried it differently. loaded cessna, shut it down, loaded js41, took off and LNAV was working fine. Any ideas what might be wrong? Greg Furmanski

Are you entering DIRECTO then your first fix? I've never seen LNAV capture till you enter that. Could not find any point where you said you did that. I'm talking about page 78 of the pilot tutorial.Chuck Biggins

Everything is done properly. The same flightplan, loaded in the same way, FMS set up correctly. LNAV armed and showing next waypoint correctly. There was one post about that problem before and someone suggested that the problem lie with saved flight situation and that reloading aircraft after loading a saved flight should help, but I didn't try that yet.Greg Furmanski

Yes but have you done what Chuck Biggins said? after climb out, flaps up etc FMS>Direct to> press enter then NAV.<< Thats a must.If you come out of FMS LNAV to use heading, the best why to go back to route is Direct to, as pressing NAV makes an intercept. I know this is not the point of your post but it looks like you forget to bring RPM back to 80. Also 143 @ 19,300ft is a very slow. Anyway GL with your problem.

Hi Keith, I don't want to seem like a wanabee developer or an almighty guru, but I can't quite overcome the urge to point a finger in the general direction of PEBKAC* with respect to your LNAV issue and using the Direct to feature of the FMS to arm the NAV mode. And that makes me suspect that your spoiler issue may also be resolved by RTFM, but I am not bothered enough to check. [PEBKAC - Problem encountered between Keyboard and chair]

Here are the screen caps I made to shot LNAV not working on this flight.

Looking at your screenshots gives a few clues that you're not doing some things correctly.First of all, you do not have the autopilot setup correctly. Engaging the AP also automatically engages the YD, yet your screenshots show the YD off. Don't turn the YD off.Second, Soft Ride artificially dampens the AP gains, and is only for use in turbulence. Turn the Soft Ride off.Third, the FMA is indicating an abnormal condition that seems to indicate improper operation of the vertical modes. Why are you in VS mode, with the rate set to "0"? Why aren't you climbing toward your preselected altitude? Finally, how did you end up so slow? It looks like you either didn't fly the profile, or you're too heavy (or it's too warm) to be that high.I hate to sound snippy, but if you're not utilizing the autopilot properly, then the LNAV issue is more than likely something you're doing wrong procedurally.Also, as mentioned earlier, after takeoff and after being vectored on course, you should pull up the Direct page, and execute a DTO the next waypoint in order to get the FMS sequenced properly. I've used LNAV without any difficulties since Beta 3 or thereabout, so this isn't a systemic problem. One thing I did note during beta testing was that if you're using the FSX default ATC and you open an IFR flightplan in-flight, or change your destination in-flight, the LNAV gives up the ghost and will randomly turn around and start heading back to the origin. The fix for this was to engage heading mode in order to avoid the turn, then DTO the FMS to the next waypoint and re-engage LNAV.

Keith,In addition to what Nick posted (spot on stuff), make sure that this problem isn't something that got saved into your initial J41 situation. I've had this happen pre-SP1, but not since. The fix, for me, was to load the situation, and then IMMEDIATELY reload the aircraft using the FSX RELOAD AIRCRAFT command. Then, save the situation again. You can save over top of the existing saved situation.I've not been able to isolate why this sometimes happens, but it seems to be related to the save flight function.

This problem has been driving me crazy. Has anyone come of with a better fix for it? Every time I load my saved flight this happens and I am tired of having to completely reload the aircraft and get all the switches to where they should be.

This problem has been driving me crazy. Has anyone come of with a better fix for it? Every time I load my saved flight this happens and I am tired of having to completely reload the aircraft and get all the switches to where they should be.

Which problem?

the turn north problem that this post is about...

the turn north problem that this post is about...

as mentioned earlier, after takeoff and after being vectored on course, you should pull up the Direct page, and execute a DTO the next waypoint in order to get the FMS sequenced properly...One thing I did note during beta testing was that if you're using the FSX default ATC and you open an IFR flightplan in-flight, or change your destination in-flight, the LNAV gives up the ghost and will randomly turn around and start heading back to the origin. The fix for this was to engage heading mode in order to avoid the turn, then DTO the FMS to the next waypoint and re-engage LNAV.

In addition to what Nick posted (spot on stuff), make sure that this problem isn't something that got saved into your initial J41 situation.

Yes I know about the DTO thing and that has nothing to do with the problem. I am not using default ATC or flight plans.Im sure it has to do with the saved flight because I can always fix the problem by creating a whole new flight from scratch every time, but I dont like to do this this mainly because there is no saved panel feature in the J41. When I fly FS, I fly from one airport to the next and so on. I do a flight, land, shut down, save it, then load the saved flight another day and continue with the next flight. Some people enjoy FS differently, but this is how I do it. I guess I was hoping that there was a way that I could save a flight and not have this occur. Clearly the, "situation" is being saved into my save flight but I am hoping to find out exactly what causes the, "situation," so that I dont have it happen every time.

Yes I know about the DTO thing and that has nothing to do with the problem. I am not using default ATC or flight plans.

I dont understand, if you are not using flight plans, then what are you asking the FMS to follow? And if you are not using the FMS, then what is it you think should happen when you press the NAV button?