Jump to content

LNAV Behaviour, obvious cause ?!


Recommended Posts

vor 37 Minuten, DGH sagte:

Any news when this will be fixed ? Happening since release in March and still happening. 

My guess, if ever, after SU6 .....

Oliver

Link to comment
Share on other sites

  • 3 weeks later...

and to continue ...

Arrival at LRSV via ILS 34, TOMUC Transition, the ND is showing a left turn intercept (wrong) while there should be a right turn at LIVNU.

 

The aircraft followed the arc nicely before it started turning the wrong way inbound LIVNU. Pilots intervention , back to the ILS inbound -> safe landing.

NAVIGRAPH (CRJ and MSFS, latest revision (2)

Oliver

Please login to display this image.

Link to comment
Share on other sites

Jup …

 

departure EHAM 27 … KUDA2P … NAV on … but overflying the first nav point after takeoff … NAV off/on  solves 

 

same wobbling after SU6 as before ( since day 1 in March ) … sharper turns at cruise … overcorrecting 

arrival LEBB (think it was  DOSUL) … not following the arc at all
 

departure from LEBB from rnw 30 this morning …. No arc following and turning left instead of right ( MAPA3A )

 

Waiting for an update that finally solves these issues for a while now …. Despite i thing the issue is known for a while And even explained … so not sure why the wait on the wobble fix (for example).

Link to comment
Share on other sites

I'm not sure if this is the same LNAV issue, but I'm still seeing the constant waving back and forth on some of my flights. This was supposedly fixed in one of the previous CRJ patches but that is not the case, although it's at least not as common. You can ignore the TURB button at the beginning -- I had tried activating that to see if it made any difference but it did not. 

 

 

 

 

Link to comment
Share on other sites

  • 3 weeks later...
vor 11 Stunden , DGH sagte:

A picture says more then 1000 words

 

 

Please login to display this image.

 

 

Looks like you are flying the RENO airrace ....
 

If this isn't fixed soon, this will be my last plane i buy from AS or made by AS. 100%. Whatever it is !!


 

Oliver

Link to comment
Share on other sites

5 hours ago, JetNoise said:

 

 

Looks like you are flying the RENO airrace ....
 

If this isn't fixed soon, this will be my last plane i buy from AS or made by AS. 100%. Whatever it is !!


 

Oliver

 

Wont get fixed. 

Link to comment
Share on other sites

  • 4 weeks later...
  • 3 weeks later...

Great that the twin otter is almost ready but how about the issue that people have for 10 months ??

 

see below EHAM-EGPH and the return flight. Wobble wobble … still overshooting 

 

 

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

I'll try my usual test route when I have a spare hour, the aircraft seems to follow the route better than a few months back ( or the -900 is just better behaved, thinking about it ). I'll have to try and work out how to hide my historic trails from LNM though.

 

BTW you can File->save map as image ( or copy map image to clipboard ) and it'll save a copy of what you're looking at, will save you taking a photo of the screen :)

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Thanks for the tip 👍

 

made the email on my iphone though so the picture is faster for me. But did not know what you suggested so thanks for the tip ! 

 

i am only flying 700. Will not ever buy another Aerosoft product before this issue is solved.
 

10 months … 

Link to comment
Share on other sites

Seems to me, the FD will consistently command a turn starting at 2X the distance required.  If it were to hold course until the waypoint is half as far as it is now, the constant-bank turn would fit the angle nicely and the aircraft wouldn't wobble chasing back onto track afterwards.

 

Look at the pictures above, and this tendency to double the turn start distance becomes clear - Imagine those same turns starting at half the distance to the waypoint than they do.  If they started there, the other side of the arc would be tangent to the next leg.

 

Some simple analytical geometry to illustrate:

 

Please login to display this image.

 

The blue and red circles are identical, note their tangents against the waypoint legs and how the blue one matches up properly.

 

Remember, the CRJ can only turn at a fixed bank angle, so it is this timing of where to start the turn that determines how it'll converge upon the next leg. As the bank angle is constant, then so is the turn radius (as long as airspeed stays constant) - The initial point for the turn is then given by the solution presented here:

 

https://stackoverflow.com/questions/51223685/create-circle-tangent-to-two-lines-with-radius-r-geometry

 

 

May we have this fixed soon?

  • Thanks 1
  • Upvote 1
Link to comment
Share on other sites

EGPF/23LUSI1A LUSIV L612 ELBUS UL612 CROFT UP16 NOKIN N862 IPZOL DCT EX

Hold at EX

EGTE ILS26 via EX1

Please login to display this image.

CRJ-900, current AIRAC data from Navigraph. Used NAV a bit more than I would usually, to see what happens. It's not the ideal route for the approach but it's the one I took today.

 

Put the AP in at 1300ft or so, before XETUN, climbing FL130 as asked to at 250kts

Please login to display this image.

I thought it was going to end up pointing the correct way there, but then it suddenly swung left.

 

Once it'd got on course again it tracked pretty well until here -

Please login to display this image.

 

and got a bit out of sorts for the next couple of WPs

Please login to display this image.

 

After that, tracked right down the line, until the hold at EX. Oh boy. Here's the approach chart for ILS/26 at EGTE -

Please login to display this image.

 

Aaand... here's what happened.

Please login to display this image.

 

I saw this wasn't going well on the outbound leg of whatever the a/c was flying & immediately armed the exit - it had EX programmed in again but almost immediately skipped that & tried to find the next WP in the approach. I hit APP pretty much as soon as it was in the ILS lobes & it almost immediately settled down laterally. What that doesn't show is the continual fight to keep the airspeed & alt in check, and the way the trim was running. I'm wondering if the trim issue isn't inadvertantly causing some course holding issues too just by the aircraft not doing what it's predicted to do.

 

--

 

Edit - 2nd flight, had the same wobble ( almost exactly the same, actually ) between CROFT & ROBVA, but this was the hold & procedural approach...

 

Please login to display this image.

 

... is it a cow maybe? I bemusedly left it doing whatever it was doing for a while. The missed approach wasn't too bad, at least - other than it just pointing the nose up when I put the alt hold back in ( despite being at the set alt already ).

  • Thanks 1
  • Upvote 1
Link to comment
Share on other sites

Caveat: noticed the WT G1000NX marketplace version still installed, will have a go without it when I can.

 

Edit 2: uninstalled WT G1000NXI from marketplace, no difference in behavior - I have no other complicated aircraft from the marketplace at all, only the Asobo stuff & the Spitfire. Flaps 8, flaps 20 no difference in behaviour. Wind is 277/5 so practically no crosswind in the hold. Outbound leg ( the one it makes a good attempt at ) seems to be a heading of about 300 .

 

Thought the hold behaviour might throw an obvious light on more subtle issues, so I set a route up just to test holding, and set the whole thing up to succeed as best I could. CRJ-900, 0 passengers, 0 cargo, 2480kg fuel. AIRAC from Navigraph up to date, installed with their FMS data thingy.

 

EGDY/26 DCT IPZOL DCT ATWEL DCT TIVER ( I put the approach in to get EX & then put the hold in, so it duplicated EX anyway )
Hold EX NW/287 107/L 185kts 3500ft 1.0 min
EGTE ILS26 via EX1

 

The hold page radial is always the reciprocal of inbd crs ( or the other way rtound ), you can't decouple them when you're setting up a hold... this doesn't seem right? is inbd crs not the course to the fix before you enter the hold, rather than while you're in the hold, which would be a bit pointless to enter. Surely you're not expected to overfly the fix on a precise track to enter a hold & turn to the correct outbound radial. In this case the entry would nominally be 126/L, but if I put that in the outbound radial is completely wrong and I can't change it without changing the entry!. The AP doesn't want to enter at 126 anyway. I'm only querying this & not taking it as the inbound leg of the hold ( like it originally appeared to be ) because in the flight the a/c seems to be attempting to fly the reciprocal of the course into the hold rather than what's set in the FMS.

 

FMS is definitely set to show Magnetic, although the declination in this part of the world is about -0.6 anyway...

 

Please login to display this image.

Route in FMS shows the hold is in the right place & roughly right shape

Please login to display this image.

 

It cut the corner a bit much after ATWEL & missed TIVER by some way.

Please login to display this image.

 

and here we get into the hold. I pulled the HUD down & controlled the speed as if I was formation flying, so the marker never left the 185kts bug. One notch of flap. I had to hit active pause to answer the door & when I unpaused we were doing 220kts(!), hence one turn is a bit wider. Altitude had crept up to 3700ft by the exit. Red dot is about where I armed the exit - FMS jumped straight to D112D rather than overflying EX again. Held the 185kts bug ( I'm not going to claim I held the exact speed ) all the way to the ILS.

Please login to display this image.

Link to comment
Share on other sites

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use