Looks like the digits are just being overwhelmed by the sun. Also, there were no updates to the radios in the last update.

@Darth-Patzer I suspect this topic will be of interest to you.

@sbanks75 2. Same for me, it's very very slow. The other problem I have with that is that it changes by itself when I start the plane. It solves the problem but it's not normal.

I noticed all kinds of autopilot issues when I switched from having the full TDS setup to a radio-only aircraft with dual kx155B. Could engage flight director and autopilot but things went a bit weir from there. Couldn't get the altitude and rate to work properly HDG, ALT, and NAV wouldn't illuminate on the KFC 150 While I could get it to hold altitude and get heading to work, nothing illuminated on the 150. I tried swapping radios then going back but nothing consistently worked. I think I got it to work properly 1x out of the last 5 flights. Restarting flight didn't fix. When doing an AP test, the yoke would turn right despite the heading bug set straight ahead, and trim would go full up despite altitude not being engaged.

The cool thing about it is that the Starship requires a bit of intuitive thinking. If you're departing from a regular temperature airport, delay the pitot heat until lined up. Heck, if you're flying on a clear Caribbean summer day, why not leave it off and save the filaments and prevent their MTBF to creep up. For example, when I depart before sunrise from an airport, or from a small airport, I simulate the lack of a GPU. I also don't import plans. I always plan in the cockpit, in the CDU. If I follow the checklist to a tee, I can quickly drain the battery. So, to save the battery, I pull the circuit breakers of the PFD and ND on both sides. It makes quite a difference. Then, when the time is right in the sequence, I pop them back in one by one.

Oh never mind I guess it has to be an existing waypoint, not a custom one.

@Mark Hi, I’ve shelved the Hotas 4 and reset alot of my settings, including the DualSense bindings, and everything is working great now. Spotting the trim sensitivity setting was a game-changer too. Thanks for the help

@Black-Square If you don't mind me asking, what do you change to make them more visible during the day? Something in the .fx file? Would love to apply that to my light mods on .to. You can DM if you'd like. Thanks Nick!!

@Mustang said in No saving state: an 'export/import' feature on the tablet to save/load state files locally I feel the same way, and don't trust anything stored anywhere I can't keep on my desk. Unfortunately, the MSFS architecture purposefully makes it impossible to save files locally from JavaScript. The "work" folder is exclusively for WASM instruments, I believe, but don't quote me.

@Black-Square @Black-Square said in Mixture lever in 114TC not working: @BiggerBoat Thanks for letting me know it's working now! I have done nothing different with the rudder trim compared to the default behavior in any of my aircraft. Sounds like a me problem, then. I'll sort it out. Thanks for the mixture fix! That was the one thing keeping me from flying. Seems like a great aircraft. Looking forward to spending time with it.

The MAX/OPT flight levels displayed on the FMS PROG page should definitely be achievable at the gross weight entered into the FMS. However, I do recall seeing another user reporting a similar behaviour previously, and that was caused by a third-party weather program generating unrealistically high temperatures at high altitudes. So the first thing that comes to mind is to double-check that the temperature is within approx. IAS +/-15℃ at high altitudes. Aside from that, we'd really need more information before we could provide a more definitive response. If you see that behaviour again, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support In the ticket, could you please include any screenshots/videos of the behaviour and attach the log file generated by the product. That will ensure our support team has enough information to be able to assist further. Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- Mark - Just Flight

Hello ! Thanks to Black Square, I could easily familiarize myself with a nice BE36 equiped with a G3X touch I am keen to also have this mod on my SIM ... Best regards

@fredgarven said in Axis control for Cowl Flaps: In case you are interested... I'm VERY Interested! Many thanks @fredgarven for this further insight into MobiFlight use for the Commander 114. Your cowl flaps control has already enhanced the experience and I look forward to exploring what else you have magically included in this project finale

The more observant will have seen that I meant Job not Jove

That's because the GNS 430 is not connected to the CDI, and cannot control the autopilot. The GTN 650 (from both PMS50 and TDS) can provide autopilot and CDI guidance, but this is a limitation of the GNS 430, unfortunately. I have requested that Working Title provide the option I need to implement this, but their priorities are understandably elsewhere.

Hi, i dont have it on hand at the moment(not home ) but i shared it on Discord FsCopilot channel under profiles Kind regards, Melvin

@durieuxdidier This sounds like something Just Flight or Just Trains support could help with. There are links on their websites www.justflight.com and www.justtrains.net        See: https://www.justflight.com/support   https://www.justtrains.net/support

@Pondimus I think on one of these installer error threads, someone mentioned they still had the option to uninstall, and after doing that they were able to install successfully. Have you tried that?

Here's what happens: After indicating an import failure, the only thing available is to select a deletion of the current plan. I'll make note of the exact language the next time it happens. After the plan deletion, when I return to the Flight Plan screen and begin manual entry the system refuses to except entry of the departure or destination airports. I can enter waypoints but not the airports. (it gives a X-side error message - I'll make note of it the next time it happens). After I force a reboot of the FMS I am able to enter a flight plan manually and the airports are accepted.

Nick, I've put together some FSUIPC presets for using the L:var_FlapSwitchOverride variable included in 1.1, but it seems after I use it for the first time, I can no longer click the switch in the cockpit and have it respond. Is this by design?