F28 Professional

Okay looks like this may have been a temporary problem. I disconnected the hardware, and restarted my PC. After the restart - things are back to normal.

Don't worry about that, Mark. I really appreciate it.
Thank you very much for your help.

We delayed the F28 release on Xbox for almost a year after the PC release so we could ensure that the product we delivered was as optimised as it could be on consoles. Therefore the latest build of the F28 is as optimised as it can get on consoles. The general performance on Xbox will likely improve in the future with the performance optimisations that Asobo/Mircorosft are expecting to bring to Xbox in MSFS 2024 and Sim Update 16.

If you are struggling with performance with any of our aircraft on Xbox, we do have the following FAQ that provides some additional recommendations that could improve the performance: https://support.justflight.com/en/support/solutions/articles/17000142069-performance-tips-for-xbox-consoles

Mark - Just Flight

Hey, thanks to the team and you Mark for listening to the feedbacks. Can't wait for this nice update and fly with a FMC! Good luck with the rest of the work <3

That's why we are in a hurry to have the UNS ;)

Yes, I hope that as well! The KLN90B would be the perfect fit for the F28.

Thank you for the request. We have logged this on our internal feature request tracker and this should be something we will be able to look into for the upcoming Version 2 update to the F28 Professional.

Mark - Just Flight

We have just looked into the pilot visibility on the F28 exterior on Xbox and this looks like it is something that is being controlled by the simulator as a performance-saving measure.

For example, if you load into a small regional airport you'll likely notice that the pilots will be visible on the exterior and they may disappear once the drone camera is moved a certain distance away from the aircraft, but if you then load into a large international airport like EGLL or KJFK, you will likely notice that the pilots will only be visible when the drone camera is much closer to the aircraft (if at all).

Unfortunately, I'm not sure if there will be anything we will be able to do to improve this as it looks to be something that is being controlled by the simulator due to performance constraints, but we have logged it on our internal bugs tracker to investigate further.

Mark - Just Flight

@Mark Thanks for your response, I solved the problem and thankfully it was nothing to do with your aircraft.

My Honeycomb Bravo, annoying, has developed axis jitter. I had the same issue with a single engine the other day (I have 2 axes bound to physical fuel control levers) and the axis moved to a position where the engine cut out.

We don't have a firm release date set for the F28 V2 update just yet but our target is certainly less than 6 months. There has been some significant progress made in the last few months and we will be sharing more information on what will be included in the F28 V2 update very soon.

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

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

@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

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!