MDFlier

Didn't notice that search results sort order defaulted to "relevancy" instead of date. I missed the earlier thread reading the irrelevant thread titles that were boosted to the top because Avsim thought that they were more relevant. Oops. Thought it was strange no one mentioned it. 🙃

If someone already posed this, please forgive me. I searched the forum and didn't see a thread yet. https://fenixsim.com/blog/entries/2025-03-28_roadmap/ ECAM will be 100% Fenix. No Prosim. "We're looking at launching later this year. We're building the A320neo, and the A321neo. The LEAPs and the GTFs will both be fully represented in XEM. And, finally, we are putting all this in one package. This is a standalone product. No prior ownership necessary." Big updates for the Ceos as well. MSFS2024 compatibility. WXR is coming. Full walk around mode is supported with external panels that open and systems to "play with". And if I am reading it correctly, their new ECAM will also be ported to the Ceos, so I guess no more Prosim anywhere? "Lastly, for customers that do opt to own both our CEO and NEO product, as a cherry on top, you will then have a surprise third airplane: a modernised CEO - based upon the significant work put into building up our NEO, it’ll be running the latest version ECAM, displays, what-have-you, on your CEO, for all you autobrake OFF enthusiasts (I get asked about this 8 times a day minimum). This is a small thank you to those who continue to support the work we do, and gives you a tonne of choice with what you would like to fly and which era of A320 you'd like to fly. " This is great news! I wanted the Neos but I wasn't going to get it from the other guys.

You have to set it where you want it to go in the Xbox app when you install it. Start Xbox app. Click your username at the top left of the window then click "settings". In the new window that appears, select 'Install Options'. Use "Change Folder" where it says "Change where this app installs games by default. Set it to "D:\Flight Simulation\". MSFS2020 will install in "D:\Flight Simulation\Microsoft Flight Simulator" (by default) and MSFS2024 will install in "D:\Flight Simulation\Microsoft Flight Simulator 2024".

You probably should have started a new thread since this one was so old. I've found that this is usually caused by a corrupted .ZIP file in the temporary folders. Once I figure out which one, I delete it and then re-run AIM. It will download a new copy instead of trying to work with the corrupted one that is already on my system. Step #1 - Figure out which .zip file it is trying to install. Close AIM. Re-start AIM to create a new log file. Try to install Jetblue. When it fails, gets stuck, etc., close AIM. Look at the last couple of lines in your Log_AIManager.txt (found in the folder where AIGTech - AI Manager.exe lives) to see if you can find the name of the last .zip file it was working with. Step #2 - Delete the appropriate .zip file from the temp folder and then re-start AIM and try to install Jetblue again. My AIG temp folder is located at C:\ProgramData\AIGTech\AIGAIM\ I believe that the airplanes are put in temp_model.

Whenever I see this, I restart my computer and then launch MSFS from the XBox app. Seems to work every time.

Wait a minute. Are you saying that some people don't eat their spaghetti with their fingers?

I figured out how to access all of my Fenix liveries. You can do the same. The "trick" is to NOT do the obvious thing, which is to select one of the "Fenix" liveries of the type that you want, and then trying to pick the airline livery you want out of the ones that you installed. As soon as you enter the change aircraft screen, type the model number you want (319, 320, 321) in the search box and press enter. Select whatever Fenix shows up. Select "Configure". NOW IS THE TRICKY PART. You should see 8 (or possibly more) airplane selections at the bottom. Do NOT select any of the Fenix livery "CFM", "CFM SL Two Class, "IAE", or "IAE Two Class" 'liveries' in that list. You will also see 4 (or more) actual airline liveries in the list. If you click on any of those, you will see at the top which model it is (Airbus A321 IAE, Airbus A321 SL IAE, Airbus A321 CFM SL, etc.). Click the livery that is the same model as the livery that you are trying to use. After the livery that you picked appears on the screen, click the Livery button, and you will see all of the liveries you installed for that model. If you selected the wrong model and do not see the livery that you want, click the variant button and then select a different model. Just ignore all of the generic Fenix ones...

You're welcome. I just realized that in my post, I said that you had to uninstall and re-install the sim in my post. You do not. Just do what is in the spoiler and those instructions will allow you to get MSFS2024 to it's original fresh install state.

Not a typo. I messed up my keyboard control assignments by selecting the MSFS 2020 "Traversal" control set under General controls in settings. I fixed it by resetting the sim as described. I went into controls and created a duplicate profile of the MSFS 2024 "Traversal" and then set duplicate to be the default profile. That's the only one I am changing from now on. I will NEVER select that 2020 traversal option again.

Yes. I had this issue. It is a real PIA to get rid of. The biggest problems start when you select the 2020 control profile. It seems like Asobo added some UI controls that we users can't normally modify from FS2020 in that profile. It caused my installation to replace the ESC key with joystick button 2. If I went into settings, I had to pull the trigger on my joystick to save the changes. Good news / Bad news. The good news is that it is easy to fix. The bad news is that you need to uninstall the sim, delete some files, re-install the sim, and then you need to start it for the 1st time after the re-install with your computer OFF the internet so that it doesn't restore the bad settings from the cloud. Here is the procedure. I copied it from a post on the MS forum, so if you want them from the OP, just search over there for it.

Thanks for the tips, guys. Believe it or not, I've made quite a bit of progress. After turning off that dynamic thingy and increasing the rolling cache to 150GB, I looked a little closer at the main settings screen. It was then that I noticed the #1 issue blowing up performance on my system. It is related to the fact that I am using a 3440x1440 monitor (21:9 aspect ratio). I somehow never saw that the "Rendering resolution" was showing 5847x2448 even though the slider was set to 100 (Great idea Asobo. Putting the rendering resolution value in the label. Brilliant!) . I thought that was odd, so I reduced the slider to 50, which changed the label to show a rendering resolution of 3440x1440. Boom! Decent performance on par with 2020, and better visuals as well !!! 🕺 Here's the strange part. After going in and out of settings a bunch of times to play with different options, I noticed that the rendering resolution was now showing 1720x720 instead of 3440x1440. The slider was still set to 50 (which actually makes sense). I changed the slider to 100 and rendering resolution changed back to 3440x1440 (This also makes sense). Performance was still great. After playing around some more, I now find that DLSS and all of it's modes including DLAA work fine now with great performance. It seems like something really jacked up the rendering resolution, and me playing around with it somehow fixed it. I don't recall ever playing with that slider before because I always looked at the full screen resolution and saw the proper 3440x1440 in there. I was planning on updating my system, but with the performance I'm getting right now, I might be able to hold off for a little while. Boating season is only 2 months away, and I won't be flying as much as I am now. My CPU is running at 50%-75% utilization, my GPU is running mostly between 80% and 94%, but I'm using 31GB of my 32GB just sitting at the gate in Boston in the Fenix.I'm seriously considering dropping by Micro Center tonight and picking up 64GB. Unfortunately, they (and most other retailers that I've checked) don't seem to have any DDR4-3600 CL16 in stock, so I 'd have to remove the 32GB I have now as Asus say it's not recommended to mix memory with different latency. I think it would help a lot, particularly when I start adding AI traffic. I've got the full load of AIG all ready to go. UPDATE - I ran over to MC and picked up 64GB of G.Skill DDR4-3600 (only $127 including tax). What a difference it makes! OMG. I can tell that my fans aren't spinning up as often or as fast as they were earlier. She's clearly not paging as much and it is making a tremendous difference in the look and smoothness of the sim. Here's the kicker. MSFS 2024 with ther Fenix at the gate at KMSP in a snowstorm is using 33.8GB. Take Asobo at their word. MSFS 2024 needs 64GB of memory to work the way that is should.

Things with MSFS2024 are pretty much where I expected them to be at this point in time. As mentioned, they simply can't have a beta large enough to cover all of the possible combinations of hardware as well as variations in network speeds from user to user. Telemetry will play a large part in fixing things. 2024 does not run well (most of the time - occasionally it does) on my machine unless I turn everything down to low and 50/50 on OLOD and TLOD, in which case it runs great. I can't get performance and visuals on par with what I get in 2020 to save my life. Not even close. (well... I've had a half dozen or so that were better than 2020, but I can't consistently get that type of performance) That being said, I still try it every other day or so so that MS/Asobo can get the telemetry data that will help them fix it. Some users are using it with no problems. Others, including me, are not. I left 2020 installed for that very reason. I expected everything that we are seeing right now. It'll get better soon. Just like 2020 did. Some people would have been better off waiting until the word on Avsim was that it was good to go before they bought it. That's what I did with 2020.

I've had 3 or 4 flights that I can only be described as spectacular. When they get past these initial issues, we're going to have a fantastic sim in our hands. I just did a Baltimore to Boston flight in the snow in the Fenix. I've flown this route many, many, many times in 2020. The approach into Boston was gorgeous. I dropped through one overcast layer only to find a second one about 1500' below me. Through the gaps in the layer below, the Boston area looked stunning. The lighting is better, the textures are better, and the clouds are better. Hand flying the approach felt great. The airplane had momentum, it felt heavy, but not sluggish, and the Fenix looks beautiful (as it does in 2020). The other flights have been great as well. That being said, there are some big issues remaining to be fixed. There's clearly a resource leak, particularly in the UI. Once you start a flight, stay out of the menus and you'll have a better chance of having a good flight. Every time I make a change to a graphic setting, I go from nice and smooth to 3-6 FPS. If you do change settings, restart the sim before you fly. Looking forward to seeing where we end up in the next 3 months.

I love how the Fenix puts a QR code to the POH on the panel so you can scan it and get the docs for that airframe. Pretty cool... Almost makes me feel like dancing. 🤭

Just do yourself one favor. DO NOT switch your controls profile from the 2024 control set to the 2020 control set. While that will change most of the key and control bindings to what they were in 2020, the 2020 control profile messes up all of the bindings for the user interface (MSFS2024 menus, etc.). You can still work through the menus using the mouse, but it is a pain in the you know what not having proper the keyboard assignments.