Please see: https://community.justflight.com/post/36185

In v0.1.3 of the Vulcan, we upgraded the GPS from the Aera GPS to the G3X Touch for better MSFS 2024 compatibility. Therefore, the functionality of the GPS has changed slightly as the G3X Touch is a more advanced GPS. To cover each of your points:

If a flight plan is created in the MSFS 2024 EFB, the "Send Route To Avionics" button must be pressed in order to import the route into the GPS. If a flight plan is created manually within the GPS, the flight plan must have a departure airport and a destination airport set in order for the autopilot to couple with the GPS (if a flight plan is created in the GPS with only a departure airport and waypoints, the route will be displayed, but the autopilot coupling will not function with an incomplete flight plan). In order for the autopilot to track the GPS flight plan, the ENGAGE knob must be pulled (with IN indicator showing white), the TRACK knob must be pulled, and REMOTE must be selected on the navigational selector.

This is a known side effect of a workaround we have put in place to improve touchscreen display interactions in our aircraft in MSFS 2024. If the workaround is no longer required after future MSFS 2024 Sim Updates, we will update the logic so that control cannot be clicked through touchscreen displays. The GPS can also be moved on top of the glareshield by clicking the upper bezel.

As the G3X Touch is a default GPS unit in MSFS 2024 (developed by Working Title), we sadly don't have any control over the scaling of the GPS. To circumvent this, we have added custom cameras for each GPS position which moves the camera closer to the GPS display. These cameras can be toggled either via the MSFS Camera menu, or via a clickspot on the right bezel of the GPS.

Mark - Just Flight

Your best bet when trying to resolve any issues or ask specific questions is always to contact Just Flight support directly:

https://community.justflight.com/topic/2/product-support

Thank you for the kind words! I'll be sure to pass these on to the rest of the team.

Mark - Just Flight

I've just looked into this, and all we do on our side is tell GSX the location of the water service door on the aircraft. That all looks to be set up correctly in the GSX profiles we include with the F28 Professional.

If you haven't already, we would recommend reporting this directly to FSDT as something for them to investigate further.

Mark - Just Flight

Nevermind, I found them under the A320 SL

It is currently in development. Last update was on 7th April

https://www.justflight.com/in-development/fly-the-line-short-haul-edition

Step-by-step instructions on how to add aircraft models and liveries into FS Traffic can be found from Page 24 onwards of the FS Traffic manual. The latest version of the manual is located at the following file directory: ...\Community\justflight-fstraffic-module\Documents

From the steps you have listed, we would recommend double-checking that the Ai aircraft that is being imported is correctly installed in the Community folder, and that the "Title=" entry from inside the aircraft.cfg is being entered into the Traffic Control Centre > Aircraft > Liveries page, not the name of the aircraft's folder.

Mark - Just Flight

There have been some file structure changes with the FS Traffic v1.0.7 update, but no intentional changes on our side to prevent the use of our models with other Ai traffic injectors.

The changes in file structure may require the developers of other AI traffic programs to update the file directories they are using to detect the FS Traffic models in their software.

Mark - Just Flight

Thanks for the feedback. I have passed this on to the FS Traffic development team for consideration in future updates.

Mark - Just Flight

The schedules listed in the Schedules Manager are a total list of scheduled flights that operated from that airport during the timeframe of the database selected. As with any Ai Traffic program, it sadly isn't feasible for us to model every possible aircraft type and paint them in every operator's livery, but we still list every flight in the schedules so that users can assign their own aircraft models and liveries to them.

For example, if you have a SF3 Ai model and a REX livery, the "Title=" entry from that aircraft's aircraft.cfg can be added to the Aircraft Manager > Liveries page and that aircraft would then show up on the correct flights.

More information on the Traffic Control Centre functions can be found in the FS Traffic manual: https://downloads.justflight.com/products/JFF003616/FSTraffic_MSFS_manual.pdf

Any livery requests can be made at the following forum thread: https://community.justflight.com/topic/4130/livery-requests

We actively monitor that thread and add new liveries to the product with every update based on those suggestions.

Mark - Just Flight

74Y is the ICAO code for the 747-400F/747-400ERF. As FS Traffic does not support cargo flights, there aren't any liveries assigned to freighter aircraft by default. If an aircraft does not have any liveries assigned to it in the Aircraft Manager > Liveries page, then that aircraft will not be generated in the simulator.

If widebody aircraft have liveries assigned to them and still aren't appearing in the simulator, we would recommend checking out the following FAQ: https://support.justflight.com/en/support/solutions/articles/17000131088-why-do-i-not-see-any-a380s-at-passenger-gates-for-example-no-a380s-at-dubai-

Mark - Just Flight

The FS Traffic module can be disabled via the Traffic Control Centre by going to Options > Enable/Disable FS Traffic.

This will disable FS Traffic traffic generation, preventing duplicate flights from generating when using other Ai traffic injectors.

Mark - Just Flight

I'm also waiting news on the King Air - can't wait for it already 😄

I seem to recall that there are some sim limitations to using WASM gauges as pop-out windows, and as we are using a mixture of WASM and HTML/JS gauges for the EFB, there may be some limitations encountered when using our EFB as a pop-out window.

This isn't something we have looked into for quite some time though, so it may have changed in recent MSFS updates. We'll log this on our internal bug/feature request tracker to investigate ahead of a future update.

Mark - Just Flight

User error. The Tacan receiver is picking up the signal about 40 miles out. I just needed to get closer.

We did test the RJ up to its maximum crosswind components of 35 knots, and sufficient yaw control was confirmed with the "Rudder Steering Axis" option enabled and disabled to maintain the runway centreline. That's not to say something in the sim, or other changes to the flight model may have changed that at some point post-release though, so we have made a note to double-check that ahead of the next update.

The "quirky" nose wheel steering/rudder control that you mentioned is a known side effect of a fix that was created to prevent conflicts between the nose wheel steering axis and rudder axis control assignments. From our testing (as well as feedback we received since that fix was applied), the current method of nose wheel steering is the better logic and should match the behaviour seen in other aircraft that have the option to disable the nose wheel steering from the rudder axis.

Mark - Just Flight

We are currently working on a significant update to the 146 Professional that will add a lot of the improvements we have developed in the RJ Professional, and the flight model improvements will be part of that.

We aren't able to provide a specific time frame for that at the moment, but it is being worked on, and it will also form our MSFS 2024 compatibility update for the 146 Professional.

Mark - Just Flight