It’s so hard for me to understand the mindset of those who make such absurd decisions.
We had a fully functional plane in MSFS2020, the Beaver was a joy to fly, and everything became nearly perfect with the free GotFriends addon, the 40th Anniversary Expansion.
And now, what changed? Did the physics change? Is flying the Beaver more “real” now?
Things have stopped working, the manual pressure pump didn’t work the last and only time I tried it in 2024, and there are issues with radios, lights, and GPS.
What a senseless decision to present a worse version of something that was almost perfect.
And just thinking that I paid for this…
I think that’s just it. Something changed in the way 2024 handles the flight model that causes it to calculate more drag, or less thrust/power for specific fuel consumption on piston engines… something. It’s happening in the 172 as well.
i have tried it out this evening in SU2 beta and it appears the fuel pumps and autopilot are functional again so that’s a bit of good news.
i haven’t really looked at the fuel consumption lately i’m gonna do a test flight tonight and compare the burn numbers. the thing is, the simbrief numbers don’t seem realistic either, it seems to be estimating a max distance of around 330nm but googles says 380 and different sources seem to have slightly different numbers
The lights are now working in SU2 beta, and the invisible chocks on the floatplane version seems to be gone now too, so that’s good. This is the first time I’ve loaded into MSFS for a while so forgive me if these things were fixed in the last SU1 update.
It’s far too easy to put the plane in a vertical roll on the ground after very light braking, even if you were taxiing really slowly on the ground. Sorry, but on a real Beaver, this kind of thing never happens, unless you brake very hard while the plane is traveling fast and with the engine a little pushed. On MSFS24, you just start from the parking lot, you roll very gently, you brake a little before turning into a turn, and if you forget to pull the yoke all the way back, the plane systematically goes forward very hard and crashes vertically, on the ground.
Might have found a new kind of bug with the DHC-2 Beaver (SU2 beta 1.4.9):
when starting..
“cold and dark” on the water,
with floats and GPS version,
the Garmin 530 430 don’t go past the “press OK” status on booting.
The buttons seem to react (move / click), but trigger no action to proceed the booting process.
Did you press it the moment it came up or did you wait a bit? There has been an issue with some aircraft where if you waited some time before pressing it, it stopped doing anything. Did you try switching the avionics off and on again?
Yes waited quite a long time, didn’t work.
But switching avionics off and on again “fixes” it as I just noticed. On the 2nd boot it can be clicked past the “OK” on the Garmin.
Love this plane but floats version still no way to remove wheel chocks, (there are none but they are enabled, making it impossible to taxi from stand) must be done via developer mode, debug, aircraft, covers and chocks.
In the SU 2 Beta, they’ve already implemented a command to remove all the parts with just one click (though some covers on certain aircraft still can’t be removed).
I believe this will be partly resolved when the normal version of Update 2 is released.
I assigned this new command to the same keyboard shortcut I use to enter the aircraft, that way, when starting a flight, with just one click, we enter the plane and remove all the bits and pieces.
It is issues like these with the Beaver that has me absolutely pretending that all the included aircraft don’t exist, with the exception of a couple, such as the Grumman Albatross. I feel for those that actually want to use Career Mode and are stuck with what they are forced to use for aircraft.
Bugs like this one are so maddening, because you know this is an SDK backwards compatibility fail and it was just pushed through (if anyone even bothered to notice it…):
These sorts of issues, throughout the default aircraft, are totally disheartening, because you know the history of seeing fixes is one rife with missed opportunities and never-going-to-happens.
And to think it was almost perfect in MSFS2020 with the GotFriends addon and the other Cargo addon.
They could have just kept it the same, or made it available as optional, but we don’t even have the option to deactivate it in the 2024 version, and activate the 2020 version, like we can with the Cessna 172 Classic.
They chose to deliver something inferior, I don’t understand.
There is a fair amount of this throughout 2024. I, also, don’t understand.
There are solid aspects of 2024 to love, but I have to strip away, ignore, and/or workaround so many of the surrounding and supporting elements that makeup all this “inferior”.
It’s is totally and utterly maddening and you have to wonder if/when we will actually be free of any of it.
I often wonder how Blackbird feels about the Beaver they developed (that carries their name on the EFB’s splash page) when it has a number of issues that plague it. Would they want to fix it if they had free license to do so? Do they expect payment? Will Microsoft not let them touch it?
If I’d developed it, I’d be driven bonkers by these negative reports, and would want to do what I could to rectify them.
