Hans Hartmann

@NoobiePilotCan you describe what your last steps were before this happened? For example "adding a waypoint with an airway" or "deleting a waypoint from the legs page"? Ideally along with the full flight plan. Sadly, the only way to figure out what went wrong is to reproduce it here. So, the more details you can give me, the better. Thank you. @signal_runnerYou should educate yourself before you start typing. C++/WASM does not implement exception handling. Even though the "try...catch" construct is part of Standard C and C++, it's not available for MSFS add-ons. Any issue will cause a so called WASM crash right away.

You're right. I made it a bit larger. The change will be available in the next update.

The CRJ for P3D v5 (including v2.4) is a 64-bit version. I just checked the project. So, you should be good with it.

You shouldn't make assumptions... pretty much every word you say is wrong.

You are. FS2020 it is and $0.

I'm not sure what I could tell you except the things I wrote in my last post. We're still working on the same things as before, but I'm not going to give you a list of when and how long people were on vacation or took a break from the CRJ and for which reason. I told you what will be in the update, that it will not be ready before end 2023 and that I won't give any further information until we are well into beta-testing. All this is still true. So, I wonder: what else do you want to know from me? Because right now, I can't think of anything new that I could tell you.

I'm not a modeller, just a programmer. Somebody else is designing the CRJ cabins. I don't know what the plans for the A330 are.

It's simple: While you are asking me to give you more information, other developers get hell from their community because they can't keep announced release dates (for whatever reason. I'm not judging them because I know the work that is involved. If it takes longer, it takes longer. It won't kill anyone). I don't want this. Just look at what happens in the Fenix Discord right now (after they announced the delay of their Block 2 update) and you will understand why I'm going with "It's done when it's done". I'm not a friend of creating hypes or posting WIP screenshots every other day. Expect to see screenshots and more detailed feature information when we're well into beta testing. I promise you that there will be a CRJ update, although it will likely not be released before the end of the year, that it will be a major one, that it will include the much awaited LNAV/VNAV fixes as well as Simbrief, Navigraph Charts, an updated model with a detailed cabin and more.

I'm working on the problem and it will be fixed. However, I'm still in the process of tracking down why this is actually happening at all. Out of the six stages of debugging, I'm currently at stage 4 ("why does that happen?"). It's not easy to find as, at least for me, it only occurs from time to time. As soon as I found the reason, I shall let you know.

The issue is known but not easy to reproduce. Sometimes it happens, sometimes not. Anyway, a fix for it was NOT part of the latest update. We're still searching.

From all we know and were shown in the E3 presentation and on the FSInsider website, it's very unlikely that the new MSFS will be any more compatible with the old FSX than P3D4 or X-Plane. For example it's guaranteed to be 64-bit so hardly any aircraft add-ons will be compatible. The future will show whether or not it will make sense to support the new MSFS.

Starting now. Release tomorrrow at 10am.