F28 Professional

@Mark I hadn't spotted this post by @zntgrg but spotted your response to my query in the other thread. Many thanks for the update and for a splendid aircraft...

@Mark
No probs - thanks for the response...I am relieved that it isn't a quirk in my own system (MrsAJZip assures me I have plenty of those to begin with!)

The F-28 Professional is a joy to fly in VR. Great stuff!

AJZip

From a few tests, it looks like its an issue with GSX integration.

If I only use the pushback request from GSX and deselect GSX integration from the settings menu on the tablet, brakes work each time.

figured this out, I just needed to turn on the lights using the light control on the overhead panel

Thanks for posting your solution. With that starting point it took me all of five minutes to get it working here :-)

OK, this is actually in the manual.

I was attempting to change the altitude restrictions on the FPL pages. The correct way to do it is, on the VNAV page, use the LSK keys next to the VNAV waypoints, select the waypoint (!), and set the altitude. Changing the restriction at BOGMU to FL110, and the restriction at the FAF did the trick.

Not very intuitive, but good fun.

Try the 8k texture pack, really improves it for me and didn't impact performance.

Yeah, it came as a surprise to me, too -- but if you keep your eyes open you might see that a clickable component of your cockpit continues glowing blue, indicating it's still selected while you're clicking around your second monitor. This might not be what caused your problem but as soon as I read your post it's what I thought of.

This is not something we are able to replicate on our side. If this occurs again, could I kindly ask you to raise a support ticket via the following link: https://www.justflight.com/support

Please include as many details as possible within the ticket so our support team can try to reproduce the issue. Information such as the airport, approach type, navdata used, simulator used and a video of the behaviour will greatly increase the chance of our support team being able to reproduce this behaviour.

Mark - Just Flight

Thanks for reporting this. We'll pass this onto the development team to investigate further.

Mark - Just Flight

Thanks for reporting this. We'll pass this onto the development team to investigate further.

Mark - Just Flight

This is something we have logged from the requests received from our other aircraft. it is something we would also like to add support for and there have been some initial discussions about it internally.

Mark - Just Flight

Consider it closed. I managed to fix it by activating 3D sound (surround sound) in the windows settings, enabled it in MSFS, and disabled it in windows again. Sounds are back to normal now!

@Martyn , 1st, sorry to ping you again.
It was this 0,01% i missed ;-).
I found the real reason for the missing "pilot calls"

In MSFS 2024 SETTINGS - SOUND the COMMUNICATIONS DEVICE OUTPUT was set to my headphones (by default (after the SU-1 Update maybe )
I put it back on SPEAKERS and the calls are back again (bc i had lost them again ...)
I recommend routing the "Pilots Calls" to the MAIN DEVICE, if possible.
When flying on Networks the Communication device will be the headsets again, thus not playing the pilot calls through the Main device (Cockpit sounds/ calls (like from the Copilot ...

Cheers
Oliver

@Mark Tks Mark!

@Mark Thank you, I am much obliged and appreciate it.

Is it possible for You to write an update from time to time when there is one? If it is not too much to ask. I bet You have plenty on your plate.

Best regards.

It's on our list of things to investigate for the next 146 update.

Mark - Just Flight

I found the solution. Within FSUIPC, set the inc variable to 100 instead of 1, then, the value is increasing.

Excellent, thanks Mark!