F28 V2 issues & suggestions so far
-
Another issue I have is unable to set the course on Nav1. Turn the knob and cant change from 000. Nav 2 is fine. Loving the v2 though
-
Can I add another "is this accurate or a bug?" question?
I've been flying V2 of the F28 in Australia (on the old MMA/Ansett routes), so the real-world weather is hot with temperatures of 25-30deg. C.
With V2 I'm often getting TGT over-temperature warning lights on initial climb once setting the TTC switches to 'Climb', and it requires large power reductions (below 90% HP - so less than standard cruise power) to keep them off, which makes climbing very slow indeed.
Climbing to higher altitudes (so lower ambient air temps) I can gradually open the throttles to standard climb power (96.5% HP) without triggering the warning lights. But even once up at cruise altitudes, the TGTs stay quite high - at FL280-300 and outside air temperatures of -20 deg. C or less the TGTs are in or just below the yellow arc at cruise power (88-91% HP).
I never got TGT warnings on climb-out with the earlier versions of the F28, even in hot and high conditions. And I'm sure the cruise TGTs were much lower.
I did do a test flight in sub-zero ground temperatures in Sweden and even at full-power takeoffs the TGTs stayed nicely within limits.
Now, this might be a realism update for V2 and the R-R Speys don't like take-offs in the deserts of Western Australia, but I don't think the F28 would be cleared for commercial service with performance at the power settings/climb rates that are needed to keep the TGTs in limits as I've found them so far!
Can I also just say that, that one quirk aside, I'm really loving F28 V2 otherwise! It's a great update and as someone who posted here about the old version's 'nodding donkey' pitch control at low speed/low weights the update, I couldn't be happier with how V2 flies - it's an absolute joy to hand-fly in circuits now, and the autopilot (especially with the new Altitude Controller option) is rock solid in every situation I've put it in so far. Lovely job, JF!
-
Can I add another "is this accurate or a bug?" question?
I've been flying V2 of the F28 in Australia (on the old MMA/Ansett routes), so the real-world weather is hot with temperatures of 25-30deg. C.
With V2 I'm often getting TGT over-temperature warning lights on initial climb once setting the TTC switches to 'Climb', and it requires large power reductions (below 90% HP - so less than standard cruise power) to keep them off, which makes climbing very slow indeed.
Climbing to higher altitudes (so lower ambient air temps) I can gradually open the throttles to standard climb power (96.5% HP) without triggering the warning lights. But even once up at cruise altitudes, the TGTs stay quite high - at FL280-300 and outside air temperatures of -20 deg. C or less the TGTs are in or just below the yellow arc at cruise power (88-91% HP).
I never got TGT warnings on climb-out with the earlier versions of the F28, even in hot and high conditions. And I'm sure the cruise TGTs were much lower.
I did do a test flight in sub-zero ground temperatures in Sweden and even at full-power takeoffs the TGTs stayed nicely within limits.
Now, this might be a realism update for V2 and the R-R Speys don't like take-offs in the deserts of Western Australia, but I don't think the F28 would be cleared for commercial service with performance at the power settings/climb rates that are needed to keep the TGTs in limits as I've found them so far!
Can I also just say that, that one quirk aside, I'm really loving F28 V2 otherwise! It's a great update and as someone who posted here about the old version's 'nodding donkey' pitch control at low speed/low weights the update, I couldn't be happier with how V2 flies - it's an absolute joy to hand-fly in circuits now, and the autopilot (especially with the new Altitude Controller option) is rock solid in every situation I've put it in so far. Lovely job, JF!
@GroverJ41 Thanks for the kind words. The TTC effectiveness at high OATs is something that was been affected by a last-minute change before release that we didn't spot. This has already been fixed on our latest internal build and will be included in the next update to the F28 Professional.
Mark - Just Flight
-
I have missing speed bugs.
And on my first flight I couldn't get the left engine started. Worked this time, though. I'll update if I have the issue again.
-
I have missing speed bugs.
And on my first flight I couldn't get the left engine started. Worked this time, though. I'll update if I have the issue again.
-
@OwlInFlight After starting from a cold and dark state, the speed bugs can be set by clicking on the relevant section of the speed card on the first officer's main instrument panel.
Mark - Just Flight
@Mark The speed bugs are not physically there on the gauge. I'm clicking the card and they don't even appear.
-
Another triumph. All Just Flight aircraft I have are splendid - and this one does not disappoint!
Just an additional issue, if I may add one:
Specifically MSFS2024 and specifically when in VR - there is a pilot's lower torso poking through the bottom of the external fuselage view where the nose wheel doors are situated.
I have tried turning off the cockpit crew on the in-cockpit tablet and tried different versions of the F28, but this fella is in all of them - from sitting on the runway prior to take off all the way to cruising at 20,000ft and beyond.
He's not there in MSFS2020 in VR and he's not there in MSFS2024 in 2D...it is specifically MSFS2024 in VR. I'm using a Pimax Crystal Light headset. I will try also with the Quest 3 later today, but I think it is unlikely to be headset dependent.
Thanks -
@OwlInFlight After starting from a cold and dark state, the speed bugs can be set by clicking on the relevant section of the speed card on the first officer's main instrument panel.
Mark - Just Flight
@Mark Compare to this V1 screenshot where they're visible.
-
Hi again. Ref the pilot hanging out of the fuselage in MSFS2024 VR, I've tried also with the Quest and it is the same there.
Just to confirm:
- It only shows in MSFS2024 in VR. When I turn back to 2D he/she vanishes
- It doesn't show in MSFS2020
- It happens with Cockpit crew option off or on
- It affects all of the versions and liveries I have used to date
Many thanks in advance if you can sort that.
-
@Mark The speed bugs are not physically there on the gauge. I'm clicking the card and they don't even appear.
@OwlInFlight I've found that the speed bugs will appear after clicking a few times. I believe it depends on exactly where you click - clicking on the column header on the speed card doesn't work, but clicking on of the actual speeds does.
-
@OwlInFlight I've found that the speed bugs will appear after clicking a few times. I believe it depends on exactly where you click - clicking on the column header on the speed card doesn't work, but clicking on of the actual speeds does.
@trisager Yeah, this was my experience, too -- I have to click on the actual speeds, whereas my memory seems to tell me that on V1 I could click on the column. However, I could be simply wrong, or confusing it with the behavior of the 146.
-
@trisager Yeah, this was my experience, too -- I have to click on the actual speeds, whereas my memory seems to tell me that on V1 I could click on the column. However, I could be simply wrong, or confusing it with the behavior of the 146.
@RPGamerous The logic of the speed charts was updated at some point with the 146. In the early builds, the speed bugs would be set based on your current flap setting - so clicking on the speed card with flaps 18 would set the flap 18 takeoff or landing speeds. In later versions, a "FLIPCHART OPTIONS" option was added to the EFB, which when enabled, allows you to click on a specific speed on the speed chart to set the bugs. If that option is disabled, the logic will be reverted to the original logic where the bugs will be set based on flap position.
I believe the "FLIPCHART OPTIONS" option has been available on the F28 EFB since the initial release, but I could be wrong with that.
Mark - Just Flight
-
Hi again. Ref the pilot hanging out of the fuselage in MSFS2024 VR, I've tried also with the Quest and it is the same there.
Just to confirm:
- It only shows in MSFS2024 in VR. When I turn back to 2D he/she vanishes
- It doesn't show in MSFS2020
- It happens with Cockpit crew option off or on
- It affects all of the versions and liveries I have used to date
Many thanks in advance if you can sort that.
@AJZip We are aware of this issue, with and without VR. Frustratingly another MSFS 2024 quirk at the moment as the position we have set for the character is being ignored by the simulator (we actually have the 2024 character set to spawn in the toilet currently so that it is hidden and doesn't overlap with the 2020 avatars in the cockpit or stick out the side of the fuselage).
We do have another temporary workaround in place that is currently being tested by our beta team. Once this is signed off it will be included in the upcoming F28 Professional update.
Mark - Just Flight
-
@AJZip We are aware of this issue, with and without VR. Frustratingly another MSFS 2024 quirk at the moment as the position we have set for the character is being ignored by the simulator (we actually have the 2024 character set to spawn in the toilet currently so that it is hidden and doesn't overlap with the 2020 avatars in the cockpit or stick out the side of the fuselage).
We do have another temporary workaround in place that is currently being tested by our beta team. Once this is signed off it will be included in the upcoming F28 Professional update.
Mark - Just Flight
