MSFS Products

Had this problem happening again today, now on 0.1.1. No controls set to prop/mixture/fuel etc

Yes, we do plan to bring the latest livery_config.ini logic across to the RJ in the next update. Mark - Just Flight

@miller39687 For the generator switch, in CaravanProfessional_INT.XML (there will be two such files in your community folder if you have the bundle), search for the line... <CODE_POS_2> 2 (&gt;L:var_GeneratorSwitch, number) </CODE_POS_2> Immediately afterwards, add: <OVERRIDE_ANIM_CODE> (L:var_GeneratorSwitch, number) 1 == if{ 0 } els{ (L:var_GeneratorSwitch, number) 2 == if{ 200 } els{ 100 } } </OVERRIDE_ANIM_CODE> For the inertial seperator, search for ASOBO_HANDLING_Lever_InertSep_Template. Delete this block of code (from <UseTemplate Name... to </UseTemplate>, and replace it with... <Component ID="HANDLING_Lever_InertSep" Node="HANDLING_Lever_InertSep"> <UseTemplate Name="ASOBO_GT_Switch_Code"> <ANIM_NAME>HANDLING_Lever_InertSep</ANIM_NAME> <NODE_ID>HANDLING_Lever_InertSep</NODE_ID> <PART_ID>HANDLING_Lever_InertSep</PART_ID> <LEFT_SINGLE_CODE> (L:XMLVAR_InterSep, bool) ! (&gt;L:XMLVAR_InterSep, bool) </LEFT_SINGLE_CODE> <ANIM_CODE>(L:XMLVAR_InterSep, bool) 100 *</ANIM_CODE> <ANIM_LAG>100</ANIM_LAG> <WWISE_EVENT_1>Caravan_Bypass_On</WWISE_EVENT_1> <WWISE_EVENT_2>Caravan_Bypass_Off</WWISE_EVENT_2> <TOOLTIP_TITLE></TOOLTIP_TITLE> <TOOLTIPID>Inertial Seperator</TOOLTIPID> </UseTemplate> </Component> Let me know if you need any help with that! Always happy to fix these things for anyone willing to edit a couple lines of code

Is it possible to automatically swap the SL40 COM radio for the SL30 NAV/COM radio in slot 2 when the NAV OBS 2 option is turned on, to solve the issue of it only being usable with two GPS units or one GPS as it is now?

It looks like the correct TACAN frequency for the LKH TACAN is 39X. Mark - Just Flight

Sorry to hear that you feel disappointed with the F28. That's the opposite of the feedback we usually receive from the wider community, and internally we are generally very happy with the quality and status of the product Just to share our perspective, last year we dedicated an entire 12 months to updating and upgrading our whole MSFS catalogue to MSFS 2024 native standard. You can read more about our 'Year of Updates' here: https://www.justflight.com/articles/end-of-year-round-up-2025-part-one Included in those updates was a significant F28 Professional Version 2 update, which added the UNS-1 FMS, new EFB functionality, interactive paper checklists, new cockpit equipment, new liveries, and a variety of other bug fixes and improvements previously reported/requested by the community. We followed that update with 3 more updates in 2025, one of which upgraded the product to MSFS 2024 native standard. The changelogs for these updates can be found at the following link, and consist of over 180-items across all updates last year: https://support.justflight.com/en/support/solutions/articles/17000135003-f28-professional-msfs-changelog All of these F28 updates, as well as the MSFS 2024 native upgrades for our entire MSFS catalogue, were provided free of charge, and it did come at the expense of taking some of our limited development resources away from our other in-development products, including the F70 & F100 Professional. As we completed the last of our MSFS 2024 native upgrades towards the end of 2025, our focus had to then shift to progressing the development on our in-development products. So far in 2026, our internal development team have been entirely focused on the F70 & F100 Professional and A300B4 Professional, and will likely remain that way for the near future. As we have hopefully demonstrated in the past 5 years, no Just Flight MSFS product is ever "complete". We continue to update/upgrade all of our MSFS products as new features become available in the simulators, new features are developed for the other products that we can be backported, and bug fixes for any compatibility issues raised by Sim Updates. To give some insight into why updating products is a very time-consuming task, they not only require development work, but they also require testing, installer creation, and marketing, which is why we typically wait for a sizeable amount of bug reports to accumulate before we decide an update is required (and bug reports naturally get few and far between as a product matures). For the F28 specifically, if we were to release an update with a single value changed in the code, the change would need to be applied to each of the four variants of the F28, in both MSFS 2020 and MSFS 2024, then it would need to be tested in each variant in each simulator. We then need to create MSFS 2020 and MSFS 2024 installers for both our store and third-party stores, which also require testing. Then we need to develop, upload, and test the PC and Xbox MSFS 2020 and PC and Xbox MSFS 2024 marketplace builds. Hopefully that helps to explain the process from our side, and gives an insight into how we plan and deliver product updates. To respond to each of your points on the F28: The wipers are functional in the F28 in both MSFS 2020 and MSFS 2024. MSFS 2024 rain effects are not currently supported, but are something we have logged on our internal feature request tracker. Beacon lights/wiper speeds: the speeds were set based on videos and sound recordings taken from the real aircraft, and we aren't aware of any bugs with this logic. As requested, a video of the beacon and wipers can be found here: https://justflight.sharefile.com/public/share/web-s71afb491ed0b40818388a597cacd1891 The DME text is not something we currently have logged on our internal trackers. The V/S control not being affected by state saving is not something we currently have logged on our internal trackers. The window shades not being visible on the exterior is not something we currently have logged on our internal trackers. If you have any feedback or require any assistance with any of our products, we would kindly recommend that you raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support Raising a ticket ensures that all feedback can be properly logged on our internal trackers, and those trackers are one of the main tools our development team uses to decide on a timescale for future updates. Mark - Just Flight

Re: MSFS - 146 Repaints/Requests I wonder if someone could do a Neptune Aviation Livery for this plane

I have that problem nearly every time when I enter the sim at a busy airport. I've never been able to solve it but what I do is once you have settled in the sim at your parking spot and dont see any aircraft, hit the esc key and then restart, and you will then get aircraft at the gates.

I can't switch the engine master switch to start while in VR in MSFS 2020! It will go to 'on' ok but every time I click it to start it just goes back off again (I only have this problem in VR as the switch works perfectly in flat screen). I've noticed that if I'm behind the front seat the switch moves to start fine as I can click it from the back but while sitting in the front seat it just always goes back to off again and I cant get the mouse pointer behind the switch. Is there a problem with the switch sensitivity area in VR? I've tried configuring the engine master switch to a button on my Turtle Beach Velocity One throttle but none of the control options - toggle engine master switch etc seems to to anything.

found that the provided paintkits work. and the "clean" interior is available already too! thanks team.