[LNAV Issues?]

Pretty simple (except in this instance).  Go to the Legs page, click on the LSK next to the active leg, which puts it into the scratchpad, click the same LSK again and activate LNAV.  However, this works best if you are more  or less headed towards that waypoint.  Works fine in everything with an FMS that I have ever flown.  

 

Hope you get things working to your satisfaction right away.  

 

[LNAV Issues?]

Joe, 

 

I used both techniques to test the direct-to (both when it was working for me, and when it was not).  But most of the aircraft (PMDG-777, -737, QW 787, FeelThere E-175 and a few others) work just fine without having to shift over to the direct-to page, so normally I monitor the legs page and use it for direct-to.  

 

Thanks again for the input.  

 

[LNAV Issues?]

Well, I tried out the CRJ again today.  First I was off-line, and everything worked just fine.  Same software versions in MSFS and the CRJ as mentioned at the start of this thread.  So, I restarted MSFS and flew the flight again--on VATSIM.  I happened that the wind favored 34L so as instructed by ATC I took off, flew runway heading, and at about 5000 feet I got one vector, then direct to FUSCO.  I flew an RNAV approach at KCRP, which required closing a discontinuity and then commanding another direct-to (to the IAF for the approach); no problems here.  

 

I took plenty of screenshots during the first flight in order to better illustrate my "problem".  However, in both flights the CRJ's FMS performed flawlessly.  After landing in KCRP I updated the AIRAC date to the current cycle, departed KCRP, and again the CRJ is performing flawlessly.  So while I do not know what was going on, it seems to have resolved itself.  

 

I DO appreciate the responses.  

[LNAV Issues?]

I almost always remember to enter the departure runway, even if there is no SID in my plan.  So why did I copy waypoint 1 and re-insert it to make it active--it is because if the plane is not on the path already in your FMS (and as depicted on the your map display), that is how you intiate a direct-to order--re-insert, activate, and engage LNAV.  Remember, at the point I did this my plane was well off the planned route as depicted on my map display because weather favored taking off on the runway pointed away from the first waypoint.  I used the HDG mode to turn towards the first waypoint, then tried to execute a direct-to in order to rejoin my planned route of flight.  

 

Later today I will do another flight in the CRJ and capture some screenshots that, hopefully, allow me to illustrate what I am seeing.  

 

[LNAV Issues?]

Try this--put your CRJ at any airport.  Load the FMS with waypoint1, waypoint2, etc.  and a destination.  Take off, but in heading mode; preferably not heading direct to waypoint1 (perhaps the waypoint is east of the field, and you take off to the west).  Use the heading mode to control the flight, and when you get the CRJ pointed toward waypoint1 (but not on the route line on the map), got to the legs page, put waypoint1 in scratchpad and try to re-enter it as the active waypoint.  I get "NOT ALLOWED", and it pretty much locks me out of using that FMS.  Look at the progress page, the MFD and the HSI--they are probably showing the heading and distance to waypoint2 even though the active (magenta) entry on the progress page is waypoint1 (as it should be).  

 

Sorry, this is from memory.  I will shift back to the CRJ in a few days and provide screenshots.  

 

[LNAV Issues?]

Well, thanks for the reply.  However, the LNAV feature is absolutely NOT working as it should.  As I write this I am flying on another compter using a different sim, so can't send you any screen shots.  When I was attempting do describe this issue, I knew it was complex and I was not describing it adequately.  However, I cannot imagine that I am the only one seeing this problem.  I'll keep watching this forum, and if nobody else chimes in I'll do another flight and take some screenshots.  Again, thanks for the effort you put into your reply.  

 

[LNAV Issues?]

I am using v. 1.0.18 on MSFS 1.26.5.0.  In the past few days I have flown a couple of non-SID departures and been unable to command a direct-to to the first waypoint on my plan.  As an example, on a flight from KMAF to KCRP, my plan was FUSCO J15 JCT J2 SAT J25 CRP.  I took off and flew runway heading to about 1000 ft, then used the heading mode to turn the aircraft toward FUSCO.  I then went to the legs page, clicked on FUSCO to put it in the scratchpad, then tried to re-enter it as my next leg.  This gave me a "NOT ALLOWED" message that I was unable to clear.  

 

I also noticed that the MFD was showing the distance to JCT, which was the second waypoint in the FMS.  And the HSI in the PFD was showing the course to JCT, not FUSCO. 

 

I have several hundred hours on this aircraft (using MSFS), and have not had this problem before.  I discovered that if I use the HDG mode to fly to my first waypoint, and get the aircraft aligned on the path to the second waypoint (as depicted in the HSI), the CRJ will fly the rest of the route with no problems.  But with the direct-to function now broken, this aircraft is of limited use, especially when flying on VATSIM with ATC.  Also, this has only been going on for a few days; perhaps as long as a week.  I mentioned the versions above, which is what is on my computer now.  I really cannot say if a MSFS or CRJ update was when I started noticing this problem, and I usually don't worry about what I have installed until I am trying to describe a problem.  

 

I hope this helps someone on you development team.