Leaderboard

So guys, I had enough time to analyze the mistakes made in the Dortmund project, to make a plan for myself, which will be included in the update. 1. I will fix the mistakes in the middle of the terminal with the interior textures. I mistakenly connected a Comp map from another texture to one of the albedo textures. Also, I will remove the jumping passengers in the middle of the terminal. 2. I will edit the texture of the runway, in principle, I have already done this. 3. I will make the boarding gates on parking lots 3-4 after dismantling the mobile Jetways. I already have all the information, including new photos taken at the airport itself, so I can thank one of the users for this. 4. I will install animated flags. The author of these flags is Christian Bahr 5. I will finish building the houses, across the road from the city side. This is the most voluminous part of the updates, so the update will have to wait a bit. Regarding the native version for MSFS 2024. Yes, it will be. I will make it by the end of the year. If I make it sooner, then it will be ready sooner. But please, don't ask me about the pricing for the native version. Regarding my new project. Most likely it will be made exclusively for MSFS 2024. What kind of project is this, officially, I haven't said anything about it yet, but I have already started working on it. These are my plans.

Logs auf der Zeitschiene anzulegen, ist ein probates Mittel zur Fehleranalyse, insbesondere dann, wenn in einer sehr offenen Software-Umgebung, wie z.B. XPlane, mit externen, also "fremden" AddOns, Plugins, teilweise bis in die Grundfesten von XPlane gehend, interagiert wird. Für eine Fehleranalyse kann es dann sehr hilfreich sein, die Situation, die konkret den Programmabsturz verursacht hat, mit den Konstellationen zu vergleichen, die davor keinen Programmabsturz verursacht haben. So lässt sich das "Suchfeld" zur Fehleranlayse meist deutlich einschränken. Wir als XPlane-User stellen uns bei jedem CTD ja auch immer als erstes die Frage: "Was ist jetzt anders, als beim letzten XPlane-Aufruf?" ... und versuchen aus der Erinnerung darauf eine Antwort als Teil der Problemlösung zu geben. Diese Chance hatte LR bisher nicht, daher jetzt die Zeitstaffelung Log1, Log2, ... Auf meinen Rechner gibt es eine Reihe von Programmen, z.B. Oracle VirtualBox, die diese Art der Log-Zeitstaffelung verwenden.

In der Tat... hier die sagenhaften Faröer, die irgendwie mit jedem XP-Update, wo die irgendwas an der Grafik schraube, besser zur Geltung kommen: (XP 12.2.0 Beta, Vskylabs R44, Faroes4XPlane, XP-Echtwetter, sonst nix und vor allem, keine Tweaks)

Are you using the recommended speed schedule of 290 KIAS to maybe FL270, then 270 KIAS (or IIRC M.72 above the changeover altitude)? Except for small altitude changes down low, NEVER use vertical speed mode for climbs, especially above FL200 or so. Trying to climb using vertical speed is guaranteed sooner rather than later to get you behind the power curve and result in having to descend first to get your speed back. This is absolutely real life. Happened to a couple of un-named commuter airline crews I personally know of when working as an FAA inspector.

Hi Pavel, Thanks to Alex for his solution comments! However, that did not work for me, as I had already applied those suggestions..... I am a retired Shell project manager and I have a PPL for 16 years: I donot recognise 'Does not work' ! So....I did find the solution, which might work also to other simmers: If you own the (nice) Justflight 'Real Taxiways Europe' you have to remove the ED:LW.BGL file: In your Community folder: go to bbsq-euro/scenery/global/scenery and delete the EDLW.bgl file. That's all and result shown in the Dortmund platform image! Thanks for your active involvement on this Forum. Much appreciated comments by the developer himselves! Looking forward to your new aiurports!

# Public Beta 12.2.0-b3 **General** - Refreshed aircraft selection grid after adding or removing favorites (XPD-16670). - Displayed a warning on Linux systems if WebKit cannot be loaded (XPD-16758). - Included art controls in safe mode startup to prevent unwanted modifications by plugins or scripts. - Starting a new flight no longer changes the fuel amount. - Added --aftermath support for AMD GPUs to gather more information in case of a crash. - Fixed a crash caused by the web server when disabled (XPD-16774). **ATC** - Fixed various crashes. - Updated ATC voice packs to AIRAC 2503. **Balloons** - Fixed broken terrain type and steepness check. - Improved airport-overflight detection reliability. - Corrected balloon speed calculation (was using the wrong wind value). - Fixed random placement zones not varying between flights. **Graphics** - Reduced color compression for yellows and reds to improve sunlight realism. - Recalibrated tonemapper to reduce green tint in specific lighting conditions. - Adjusted exposure and exposure fusion for better contrast handling between cockpit interior and exterior. **Weather** - Improved physics for icing and turbulence within clouds.

Öhm... sorry, ich war 'ne Weile weg, persönliche Gründe und so. Da ich hier aber verantwortlich bin wollte ich trotzdem noch ein Statement dazu abgeben, auch wenn mir das wahrscheinlich wieder um die Ohren fliegt. Die Bump in der Runway kommt wahrscheinlich daher, so vermute ich jedenfalls, dass der Mesh-Patch nicht die gesamte Runway abdeckt und die Höhen im Ortho4xp-Mesh dort von den Höhen im Standard-Mesh abweichen. Das Problem bei der Behebung ist aber folgendes und wahrscheinlich jetzt für viele nicht nachvollziehbar, da es sich wieder um 'kaufmännische Gründe' handelt: Das Mesh wurde nicht von Maps2XPlane erstellt sondern anno dazumal von irgendwem anderen, das war noch zu XP10-Zeiten, und da gab es bis zur XP12-Version nichtmal einen Ortho-Patch für die Szenerie. Weil das Mesh aber nicht von Maps2XPlane ist wäre eine richtige Neuauflage des Meshs kaufmännisch problematisch, das müsste dann alles neu gemacht werden und dafür ist die Vorlage 'Zürich V2' einfach schon zu alt - damit die XP11-Szenerie also überhaupt ein XP12-Update erhalten hat (das wurde seitens der Projektleitung erstmal abgelehnt) musste ich hier das alte Mesh irgendwie selbst zurechtfummeln auf Basis dessen, was es hergab und der nicht ganz optimale Ortho-Patch ist streng genommen eine Zugabe, die Matthias hier dankenswerter Weise für uns erstellt hat. Matthias kann da aber gar nichts dran ändern weil dafür müsste ich das ganze eigentliche Mesh neu machen und die Runway dann komplett inkludieren, was wiederum andere Probleme mit sich bringt (es gibt da einen Grund für, dass der Patch so zugeschnitten ist). Am Ende ist Zürich leider auch schon ein sehr altes Projekt, dass über die Jahre ohne Zusatzkosten für den Kunden weitergepflegt wurde, da sind dann irgendwann hier und da Grenzen erreicht - ich bin letztlich selbst glücklich damit, dass die XP12-Version letztlich genehmigt wurde (ich mag den Flughafen und wollte ihn unbedingt 'richtig' im XP12 haben) und soweit auch gelungen ist, bis scheinbar auf jetzt dieses Problem. Ich habe hier, wie üblich, versucht, das bestmögliche rauszuholen - ein perfektes neues Mesh als Vorrausetzung hätte bedeutet dass die XP12-Version gar nicht gemacht/veröffentlich worden wäre.

Macht doch nicht so ein Drama aus solch einer Kleinigkeit.

Maps2XPlane feiert in diesem Monat sein 10-jähriges Jubiläum und damit ein Jahrzehnt der Entwicklung hochwertiger, maßgeschneiderter Landschaften für den X-Plane-Flugsimulator. Vom ersten Projekt Antarctica4XPlane bis hin zu detailgetreuen Nachbildungen von Regionen wie Spitzbergen, den Färöer, den Seychellen, Saint Croix und den Gesellschaftsinseln bieten wir virtuellen Piloten vielfältige und immersive Landschaften. Alle Details zu den einzelnen Projekten eines spannenden Jahrzehnts der Entwicklung, sowie einen Ausblick auf die Zukunft findet ihr im neuesten Blog-Beitrag auf unserer Website. Vielen Dank XP Community für euren Support: Auf ins nächste Jahrzehnt! P.S. Falls euch in eurer Sammlung noch eines oder mehrere unserer Add-ons für X-Plane fehlen, lasst euch diese Gelegenheit nicht entgehen: Zur Feier des Meilensteins sind alle bestehenden Szenerie-Pakete von Maps2XPlane ab sofort mit 50 % Rabatt erhältlich – exklusiv im Aerosoft Shop, bis zum 21. April 2025.

Hey thanks for the link! I have been watching his videos lately. There was another guy, American guy, that I had saved in my youtube playlists but have somehow disappeared. He was a real CRJ pilot as well and he had quite a bit of good videos with some great info as well. But I can't seem to find his channel now.

Check out this Discord. YourSimCFI is a real world CRJ9 pilot and avid flightsimmer. A lot of CRJ Q&A can be answered there and his YouTube channel is outstanding. https://discord.gg/NAAzzh6t

Ah, you see, after all, EDLW was in conflict with Justflight "Real Taxiways Europe". Quite possible. But I'm glad that you identified it and were able to solve the issue. This is important, because other users may also encounter these problems. It's very good that these nuances are discussed on the forum and solutions have been found for them. Thanks Peter!

Sieht gut aus.

Hello Pavel, great that you tackled Dortmund and made a very nice scenery! I just bought it and i have the same issue just as Peter has. Could it have something to do with GSX? Edit: Ok, i think i fixed the issue. When i wanted to select Dortmund as my departure airport i zoomed in and wanted to select Gate 5. I noticed that i had two "dots" showing me Gate 5 right next to each other. So i figured i have to disable EDLW in the GSX menu. And viola, the elevation bug has been fixed. Also only one "Gate 5" shows up on the map. Edit 2: Oh, it might also have been under the "Content Manager". I searched for "Germany" and there was a very small Germany I Cities Update with just a few kb which was not installed. I also installed that prior to the GSX thing in me first edit.

I managed to find the solution, which wasn't listed on Simmarket. I downloaded the update via the Simmarket app, which is not a good idea. You need to go to the Simmarket website, click Download, and download the Aerosoft One module. From Aerosoft One, enter the serial number shown on the Simmarket download page.

On the Aersoft downloaded version, it is here : C:\Users\[USERNAME]\AppData\Local\MSFSPackages\Community\aerosoft-crj\SimObjects\Airplanes\Aerosoft_CRJ_900

Yes, I still have that on my list and it will be done, though I cannot tell exactly when. Meanwhile the recommendation remains to use it without photogrammetry/TIN active in MSFS2020. In any case it will only be a bugfix for the bumpy terrain. All the new features like higher resolution ground textures, new airside modelling etc. will only be available in the MSFS2024 version, which will is currently planned to remain free for buyers of the MSFS2020 version (and vice versa). Bests, Sascha

Thank you so much for sharing what you found to resolve the issue. That's what makes peer-to-peer help work. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

i like to draw range rings on the fix for my destination airport at 15,10 and 5nm to help with speed management. however, whenever i try this, only the 15 and 5 rings show up. after experimenting a little bit i think it only draws the first ring you enter and the last one, but none in between. i've compromised by just doing 15 and 5 for now. i also had a wasm crash while i was messing with the rings, it just completely froze up the avionics, i think when i deleted one of them, i haven't spent much time trying to repo this but i saw a similar bug mentioned elsewhere. i can't find that post at the moment unfortunately. cheers

You really shouldn't fly M0.72 up to high levels, depending on your weight you are massively increasing your chances to stall or just fall on the back side of the power or lift/drag curve. We used to use 250/290/0.74/0.77... The 0.74 was up to FL360, from there 0.77. I'd even argue it is easier to do 250/280/0.77 and skip the extra step. Worked well on the real thing.

Super, danke für die Info. Jetzt habe ich mir noch die letzte fehlende Szenerie für Maps2Xplane gegönnt. @maps2xplane Weiter so.... Ich freue mich immer über eure tollen Szenerien. Die sind schon einzigartige.

Hi, Just my opiniun, I have my msfs 2024 installation on my D nvme ssd drive, after the installation from the driver it is situated in my community folder, the way I have it running is when you start MSFS 2024 and you are in the start screen before loading a flight I run the shortcut in my start menu and after that I starting my flight and everything works fine. Cheers, Ruud

und wurde in den Release Notes zur Alpha 1 am 14.03.2025 auch benannt: Die Formulierung finde ich etwas unglücklich. "no longer overwritten" suggeriert, sie würden nie wieder "überschrieben". Das wird sie aber doch. Nur eben zusätzlich eine History angelegt. Eindeutiger wäre gewesen "no longer just overwritten"

If one sets a FLEX of say 50, reducing the N1 to 83 for example, TOGA thrust significantly overshoots the n1 limit to the early-mid 90s before settling. By that time we're rotated. This is a significant issue present in the very first crj release in 2020, and still hasn't been fixed. Please, please priortise this, take-offs feel very overpowered.

i had a similar issue to this but i believe it was just that simbrief was overly optimistic about what altitude i should be cruising at, which suggested FL360. i was climbing at climb detent power, speed mode, 0.72 set, and at around FL350 i started gradually losing speed, the plane started nosing up, and seemed generally like it was kind of struggling. as the speed dropped some more i watched it and it looked like it was eventually going to stall out, so i turned off the a/p, nosed over, and set a new altitude of FL310. it was fine after that. i think with 10k fuel and full passengers 360 was probably just past the max altitude for that weight maybe. i'm not sure how accurate the simbrief profile is tbh.

Excellent news! Very much looking forward to the update, and to a potential remake as well

Hi, what is actually important for the installer is the path to the UserCfg.opt file, which right now cannot be different from what the installer is expecting for MSFS2024, by default. From this file, it will read-out the path to your community folder. The file should either be here in case of a Microsoft Store install: Or here, in case of a Steam install: You also have to install the application for the same user that MSFS2024 was installed for. Please double check where the file is located on your system.

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.

What types of approaches are they? The CRJ is not approved for certain (most?) RNAV approaches, and the FMS filters out a lot of things it considers unusable (see the pinned topic on missing airports and runways). There's something vaguely familiar about this question, like it was asked for V1 and the above was the answer. If I find the old topic I'll link it here, or if you feel like taking a dive into the past. EDIT: here it is: Perhaps the filtering has changed? Are these RNP approaches that you aren't seeing whereas GPS ones still are?

OK, I seem to have fixed the problem. I don't know what caused it. I had been trying to use the 900 this whole time. So I tried the 700 and it worked, so then I tried the 1000 and it worked too. Then I went back to the 900 and now it is working as well. I don't know why it behaved that way but for now it's working as it should.

I took the liberty of re-titling your post to describe the issue. That should help others add to this instead of starting new threads. Please advise if you're using any hardware devices and/or helper apps like SPAD or AxisAndOhs. And please confirm it's on a PC.

Ok, I just flew another flight following this tutorial. Even though it's not for V2, I was able to reach FL330 and maintain it no problems. Now if I can just start the APU I'll be a happy simmer.

My picture for this month: Just arrived in Boston with the A380, then the loaders can come to unload!

I think the product page is pretty clear: As the product uses many FS2024-specific features, it would require some serious work from Jo to make it FS2020 compatible. Mathijs Kok PMDG

The PFD's are difficult to read when at a normal seat position in the sim, as has been pointed out in the past. I'm sure IRL everything is perfectly legible as it should be. The CJ4 PFD suffered from the same issue, where you have similar colors of text and background, resulting in a low contrast situation that's exacerbated by distance from the display. The way Working Title solved the issue was to put a very, very, subtle outline (almost a slight drop shadow) around these low contrast items. In the CJ4 you don't even notice it's there, but the QoL result is a vastly improved readability of the PFD and ND at normal cockpit camera positions. In the CRJ, I'm talking about stuff like the Vspeed lines/text on the speed tape, the snowflake, etc...

Dann wird es ja spannend. Ich wünsche euch ein gutes Gelingen.

Hi Alex. You're great, it's great that you found a solution to the altitude problem. I wouldn't have thought that if Dortmund is selected in GSX in the manual settings for jetways, it could affect the altitude so much. By the way, the solution to this problem needs to be highlighted somehow, because you and Peter are not alone, I think So, it's great that you figured it out. Thanks!

Update: Uninstalled and re-installed. Did NOT update the nav data via the Navigraph hub as I had done before. Loaded fine, set all items in the EFB as needed. Updated Navigraph data via the EFB. Restarted the sim. Nothing works again. I am zeroing in on the Navigraph data as the cause. I will un-install and start over without navigraph update. Back later.

Thanks. Regarding GSX Pro. Pushback in GSX cannot push airplanes with its tail back. So yes, Aerosoft pushback pro is best for this, it can do it and I use it at airports like Dortmund or London City Airport EGLC. It is easy to use, has enough settings. There is a free version of pushback, it was developed by the same author as Aerosoft pushback pro. A professional version has already been developed on its basis. You can choose for yourself from these two Pushback add-ons which suits you better.

Thanks Pavel, thanks for taking the time to provide such a detailed response. I am moved by some of your earlier comments which show your determination and commitment despite various personal difficulties and this deserves to be rewarded. I am just about to purchase and we'll see what goodies may come up in the future as I feel we're all in very safe hands. Just another quick question ... it mentions, Aerosoft Pushback Pro is required to get push-in to work ... is this still valid as I use GSX Pro please?

Hello Pavel, Congratulations on the release of Dortmund which looks great and will be another welcomed addition to my payware collection. I only use MSFS 2024 and whilst the product description says 'backwards compatibility', I'm not sure if I would be better waiting for you to release a native version for MSFS 2024? You have previously hinted there will be a small upgrade fee which is fine by me but will the total cost to purchase the current version plus upgrade, equal the full price of the MSFS 2024 version?

No idea what's going on in that picture. Are you having a GSX issue? Maybe contact the GSX dev, he seems helpful.

We are about two hours into the first business day since your post, I don't think many companies offer support during weekends. Two of your questions are also related to hardware/software outside of Aerosoft control...

Coupled VNAV is available as an option. I believe it was standard on the 1000 and maybe some late 900s. These aircraft will have a VNAV button, and it practically functions like VNAV you might know from Boeing or Airbus, but you have to manage thrust yourself.

If you have an issue with the CRJ, we first recommend posting here in the community forum, where other community members can view what you have posted and provide input. If the issue is believed to be a bug within the product, the best way to report the issue is by creating a ticket at https://helpdesk.aerosoft.com/hc/en-gb/requests/new When creating a ticket, please be sure to fill out all the input boxes, as well as providing exact reproduction steps so that developers and support staff can attempt to reproduce the issue. Our support team will then get back to you directly to provide further assistance.

It has been conveyed (here) and by pretty much every dev, product and update intakes into the Marketplace are expected to be delayed. This is nothing new, and you can't put this on Aerosoft.

Perhaps because Microsoft has not released it yet? Aerosoft just does not know when it will be available on the Marketplace. That is 100% up to Microsoft and can take one week or many weeks. When it is available, I will be sure to inform customers. Btw, as the original was not available for Xbox (the SDK was not ready at that time), all customers had the option to buy it directly from Aerosoft or other vendors.

I am having the same issue. And due to this it keeps the parking brake locked on as well.

Hallo allerseits, wie hoffentlich die meisten von euch mitbekommen haben, haben wir (das sind ich sowie ein in Entstehung befindlichen bisher namenloses Team) angefangen, bestehende Aerosoft-XP11-Szenerien für XP12 zu überarbeiten. Dieser Thread dient dazu über das Projekt und die jeweiligen Updates und Veröffentlichungen zu informieren, damit ihr da nichts verpasst. Da wir bereits einige Szenerien mittlerweile veröffentlicht haben möchte ich erstmal einen kurzen Überblick über diese Szenerien geben, aktuell sind folgende Szenerien vollständig für XP12 aktualisiert und stehen als Downloads zu Verfügung: Dortmund XP Paderborn XP Airport Berlin-Brandenburg V2 XP Airport Zurich V2 XP Airport Friedrichshafen XP Airport Berlin-Tegel XP Airport Manchester XP Airport Madrid XP Tromso XP Helgoland XP Alle Szenerien basieren auf dem letzten Stand ihrer jeweiligen XP11-Versionen und wurden in allen notwendigen Bereichen überarbeitet um sie zu vollwertigen XP12-Szenerien mit Unterstützung aller neuer Szenerie-Features, wie Jahreszeiten, Wettereffekten und so weiter zu machen. Dabei werden die Szenerien jetzt nicht einfach nur portiert, das Ziel ist stattdessen die XP12-Versionen gegenüber ihren XP11-Vorgängern zu verbessern wo möglich, wobei dann viele Details weiter optimiert und überarbeitet werden, zB. mit neuen Detail-Texturen für den Ground, überarbeitete Luftbilder mit neuer Farbanpassung, Bump-Maps und saisonalen Varianten, neuem volumetrischen Gras, wenn nötig auch neuen Custom Meshes (natürlich von Maps2XPlane) und vielen kleinen Korrekturen und Bug-Fixes. Diese Updates sind für Besitzer der jeweiligen XP11-Versionen kostenlos (wenn über Aerosoft gekauft, andere Anbieter handhaben das überweigend auch so aber es kann da Ausnahmen geben, da es den diversen Stores obliegt, wie sie derartiges handhaben). Besitzer der XP11-Versionen können prinzipiell hin und wieder in die XP12-Sektion in Aerosoft One schauen um zu sehen, welche ihrer Szenerien bereits verfügbar sind. Zuletzt noch etwas Erwartungsmanagement: Die Szenerie-Updates sind, solange die Produktbeschreibung nicht explizit etwas anderes sagt, inhaltlich auf demselben Stand wie die XP11-Versionen und vom Prinzip her trotz aller Verbesserungen eher technische Updates und keine komplett neu gebauten Szenerien was dazu führen kann, dass bei einigen nicht der aktuelle Ausbaustand des realen Vorbilds dargestellt wird wenn das reale Vorbild sich seit dem Erstellen der XP11-Version baulich verändert hat - derartige Modellierungsarbeiten sind aus diversen Gründen nicht Teil des XP12-Update-Projekts. Wir hoffen ihr habt mindestens soviel Spaß mit den überarbeiteten XP12-Szenerien wie wir bei der Arbeit an diesem Projekt. Agi