Steve Dra

I think I saw another simmer in the iFly Discord channel mention he had this problem too. I couldn't find it for reference, but I'm sure it was in the chit-chat channel as I didn't see it in the "MRO" (bug reporting) section. If you experience it again, can you gather as much info as you can and report it over there? That is the only way we can get a possible fix. Yes...not that I can talk professionally on its flight dynamics (but we have someone here who can 😉), I know any ported models will suffer limitations when it comes to detailed CFD integration. We can't wait to get our hands on the 2024 native model, and as soon as we do and can talk publically about it, you can bet we will. :)

Kenco is streaming it now. (17:26Z)

TwoTone Murphy was showcasing it about an hour ago...I watched a bit and like how the weather rendered. He was on the ground and going thru the settings and it seemed robust. I left before he made any opinions, but he seemed to like it. He's on arrival now so he may have a final opinion on it after the flight (its 13:18z now as I type this).

I use it all the time...works perfectly for me. The trick is that you have to use the "Intelligent Cruise" features iFly built into the aircraft so it behaves properly in cruise when 4x is automatically activated. With it on, once you hit your cruise altitude (It won't engage in climb or decent)....It will go up to 4x in between waypoints on your flightplan. It will switch to 1x a few miles before a turn, and then back to 4x after the turn. One trick I use to really speed things up is review the flightplan and delete any waypoints that are essentially drawing a straight line, because the sim will slow to 1x at each of them (in cruise). If they are mandatory, then you keep them, but I don't fly on Vatsim (while testing), so I take shortcuts all the time to MAXimize my testing time. :)

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: In MSFS settings, turn on Developer mode. 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. Load the plane...do not import or manually load a flightplan, just load enough fuel to make the trip. 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) load CLEAR weather. 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) 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 🤪 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.

By far the best time to fly in flightsim (Sunrise is great too). I've found myself purposely moving the time slider to get just that perfect sky...here is a sunset departure out of KPIE And a sunrise out of Chicago this morning.

That could be one of the many problems....some users mention they've done it, other's have not mentioned if they did. The bottom line is that iFly and Flight1 are keenly aware of the performance issues users have been reporting, and while their reports are smattered all over the many discord channels Flight1/iFly maintains, the sections the moderators implore simmers to use (the MRO sections), most folks just don't. I filtered the channels to only show posts that have the word "performance" in them...here is what I found: 837 total (for all versions not just SP1 released Friday) 270 were in chit chat (where the channel topic says "For general chit-chat regarding the iFly MAX. This channel is not officially monitored for support." 202 were in user-to-user support (the pinned post by Flight1 says "you can use this forum for user-to-user support questions. Do not expect a staff reply here, but there may be instances where other members may have an answer for you. If your post requires potential attention from official staff, please post in the MAX8 MRO - OFFICIAL SUPPORT section." 87 were in MRO, and only 7 since the release of SP1 The other 311 posts were all over the place like in screenshots, etc. Performance issues after an update are a staple in any computer title...this is nothing new. I've experienced it as much as anyone on titles where I was not in the beta team. For those that I was a part of, you can be sure I reported and troubleshot it to the best of my ability, and in this particular case with SP1, none of the beta team reported issues. Maybe it's because we initially test with clear community folders (adding our 100s of add-ons after the current build is deemed stable by the team), do a clean install every time we get a new version, clear caches, etc...or whatever proven steps taken to reduce the chance of performance issues. Some of us do negative testing, and I personally always do "customer installs" (no offense), where I purposely ignore all the pre-install/post-install steps, just to see what happens and have mitigations/responses ready for when the flood of these type of posts start arriving 10 minutes after the release. Some of the time, the "customer install" goes fine...at 1st. Then after a few hours in the air, things go wonky...where have I heard that before? 🤔. Then I do a full re-install, try again with the recommend steps, and I never had performance issues after that. That is the best we can do as beta testers. We can't report what we don't experience. It's not a conspiracy theory. iFly certainty didn't release SP1 because it "was rushed out out of pure spite just to quiet down the critics..." 🙄

I'm baffled as to why so many are experiencing these performance issues when none of the beta team seemed to encounter it. I was thinking it may have been a last moment edit by the devs in the last RC build before release and we didn't get a lot of time to fly/test it....but I've flown a dozen flights since release with no change in my excellent performance (7800x3d, 32gb slow ram, 4070ti and above moderate settings). I saw someone mention in our discord it was generally happening in the 8200 model...but that is the one I fly almost exclusively with my Allegiant paint (and they fly out of my home airport KPIE). Some also said that the memory gets eaten as the flight progresses...some saying its down to 15-20 frames after 20 mins. All my flights are generally 1-3 hours, and I've never experienced this. Maybe the folks who are knowledgeable about these things will get the dev team some good info when reporting their findings on their machines. I know for a fact that if you jump into a flight after installing, without the proper exits and reboots before trying an actual flight, you'll get abysmal performance.

They are a bit slow with the wheel. I use left click and hold on the knob to turn it left and right click/hold to turn it right quickly.

Click the screw in the upper right corner of the CDU is sits above

That may not be too far from the truth. 🤔 As @Stearmandriver noted, the iFly devs are very receptive to suggestions by the beta team, and I and Jviation may have had some late inning suggestions regarding the texture/model configuration that could have impacted the timeline. But rest assured, they were well worth it 😉

Thanks Mark. I don't have a list of all the liveries handy, and iFly has taken the iFly manager app offline just now, which denies us access to all the liveries. When its back up you can browse thru the list (there is a LOT) But rest assured that all the Icelandair colors have been done by the legendary Jviation...one of the best painters in our community. 😉 I did not see Flyr in the list of liveries included with the plane...but I'm confident that it may have already been done (have not checked flightsim.to)

Not really. They moved (optimized) some of the textures on the maps, changed the engine parts map, and a few other things. At first glance, an old livery may look ok in the new SP1 release, but you'll see some oddities like the engine exhaust area, for example. In addition, they moved all the rivets, panel lines and screws onto the model (or are decals with super high resolution), so the painted rivets will have to be removed by the painters. At normal viewing distances, you may not even notice...but up close you'll see both the painted and modeled rivets (and most panel lines). The great thing about this is that you can zoom in until your nose is touching the skin of the fuse and the rivets and lines screws will not blur...at all. Painters should have little trouble updating their liveries, and I expect they'll get to it pretty quick. All the liveries that come with the update that were painted by me and Jviation will have all the updates ready to go.

I've been heads down getting liveries ready for the release...but in addition to all the updates in SP1 most folks glaze over is the addition of the 8200 variant. With that, Jviation and I have been busy painting liveries for the new model (and updating our existing ones for the standard Max 8) I'm sure to the delight of the Ryanair fans that, above all other airliner "enthusiasts"...seem to be the most highly "spirited" when it comes to their airline, hehe. Here are a few screens for those who don't frequent iFly's Discord: This is "just" a MAX 800...but a nice example of Jviation's excellent painting skills that will come with the update. And here is the interior with the new 8200 cabin: For a free update....the community is getting one heck of an upgrade in this "Service pack". ;)

Mike, I sent you a PM to see if I can help off-line.