g3000-v0.7.2

Working Title G3000

Latest version: v0.7.2

Description

This is a mod for MSFS2020 that aims to improve the in-game G3000 and G5000. The goal is to bring functionality closer to the real-life units, with a focus on both features and layout/UI.

This mod was created with cross-compatibility in mind. It modifies the minimum number of base files possible to achieve its goals, so it should be compatible with most other mods, including all other WorkingTitle mods. However, because of the nature of the mod, it will conflict with other mods that make changes to the G3000.

Installation

Download workingtitle-g3000-v0.7.2.zip from the Github release page. Do not download the Source code files unless you are sure you want those.

To install, copy the workingtitle-g3000 folder from the zip file into your Community directory.

If you want to enable the road display for the navigation map, you must also download workingtitle-g3000-roaddata-v0.2.0.zip from the Github release page. To install the road data package, copy the workingtitle-g3000-roaddata folder from the zip file into your Community directory. Requires 1.4 GB of hard drive space.

Configuration File

Certain mod settings can be customized via a configuration file which is located at workingtitle-g3000\html_ui\WTg3000.cfg. Documentation for the various settings can be found in the file itself. If you make changes to the file while the game is running, you must restart the game for the changes to take effect.

If you make changes to the configuration file, remember to back it up before updating the mod.

Navigraph Account Linking

This mod enables the G3000/5000 to natively display Navigraph charts. Use of this feature requires an active Navigraph Ultimate subscription (and internet connection). You will also need to link your Navigraph account within the sim. To do so, follow the instructions below:

1. Use the GTC (touchscreen controller) to navigate to MFD Home -> Utilities -> Database Status.
2. Click on the Navigraph Charts row. A pop-up will appear.
3. A browser window should open automatically. If this does not happen, you will need to manually open a browser and navigate to the provided URL.
4. You will be prompted to log in to your Navigraph account and allow access. The mod does not store your Navigraph username or password anywhere, nor does it even have access to this information at any point during the authentication process.
5. After completing step 4, press the "Link Account" button on the GTC pop-up. A message will appear on the GTC indicating either success or failure.

During a flight, you can check your Navigraph account link status in the GTC Database Status page. If both the Standby and Active fields display "Available", this means an account has been linked and chart database access is available. If the Standby field displays "Available" and the Active field displays "None", this means an account was linked but access has expired and you need to re-authenticate using the above process to restore chart database access. If both fields display "None", this means no Navigraph account has been linked.

Release Highlights for v0.7.2

Please refer to the changelog for a more detailed description of changes in this release.

• Added support for advisory VNAV guidance. The FMS can now calculate VNAV descent profiles and provide information on top of descent, bottom of descent, required vertical speed, and vertical path deviation. The autopilot still does not support V PATH mode.

Fixes

• [FPLN] Fixed a bug that prevented editing of the active flight plan under certain circumstances.
• [PFD] Autopilot display now correctly shows ALTS armed indication while in PITCH mode.
• [NavMap] Flight Plan Text Inset now displays cumulative ETE instead of leg ETE when CUM mode is selected.

Known Issues

• [FPLN] There is currently a bug with the sim's built-in flight plan management system which prevents waypoints from being properly added to the flight plan while an approach is loaded. As a result, inserting waypoints or airways into the Enroute segment of the active flight plan with an approach loaded will desynchronize the FMS flight plan from the sim's flight plan and lead to unexpected behavior. As a workaround, enter waypoints before loading an approach. If you need to enter waypoints after an approach has been loaded, remove the approach, make the necessary edits, then reload the approach. Lastly, if the FMS active flight plan becomes desynchronized, you can fix it by deleting the active flight plan via the Flight Plan Options menu.
• [FPLN] There is another issue with the sim's built-in flight plan management system related to having consecutive legs with the same waypoint fix in the active flight plan (non-consecutive legs with the same waypoint fix are OK). This can cause numerous types of unexpected behavior. As such, avoid creating an active flight plan with consecutive legs with the same waypoint fix (the one exception is that the first approach leg may have the same fix as the leg immediately before it). Deleting the active flight plan via the Flight Plan Options menu will resolve any problems related to this bug.
• [PFD] Citation Longitude: the PFD altimeter baro setting may be a bit slow to update when turning the PFD baro knobs. As a side effect of syncing the PFD altimeter baro settings to that of the standby altimeter, the sync is paused as long as the baro knobs are being turned in order to prevent inputs from being eaten.
• [PFD] TBM 930: Co-pilot PFD softkeys are nonfunctional.
• [NavMap] Airspaces are currently not available to display. The way the game loads data for these features is unreliable at best, and more time is needed to come up with a satisfactory solution to rendering them. Expect them to be added back at a later date.
• [NavMap] The flight plan renderer currently does not draw turn anticipation arcs or turn to intercept legs. These will be added later.
• [NavMap] All airport waypoints are shown as if they are serviced, regardless of whether they actually are. This is because waypoint data from the game is currently missing this information.
• [NavMap] Airport waypoint symbols will only show around a certain geographic distance from the center of the map (this does not apply to airports that are part of the active flight plan). This is due to the way the game searches for airports (the number of results is limited for performance reasons and there is no option to filter the search e.g. by size to reduce the performance penalty).
• [Weather Radar] When NEXRAD is enabled for the navigation map in the right MFD pane, the weather radar display in the left MFD pane will have artifacts. This does not occur with the opposite arrangement (i.e. NEXRAD enabled in left MFD pane, weather radar in right MFD pane). The bug also occurs when enabling NEXRAD for the PFD inset map. A workaround for now is to simply disable NEXRAD or to enable it in the left pane instead of the right (and disable it for the PFD inset map) if you wish to use it in conjunction with the weather radar.
• [Misc] MSFS will take an increased amount of time to fully shut down (up to several minutes) when closing the game after starting a flight that uses the road data package. The game window will still close promptly, but the game process will run in the background and game audio can be heard. The process is not frozen and will eventually shut down on its own, however if you wish to speed up the process, you can manually end-task or end-process MSFS through Task Manager. Disabling world regions for the road data package in the mod configuration file will also speed up the shut down process.
• [Misc] TBM 930: the standby airspeed indicator still redlines at lower speeds than it should. If this bothers you, change the crossover_speed setting in asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\flight_model.cfg to 0. If you use the TBM improvement mod, you should change the value in the flight_model.cfg file found in that mod's folder.

FAQ

• Q: I copied the mod folder to my Community folder but don't get any of the new features. What do I do?
  • A: Make sure you downloaded the correct mod folder. It should be named workingtitle-g3000 and be contained in a .zip file named workingtitle-g3000-v[version number].
• Q: Why do I no longer have synthetic vision on the PFD after installing the mod?
  • A: The mod introduces the option to toggle synthetic vision on/off and the setting defaults to off. To turn it back on, use the touchscreen controllers and navigate to PFD Home -> PFD Settings -> SVT Terrain Enable. Alternatively, for the TBM 930 only, use the PFD softkeys to navigate to PFD Settings -> Altitude Overlays -> Synthetic Terrain.
• Q: When I copy the mod folder to my Community folder, why do I get an error saying the file path name is too long?
  • A: This is a Windows issue. By default, Windows limits file paths to 260 characters. You can disable this limit by modifying the system registry (not as scary as it sounds). Tutorials for how to do so can easily be found with a Google (or Bing) search.
• Q: Why do I sometimes get low performance/FPS with the mod?
  • A: The single largest performance sink (when it comes to avionics) is the navigational map. The mod actually uses a completely new code base for the navmap that is more performant than the default. However, the mod also allows many more features to be drawn on the map than is possible with the unmodded map (as well as allowing for two independent navmaps to be displayed on the MFD), which is where performance can start to suffer. Generally, the more waypoints and text labels drawn on the map, the greater the impact on performance. In addition, if you have the road data package installed, you may see improved perf...

g3000-v0.7.1

Working Title G3000

Latest version: v0.7.1

Description

This is a mod for MSFS2020 that aims to improve the in-game G3000 and G5000. The goal is to bring functionality closer to the real-life units, with a focus on both features and layout/UI.

This mod was created with cross-compatibility in mind. It modifies the minimum number of base files possible to achieve its goals, so it should be compatible with most other mods, including all other WorkingTitle mods. However, because of the nature of the mod, it will conflict with other mods that make changes to the G3000.

Installation

Download workingtitle-g3000-v0.7.1.zip from the Github release page. Do not download the Source code files unless you are sure you want those.

To install, copy the workingtitle-g3000 folder from the zip file into your Community directory.

If you want to enable the road display for the navigation map, you must also download workingtitle-g3000-roaddata-v0.2.0.zip from the Github release page. To install the road data package, copy the workingtitle-g3000-roaddata folder from the zip file into your Community directory. Requires 1.4 GB of hard drive space.

Configuration File

Certain mod settings can be customized via a configuration file which is located at workingtitle-g3000\html_ui\WTg3000.cfg. Documentation for the various settings can be found in the file itself. If you make changes to the file while the game is running, you must restart the game for the changes to take effect.

Navigraph Account Linking

This mod enables the G3000/5000 to natively display Navigraph charts. Use of this feature requires an active Navigraph Ultimate subscription (and internet connection). You will also need to link your Navigraph account within the sim. To do so, follow the instructions below:

1. Use the GTC (touchscreen controller) to navigate to MFD Home -> Utilities -> Database Status.
2. Click on the Navigraph Charts row. A pop-up will appear.
3. A browser window should open automatically. If this does not happen, you will need to manually open a browser and navigate to the provided URL.
4. You will be prompted to log in to your Navigraph account and allow access. The mod does not store your Navigraph username or password anywhere, nor does it even have access to this information at any point during the authentication process.
5. After completing step 4, press the "Link Account" button on the GTC pop-up. A message will appear on the GTC indicating either success or failure.

During a flight, you can check your Navigraph account link status in the GTC Database Status page. If both the Standby and Active fields display "Available", this means an account has been linked and chart database access is available. If the Standby field displays "Available" and the Active field displays "None", this means an account was linked but access has expired and you need to re-authenticate using the above process to restore chart database access. If both fields display "None", this means no Navigraph account has been linked.

Enabling Offline AI and SimConnect (e.g. VATSIM) Traffic

The base sim only provides information on Live AI Traffic to JS/HTML instruments. As a result, by default the mod's traffic systems only support Live AI traffic. However, the mod provides the option to enable support for Offline AI and SimConnect-injected traffic using a third-party app. To do so, please complete the following steps:

1. Download and install laurinius's MSFS Traffic Service app (https://github.com/laurinius/MSFSTrafficService). The app requires .NET Core 3.1 to run (https://dotnet.microsoft.com/download).
2. Change the useTrafficService setting in the mod configuration file to true.
3. Start the MSFS Traffic Service app and ensure that the service is running (this can be done before or after starting the sim).
4. (Optional) Configure the port used by MSFS Traffic Service app by changing the port number within the app itself and changing the trafficServicePort setting in the mod configuration file to match. Not recommended unless the default port (8383) is not working and you know what you are doing.

Once you have completed these steps, the mod will display and issue traffic alerts for the additional types of traffic supported by the MSFS Traffic Service app. If the mod encounters any errors retrieving traffic data from the traffic service app during a flight, it will fall back to using the default sim's traffic data until it detects that the traffic service app is sending good data again. Lastly, it is recommended to set the useTrafficService mod configuration setting to false when you are not planning to use the traffic service app; while leaving the setting at true will not result in any errors, it does incur a small and otherwise unnecessary performance cost.

Release Highlights for v0.7.1

Please refer to the changelog for a more detailed description of changes in this release.

• Updated the GTC Direct To page.

Fixes

• [Compatibility] Fixed a compatibility issue with Sim Update 4 where the FMS would not automatically activate approaches.
• [FPLN] Reduced the chance of failing to import enroute waypoints into the FMS when loading a flight plan from the world map.
• [FPLN] Fixed a bug where for certain ILS/LOC approaches, the FMS would automatically switch autopilot navigation source to NAV1/NAV2 before the plane was inbound on the final approach course.

Known Issues

• [FPLN] There is currently a bug with the sim's built-in flight plan management system which prevents waypoints from being properly added to the flight plan while an approach is loaded. As a result, inserting waypoints or airways into the Enroute segment of the active flight plan with an approach loaded will desynchronize the FMS flight plan from the sim's flight plan and lead to unexpected behavior. As a workaround, enter waypoints before loading an approach. If you need to enter waypoints after an approach has been loaded, remove the approach, make the necessary edits, then reload the approach. Lastly, if the FMS active flight plan becomes desynchronized, you can fix it by deleting the active flight plan via the Flight Plan Options menu.
• [FPLN] There is another issue with the sim's built-in flight plan management system related to having consecutive legs with the same waypoint fix in the active flight plan (non-consecutive legs with the same waypoint fix are OK). This can cause numerous types of unexpected behavior. As such, avoid creating an active flight plan with consecutive legs with the same waypoint fix (the one exception is that the first approach leg may have the same fix as the leg immediately before it). Deleting the active flight plan via the Flight Plan Options menu will resolve any problems related to this bug.
• [PFD] Citation Longitude: the PFD altimeter baro setting may be a bit slow to update when turning the PFD baro knobs. As a side effect of syncing the PFD altimeter baro settings to that of the standby altimeter, the sync is paused as long as the baro knobs are being turned in order to prevent inputs from being eaten.
• [PFD] TBM 930: Co-pilot PFD softkeys are nonfunctional.
• [NavMap] Airspaces are currently not available to display. The way the game loads data for these features is unreliable at best, and more time is needed to come up with a satisfactory solution to rendering them. Expect them to be added back at a later date.
• [NavMap] The flight plan renderer currently does not draw turn anticipation arcs or turn to intercept legs. These will be added later.
• [NavMap] All airport waypoints are shown as if they are serviced, regardless of whether they actually are. This is because waypoint data from the game is currently missing this information.
• [NavMap] Airport waypoint symbols will only show around a certain geographic distance from the center of the map (this does not apply to airports that are part of the active flight plan). This is due to the way the game searches for airports (the number of results is limited for performance reasons and there is no option to filter the search e.g. by size to reduce the performance penalty).
• [Weather Radar] When NEXRAD is enabled for the navigation map in the right MFD pane, the weather radar display in the left MFD pane will have artifacts. This does not occur with the opposite arrangement (i.e. NEXRAD enabled in left MFD pane, weather radar in right MFD pane). The bug also occurs when enabling NEXRAD for the PFD inset map. A workaround for now is to simply disable NEXRAD or to enable it in the left pane instead of the right (and disable it for the PFD inset map) if you wish to use it in conjunction with the weather radar.
• [Misc] MSFS will take an increased amount of time to fully shut down (up to several minutes) when closing the game after starting a flight that uses the road data package. The game window will still close promptly, but the game process will run in the background and game audio can be heard. The process is not frozen and will eventually shut down on its own, however if you wish to speed up the process, you can manually end-task or end-process MSFS through Task Manager.
• [Misc] TBM 930: the standby airspeed indicator still redlines at lower speeds than it should. If this bothers you, change the crossover_speed setting in asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\flight_model.cfg to 0. If you use the TBM improvement mod, you should change the value in the flight_model.cfg file found in that mod's folder.

FAQ

• Q: I copied the mod folder to my Community folder but don't get any of the new features. What do I do?
  • A: Make sure you downloaded the correct mod folder. It should be named workingtitle-g3000 and be contained in a .zip file named workingtitle-g3000-v[version number].
• Q: Why do I no longer have s...

g1000-v0.3.7

changes on 0.3.7

• Fixed bug that could cause display issues in the same area as live traffic.

cj4-v0.12.5

Working Title CJ4 v0.12.5

Welcome to the Working Title CJ4 v0.12.5. This version brings compatibility for MSFS Sim Update 4, as well as a number of other enhancements and small fixes, including traffic display (TFC) that will show the new SU4 SimConnect injected traffic from online services like VATSIM and IVAO. TCAS Control options are also available in the FMS, but TA/RA advisories have not yet been implemented.

In this release we also have a number of community submissions. Thanks to everyone, as always, for your contributions! We really love working with you all.

READ THE GUIDE

Please, please, please read the guide for instructions on using features. A lot of hard work went into writing the guide and the Discord channels are clogged with questions that are readily answered in the guide.

GUIDE: https://docs.google.com/document/d/1qzxPMTSQRkvau8QOi7xUqNvjx9rbww_qHlso5AT5OnI

Installation

Installation is easy, simply copy the workingtitle-aircraft-cj4 folder inside the zip file to your MSFS Community folder.

Important: We recommend that you fully delete the previous workingtitle-aircraft-cj4 folder before copying this release.

Changes

• Added Traffic Display (TFC) to the PFD and MFD
• Added "ALT TAG" option on the FMS TCAS CONTROL page
• Added ABOVE/NORM/BELOW options on the FMS TCAS CONTROL page
• Lots of great cosmetic improvements to the PFD (thanks charles-vomacka!)
• Adjusted the green band on the trim in extended view (thanks Slip!)
• Adjustments to external lighting (thanks Uwajimaya!)
• More accurate AoA display (by Slip)
• Fixed ITT scale ranges on the MFD (by Slip)
• Overhaul of the SAI (by Slip)
• Fixed ZFW calculation concerning pax weight (thanks thor!)
• VSi bug improvements on the PFD
• Minor bugfixes

⚠️ Known Issues

• In the latest versions of Navigraph data, some "lettered" or non-runway-specific approaches now appear as something like RNAV A - 00 and do not allow the selection of a landing runway, preventing using the Approach Refs page - this is something we will be working to address in the future.
• Some external applications that use the GPS/Flight plan SimVars may not function correctly or as expected when FP Sync is off.
• Loading and saving flights can have bad results.
• Custom liveries can render FADEC inoperative if they ship with a panel.cfg. Painters should reference our new Repainter's Guide for solutions.
• Autopilot modes cannot be triggered via key bindings or controllers and must currently be triggered in the cockpit with the mouse. External binding applications are adding support for LVars and HEvents. Used SimVars are documented in our Guide on SimVars.
• Sometimes a heading to altitude instruction on takeoff will display further than the first RNAV fix on an RNAV departure procedure; in these cases the workaround is to cross-check the DP chart and remove the erroneous waypoint either by deleting the heading to altitude fix or dropping the first RNAV fix onto the magenta line in the LEGS page.
• Due to sim autopilot bank rate limitations, the aircraft may overshoot on certain RNP approaches with tight turns. If you encounter this, we recommend hand flying the approach with the given lateral and vertical guidance.

gx-v0.1.0-dev8

Changes in 0.1.0-dev8

• Fixed bug that could cause display issues in the same area as live traffic.

gx-v0.1.0-dev7

Changes in 0.1.0-dev7

• Fixed bug in synthetic vision toggle
• Corrected attitude indicator width error on King Air
• Corrected text on audio panel button

Changes in 0.1.0-dev6

• rebase onto new G3X code
• apply improved styling
• port over CAS and autopilot functionality

Changes in 0.1.0-dev5

• Fixed compatibility problems with FBW A320
• Fixed nav map not drawing approach paths

Changes in 0.1.0-dev4

• Compatibility for 1.12.13.0

Changes in 0.1.0-dev3

• Compatibility for 1.10.7

Changes in 0.1.0-dev2

• Fix "giant map icon" problem in Seattle area

Changes in 0.1.0-dev1

• Map menu page with numerous new features:
  • North up, track up, and DTK up options
  • NEXRAD and topo overlays
  • Multiple zoom options including auto-zoom on touchscreen
• Completely new autopilot control system via touchscreen
• Completely new menu system supporting independent per-page menus
• Redesigned PFD with wind data information and CAS system
• Graphical overhaul: more authentic, less ugly blue gradient
• Optional simulation of GAP-26 regulated pitot heater (see pitot.md)

g1000-v0.3.6

changes on 0.3.6

• Updated for 1.16.2.0

changes on 0.3.5

• Updated for 1.15.7.0
• Fixed compat problems with stock G3000

Notice

Due to changes in how planes load their configurations in WU4, we had to change the code that loads custom display gauges from WTEngineDisplay.xml, as is done with our sample for the G36. In order to get these to work now, aircraft creators or modders must put the contents of the WTEngineDisplay section directly into panel.xml, within the body of the main PlaneHTMLConfig section. This is unfortunate, but it was the only way we could preserve this functionality. Doing this to your panel.xml is fully backwards compatible and will not break planes that don't use the modded G1000.

changes in v0.3.4

• Fixed compatibility problems with FBW A320
• Fixed nav map not drawing approach paths

Changes in v0.3.3

• Compatibility with and improvements from v1.12.13.0.

Changes in v0.3.2

• Compatibility fix for 1.10.7.

Changes in v0.3.1

• Keep the G1000 from breaking synthetic vision on the G3000 and G3Xes
• Fix WPT-page maps breaking on the MFD when in Track Up.

Changes in v0.3.0

Main features

• Added track-up mode for both PFD and MFD
• Fixed unwanted U-turn on ACTIVATE APPROACH
• Fixed reversed behavior of NOSE UP/DN buttons in FLC mode
• Added a preference saving system tied to plane model
• Configured it to currently preserve the following across sessions:
  • PFD and MFD brightness
  • V Speeds
  • Track up mode
  • Barometer mode
  • HSI settings for BRG1, BRG2, and DME
• Support loading plane configuration information even in encrypted planes
• Detect hardware avionics knobs in all models and configure them automatically
• Added support for additional XML-configurable ENGINE pages on MFD
• Lots of changes to colors and styling to closer match reality

PFD and MFD enhancements

• Added a flight path marker on the PFD when in Syn Vis mode above 30kts
• Added new vertical column type gauge for engine display
• Updated circular gauge to support custom gradations and rounding
• Added a new blinking yellow status for engine gauges
• Correctly handle wind data when on ground or wind speed <1 knot
• Fixed reversed wind arrow at all times on MFD
• Improve MFD soft key menus, including new switch for TRACK UP
• Increased MFD max range to 2000 with more intermediate steps
• Move weather radar to MAP page group, only show if radar is on board
• Change brightness of PFD/MFD knobs and softkeys along with display

Styling improvements

• Change PFD and MFD headers to more closely match the real font size, spacing, and colour
• More accurate colors on attitude indicator, horizon, and map; new gradient on horizon
• Updated flight director and attitude arrows
• Updated styling of airport waypoint info page (more to come)
• Updated styling of softkey menus to be more realistic

Miscellaneous

• Added sample engine page configuration for G36 Bonanza
• Fix false DON'T SINK alert when flying patterns / touch and goes
• Improve representation of whole numbers as decimals

g3000-v0.7.0

Working Title G3000

Latest version: v0.7.0

Description

This is a mod for MSFS2020 that aims to improve the in-game G3000 and G5000. The goal is to bring functionality closer to the real-life units, with a focus on both features and layout/UI.

This mod was created with cross-compatibility in mind. It modifies the minimum number of base files possible to achieve its goals, so it should be compatible with most other mods, including all other WorkingTitle mods. However, because of the nature of the mod, it will conflict with other mods that make changes to the G3000.

Installation

Download workingtitle-g3000-v0.7.0.zip from the Github release page. Do not download the Source code files unless you are sure you want those.

To install, copy the workingtitle-g3000 folder from the zip file into your Community directory.

If you want to enable the road display for the navigation map, you must also download workingtitle-g3000-roaddata-v0.2.0.zip from the Github release page. To install the road data package, copy the workingtitle-g3000-roaddata folder from the zip file into your Community directory. Requires 1.4 GB of hard drive space.

Configuration File

Certain mod settings can be customized via a configuration file which is located at workingtitle-g3000\html_ui\WTg3000.cfg. Documentation for the various settings can be found in the file itself. If you make changes to the file while the game is running, you must restart the game for the changes to take effect.

Navigraph Account Linking

This mod enables the G3000/5000 to natively display Navigraph charts. Use of this feature requires an active Navigraph Ultimate subscription (and internet connection). You will also need to link your Navigraph account within the sim. To do so, follow the instructions below:

1. Use the GTC (touchscreen controller) to navigate to MFD Home -> Utilities -> Database Status.
2. Click on the Navigraph Charts row. A pop-up will appear.
3. A browser window should open automatically. If this does not happen, you will need to manually open a browser and navigate to the provided URL.
4. You will be prompted to log in to your Navigraph account and allow access. The mod does not store your Navigraph username or password anywhere, nor does it even have access to this information at any point during the authentication process.
5. After completing step 4, press the "Link Account" button on the GTC pop-up. A message will appear on the GTC indicating either success or failure.

During a flight, you can check your Navigraph account link status in the GTC Database Status page. If both the Standby and Active fields display "Available", this means an account has been linked and chart database access is available. If the Standby field displays "Available" and the Active field displays "None", this means an account was linked but access has expired and you need to re-authenticate using the above process to restore chart database access. If both fields display "None", this means no Navigraph account has been linked.

Enabling Offline AI and SimConnect (e.g. VATSIM) Traffic

The base sim only provides information on Live AI Traffic to JS/HTML instruments. As a result, by default the mod's traffic systems only support Live AI traffic. However, the mod provides the option to enable support for Offline AI and SimConnect-injected traffic using a third-party app. To do so, please complete the following steps:

1. Download and install laurinius's MSFS Traffic Service app (https://github.com/laurinius/MSFSTrafficService). The app requires .NET Core 3.1 to run (https://dotnet.microsoft.com/download).
2. Change the useTrafficService setting in the mod configuration file to true.
3. Start the MSFS Traffic Service app and ensure that the service is running (this can be done before or after starting the sim).
4. (Optional) Configure the port used by MSFS Traffic Service app by changing the port number within the app itself and changing the trafficServicePort setting in the mod configuration file to match. Not recommended unless the default port (8383) is not working and you know what you are doing.

Once you have completed these steps, the mod will display and issue traffic alerts for the additional types of traffic supported by the MSFS Traffic Service app. If the mod encounters any errors retrieving traffic data from the traffic service app during a flight, it will fall back to using the default sim's traffic data until it detects that the traffic service app is sending good data again. Lastly, it is recommended to set the useTrafficService mod configuration setting to false when you are not planning to use the traffic service app; while leaving the setting at true will not result in any errors, it does incur a small and otherwise unnecessary performance cost.

Release Highlights for v0.7.0

Please refer to the changelog for a more detailed description of changes in this release.

• Added the ability to insert airways into flight plans.
• Added support for standby flight plans.
• Added the Flight Plan and Procedure Preview panes.
• Added the Flight Plan Text Inset window for the Navigation Map.
• For the Longitude: the GTC Flight Plan Keypad now supports direct entry of routes into flight plans (please refer to the changelog for the syntax).

Fixes

• [FPLN] Fixed a bug where the GTC Flight Plan page would display a different active leg from the navigation map and PFD navigation status bar.
• [GTC] The Flight Plan page should now report accurate leg-leg distances for all flight plan legs.
• [GTC] The Back button now works properly in the Procedure Selection pages.
• [GTC] The Waypoint Keyboard now provides accurate indications of when a match for the entered waypoint ident has been found.
• [GTC] Fixed a graphical glitch affecting certain touchscreen buttons.
• [Charts] The mod should now be better at "remembering" Navigraph account access and should not require account re-linking as frequently.
• [VFR Map] Fixed a bug preventing the VFR Map from being moved when it was not detached to a separate window.

Known Issues

• [FPLN] There is currently a bug with the sim's built-in flight plan management system which prevents waypoints from being properly added to the flight plan while an approach is loaded. As a result, inserting waypoints or airways into the Enroute segment of the active flight plan with an approach loaded will desynchronize the FMS flight plan from the sim's flight plan and lead to unexpected behavior. As a workaround, enter waypoints before loading an approach. If you need to enter waypoints after an approach has been loaded, remove the approach, make the necessary edits, then reload the approach. Lastly, if the FMS active flight plan becomes desynchronized, you can fix it by deleting the active flight plan via the Flight Plan Options menu.
• [FPLN] There is another issue with the sim's built-in flight plan management system related to having consecutive legs with the same waypoint fix in the active flight plan (non-consecutive legs with the same waypoint fix are OK). This can cause numerous types of unexpected behavior. As such, avoid creating an active flight plan with consecutive legs with the same waypoint fix (the one exception is that the first approach leg may have the same fix as the leg immediately before it). Deleting the active flight plan via the Flight Plan Options menu will resolve any problems related to this bug.
• [PFD] Citation Longitude: the PFD altimeter baro setting may be a bit slow to update when turning the PFD baro knobs. As a side effect of syncing the PFD altimeter baro settings to that of the standby altimeter, the sync is paused as long as the baro knobs are being turned in order to prevent inputs from being eaten.
• [PFD] TBM 930: Co-pilot PFD softkeys are nonfunctional.
• [NavMap] Airspaces are currently not available to display. The way the game loads data for these features is unreliable at best, and more time is needed to come up with a satisfactory solution to rendering them. Expect them to be added back at a later date.
• [NavMap] The flight plan renderer currently does not draw turn anticipation arcs or turn to intercept legs. These will be added later.
• [NavMap] All airport waypoints are shown as if they are serviced, regardless of whether they actually are. This is because waypoint data from the game is currently missing this information.
• [NavMap] Airport waypoint symbols will only show around a certain geographic distance from the center of the map (this does not apply to airports that are part of the active flight plan). This is due to the way the game searches for airports (the number of results is limited for performance reasons and there is no option to filter the search e.g. by size to reduce the performance penalty).
• [Weather Radar] When NEXRAD is enabled for the navigation map in the right MFD pane, the weather radar display in the left MFD pane will have artifacts. This does not occur with the opposite arrangement (i.e. NEXRAD enabled in left MFD pane, weather radar in right MFD pane). The bug also occurs when enabling NEXRAD for the PFD inset map. A workaround for now is to simply disable NEXRAD or to enable it in the left pane instead of the right (and disable it for the PFD inset map) if you wish to use it in conjunction with the weather radar.
• [Misc] MSFS will take an increased amount of time to fully shut down (up to several minutes) when closing the game after starting a flight that uses the road data package. The game window will still close promptly, but the game process will run in the background and game audio can be heard. The process is not frozen and will eventually shut down on its own, however if you wish to speed up the process, you can manually end-task or end-process MSFS through Task Manager.
• [Misc] TBM 930: the ...

g3000-v0.6.2

Working Title G3000

Latest version: v0.6.2

Description

This is a mod for MSFS2020 that aims to improve the in-game G3000 and G5000. The goal is to bring functionality closer to the real-life units, with a focus on both features and layout/UI.

This mod was created with cross-compatibility in mind. It modifies the minimum number of base files possible to achieve its goals, so it should be compatible with most other mods, including all other WorkingTitle mods. However, because of the nature of the mod, it will conflict with other mods that make changes to the G3000.

Installation

Download workingtitle-g3000-v0.6.2.zip from the Github release page. Do not download the Source code files unless you are sure you want those.

To install, copy the workingtitle-g3000 folder from the zip file into your Community directory.

If you want to enable the road display for the navigation map, you must also download workingtitle-g3000-roaddata-v0.2.0.zip from the Github release page. To install the road data package, copy the workingtitle-g3000-roaddata folder from the zip file into your Community directory. Requires 1.4 GB of hard drive space.

Configuration File

Certain mod settings can be customized via a configuration file which is located at workingtitle-g3000\html_ui\WTg3000.cfg. Documentation for the various settings can be found in the file itself. If you make changes to the file while the game is running, you must restart the game for the changes to take effect.

Navigraph Account Linking

This mod enables the G3000/5000 to natively display Navigraph charts. Use of this feature requires an active Navigraph Ultimate subscription (and internet connection). You will also need to link your Navigraph account within the sim. To do so, follow the instructions below:

1. Use the GTC (touchscreen controller) to navigate to MFD Home -> Utilities -> Database Status.
2. Click on the Navigraph Charts row. A pop-up will appear.
3. A browser window should open automatically. If this does not happen, you will need to manually open a browser and navigate to the provided URL.
4. You will be prompted to log in to your Navigraph account and allow access. The mod does not store your Navigraph username or password anywhere, nor does it even have access to this information at any point during the authentication process.
5. After completing step 4, press the "Link Account" button on the GTC pop-up. A message will appear on the GTC indicating either success or failure.

During a flight, you can check your Navigraph account link status in the GTC Database Status page. If both the Standby and Active fields display "Available", this means an account has been linked and chart database access is available. If the Standby field displays "Available" and the Active field displays "None", this means an account was linked but access has expired and you need to re-authenticate using the above process to restore chart database access. If both fields display "None", this means no Navigraph account has been linked.

Enabling Offline AI and SimConnect (e.g. VATSIM) Traffic

The base sim only provides information on Live AI Traffic to JS/HTML instruments. As a result, by default the mod's traffic systems only support Live AI traffic. However, the mod provides the option to enable support for Offline AI and SimConnect-injected traffic using a third-party app. To do so, please complete the following steps:

1. Download and install laurinius's MSFS Traffic Service app (https://github.com/laurinius/MSFSTrafficService). The app requires .NET Core 3.1 to run (https://dotnet.microsoft.com/download).
2. Change the useTrafficService setting in the mod configuration file to true.
3. Start the MSFS Traffic Service app and ensure that the service is running (this can be done before or after starting the sim).
4. (Optional) Configure the port used by MSFS Traffic Service app by changing the port number within the app itself and changing the trafficServicePort setting in the mod configuration file to match. Not recommended unless the default port (8383) is not working and you know what you are doing.

Once you have completed these steps, the mod will display and issue traffic alerts for the additional types of traffic supported by the MSFS Traffic Service app. If the mod encounters any errors retrieving traffic data from the traffic service app during a flight, it will fall back to using the default sim's traffic data until it detects that the traffic service app is sending good data again. Lastly, it is recommended to set the useTrafficService mod configuration setting to false when you are not planning to use the traffic service app; while leaving the setting at true will not result in any errors, it does incur a small and otherwise unnecessary performance cost.

Release Highlights for v0.6.2

Please refer to the changelog for a more detailed description of changes in this release.

• Enabled support for laurinius's MSFS Traffic Service app (available on Github), which adds Offline AI traffic and SimConnect-injected traffic to the mod's traffic systems. This feature requires that you download and install laurinius's app separately and must be manually enabled via the mod config file.

Fixes

• [General] Fixed a bug with initializing airport data with no listed runways.
• [NavMap] While in TRACK UP mode on the ground, the compass arc's reference tick mark now correctly indicates the aircraft's current heading instead of ground track (which cannot always be reliably calculated on the ground).
• [Traffic] Fixed an error with ground track computation for traffic contacts.
• [PFD] Airspeed altimeter speed bugs are no longer mispositioned when airspeed is below the minimum indicated airspeed.
• [GTC] Fixed a bug where the Charts page would sometimes automatically change the selected airport after closing a popup or navigating back to it from the pan/zoom control page.

Known Issues

• [PFD] Citation Longitude: the PFD altimeter baro setting may be a bit slow to update when turning the PFD baro knobs. As a side effect of syncing the PFD altimeter baro settings to that of the standby altimeter, the sync is paused as long as the baro knobs are being turned in order to prevent inputs from being eaten.
• [PFD] TBM 930: Co-pilot PFD softkeys are nonfunctional.
• [NavMap] Airspaces are currently not available to display. The way the game loads data for these features is unreliable at best, and more time is needed to come up with a satisfactory solution to rendering them. Expect them to be added back at a later date.
• [NavMap] The flight plan renderer currently does not draw turn anticipation arcs or turn to intercept legs. These will be added later.
• [NavMap] All airport waypoints are shown as if they are serviced, regardless of whether they actually are. This is because waypoint data from the game is currently missing this information.
• [NavMap] Airport waypoint symbols will only show around a certain geographic distance from the center of the map (this does not apply to airports that are part of the active flight plan). This is due to the way the game searches for airports (the number of results is limited for performance reasons and there is no option to filter the search e.g. by size to reduce the performance penalty).
• [Weather Radar] When NEXRAD is enabled for the navigation map in the right MFD pane, the weather radar display in the left MFD pane will have artifacts. This does not occur with the opposite arrangement (i.e. NEXRAD enabled in left MFD pane, weather radar in right MFD pane). The bug also occurs when enabling NEXRAD for the PFD inset map. A workaround for now is to simply disable NEXRAD or to enable it in the left pane instead of the right (and disable it for the PFD inset map) if you wish to use it in conjunction with the weather radar.
• [Misc] MSFS will take an increased amount of time to fully shut down (up to several minutes) when closing the game after starting a flight that uses the road data package. The game window will still close promptly, but the game process will run in the background and game audio can be heard. The process is not frozen and will eventually shut down on its own, however if you wish to speed up the process, you can manually end-task or end-process MSFS through Task Manager.
• [Misc] TBM 930: the standby airspeed indicator still redlines at lower speeds than it should. If this bothers you, change the crossover_speed setting in asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\flight_model.cfg to 0. If you use the TBM improvement mod, you should change the value in the flight_model.cfg file found in that mod's folder.

FAQ

• Q: I copied the mod folder to my Community folder but don't get any of the new features. What do I do?
  • A: Make sure you downloaded the correct mod folder. It should be named workingtitle-g3000 and be contained in a .zip file named workingtitle-g3000-v[version number].
• Q: Why do I no longer have synthetic vision on the PFD after installing the mod?
  • A: The mod introduces the option to toggle synthetic vision on/off and the setting defaults to off. To turn it back on, use the touchscreen controllers and navigate to PFD Home -> PFD Settings -> SVT Terrain Enable. Alternatively, for the TBM 930 only, use the PFD softkeys to navigate to PFD Settings -> Altitude Overlays -> Synthetic Terrain.
• Q: When I copy the mod folder to my Community folder, why do I get an error saying the file path name is too long?
  • A: This is a Windows issue. By default, Windows limits file paths to 260 characters. You can disable this limit by modifying the system registry (not as scary as it sounds). Tutorials for how to do so can easily be found with a Google (or Bing) search.
• Q: Why do I sometimes get low performa...

g3000-v0.6.1

Working Title G3000

Latest version: v0.6.1

Description

This is a mod for MSFS2020 that aims to improve the in-game G3000 and G5000. The goal is to bring functionality closer to the real-life units, with a focus on both features and layout/UI.

This mod was created with cross-compatibility in mind. It modifies the minimum number of base files possible to achieve its goals, so it should be compatible with most other mods, including all other WorkingTitle mods. However, because of the nature of the mod, it will conflict with other mods that make changes to the G3000.

Installation

Download workingtitle-g3000-v0.6.1.zip from the Github release page. Do not download the Source code files unless you are sure you want those.

To install, copy the workingtitle-g3000 folder from the zip file into your Community directory.

If you want to enable the road display for the navigation map, you must also download workingtitle-g3000-roaddata-v0.2.0.zip from the Github release page. To install the road data package, copy the workingtitle-g3000-roaddata folder from the zip file into your Community directory. Requires 1.4 GB of hard drive space.

Configuration File

Certain mod settings can be customized via a configuration file which is located at workingtitle-g3000\html_ui\WTg3000.cfg. Documentation for the various settings can be found in the file itself. If you make changes to the file while the game is running, you must restart the game for the changes to take effect.

Navigraph Account Linking

This mod enables the G3000/5000 to natively display Navigraph charts. Use of this feature requires an active Navigraph Ultimate subscription (and internet connection). You will also need to link your Navigraph account within the sim. To do so, follow the instructions below:

1. Use the GTC (touchscreen controller) to navigate to MFD Home -> Utilities -> Database Status.
2. Click on the Navigraph Charts row. A pop-up will appear.
3. A browser window should open automatically. If this does not happen, you will need to manually open a browser and navigate to the provided URL.
4. You will be prompted to log in to your Navigraph account and allow access. The mod does not store your Navigraph username or password anywhere, nor does it even have access to this information at any point during the authentication process.
5. After completing step 4, press the "Link Account" button on the GTC pop-up. A message will appear on the GTC indicating either success or failure.

During a flight, you can check your Navigraph account link status in the GTC Database Status page. If both the Standby and Active fields display "Available", this means an account has been linked and chart database access is available. If the Standby field displays "Available" and the Active field displays "None", this means an account was linked but access has expired and you need to re-authenticate using the above process to restore chart database access. If both fields display "None", this means no Navigraph account has been linked.

Release Highlights for v0.6.1

Please refer to the changelog for a more detailed description of changes in this release.

• Performance optimizations for the GTC Map Settings and Nearest Waypoints pages.

Fixes

• [Compatibility] Fixed an error related to parsing certain Navigraph approach data that would cause major performance degradation as well as other undesired effects related to flight plan logic and rendering.
• [Compatibility] Automatic ILS frequency loading now works properly when using Navigraph FMS data.
• [NavMap] Fixed an error that would sometimes cause the active flight plan waypoint to become "stuck" on the map after removing it from the flight plan.
• [Traffic] If a contact is lost while triggering a traffic advisory, the traffic advisory is now properly removed.
• [PFD] Fixed a regression introduced in v0.6.0 that caused the airspeed indicator reference speed bug to be slightly out of position.

Known Issues

• [PFD] Citation Longitude: the PFD altimeter baro setting may be a bit slow to update when turning the PFD baro knobs. As a side effect of syncing the PFD altimeter baro settings to that of the standby altimeter, the sync is paused as long as the baro knobs are being turned in order to prevent inputs from being eaten.
• [PFD] TBM 930: Co-pilot PFD softkeys are nonfunctional.
• [NavMap] Airspaces are currently not available to display. The way the game loads data for these features is unreliable at best, and more time is needed to come up with a satisfactory solution to rendering them. Expect them to be added back at a later date.
• [NavMap] The flight plan renderer currently does not draw turn anticipation arcs or turn to intercept legs. These will be added later.
• [NavMap] All airport waypoints are shown as if they are serviced, regardless of whether they actually are. This is because waypoint data from the game is currently missing this information.
• [NavMap] Airport waypoint symbols will only show around a certain geographic distance from the center of the map (this does not apply to airports that are part of the active flight plan). This is due to the way the game searches for airports (the number of results is limited for performance reasons and there is no option to filter the search e.g. by size to reduce the performance penalty).
• [Weather Radar] When NEXRAD is enabled for the navigation map in the right MFD pane, the weather radar display in the left MFD pane will have artifacts. This does not occur with the opposite arrangement (i.e. NEXRAD enabled in left MFD pane, weather radar in right MFD pane). The bug also occurs when enabling NEXRAD for the PFD inset map. A workaround for now is to simply disable NEXRAD or to enable it in the left pane instead of the right (and disable it for the PFD inset map) if you wish to use it in conjunction with the weather radar.
• [Misc] MSFS will take an increased amount of time to fully shut down (up to several minutes) when closing the game after starting a flight that uses the road data package. The game window will still close promptly, but the game process will run in the background and game audio can be heard. The process is not frozen and will eventually shut down on its own, however if you wish to speed up the process, you can manually end-task or end-process MSFS through Task Manager.
• [Misc] TBM 930: the standby airspeed indicator still redlines at lower speeds than it should. If this bothers you, change the crossover_speed setting in asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\flight_model.cfg to 0. If you use the TBM improvement mod, you should change the value in the flight_model.cfg file found in that mod's folder.

FAQ

• Q: I copied the mod folder to my Community folder but don't get any of the new features. What do I do?
  • A: Make sure you downloaded the correct mod folder. It should be named workingtitle-g3000 and be contained in a .zip file named workingtitle-g3000-v[version number].
• Q: Why do I no longer have synthetic vision on the PFD after installing the mod?
  • A: The mod introduces the option to toggle synthetic vision on/off and the setting defaults to off. To turn it back on, use the touchscreen controllers and navigate to PFD Home -> PFD Settings -> SVT Terrain Enable. Alternatively, for the TBM 930 only, use the PFD softkeys to navigate to PFD Settings -> Altitude Overlays -> Synthetic Terrain.
• Q: When I copy the mod folder to my Community folder, why do I get an error saying the file path name is too long?
  • A: This is a Windows issue. By default, Windows limits file paths to 260 characters. You can disable this limit by modifying the system registry (not as scary as it sounds). Tutorials for how to do so can easily be found with a Google (or Bing) search.
• Q: Why do I sometimes get low performance/FPS with the mod?
  • A: The single largest performance sink (when it comes to avionics) is the navigational map. The mod actually uses a completely new code base for the navmap that is more performant than the default. However, the mod also allows many more features to be drawn on the map than is possible with the unmodded map (as well as allowing for two independent navmaps to be displayed on the MFD), which is where performance can start to suffer. Generally, the more waypoints and text labels drawn on the map, the greater the impact on performance.
• Q: Does the mod support VNAV or inputting airways into the flight plan?
  • A: Not yet. Support will be coming with a future update.
• Q: Why can't I see multiplayer traffic on the traffic displays?
  • A: Currently only Live AI traffic is supported due to limitations in which traffic data is available to JS/HTML instruments.

Credits

• Custom city database is sourced from simplemaps (simplemaps.com/data/world-cities) under the CC Attribution 4.0 license.
• Border data is sourced from Natural Earth (www.naturalearthdata.com).
• Thank you to StuTozer/ElectrikKar for allowing us to integrate his Touchscreen Restyled Mod.
• This mod uses the Roboto family of fonts (designed by Christian Robertson), licensed under Apache 2.0.
• This mod uses the d3-array, d3-geo, and topojson libraries.
• This mod uses the spacetime and tz-lookup libraries.