And all that time spent could not go into making the other aircraft 2024-compatible…

Thanks for reporting this. Yes, it looks like this only occurs when switching from a GPS unit to the "No GPS" option; it shouldn't occur if loading into the aircraft with the "No GPS" selected by default. As you have mentioned, the workaround for now will be to ensure VLOC is selected on the GPS prior to selecting the "No GPS" option. Another workaround will be to select the "No GPS" option on the EFB, then restart the flight so that the "No GPS" option is selected by default. We have logged this on our internal bug tracker, and we will investigate further ahead of the next update to the PA-38 Tomahawk. Mark - Just Flight

Yes, unfortunately, it's not possible to update the nav database on Xbox . We are looking into some methods to allow Xbox users with a Navigraph subscription to update their navdata in our aircraft. We're not able to provide a timeframe for when that may be available at this stage, but we will be sure to keep everyone updated once we have more to share. Mark - Just Flight

@Marionettework I saw! Maybe I can get advanced access to help find other issues 😂

Where did you buy the software?

You are correct! In SYNC mode, the radar acts as a single transducer, controlled by either the left or the right CDU, and displayed on the pilot's ND, copilots ND, and MFD with all the same parameters and modes. In SPLIT mode, the radar acts as if it were two separate transducers, controlled separately by the left and right CDU's. This would allow the pilot and copilot to each control the radar as they see fit for the situation, but also to display a different radar depiction on the MFD from the pilot's ND. As you said, this might be most useful for keeping an eye on long range weather on the MFD while looking at nearby terrain on the ND, or a similar combination.

The v1.0.2 changelog is now available here: https://support.justflight.com/en/support/solutions/articles/17000146695-146-professional-xp12-changelog Apologies for the delay in making that available. Mark - Just Flight

I'm delighted so many people are taking interest in this old system. I do not simulate any "bad" signals, but I do simulate signal strength around the world for each station. If the signal is poor, the system will automatically disregard it. I gather that the disabling feature was predominantly used under the guidance of some publication that identified when stations were out of service. The same goes for GPS satellites, which can also be deselected by number in Starship's avionics. I had no idea someone had written a genuine Omega emulator! I am familiar with the lane system due to LORAN units, but luckily, Starship does all the Omega adjustments automatically, and there is no interface to view them. I have been wanting to create a LORAN navigator for my aircraft for a while, but it's the complexity of the lane and chain adjustments that are keeping me away.

The only cause I recall of the Flight Director indicating too great a pitch during takeoff/climb was a throttle axis spiking issue. That's covered in my previous response in this thread, along with a potential workaround for that. Another way of working out if it is throttle axis spiking related, will be to temporarily unplug any external hardware with a throttle axis assignment from your PC (joystick, throttle quadrant, etc.) and then load a flight in the RJ on the runway. With a flight loaded on the runway, enter a flight plan in the FMS takeoff as normal. If the flight director bars indicate 8 degrees pitch up for the takeoff roll, and then indicate the pitch required to maintain V2+10 during the initial climb, then they are behaving as expected and the cause will likely be related to a spiking issue in the throttle axis. If the issue persists with no throttle axis assignment in play, the could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the support ticket, if you could supply a video of the behaviour, then our support team will have the best chance of either reproducing that behaviour and be in the best position to assist with further troubleshooting. Mark - Just Flight

The failure/walkaround features are something we have logged on our internal feature request tracker for the PA28s, but nothing is in the works at the moment. It may be part of a larger update or upgrade to our PA28 fleet in the future, but we'll share more details once the scope of those potential updates/upgrades are finalised. Mark - Just Flight

They have been added and ready to go. I'm sorry that it's taken so much longer for a Duke update than I ever anticipated. I wanted to coordinate with the official MSFS 2024 release of my aircraft, since things have changed in both versions, but the speed of breaking changes in MSFS 2024 has taken six months to slow down to where I finally feel comfortable presenting my aircraft in MSFS 2024. Updates for all my existing standalone aircraft after Flight Sim Expo, I promise!

Not to worry! You can take your Starship off-roading to your heart's content. The inertial separators will make you immune to FOD damage. While this is not 100% realistic, I did it precisely so users could fly from unimproved strips without discovering excessive damage. The tablet displays have a 0-100% engine health bar for each engine, and you will be able to watch the FOD particulate as it travels through the induction system. I'll look forward to seeing your Starship bush flying!

Integration with navigraph charts would be incredible in the EFB, or having the possibility to use the new MSFS2024 EFB in the 3D cockpit.

@jmarkows "Jet Flap Pre-Swirl", IFYKYK.

I just got the Turbine Duke a few days ago. I use the PMS GTN 750 and have had mulitple CTDs, and I don't have this issue with any other aircraft. Sad, cause I really like flying it.

Hello, I was having this problem and reached out to Just Flight support. I thought it might be helpful to share their reply here, as (as far as I can tell) I seem to have solved the problem by following some of their suggestions. In my support ticket I had let them know that my Community folder was completely empty, and that I was getting CTD with Windows showing CoherentGTJS.dll or CoherentGTCore.dll as the cause of the crash. Of their suggestions below, I only did two things. I cleared the shader cache (Google how to do it, there are a few more steps than they describe) and I uninstalled and reinstalled all of the Visual C++ redistributable libraries (available from Microsoft, google it). I have not been getting CTDs any more (so far, and granted it was hit and miss when it was happening). Here's their full reply: Crashes involving CoherentGTJS.dll or CoherentGTCore.dll are commonly reported in applications like Microsoft Flight Simulator (MSFS) and are typically related to UI rendering issues, as these DLLs are part of the Coherent GT UI middleware used for in-game interfaces. The common causes for this issues are: Memory corruption or heap allocation issues – These DLLs often crash due to corrupted memory pointers, especially when interacting with other mods or third-party content​. Outdated or incompatible GPU drivers – Many users report that updating or rolling back GPU drivers can resolve the issue​. Corrupted installation or cache – A fresh install of the game or clearing the shader cache sometimes helps. Outdated Visual C++ Redistributables or DirectX – Ensuring all runtime libraries are up to date is essential​. Here are some steps you can try: Update GPU Drivers: Use the latest stable version from NVIDIA/AMD. If the issue started after an update, try rolling back to a previous version. Update Windows and Runtime Libraries: Ensure Windows is fully updated. Reinstall the latest Visual C++ Redistributables and DirectX. Clear Shader Cache: For NVIDIA: Go to NVIDIA Control Panel → Manage 3D Settings → Shader Cache → Clear.

Keeping the battery bus thread alive... I've finally had some down time that allowed me to install v1.4 of the Analog King Air. Loving it so far. Want to run something by the group to make sure its not a "me" problem. I think the taxi lights should run off of the battery/center bus. But they don't seem to be that way in MSFS 2020. Has anyone else noticed this? Stefan

Same here, any fix?