1 hour ago, Noel said:

That's nice you're happy for me, but wouldn't it be more useful to be curious as to why I'm not having any issues (and many others I read), and you are?

I'd say we all have different definitions of "perfect route tracking". You might not notice problems that other people do, especially real world pilots. There's nothing wrong with it, just two different perspectives and therefore two different evaluations.

1 hour ago, Noel said:

That's nice you're happy for me, but wouldn't it be more useful to be curious as to why I'm not having any issues (and many others I read), and you are?

No, it's been sent to the recycle bin, far better aircraft to use now. I was just hopeful they had finally sorted the issues, but it seems on their admission they did not sort this issue.in this update          ( Despite acknowledging it months ago)

i haven't had any problems with the CRJ tracking in LNAV. every so often it might overshoot a turn, requiring a bank to correct back on course, but these are very small and don't happen all the time.

i recall in FSX and P3D, some addon aircraft would start having LNAV problems when framerate dropped below a certain point, or stuttering got bad enough that the code handling autopilot flight control inputs was constantly "behind the curve" trying to correct back on course. dunno if it's relevant here but something to consider/experiment with.

1 hour ago, Car147 said:

No, it's been sent to the recycle bin, far better aircraft to use now. I was just hopeful they had finally sorted the issues, but it seems on their admission they did not sort this issue.in this update          ( Despite acknowledging it months ago)

That's right--because there is no issue.  I did read somewhere people who bought the CRJ from the Marketplace have had issues, and those from the dev not.

I got it from marketplace, not had any issues with it. Granted it maybe a day or two behind on updates.

As for the zig zagging, this is something I haven't experienced. Some times the user is the issue rather than the product.

As for the don't buy Aerosoft, don't buy it then, but try to leave those who have purchased and enjoy the product to speak about the product they own and fly with out the constant aerosoft bashing.

P.S not employed by Aerosoft

45 minutes ago, garlicbread11 said:

I got it from marketplace, not had any issues with it. Granted it maybe a day or two behind on updates.

As for the zig zagging, this is something I haven't experienced. Some times the user is the issue rather than the product.

As for the don't buy Aerosoft, don't buy it then, but try to leave those who have purchased and enjoy the product to speak about the product they own and fly with out the constant aerosoft bashing.

P.S not employed by Aerosoft

Really? I think you will find, the usual " We could not replicate it " as the usual cop out.they announced. but not to worry or continue this thread. plenty other decent aircraft to fly, just sadly thought they may have fixed an issue that affects more than just you and the other word not allowed.

Edited June 27, 20223 yr by Car147

2 hours ago, Noel said:

That's right--because there is no issue.

You don't see this particular problem, and thus it does not exist. This is the attitude that ruins discussions.

I have seen this issue in all versions of the CRJ so far, from the FSX version to the current MSFS iteration. It exists, it is not user error (I fly the real thing for a living, I'd like to think I have a vague idea of how it should or should not work).

People who enjoy the addon and don't experience or simply don't notice the issues (ignorance is bliss kind of thing) are very welcome to keep on enjoying it and expressing that. On the same principle, people who do not enjoy the addon and are experiencing issues should be just as free to express that.

Aside from that, no one should be as clueless as to say an issue does not exist when it has been clearly shown by users and acknowledged by the dev to exist.

 

 

2 hours ago, Prpn said:

Aside from that, no one should be as clueless as to say an issue does not exist when it has been clearly shown by users and acknowledged by the dev to exist.

My comment was rhetorical--obviously "it" is an issue for some it's been stated loud and clear in this thread.  What is not clear, is why it is for some, and not others.  Not staying on course was an issue for the first several flights when I first bought it and gradually I got sufficient at cleaning up the route and approaching corners at a speed so as to stay on track, or whatever it is that is allowing me to no longer have a problem w/ LNAV tracking.  Of course, since I did experience overshoot initially and loss of tracking, the first thought I have is why is it I used to, and no longer do, and others still can't get it to cooperate for them.  I hope you can appreciate the perspective. 

2 hours ago, Prpn said:

or simply don't notice the issues  (ignorance is bliss kind of thing)

Maybe we're talking about different things.  As a real world and CRJ non-pilot I don't know how the real deal is supposed to function, and as Fiorentini mentions the AS CRJ's LNAV apparently isn't operating as the real deal's, so yes I'm word not allowed of this type of issue other that this is what I'm told here.  What I do know, is after initializing the GPS position, inputting the departure/arrival airports, the departure runway, any SID/STAR that I might use, and all waypoint enroute, and inputting cruise alt and the other performance parameters via the EFB, after TO I click the NAV button along w/ SPEED and turn on the autopilot and it tracks perfectly.  So yes, to me "LNAV" works fine right on thru to an RNAV or ILS approach all stays well, provided I update the route as needed for changes.

Edited June 27, 20223 yr by Noel

I have experienced this "hunting", perhaps once in every 20 or so flights on the CRJ. 

I switch to heading mode, get back on flight path, re-engage LNAV and it usually stays put.

Way back in the fs9 days, a few aircraft would have this problem, there was a setting somewhere (.air file or aircraft.cfg) called pitot_static=1, and increasing this to 2 or 3 would eliminate the 'hunting'.  Alas, I'm sure that setting no longer exists in MSFS, probably called something else now.

On 6/26/2022 at 7:39 PM, btacon said:

No zig zag for me. LNAV is quite stable.  

same, LNAV stable, VNAV tricky but most likely pilot error 😉

On 6/27/2022 at 8:14 PM, Car147 said:

Really? I think you will find, the usual " We could not replicate it " as the usual cop out.they announced.

........or, perhaps they just could not replicate it.

After all, I can't replicate it.  The NAV tracks perfectly for me.  Some mild overshoots, which as others have said, are a flaw in the stock Asobo GPS NAV function but not one bit of zig zagging.

Have you checked controller sensitivites?   Perhaps an axis is intermittently 'nudging' the plane and disturbing the AP.

1 hour ago, JYW said:

........or, perhaps they just could not replicate it.

After all, I can't replicate it.  The NAV tracks perfectly for me.  Some mild overshoots, which as others have said, are a flaw in the stock Asobo GPS NAV function but not one bit of zig zagging.

Have you checked controller sensitivites?   Perhaps an axis is intermittently 'nudging' the plane and disturbing the AP.

Wrong, they are well known for cop outs. Please explain how my Thrustmaster warthogg set up works perfectly with the Fenix a320, the FBW A320, the PMDG 737, the Leonardo Maddog, the kodiak, etc, etc. this is the only aircraft (the CRJ) that does not properly follow  a lnav path, it's even worse if the turn is over 30 degree's. I have gone through all the settings for the controllers numerous times.

You tell me it's fine, i know it's not! Now i am done here, but i'll say one thing, i will Never, buy another Aerosoft Aircraft.

Edited June 28, 20223 yr by Car147

1 hour ago, JYW said:

........or, perhaps they just could not replicate it.

After all, I can't replicate it.  The NAV tracks perfectly for me.  Some mild overshoots, which as others have said, are a flaw in the stock Asobo GPS NAV function but not one bit of zig zagging.

Have you checked controller sensitivites?   Perhaps an axis is intermittently 'nudging' the plane and disturbing the AP.

Well for me at least it's exactly those overshoots I'm talking about. When you overshoot, you have to come back to correct, and the CRJ tends to overshoot again on correction, which ends up being a zig zag. It feels often like I'm catching a localizer in the middle of my flight.
It's doing this on certain turns for me, definitely on climb out turns. I'd certainly expect from a 50-60 dollar airliner to NOT EVER overshoot on basic turns during the climb out (this make the CRJ borderline unflyable e.g. in parallel runway takeoffs on VATSIM, I'd get yelled at by the ATC and rightly so).
But expectations may vary, so no sense in arguing about that. The CRJ is not a bad product and I've had my fair share of fun with it in 2021, but it's seriously overpriced by now with the 737, Fenix and 146 out. As long as the price stays like that one should expect more from Aerosoft in my opinion.

That's so weird.  Rare to get any overshoots and never any zig zag.