F28 Professional

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.

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!

For feedback such as this, we kindly ask you to raise a ticket with Just Flight support via the following link: https://www.justflight.com/support Included with the ticket, if you could provide a video of the behaviour and/or steps on how to reproduce it, then that will allow us to look into this and log it as a bug if required. Mark - Just Flight

We are aware of several map-related issues in MSFS 2024. These are currently under investigation. Mark - Just Flight

Thanks for the suggestion. We have logged this on our internal feature request tracker for our development team to consider for a future update. The current TCAS VSI / Analog radio transponder configuration is however accurate to our reference aircraft. Mark - Just Flight

Replying to my own message in case this helps anyone! I had previously cocked up the checklist procedures so had hit the "cold and dark" option in the EFB but it appears that this doesn't reset the aircraft back to "defaults". The only thing that worked was restarting my flight in the simulator pause menu and everything worked correctly after that. Not sure if I'm not understanding the purpose of "cold and dark" or if this is a bug but I'm tempted to go with the former rather than the latter!

@GroverJ41 That's sorted it! You need the parking brake off AND the chocks (which, in MSFS, is a duplicate of the parking brake). I'll check things out on my next flight to see what you need to do in the air to get it to work.

Found e solution.... was a local mod on my Community folder.. Delete it now all fine!

That likes more like a flightpath being displayed from some in-sim settings ..

I think your suggestion resolved the issue. I have checked all electrical systems, waited a while, and the UNS powered. I'm not really clear on what made the difference, but the system is running. Thank you for your response.