That's how it works in the real plane.

Die Frage ist eher, wie, warum, wer es einschaltet. Die KA hat kein Autothrottle. Da hilft nur permanentes Überwachen und dagegenhalten. 🙂  

First of all, sorry I do not have screenshots since I create this post some hours after my last flight.   I made now 5 flights with it and altough many things did improve with the aircraft, things are still not up to standards. Im limitting myself only to autoflight and flight controls but there are more (like fsx like textures in the cockpit, etc).   1.) Takeoff does not feel correct all the times. Even tho I did set the trim correctly according to the efb, the nose tends to shoot up (or even autorotate) without flex settings. With Flex it does seem a bit better. 2.) Direct To does not calculate the best intercept path but does so from the current position. Therefore the airplane does overshoot and flies a 30 degree intercept towards the line drawn from the executed position. Vatsim controllers are not amused.. 3.) FMA != what the airplane does. I had the issue in v1 already, that sometimes the ILS seems to be active on the FMA and autopilot is in approach mode, it tends to deviate drastically from the actual beam. By deviating I mean it might be following a path which is 5 degree left or right of the beam leading to you missing the runway by miles. Happened once - in eddf 07R-Z. 4.) Transition from FMS to ILS which should occur automatically has as of 5 flights worked once - in all other cases I had to manually set it to the correct source. Not sure if that is the correct behavior 5.) Pitch control feels rubberbandish on approach. I dont have that weird feeling with the md80, the 320 (I know not the best comparison) and not with the HS cl650 in xplane. 6.) Fadec engines still overshoot the N1 limit in some cases but it tends to be better than v1. 7.) When you manage to get into overspeed and select a lower altitude, reduce the target speed and select speed mode the aircraft pitches down to around 7 degrees and completely ignores the speed you have set. Adding spoliers just makes it dive even more. I would expect it to slow to the target speed instead of YOLO'ing to its doom at 360 KIAS. 8.) Holds... While they are a major improvement since the first version the airplane still tends to perform kind of weird rectangular shapes sometimes. Nothing too bad but still something I noticed.   As of now every single flight something went wrong in one way or the other. Which is a little bit frustrating given the exceptionally long wait for an update to fix the issues which are here since the inital version.    Generally it is an improvement and its nice that AS finally starts to support their aircraft - which is a step in the right direction - but in comparison to your competition this aircraft still needs some work to be flyable.

It is working. Only shows rain - not clouds. Try it in a situation with rain. It is NOT a proper WXR radar.

Congratulations on releasing this long awaited CRJ V2 update, the improvements are evident and appreciated.  However, the CRJ V2 product page shows terrain and weather radar as implemented systems, and whilst I can see that the terrain radar is operational, I cannot get a return from the WXR. I am using both the EFIS & WXR panels to enable these systems. Also, the PDFs supplied with this aircraft are a mix of various CRJ legacy products as well as this latest iteration (one even mentions FSX/P3D) so it’s hard to know if I’ve missed a step anywhere, though I think not.  Weather was through Active Sky AND a MSFS 2020 thunderstorm preset.  Please can Aerosoft confirm whether the WXR is functional or not? Thank-you.    NB. I’m not looking for a debate on the usefulness of the default WXR API. Hopefully a proper WXR will at some point emerge but until then this must suffice as it is all we have. Indeed, very few others appear to be making a stand on WXR implementation as others appear content with just refuting the present API instead of pushing the point. 

HAllo Miche, hast du wirklich alles über das Anschneiden von Radialen wieder vergessen? Man wird eben nicht jünger.   Zu Deiner ersten Frage, drehen bis die "Nadel" in der Mitte ist stimmt. ABER Die From/To Flagge muss auf TO stehen, nur dann ist die Anzeige ein QDR.

You need to address the Lvars via FSUIPC. It is currently possible. For details, please for to the FSUIPC forum :  https://forum.simflight.com/forum/183-fsuipc7-msfs/  

Good afternoon,  I submitted a ticket already but per the FAQ I'm creating a topic here as well.    The TCAS range is scaled wrong in every mode except for the Traffic Display mode on the ND. In flight plan mode, when an aircraft is 5NM away, it's showing 2.5NM, when it's 10NM, it's showing 5NM etc. This issue has been brought up before but never received any feedback. Not sure how easy of a fix that is, but it is definitely an immersion killer. Attached is a screenshot showing the issue. The left display shows the incorrect distance of targets, while the right one shows the correct distance.    Any feedback would be greatly appreciated.  Thank you

Please login to display this image.

I have no Axis and Oh just FSUIPC7. How can I use these scripts within FSUIPC?

Here are the code of the RPN scripts for the FCP Altitude Selector :  INCREMENT :  (L:ASCRJ_FCP_ALT_SEL,·Number)·10·+·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·++·(>L:ASCRJ_FCP_ALT_CHANGE,·Number) DECREMENT :  (L:ASCRJ_FCP_ALT_SEL,·Number)·10·-·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·--·(>L:ASCRJ_FCP_ALT_CHANGE,·Number)