So, in FSUIPC I have the condition levers set in Axis as "Send to FS Preset". And the preset being "BS Starship Condition Lever 1 (2) Axis". No ranges or anything. Just like that. In the profile, they show up as: x=xU,256,F,PBS_Starship_Condition Lever 1 Axis,0,0,0,(star character)-1 -{ TO SIM: Preset Control }- x=xZ,256,F,PBS_Starship_Condition Lever 2 Axis,0,0,0,(star character)-1 -{ TO SIM: Preset Control }- Where the "x" will be different in your case. I also type (star character) instead of the actual character as the forum interprets it as Italic. But yes, I mean the Shift-8 sign to invert the movement.

@intjmastermind It would not even the legal to key in the procedure yourself in the real world. FAA and EASA rules explicitly state that you have to get them whole from a database. But I agree with you. Such an option would be great. Imagine starship would still be supported. It won’t be a far fetched idea that the avionics would have been upgraded accordingly. I don’t need full VNAV guidance. Just the procedures. And at least a GTN 650.

@Deadeye313 I looked at the SIDS and STARS extensively for the starship. Both FAA and EASA do require the procedure to be able to load from a database. Neither the KNS nor the starship can do that. I am debating if you can user program a procedure in starship yourself, as a stored flightplan, to be loaded. But that is different story.

Thank you for the feedback. I've just had a read of the FCOMs, and it does look like the speed brake lever should return to the IN position during automatic retraction. I have logged this on our internal tracker for our development team to look into further. Mark - Just Flight

For any AFCAS/ATS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product. 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

May be of interest... https://community.justflight.com/topic/11221/question-about-upcoming-updates Cheers James

@Black-Square Thank you for fixing it, I really appreciate your constant support to the community. I also highly respect you for having to deal with all of us xD Have a good day!

@Black-Square Hi Nick, looking forward to the upgrades....I see echo19 has created a soundpack for theTBM850....Will any of this batch of upgrades include an official BlackSquare TBM850 soundpack update? Cheers James

If the FAs/Cabin Crew are standing up and doing a safety demo then technically the cabin is not secure until they are also all sat down and fastened with their seatbelts. The cabin security is not only for passengers but for cabin crew as well. The airline operator I work for would usually have the "Cabin is secure for take off" somewhere between us shutting the door after final passenger count and taxi and arrival at the hold point for take off. We are permitted to pushback, engine start and taxi all the way to the hold point but cannot take off. This is an option for you in case you don't want to be late. I think there is an ARM DOORS function on the EFB to do it earlier as well

Surely some self control is all that's needed there! Perhaps what would be nice is something like the old fsx a2a aircraft where on the pop up/tablet etc you can choose to inspect the aircraft which when lists the damage/wear and tear.

I've figured out where things went wrong. I used the Contrail store to check the version installed, and that indicated wrong. So now I have the latest version installed. I checked the changelogs of the last 2 versions, and indeed all these issues I have were actually incorrect and fixed in those later versions which I did not have. So when I reinstalled suddenly the plane behaved differently than I remembered, simply because I had an outdated version before I was used to. Mods feel free to remove or close this topic if necessary.

Disclaimer, not a dev, info might be gappy or misremembered: FS9, FSX, and MSFS have for ever and always had essentially no way to realistically implement proper turboprop simulation due to core sim limitations, which I'm sure you might know. In recent years BS and a few other developers have managed to squeeze somewhat realistic behaviour out of the platform despite its faults, but still it's only ever been possible to properly recreate turboprop physics by running the addon's physics outside the sim which is rare (Majestic is the only one I know to have done it). Nick is a magician, but even so there's only so much that can be done in recreating a turboprop within MSFS, at least up until now. SU6 included a lot of turbine simulation improvements in its change log, hopefully this will translate to an easier life for devs and a more faithful recreation for us consumers. It's all hope for now though, I haven't seen any devs comment on it yet and it wouldn't be very surprising to find out that the changes hasn't helped all that much, but my fingers are very much crossed! Edit: Again, with no specific knowledge, it's also possible that the SU6 improvements could be great for a ground-up project, but require a complete rework of existing products. Just speculation.

@Black-Square Thanks for help, your code works well, but I'll use it as a temporary solution. Is there any chance that you could output these needle variables to some simvars in a future update?

It’s not certified, so no.

I have the TDS GTNXi and it is usually in my cockpits. Not used it once in the Commander yet as just feels so freeing without it lol

SU6 seems to have resolved ALL of the LOD issues inside of the cockpit - even the CO2 detectors in VR (woohooo). But not this one - the Duke's recognition lights are still inside the fence and blinding.

Can you share with us the route?

@Black-Square I might add. the default set pitot heat key-bind is also not working for me in msfs2024.

FYI Nick - SU6 fixed the LOD issues with the CDU etc with the Pimax crystal super and the Starship. Everything looks to be rendering great now

Nick, I tried the following as you suggested. Switched ON Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 ;Turns the Left Generator switch to the ON position Delay execution for 500 ms ;Pause execution momentarily to see each action happen Set LVAR:var GeneratorTrip L to 0 This functionally worked, but it doesn't display the switch being put up into the Reset position, and then back to the On position. What I ended up doing was the following. It puts the switch into the on position, momentarily into the Reset position, then "visually" back to the on position. Removing the delays after setting LVAR:var GeneratorReset L to 0 prevents me from "seeing" the switch actually turn back off and then back on. The first Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 leaves the switch in the off position for some reason (I don't know why), but the second Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 moves it back to the on position as desired. Then the Set LVAR:var GeneratorTrip L to 0 tells the system that the reset was done. I published a snippet online in SPAD for just this switch, so anybody else that ran into this issue can use this solution. I'm glad that I was finally able to get this working. Thanks for your help. Switched ON Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 ;Turns the Left Generator switch to the ON position Delay execution for 500 ms Set LVAR:var GeneratorReset L to 1 ;Set the Left Generator switch to the RESET position Delay execution for 500 ms Set LVAR:var GeneratorReset L to 0 ;Return the Left Generator switch to the ON position (Actually turns it off) Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 ;Turns the Left Generator switch to the ON position Set SIMCONNECT:GENERAL ENG MASTER ALTERNATOR:1 to 1 ;Turns the Left Generator switch to the ON position Set LVAR:var GeneratorTrip L to 0 ; Tells the system that the reset was done.[image: c9c170c7-1b24-45f5-a58c-be145747dbdc.jpg]