MSFS Products

@Mark said in Where are airline configuration options saved?: The livery_config.ini only supports the default liveries in the RJ at the moment, and I believe any third-party liveries will always load in with all equipment enabled. That right there is why I've been pulling my hair out then. Every single third party livery does indeed load with all equipment enabled by default on every single flight (even if I exit to main menu/close the sim). I'll sit tight for the next RJ update now, thank you.

I've been using the same ambient occlusion settings for my aircraft since the beginning, so I wonder if this is just MSFS 2024's dynamic exposure compensation.

I have just looked into this, and it doesn't look like the PRIMER control assignments are supported in the PA38. I have therefore logged this on our internal bug tracker, and we'll add support for those in the next update. Thanks for reporting this. Mark - Just Flight

We're not aware of any brake issues in Vulcan, however, if you're using MSFS 2024 there have been some changes to Parking Brake control assignments in SU3 that could be causing a conflict. See: https://forums.flightsimulator.com/t/parking-brake-cant-toggle-on-off/734585 If brake issues exist in multiple aircraft, that typically points to either a control assignment conflict. Mark - Just Flight

You should always set take-off power as 100% on the thrust indicators. Changing the thrust index changes what the indicators regard as 100% thrust, but that's the indicator you always want to hit. The lower the thrust index, the lower the LP and HP rpm indication at 100% thrust indication - you can see this if you set different thrust indexes on each engine or hold the aircraft on the brakes, set 100% on the indicators, then change the thrust index. As you noted, the information needed to do a proper FTTO (runway length vs. aircraft weight) isn't available. So what you can accurately do is a full rated thrust takeoff, setting the maximum thrust index for the given elevation and temperature. This is what the Thrust Index tables in the JF manual and on the in-cockpit paper checklists let you set, and what will be automatically set when you click the a square on the speed reference card, along with the relevant bug speeds. With a full rated thrust takeoff, if you've calculated the thrust index accurately, you should reach 100% thrust on the indicators with the throttles in the detent. In a FTTO, you would advance the throttles until you registered 100% indicated thrust, which may be before the detent is reached, because you are setting the thrust index for a temperature that's much higher than reality. The main purpose of the detent is to provide a clear throttle setting for the minimum throttle setting needing for the engines to produce rated power and the aircraft to achieve its certified performance. With the throttles in the detent and pitch matching the profile commanded by the flight director in Speed Control mode (not modelled in the JF F28), the aircraft is guaranteed to meet the requirements for obstacle avoidance etc. even on one engine. With the throttles below the detent, this isn't guaranteed, which is why the manual says you have to advance the detent OR beyond to achieve 100% thrust when you need full rated power. A Flexible TO is foregoing this guarantee when you have a lot of runway to spare, so you don't need to hit the detent. But if you had an engine failure after V1 you'd advance the throttle of the good engine to full thrust. The detent also indicates/activates other things like the automatic speed brake/lift dumper retract function, and the TTC system, but it's mostly there to indicate the max rated thrust position.

We don't have a date to share at the moment, but it'll be towards the end of the month. Mark - Just Flight

Thank You for Yours answere. Working GA traffic on to ground and air is more than welcome product. Regards Rolf

Purchases on the marketplace are platform specific. You can't transfer from Steam to MS store or vice versa. Microsoft Flight Simulator FAQ – Microsoft Flight Simulator Support https://share.google/vZnfJK0vIgmYp0Hly

I have just tested this on my side, and the state saving is working as intended. I'll list a few things below that may be worth checking: "State Saving" must be enabled on the EFB prior to exiting a flight (the State Saving box will be light grey on the EFB when enabled). With State Saving enabled, the aircraft's state at the time of exiting the flight will be saved, and then reloaded the next time a flight is started in the aircraft. The State Saving should cover all controls in the cockpit, as well as external equipment such as the Chocks, Tie-downs, and Towbar. Ensure the simulator is closed down correctly via the Main Menu, rather than using Alt+F4 or Task Manager to force it to close. We don't officially support any of our products on the MSFS Sim Update Betas. Although you mentioned it in your post, I thought I would bring this up just on the off chance that you were using the SU4 Beta. The Sim Update betas are beta releases, so bugs are expected, and we have seen some odd behaviours like this in previous betas. Mark - Just Flight

Hello, I am trying to install the PA28 Arrow III for MSFS 2020 but I am getting the attached message saying my extension is too long. [image: 66cf837d-5af9-40f2-a678-3ccdc4858601.png] Instead of using C: I am using my E: which has MSFS installed and working. I found this link on the Just Flight support page. https://support.justflight.com/support/solutions/articles/17000124650-long-file-path-issues-msfs2020 But this does not resolve this issue either. Can anyone help resolve? Thanks for any help.