longhaul747

Just completed my SEA-ANC flight and no CTD. It was pretty smooth sailing until on final I got one of the famous FS2024 memory error pop ups and it started to get little pauses when I changed views but luckily it never CTD on me. I think it might need more testing to know for sure but I think its extremely positive it did not CTD on this flight and after the update. Actually the 1st successful flight with SP1.

I am taking this up for a SEA-ANC flight checking to see if the CTD issue I have been having is fixed? I have noticed so far the plane feels a little less resource heavy on my machine. This certainly helps one way or another I would think! Please Stand By......

Yes, Unfortunately very true!

Unfortunately I got another CTD about 6 hours into the flight. I was over Greenland so not much more to go. This time it was sort of self induced but was going to happen any as soon as I started doing stuff anyway. All was well so I went to an exterior view of the aircraft. The sim stuttered and paused for a second and I got a pop in the audio. At that point I know I was doomed. Went back into cockpit view and it was pausing and stuttering pretty bad but still working. As soon as I dialed in a higher flight level on the AP it froze and about 5 seconds later shut down. This is a classic memory leakage issue. Probably related to the bug already reported. Different systems will react different with the bug but it will probably be fixed when the fix the official bug that has already been reported for FS2024. I plan to do some more debugging and joining the discord so I can report it and read about others with the issue. I don't think I am alone though.

So far so good...4 hours 10 minutes in. I have not gone this long without a CTD so far on SP1. Currently over Hudson Bay Canada.

With promotional videos like this coming out it can't be very long now!

Right now I am doing flight #4 as an acid test. Hopefully clearing the WASM folder helps! All the flights so far have been somewhat similar but the crash at the CTD was at the 2 to 2.5 hour mark each time. First was SEA-ANC and the second flight was SEA-KEF. Third flight was KEF-SEA and same results each time. Most of the time I am a pretty lazy flight simmer. Because of time constraints I usually just program DIR routing and not so much with way points. I don't think its a lot of way points causing the issue. I am going with strictly a memory leakage issue of some sort! Right now as I type this I am attempting to do SEA-KEF again. Currently about 57 minutes into the flight. I hope its now stable after clearing the WASM folder but I won't know for about another 2 hours. If not I will attempt to debug with the information above and I need to join the iFly discord anyway. I would not be entirely shocked if my system is now reaching a point that with the higher detailed scenery and airplanes coming into the market it will have a harder and harder time. Its a 2021 upper mid level build. CPU is surprisingly still current but my graphics card is showing its age being a 2070 Super. A new system is in my budget forecast for next Fall but it will only happen if the stars align. Lately they have not been aligning well this year. Amazingly despite my systems age it runs FS2024 really well. In fact I see better performance than what some people get with faster systems. So it is hard to say but I would like to be able to crank my display settings a bit. Some of it is on high but other settings mid level.

I did after a bit of searching find the WASM folder for the SP1 version of the iFly MAX 8. Microsoft.Limitless_8wekyb3d8bbwe\WASM\MSFS2020\ifly-aircraft-737max8 It's in the MSFS2020 folder even though it is installed in FS2024. I cleared it and rebooted the simulator and reloaded the iFly MAX 8. Everything was working fine but the real acid test will be tomorrow when I try a long haul flight again. I am also getting an Asobo Crash Log and its definitely something with the iFly MAX 8. It's mostly gibberish but I see a bunch of WASM related error dumps in the log. So hopefully clearing the WASM files and having the system rebuild them under the SP1 hopefully makes a difference. It has with some models in the past!

I did delete the old liveries and install the updated ones. So its likely not that I would think. Now the WASM folder is interesting and I have not deleted it but wanted to do that. This does feel similar to some types of WASM crashes I have seen. Now the irony is where is the iFly WASM folder? I found instructions for locating it but interestingly the iFly MAX was not listed in there. I believe it was in the past but I wonder if they somehow moved it?

I did read this bit of info that iFly put out. Its currently set for auto and I don't launch it manually. It loads automatically when I load the aircraft as recommended. It seems at least on my system the memory issue is still present even when following iFly's recommendations.

Unfortunately I had my 3rd CTD at the 2 to 2.5 hour mark with the iFly MAX 8 in FS2024 today. Last night I completely uninstalled and reinstalled it in the hopes it would not happen again. This not something that usually happens on my system with other aircraft and the iFly MAX 8 before SP1. It is my opinion something is still a bit haywire with the FS2024 install at least for some users. This has been reported by some others out there. I do know its an experimental build but not sure if this specific issue is related to that? Its possible this new build in SP1 is just very resource heavy and many mid level systems just give it up after a period of time. Hopefully someone else out there has found a fix for it? For now I am not going to fly with it much until an update comes out that hopefully addresses the issue.

I uninstalled and reinstalled the MAX 8 today in an effort to cure the 2 hour CTD in FS2024 that has now happened twice. I noticed I forgot to delete the previous ifly-aircraft-data folder during the first uninstall of the older version for the new install of SP1. I kind of doubt it has anything to do with it but just maybe it does? I will find out tomorrow when I try yet another long haul flight. Yesterday it CTD 2 hours into an SEA-ANC flight and today it did it again right at the 2 hour mark on a SEA-KEF flight. Usually when I am doing something else like hitting a switch or or changing views. The whole FS2024 program just disappears instantly.

It's probably going to be another year at least for the MAX 9 at this rate. The MAX 7 and 10 can wait since they are not certified and in service yet but the MAX 9 is the work horse and more popular than the MAX 8 in US skies at least. I hoping to see iFly introduce it a bit sooner but it is what is what it is. Maybe with a bit of luck it will come sooner? The native version for FS2024 just might make it out in the next few months. After that work begins on the MAX 9. Not sure if it is still this way but back in the old days once you have the systems finalized the rest is just modeling. Of coarse the models are a lot more detailed but I imagine perhaps a 3 or 4 months after the FS2024 MAX 8 is released? Just maybe the MAX 9 will make it time to for Christmas? We will just have to see!

I like the new model and it flies really well. Really like the update except I am getting a CTD pretty much on the clock at the 2.5 hour mark. This is FS2024 and I heard of some issues in FS2024 so hopefully its a known issue and be fixed in an update. Also some new news on the Max 9 would be nice. In the US market the Max 9 is where it's mostly at except on some thinner long range routes in many cases. SWA being the exception flying Max 8 exclusively.

Not really anything new despite several updates. They recently announced a version 2 of the 727 with lots of updates and improvements. No real information on what the improvements or other details or any sort of time line. I guess we will know more in the future! I hope they throw in a non hush kit model at some point soon.