4 hours ago, DAD said:

But that seemingly requires a Navigraph subscription?

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.

3 hours ago, Stearmandriver said:

Most of these issues are coming from old liveries hanging around. Be sure you follow the install instructions to the letter, to nuke every bit of old liveries first. For reference, I easily hold 60fps in cruise with FSR3 frame gen on, everything high or ultra, on an i9 and 3070. Without frame gen, 45fps is still easy. So you've got some kind of conflict happening.

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.

3 hours ago, Stearmandriver said:

to nuke every bit of old liveries first.

I deleted everything, only liveries I have so far are for the 8200

I'll try the standard model tomrrow

Edited 13 hours ago13 hr by Tuskin38

3 minutes ago, Steve Dra said:

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.

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

Is GSX compatible with iFly 737? I tried to push back via GSX and airplane tip over on its tail .

I don't use GSX, so I don't know anything about that.

I agree with Steve about the performance problems; this looks to be very user-specific, but it does appear that something is not playing well with some systems. It's just so bizarre that no one experienced it in beta; there have to have been at least three or four dozen beta testers on the team. Obviously there are more than that many different user system configurations, but what bad luck no one experienced it earlier.

It'll be figured out.

Any word on a GSX Pro update for seated passengers to appear correctly in the cabin for iFly SP1?

Edited 11 hours ago11 hr by amsfsx02501

no issues for me they seat as normal as before you need to uncheck/ recheck the ifly seated pax in the gsx section as per any update of any aircraft

Edited 9 hours ago9 hr by pete_auau

2 hours ago, sd_flyer said:

Is GSX compatible with iFly 737? I tried to push back via GSX and airplane tip over on its tail .

no issues for me gsx work fine with push back

2 hours ago, sd_flyer said:

Is GSX compatible with iFly 737? I tried to push back via GSX and airplane tip over on its tail .

Working fine here

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.

33 minutes 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.

Well, for me it's working beautifully, I don't use CPDLC so I can't comment on it, but the new EFB is very well done and easy to use, the performance os great so far, and in all honesty I can't even cobsider this first release inferior to the PMDG 737-700 I also own...

Very satisfied customer here 👍👍👍

42 minutes 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.

This comment doesn't really make sense.

1. SP1 was never going to be native 2024. That was communicated very clearly on the roadmap after initial release. SP1 first, native 2024 next, Max9 and further versions after, hotfixes as necessary. There has been no change here.

2. There was no rush in releasing this. It has been in extensive testing literally for months. I couldn't even begin to create a log of all the fixes and improvements. There never was a release timeline, beyond "when ready".

3. There's nothing "broken" in this build. If there was, everyone would be experiencing problems and clearly, the majority of users are not. I'm not saying that some users aren't experiencing issues related to conflicts on their individual systems - the devs are aware of the discord threads and I'm sure will be looking at fixes, but this is to be expected with a release of this magnitude. But, none of the testers saw these issues and feedback is overwhelmingly positive from most users, so clearly the release is not "broken".

I understand frustration, but inflammatory and overly dramatic rhetoric isn't going to help diagnose or fix anything, and misinformation is never helpful.

All ok here, did a 3hr flight last night. PC specs below.

14 hours ago, DAD said:

But that seemingly requires a Navigraph subscription?

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).