13 hours ago, Ray Proudfoot said:

@MariuszKr why are you quoting your own post and replying to it?

I think for emphasis.

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!

1 hour ago, longhaul747 said:

Microsoft.Limitless_8wekyb3d8bbwe\WASM\MSFS2020\ifly-aircraft-737max8

Glad you found it. Mine would be in something like …/localroaming/packages/…wasm/…

Anyway you should have gotten the right one. Good luck with your acid test

As far as i know there is a Hotfix in the work for MSFS2024 for some problem that happens in MSFS2024 but not in MSFS2020 !

But all takes a little while at the IFLY devs..

cheers 😉

Edited 15 hours ago15 hr by pmplayer

3 hours ago, longhaul747 said:

I did after a bit of searching find the WASM folder for the SP1 version of the iFly MAX 8.

What do you need to search it for? You can go directly to it in the IFly Manager by using the "Manage Product" button and then clicking on "Data Folder"

13 hours ago, longhaul747 said:

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 can understand your frustration. I wonder if some deep investigation may help as I'm not sure if it might be something regarding routes and FMC induced CTDs.
I say this because I noted on your 1st 2 flights, you flew similar routes, and maybe you did on the 3rd? (I frequently fly out of my hometown airport on multiple, similar routes)

I've seen it in the past (in several vendor's planes that have intricate connections with navigation databases, not just iFly), where an errant waypoint, procedure, etc in the database has a data point sitting out there, just waiting for someone with just the right PC configuration, external hardware, MSFS settings, etc to trigger a CTD when the plane either encounters that waypoint, or its entered in the FMC. And even if it lets the waypoint, or combination of specific waypoints pass on the ground during preflight...it won't cause havoc until the sim has been running a few hours, caches fill up with data, empty as you progress on your route, fill up again with more data, on and on, until a limit or trip point is reached, then you're suddenly looking at a desktop screen again.
Sometimes the trigger is you innocently clicking a LSK on the CDU around that 2-4 hour point, and chamber in the CTD barrel was already loaded, just waiting for you to touch that key.

Sounds crazy and far-fetched sometimes, but computers and highly complex and data-intensive software can create all sorts of "gremlins"...so much that a movie was produced echoing it (Phobe Cates....sigh).

To me....it's baffling that I can fly this plane, on my pc with impunity, having great performance, no errors, while others struggle to even get it loaded and parked at the gate. This is the very nature of our ability to have computers so varied in their parts and configs, that issues are bound to crop up.

Anyway, TLDR....if you could go to the official iFly Discord and post your issue in the MRO section with your PC config, details of your MSFS settings (I just grab screenshots of the pages and post them), the livery you were flying, in 2020/2024, MSFS Store or Steam version, and a copy of the 3 routes you've flown to produce the CTD, I'll see if I can replicate your conditions and reproduce the CTD.

In the interim, if you could:

1. In MSFS settings, turn on Developer mode.
   

2. When parked at the gate, you should see the developer's black ribbon at the top of your screen, Click Debug/Display FPS.
   If its solid red and the FPS is low already...your system is struggling (I know I'm stating the obvious, but this helps when you're getting closer to the 2 hour mark. I'd grab some screenshots of the FPS meter around the 2 hour mark, in case you CTD so we can see what the state was beforehand)
   I have a "modest" PC, 7800X3d, 32gb slow (3000) ram, 4070ti and modest MSFS settings, and you can see even with a solid cloud base, I'm pure green with 70 frames, It doesn't' flicker red/green. Sure it does on the ground at KTPA from VerticalSim with its complex scenery, but the experience is smooth because its just touching red for milliseconds.
   

3. Load the plane...do not import or manually load a flightplan, just load enough fuel to make the trip.

4. load a default iFly livery (the orange one)...try to pick the same seating config as the airline you were using (I'm guessing Alaska based on the routes)

5. load CLEAR weather.

6. Take off and use heading select to turn to the general direction of one of your previous destinations. Use the MCP to climb up to the flight level you had previously flown. (we're trying not to touch the CDU in this experiment)

7. Open the Window's task manager (CTRL+SHIFT+ESC shortcut). Sort the columns by Memory (click the header...maybe twice to get the most memory-intensive app to the top, should be MSFS by far)
   Check the memory as you get closer to the 2 hour mark...if its 90% or higher, you may encounter.....anomalies 🤪
   

8. If you do get a CTD....use this screen below, follow the directions on the left to help you open the event viewer and save your Windows error log (this will help iFly analyze your issue and possibly find the cause).
   In Step 3...change the "Logged" field to Custom range...and change the times to a few mins before you started MSFS to a few mins after the CTD (those log files can be huge)...then save the file.
   

   
   
   

   I know this sounds like a lot...but this is what we go thru in the beta team when we are tracking down errors. No, I'm not implying that iFly has just enlisted the community to be it's beta team, but you seem genuinely interested in resolving your issue, have brought it to this forum in a respectful, adult manor, and I want to try and help you resolve this.
   This also helps everyone experiencing this if we can find the cause, that is why it's so important for folks who want to genuinely help fix issues with a popular title that is acting outside what the beta team never saw, we get this info in our official bug reporting area.
   
   I'll check out your report over at the iFly's MRO Discord section, and work with you further over there and hopefully get you flying this bird as it was intended . 😉 Just let me know when its there as I don't scour the channels daily...I'm just on the beta team and the painter...not support.
   

Concierge Service Steve. Top notch Grace!

-B

is anyone seeing massive CPU Usage for the iFly-EFB.exe ? I have about 10% here

Michael Moe

Edited 5 hours ago5 hr by Michael Moe

2 hours ago, Steve Dra said:

I can understand your frustration. I wonder if some deep investigation may help as I'm not sure if it might be something regarding routes and FMC induced CTDs.
I say this because I noted on your 1st 2 flights, you flew similar routes, and maybe you did on the 3rd? (I frequently fly out of my hometown airport on multiple, similar routes)

I've seen it in the past (in several vendor's planes that have intricate connections with navigation databases, not just iFly), where an errant waypoint, procedure, etc in the database has a data point sitting out there, just waiting for someone with just the right PC configuration, external hardware, MSFS settings, etc to trigger a CTD when the plane either encounters that waypoint, or its entered in the FMC. And even if it lets the waypoint, or combination of specific waypoints pass on the ground during preflight...it won't cause havoc until the sim has been running a few hours, caches fill up with data, empty as you progress on your route, fill up again with more data, on and on, until a limit or trip point is reached, then you're suddenly looking at a desktop screen again.
Sometimes the trigger is you innocently clicking a LSK on the CDU around that 2-4 hour point, and chamber in the CTD barrel was already loaded, just waiting for you to touch that key.

Sounds crazy and far-fetched sometimes, but computers and highly complex and data-intensive software can create all sorts of "gremlins"...so much that a movie was produced echoing it (Phobe Cates....sigh).

To me....it's baffling that I can fly this plane, on my pc with impunity, having great performance, no errors, while others struggle to even get it loaded and parked at the gate. This is the very nature of our ability to have computers so varied in their parts and configs, that issues are bound to crop up.

Anyway, TLDR....if you could go to the official iFly Discord and post your issue in the MRO section with your PC config, details of your MSFS settings (I just grab screenshots of the pages and post them), the livery you were flying, in 2020/2024, MSFS Store or Steam version, and a copy of the 3 routes you've flown to produce the CTD, I'll see if I can replicate your conditions and reproduce the CTD.

In the interim, if you could:

1. In MSFS settings, turn on Developer mode.
   

2. When parked at the gate, you should see the developer's black ribbon at the top of your screen, Click Debug/Display FPS.
   If its solid red and the FPS is low already...your system is struggling (I know I'm stating the obvious, but this helps when you're getting closer to the 2 hour mark. I'd grab some screenshots of the FPS meter around the 2 hour mark, in case you CTD so we can see what the state was beforehand)
   I have a "modest" PC, 7800X3d, 32gb slow (3000) ram, 4070ti and modest MSFS settings, and you can see even with a solid cloud base, I'm pure green with 70 frames, It doesn't' flicker red/green. Sure it does on the ground at KTPA from VerticalSim with its complex scenery, but the experience is smooth because its just touching red for milliseconds.
   

3. Load the plane...do not import or manually load a flightplan, just load enough fuel to make the trip.

4. load a default iFly livery (the orange one)...try to pick the same seating config as the airline you were using (I'm guessing Alaska based on the routes)

5. load CLEAR weather.

6. Take off and use heading select to turn to the general direction of one of your previous destinations. Use the MCP to climb up to the flight level you had previously flown. (we're trying not to touch the CDU in this experiment)

7. Open the Window's task manager (CTRL+SHIFT+ESC shortcut). Sort the columns by Memory (click the header...maybe twice to get the most memory-intensive app to the top, should be MSFS by far)
   Check the memory as you get closer to the 2 hour mark...if its 90% or higher, you may encounter.....anomalies 🤪
   

8. If you do get a CTD....use this screen below, follow the directions on the left to help you open the event viewer and save your Windows error log (this will help iFly analyze your issue and possibly find the cause).
   In Step 3...change the "Logged" field to Custom range...and change the times to a few mins before you started MSFS to a few mins after the CTD (those log files can be huge)...then save the file.
   

   
   
   

   I know this sounds like a lot...but this is what we go thru in the beta team when we are tracking down errors. No, I'm not implying that iFly has just enlisted the community to be it's beta team, but you seem genuinely interested in resolving your issue, have brought it to this forum in a respectful, adult manor, and I want to try and help you resolve this.
   This also helps everyone experiencing this if we can find the cause, that is why it's so important for folks who want to genuinely help fix issues with a popular title that is acting outside what the beta team never saw, we get this info in our official bug reporting area.
   
   I'll check out your report over at the iFly's MRO Discord section, and work with you further over there and hopefully get you flying this bird as it was intended . 😉 Just let me know when its there as I don't scour the channels daily...I'm just on the beta team and the painter...not support.
   

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.

Still haven't touched it yet. Does 4x time acceleration work correctly?

2 hours ago, longhaul747 said:

Hopefully clearing the WASM folder helps!

fingers crossed!

7 minutes ago, DAD said:

fingers crossed!

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.

4 hours ago, Michael Moe said:

is anyone seeing massive CPU Usage for the iFly-EFB.exe ?

I'm not getting great performance on this update. It's definitely not bad, but far more power hungry than the Fenix birds. Maybe the they'll do some further optimizing.

5 hours ago, G-YMML1 said:

Still haven't touched it yet. Does 4x time acceleration work correctly?

Yes, on straightaways it's nice and solid here. You'll want to drop it back for turns.