F28 Professional

We don't have anything further to announce at the moment beyond what we've posted above, but we are aiming to share more details on the F28 V2 update next month.

Mark - Just Flight

@Lobster404 That's a great solution! I too had issues with that start engine button (I use Spad Next) What I would do is spam the LVAR many times over a few seconds and that would usually do it but this solution looks better.

I program a short press as the #2 engine and a long press as #1 engine.

My setup with a Loupedeck: https://youtu.be/IFQsMRxZ-kk?si=Q8A5TFLIAkXru2fK

Thanks for sharing!

Thank you for reporting this, and for the very detailed feedback. I have been able to replicate this and I have logged all of this on our internal bugs tracker for us to investigate ahead of the next update to the F28.

We will need to check to see if there may have been a reason why we coded it this way (the simulator has some strange quirks with the COM/NAV radios so sometimes we have to add some unconventional code to ensure it all works correctly in normal conditions) but we will see what we can do and hopefully we can improve this logic. We are currently working on a "Version 2" update to the F28 Professional, so will ensure any changes to the COM/NAV radio logic are included in that update.

For reference, the coding for the COM/NAV radios is all located inside the aircraft's WASM files, so there isn't anything that could be edited from an end user's perspective, it would require us to update the code within the WASM files and release an update.

Mark - Just Flight

@TJ-Turner

The 'situation' such as it is, can be likened to that of Norma Desmond. It's the pictures that got small....
As products have got more detailed they have shown up the shortcomings of the X-Box S. Some titles will run fine on that platform - some won't. We have been working on various builds of the F28 (and some other titles) to try and optimise them to run on what is, essentially, a reasonably adequate gaming PC from 2020. Sadly, as with any PC that is showing its age, all the dialogue in the world is no substitute for more RAM or a better graphics card - or a game that doesn't stretch the machine's resources.
Hopefully, the next round of builds will provide something that will be ready for its close-up.

The above, written in February is still true. We awaitied SU15 but that didn't deliver any changes. We will continue to tinker with the F28 to optimise it for X-Box release.

@Mark that’s brilliant news, thanks!

If you use Simbrief, I've been playing with the latest version that includes a takeoff performance calculator.

It doesn't have preset data for the F.28 but it does have it for the F.70 and can give a calculated Flex Take Off temperature.

I've been loading data for my F.28 into that, then bumping up the weight by 10 per cent or so to account for the lower power/weight ratio of the F.28.

So far it's always spat out Flex temperatures in the 40-45 deg.C range.

Using the thrust index numbers to go with those temperatures certainly seems to do a good approximation of a Flex takeoff - less of the frantic 'pocket rocket' climb that you get at full rated thrust. I feel you could bump the assumed temperature even higher but without the proper data it seems a good compromise.

@Friese2020 Made a fault in post #5; The A2A Comanche was the one I should have referred to. NOT the WB172. :-(

@Mark Hi,
Turned off state saving, I found no key binding, on 3rd try the plane turn on normally and it was a pleasure to fly (Berlin to Copenhagen landing RWY 30 in full ILS).

State saving acts strange , I turned off the plane all knobs and switches turned off but when starting half of them were on.

Will try to see if I can outline precisely the problem for you to investigate.

Thank you for the reply. You are a wonderful team I love you r products.

The engine sticking at 15-20% suggests that fuel isn't being introduced into the engine. Do you perhaps have any control assignments that could be triggering a fuel pump or fuel valve that is preventing fuel from being introduced to the engine?

A quick way of testing this will be to unplug any external hardware (yokes, throttle quadrants, etc), then try an engine start with everything unplugged. If both engines start correctly with everything unplugged, then a control assignment conflict is likely the cause.

If it is a control assignment conflict, you can go to MSFS Options > Controls Options, and click on the tab with the name of one piece of external hardware you have plugged in. Then, in the "SEARCH BY NAME" field, searching for "FUEL" should show you all the MSFS control assignments related to the fuel system and also show you which you have axis/buttons/switches assigned to on your external hardware. The control assignments that are causing a conflict can then be deleted here, or a new controller preset can be created using the "OPEN PRESET MANAGER" button at the bottom of the page.

Hope that helps.

Mark - Just Flight

@Mark Thanks for the heads up, i"m looking forward to the update.

I believe you would need to restart the flight in order for the lock wiring to reappear. You may also need to disable state saving (if enabled) to prevent the aircraft from loading in with the valve already open.

Mark - Just Flight

tHANKYOU VERY MUCH, I WILL GIVE IT A TRY!

We'll make a note to add that to the manual for the next update.

Mark - Just Flight

Found my own solution. For future onlookers use this instead:
c128c716-6c23-4708-add9-b99f91832927-image.png

Thank you for reporting this. We have updated our F28 Professional GSX profiles at the following link to fix this issue: https://support.justflight.com/en/support/solutions/articles/17000134895-f28-professional-gsx-profiles

Mark - Just Flight