8 minutes ago, btacon said:

Well that’s not what I expected, but it’s workable to a fashion.  What I looked for and expected was a clickable single field where totals could be entered.  For example in your fuel example to the right of the slider a value of 1091 can be seen.  If that was editable I would agree with your premise but what you are showing is both convoluted and not intuitive to the device IMO and so my take on the EFB remains…”meh”.  Thanks for the education and Blue Skies.

-B

On the iFly, enter weights and fuel in the EFB. 

10 minutes ago, Bobsk8 said:

On the iFly, enter weights and fuel in the EFB. 

Yes.  As you can in the iFly bird I would expect the Asobo/WT EFB to exhibit the same behavior. Unfortunately it does not, hence…meh.

-B

11 hours ago, DModjo said:

Sad to read that developers are already wrapping up development for MSFS 2020. Especially when 2024 is still a piece of junk.

I guess there are still some childish individuals out that will make an idiotic statement to get a rise out of folks. Grow up. 2024 may have started off with a ruff start, but it's the best sim out there now. I haven't touched 2020 in over 9 months now. It was a great sim and I'll miss it but It's getting close to house cleaning it from my HD very soon. It might not make the cut during Xmas holidays.

Is a pity that the issue at the Max which cannot fly straight at acelerated time rates more than 2, is not mentioned as to be fixed.-

8 hours ago, Christopher Low said:

Come on. Let's not get silly. Everybody knows that the best flight simulator ever was Flight Unlimited 3 (with the FU2 San Francisco scenery installed) 

Actually was that also able to replicate jet engine power loss in a storm?  I know one sim did...

I would not be surprised if that was the case. Despite its rushed release, Flight Unlimited 3 was way ahead of its rivals in many departments. I have really fond memories of the time (2000-2008) when I used Flight Unlimited 3 exclusively. I remember one time suffering an engine failure in the Beechjet 400A, and somehow managing to get it down on a runway with some severe asymmetrical thrust!

18 hours ago, btacon said:

The structural differences between MSFS 2020 and 2024 are too vast and extremely time and labor consuming to develop for both

But... 🤔... 

10 hours ago, btacon said:

Yes.  As you can in the iFly bird I would expect the Asobo/WT EFB to exhibit the same behavior. Unfortunately it does not, hence…meh.

-B

Difference between a good payware and default aircraft. 

20 hours ago, RNAVV19R said:

Finally!

Maybe it's just me but the overall texture of the cockpit wall around the EFB looks much improved...

One thing I didn't see specifically mentioned was getting the RAAS system to work in 2024.    I hope that it's simply covered under "general bug fixes" because I really want this feature.    Was hoping they'd get it to work in the latest update but I guess not. 

Surprised to hear that SP1 isn't even in beta yet.

1 hour ago, 11bee said:

One thing I didn't see specifically mentioned was getting the RAAS system to work in 2024.    I hope that it's simply covered under "general bug fixes" because I really want this feature.    Was hoping they'd get it to work in the latest update but I guess not. 

Surprised to hear that SP1 isn't even in beta yet.

The only item I find annoying in the iFly, is  the speed brake arm, when you assign a control to it, vibrates back and forth. If you manually move it with the mouse, it is fine. Seems like a really simple fix, but it has been that way since day one. 

3 hours ago, Bobsk8 said:

The only item I find annoying in the iFly, is  the speed brake arm, when you assign a control to it, vibrates back and forth. If you manually move it with the mouse, it is fine. Seems like a really simple fix, but it has been that way since day one. 

Thanks for mentioning this. I thought it was something wrong with my controls. 

9 hours ago, sloppysmusic said:

But... 🤔... 

not really the easy backwards compatibility that Asobo promised customers (and developers) indeed.

That realisation/disappointment has been documented quite early on by Raul of FSreborn. 
A lot of custom code behaves differently in 2020 vs 2024. 
Then there is the very different LOD and texture handling of the models on top of that, which turns the development for both sims into separate pipelines as well. 
 

Too much work unfortunately for developers to handle sustainably in return of a 2020/2024 package price or a small upgrade fee (as customers rightfully expected after reading the initial Asobo compatibility announcements)

I assume that this "twin pipeline" development is not as much of a problem for airport addons? Most airport developers still seem to be releasing new products for both simulators.

Edited August 15, 2025Aug 15 by Christopher Low

1 hour ago, Sylle said:

Too much work unfortunately for developers to handle sustainably in return of a 2020/2024 package price or a small upgrade fee

Retaining compatibility is what dropped P3D out of the lime light … 4 year gap until breaking changes seems reasonable compromise.  Can’t progress without forcing change in a product this complex.

I respect MS/Asobo stances, keep up or drop out.

Edited August 15, 2025Aug 15 by SayAgain