2 hours ago, MariuszKr said:

It feels like this SP1 (1.1.0.0) was rushed out out of pure spite just to quiet down the critics before the one-year anniversary. Dropping an incomplete update, cutting promised features like CPDLC, and keeping the MSFS 2024 version labeled as 'Experimental' is a joke.

It’s a classic defensive move: 'You didn't want to wait, so here is a broken build, now deal with the performance drops, broken liveries, and bugs yourselves while we blame the platform.' Instead of taking responsibility for a year of delays, they delivered a headache. True propaganda over engineering.

I think you are a joke !!

This is just a great work and update for me, the only thing to say is that i speak for MSFS2020..

cheers 🤔

2 hours ago, MariuszKr said:

It feels like this SP1 (1.1.0.0) was rushed out out of pure spite just to quiet down the critics before the one-year anniversary. Dropping an incomplete update, cutting promised features like CPDLC, and keeping the MSFS 2024 version labeled as 'Experimental' is a joke.

It’s a classic defensive move: 'You didn't want to wait, so here is a broken build, now deal with the performance drops, broken liveries, and bugs yourselves while we blame the platform.' Instead of taking responsibility for a year of delays, they delivered a headache. True propaganda over engineering.

Nonsense.... you're almost certainly either using an old (non-supported) livery, or you haven't installed correctly, according to the SP1 instructions.

But rather than investigate your mistakes, it is of course "a terrible update" 😄

2 hours ago, MariuszKr said:

It feels like this SP1 (1.1.0.0) was rushed out out of pure spite just to quiet down the critics before the one-year anniversary. Dropping an incomplete update, cutting promised features like CPDLC, and keeping the MSFS 2024 version labeled as 'Experimental' is a joke.

It’s a classic defensive move: 'You didn't want to wait, so here is a broken build, now deal with the performance drops, broken liveries, and bugs yourselves while we blame the platform.' Instead of taking responsibility for a year of delays, they delivered a headache. True propaganda over engineering.

It's a you problem mate. I followed the installation guide step by step and I couldn't be happier with performance and all the new fetures.

25 minutes ago, MassiveSim32_Jase said:

a you problem mate. I followed the installation guide step by step and I couldn't be happier with performance and all the new fetures.

Ditto for me. Followed instructions, no issues. Runs and performs great. YMMV. TANSTAAFL. Blue skies,

-B

Edited 3 hours ago3 hr by btacon

11 hours ago, Stearmandriver said:

Ok, received answers. For the simbrief flightplan import and automatic fuel/payload loading, both a simbrief and navigraph account (both free) are required. You do not need a navigraph subscription.

Apparently this is all explained the the documentation in the, go figure, "documentation" folder 😁. I haven't read it myself haha, or I would have pointed you there in the first place. Sorry lol.

Thanks, confirmed. connected to my (free) Navigraph account, linked my SimBrief ID and all fine, FP was imported. apologies for not RTFM before ;-)

1 hour ago, JYW said:

It doesn't. It just looks that way. Scan or go to navigraph/code (or whatever) to link your SB to the iFly... then SB import works. At first this appears to be for charts but it's not - it's just to link your Simbrief. It's just because they refer to SB as 'Navigraph' (which to be fair it is).

Thanks, Bill. As said before, that did the trick

19 hours ago, sd_flyer said:

That is it! Thank you very much! I feel so stupid LOL

you saved me too. did not take into account to use the mouse wheel. may change it to MSFS logic in the manager...

Nice! I like the new EFB. I prefer it to the PMDG now.

11 hours ago, UAL4life said:

Maybe they didn’t uninstall properly? I’ll be sure to try and uninstall the aircraft and liveries prior to installing the new update…

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 held off on buying the Max until SP1, and so far I'm really pleased. Obviously no software is ever perfect, but my first impressions have been very positive. My favorite thing by far is how it hand-flies. Last night I had one of the most satisfying landings I've had in the MSFS 2020/2024 ecosystem in the last six years, into Palma de Mallorca at sunset.

4 hours ago, MariuszKr said:

It feels like this SP1 (1.1.0.0) was rushed out out of pure spite just to quiet down the critics before the one-year anniversary. Dropping an incomplete update, cutting promised features like CPDLC, and keeping the MSFS 2024 version labeled as 'Experimental' is a joke.

It’s a classic defensive move: 'You didn't want to wait, so here is a broken build, now deal with the performance drops, broken liveries, and bugs yourselves while we blame the platform.' Instead of taking responsibility for a year of delays, they delivered a headache. True propaganda over engineering.

The joke is you. You clearly didn't follow installation instructions. It's running fine here and after the last livery update, all is golden. Instead of making moronic statements, why don't you try some constructive criticism like everyone else. What a caveman statement.

No problems my end. Loving the new EFB and is once again a joy to fly.

23 minutes ago, outermarker said:

I held off on buying the Max until SP1, and so far I'm really pleased. Obviously no software is ever perfect, but my first impressions have been very positive. My favorite thing by far is how it hand-flies. Last night I had one of the most satisfying landings I've had in the MSFS 2020/2024 ecosystem in the last six years, into Palma de Mallorca at sunset.

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.

First flight with SP1. Things went perfectly. No performance issues noted. Love the updated engine sounds. The EFB is a massive step forward and I can now save panel states with no issues. Sorry some are reporting issues but I gotta believe it's something with their systems. As was noted above, this thing is a blast to hand-fly. Nice work iFly, now get me the -10 in time for the real thing to be delivered.

Everything seems fine so far but I'm stumped on how to spin up the ALT value. It might have to do w/

22 minutes ago, 11bee said:

First flight with SP1. Things went perfectly. No performance issues noted. Love the updated engine sounds. The EFB is a massive step forward and I can now save panel states with no issues. Sorry some are reporting issues but I gotta believe it's something with their systems. As was noted above, this thing is a blast to hand-fly. Nice work iFly, now get me the -10 in time for the real thing to be delivered.

Just completed the update, setup everything in the lovely new EFB and about to TO from LIPZ>EHAM. Looks fabulous so far!

I was hoping this might have been resolved, though chances are IFly didn't know about it and maybe I can contact them thru Discord. I use Spotty26's lovely FlyBy cam option and as of the moment of the 5 planes I fly this is the only one that does this, which someone suggested is an LOD issue. Pardon the HDR10:

Edited 35 minutes ago35 min by Noel