Hoffie3000

Have you install the experimental update also? From 2.2.0.0 to 2.2.0.1? Some people forgot this and get then this strange behaviour.

Please read the last post why you should always load a default aircraft first: Wolfgang

Are you shure you have choose an ILS approach or have you mixed up with a RNAV approach? This "not capture GS, stay at present altitude" looks for me for a RNAV approach. This required an different handling. Wolfgang

LIRN funktioniert ohne Probleme in V5, Roma habe ich nicht. Wolfgang

I would say there is something wrong in your CRJ installation: I find my CRJ folder here: C:\Users\username\Documents\Aerosoft\Aerosoft CRJ Pro v5 [FMSDefaults] DOW_550=45749 DOW_700=45749 DOW_900=48749 DOW_1000=54749 I have the same CRJ installation as you have Wolfgang

Well, no wrong numbers here if I use the weights from your screenshot. Wolfgang

If I type in your provided flightplan I get that: Look at the distance of 10.4nm vs 63.1nm of your screenshot. Wolfgang

Only version 2.2.0.0 or have you update via experimental update to version 2.2.0.1? Wolfgang

You find some information in the document folder of the CRJ: Vol5_Aircraft Operating Manual_Part_2.pdf Page 78 Wolfgang

Have you load a default FSX aircraft first before switching to the CRJ? This is mandatory for proper work of the CRJ.

No problems with KDEN/Flightbeam with me. Tested with the CRJ700 and CRJ900. AIRAC2008 Wolfgang

Well. it seems that is Hans "blind site" 🙂 I reported this TCAS issues in the beta part of the forum but don´t get an answer: Hans, how do you see the TCAS module from your perspective? Are you working on improving this module? Anomalies: Display of aircraft only within 10nm radius. Display in the wrong place on the display, because always a bit too late in the calculation (I compared it with FS-Commander and in the outside view). If required I have screenshots. No sliding display of the TCAS contact in the display, only first contact within the 10nm and then again when leaving the 10nm radius. This results in jumps of the displayed aircraft in the display. The current altitude (ABS) of the displayed aircraft is always shown. REL does not work. For Traffic <10nm in the outside view you can display different values. I use altitude, speed and callsign. While the altitude match with FS-Commander, they are always shown delayed on the TCAS display. I know he is at time busy in real world business for a week or two but I hope he will find time then to fix this issues. Wolfgang

Auch ohne Prepar3D.cfg tweaks, also mit den original Einstellungen, sieht EDDF bei mir gut aus und die Texturen laden auch zügig wenn ich in den Bereich des Flughafens komme. Warum hast Du GES deaktiviert? Bei mir langen die drei EDDF Orbx-Files in GES um ein kleines Höhen Problem im Bereich der Rwy07L zu lösen. Die Speichernutzung der GraKA ist mit dem default Aircraft auch nur bei knapp 3GB. Wie sehen den Deine World Optionen in P3D aus? Überlege mal ob Du nicht auf den HF2 von P3Dv5 updaten solltest. Da wurden einige üble Fehler bereinigt.

This is not an error or bug. This is the way you should use the CRJ always. First load a default aircraft and then switch to the CRJ. The CRJ is developed based on always the actual P3D-SDK and needs some P3D moduls to proper work but if you load the CRJ direct these moduls are not yet loaded. Result can be a CTD or other strange behaviours. Wolfgang