Skip to content
This repository has been archived by the owner on May 16, 2024. It is now read-only.

Releases: Working-Title-MSFS-Mods/fspackages

g3000-v0.6.0

25 Apr 21:07
Compare
Choose a tag to compare

Working Title G3000

Latest version: v0.6.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.6.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.

Release Highlights for v0.6.0

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

  • Implemented traffic awareness and alert systems for both the TBM930 and Longitude.
  • Added Navigraph charts integration. Use of this feature requires a paid Navigraph subscription.
  • Updated the touchscreen controller Nearest Waypoints pages, and added the ability to filter airports by runway surface and length.
  • Added Intersection, VOR, and NDB Info pages for the touchscreen controller.
  • Added an option to turn off the custom VFR Map in the mod config file. If the custom VFR Map is disabled, the game will revert to using the default VFR Map.
  • Performance optimizations for the navigation map.

Fixes

  • [Compatibility] For the Longitude: increased the default CRU thrust limit to 95% N1. This will allow the airplane to maintain Mmo at higher altitudes for those who have installed dakfly's Longitude performance mod.
  • [General] The aural minimums alert no longer triggers immediately after takeoff.
  • [General] Calculations for distance and ETE are now more accurate for flight plan legs that involve transition turns.
  • [General] For the Longitude: altimeter pressure setting increment/decrement hotkeys now work properly again.
  • [NavMap] Fixed a game freeze related to rendering certain airways.

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.

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.

cj4-v0.12.1

15 Apr 00:40
b97ecbb
Compare
Choose a tag to compare

Working Title CJ4 v0.12.1

Welcome to the Working Title CJ4 v0.12.1. This version brings a few small bug fixes and updates to our v0.12.0 release.

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

  • Fixed bugs with parsing TUN page inputs.
  • Minor cleanup on DSPL MENU FMC page.
  • Fixed bugs with leg altitude (constraint) parsing to address some incorrect constraints in some European approaches.
  • Fix for erroneous sim autopilot altitude capture when using a hardware button tied to all the altitude slots and not just slot 1.
  • Fix for some erroneous situations where VNAV PATH kicks you to PTCH incorrectly.
  • Fix for sequencing missed approach on Go-Around after a new approach is selected.

⚠️ 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 the new REPAINT_README.md file included in the docs folder of the Github repository.
  • 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 here
  • 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.

g1000-v0.3.5

14 Apr 22:59
Compare
Choose a tag to compare

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.

cj4-v0.12.0

04 Apr 23:38
b10c628
Compare
Choose a tag to compare

Working Title CJ4 v0.12.0

Welcome to the Working Title CJ4 v0.12.0. This version brings a boatload of bug fixes and tweaks, including a new custom vertical autopilot that has allowed us to add altitude capture for PTCH mode, TO/GA modes and improve the altitude capture mechanics of the autopilot.

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

VNAV CLIMB

VNAV Climb should now be working correctly - we know that we've warned many people in past versions to turn it off if it isn't working, but at this point we believe it works as designed. As a refresher, in the CJ4, VNAV in climb is NOT A PATH. It simply provides protection for the pilot to not exceed an AT or AT OR BELOW constraint in the departure procedure. The protection exists ONLY for waypoints that are loaded into the FMC as part of a DEPARTURE PROCEDURE. If you add other waypoints beyond the DP, those constraints will not be respected as climb constraints.

AUTOPILOT/MODES

  • Enabled APPR mode for ILS when tuned in PFD even when an approach is not loaded in the FMC.
  • Added custom vertical autopilot to manage altitude capture and hold modes. (note: the ALT button is now tied to H:WT_CJ4_AP_ALT_PRESSED and the emissive lvar is L:WT_CJ4_ALT_HOLD)
  • Added altitude capture for PTCH mode.
  • Added altitude capture for TO/GA modes.
  • Enabled ability to arm LNAV on the ground and set activation at 400' AGL.
  • Fixed bug with not being able to turn off the Flight Director when FMA modes are annunciated - the FD button will now disable all modes when being turned off, as long as the AP is not on.
  • Fixed bug that prevented VNAV button press from being read when APPR mode was active - now it is only force disabled when GP/GS have been captured and those are the active vertical modes.

PFD

  • Added PITCH REF value to the FMA when in PTCH mode.
  • PFD Baro preset bug fixed where improper units would sometimes display with the baro preset window open.
  • Fixed bugs with selected altitude < 0 or > 45,000; these values will not display AND the simvar values will not exceed those limits (you can't get stuck below 0 anymore).
  • Removed inaccurate feature of resetting the FMA modes upon landing - they will now remain in the last selected modes until the FD is turned off.

MFD

  • Improved map/terrain mask (thanks Slip!).
  • Improved ROSE/ARC display to better reflect the real aircraft.
  • Improved min wind vector/speed display.
  • Fixed bug where DES waypoint would appear even after it had been passed sometimes on the map.
  • Improved gps track bug on MFD/PFD and enable during ground ops.
  • Added ability for FMS Text VNAV window to display climb data even when no descent/arrival is picked, and also to show arrival/TOD data after climb constraints have passed.
  • Fixed the Range Banana (altitude intercept arc) on the PFD/MFD to only display the point where the SELECTED altitude will be intercepted, not the VNAV altitude.

FMC

  • Added runway slope calculations to Takeoff and Landing Ref pages - you can now enter a slope and the relevant TOFL/LFL number will adjust accordingly.
  • Added landing factor distance selection on Approach Ref page - you can now select the landing factor.
  • Added ability to enter custom/new pax weight on PERF INIT page using format "/XXX" or "5/XXX" and the pax weight value is persistent.
  • Added ability to enter Gross Weight on PERF INIT page to override ZFW and/or Pax/Cargo inputs.
  • Fixed bug where the final approach fix calculation in LNAV sometimes chose the missed approach waypoint as the FAF.
  • Fixed bug that sometimes caused the departure runway to be undefined (black FMC screen) after flight plan import.
  • Adjusted DIRTO and Vertical Direct page and capabilities to fix bug not allowing a second vertical direct, not allowing a vertical direct to a current direct to waypoint.
  • Added ability to select any vertical waypoint with a constraint for a direct to; when constraints are A/B or A/ the altitude targeted will be the ABOVE value.
  • Fixed bug causing VREF/VAPP display error in FMC in certain circumstances.
  • Removed departure runway altitude from flight plan and LEGS page.
  • Added COM 1/2 CONTROL page. (thanks Slip!)
  • Added ADF Control Page. (thanks Slip!)
  • Changed behavior of LSK 1L to enable TUNE 1/2 page access while in the NAV 1/2 CONTROL menu. (thanks Slip!)
  • Enabled ATC CONTROL page from dispatch. (thanks Slip!)
  • Fixed formatting typos on ATC CONTROL page and TUNE 2/2. (thanks Slip!)

VNAV

  • Fixed bug that would prevent a climb in cases where there is no SID, but a STAR exists and has constraints.
  • Adjusted VNAV FMS Text window to display descent data as soon as the last departure constraint is passed, instead of waiting until the departure procedure has been completely flown.
  • Fixed bug with missing some A/B or A/ constraints in the first descent segment in some rare cases.
  • Changed behavior of path smoothing to cause the first descent segment to always be at the requested VPA in the VNAV DESCENT setup page.
  • Fixed bug with VNAV calculations after a DIR TO.
  • Adjusted behavior after FPLN change is made that adjusts the PATH; if the new PATH causes an out-of-activation range problem, AP mode changes to PTCH.
  • Fixed bug where after PATH arms in an ABOVE PATH intercept situation, PATH won't disarm even if you deviate from intercept parameters.
  • Extensive debugging and fixing of obscure/non-normal cases.

FLIGHT MODEL

  • Adjusted idle thrust.
  • Adjusted 75% thrust error in thrust table.

MODEL

  • Adjusted behavior of the panel light knob to replicate the function of the knob in the real aircraft - full on is DAY setting, and this is the ONLY setting to get daytime charts.

⚠️ 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 the new REPAINT_README.md file included in the docs folder of the Github repository.
  • 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 here
  • 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.

g3000-v0.5.1

29 Mar 15:20
Compare
Choose a tag to compare

Working Title G3000

Latest version: v0.5.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.5.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.1.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.3 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.

Release Highlights for v0.5.1

Fixes

  • [Compatibility] Fixed compatibility issue with darkfly's Longitude performance mod.
  • [PFD] The autopilot display will now correctly flash an autopilot disconnect warning when the autopilot is disconnected through means other than pressing the AP key.
    • For the TBM 930: the warning will flash indefinitely until it is acknowledged by pressing the AP/Trim disconnect switch on the control wheel.
    • For the Longitude: the warning will flash for 5 seconds, then stop.
  • [PFD] Fixed airspeed indicator behavior when IAS is below the minimum reportable speed (20 KIAS for the TBM930, 40 KIAS for the Longitude):
    • The IAS display shows "---" instead of the minimum speed.
    • The trend vector is hidden.
  • [PFD] For the Longitude: the autopilot display will now flash an autothrottle disconnect caution alert when the autothrottle is turned off.
  • [PFD] For the Longitude: fixed erroneous display in the navigation status display ETE field when ground speed is 0.
  • [PFD] For the Longitude: the airspeed indicator now always shows the reference speed (and bug).
  • [PFD] For the Longitude: 'NO WIND DATA' annunciation no longer overflows its container.
  • [GTC] The "Home" button in the Timers page now works properly.
  • [GTC] When in the Map Pointer Control page, pressing the bottom knob will now exit the page as intended.

Known Issues

  • [PFD] Citation Longitude: the standby altimeter baro knob does not function properly. The standby altimeter is now slaved to the PFD altimeter (so changing the PFD altimeter baro setting automatically changes the standby altimeter's as well).
  • [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] Traffic is temporarily disabled. This feature will be added back in a future release.
  • [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.

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.

g3000-v0.5.0

28 Mar 14:43
Compare
Choose a tag to compare

Working Title G3000

Latest version: v0.5.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.5.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.1.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.3 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.

Release Highlights for v0.5.0

  • Enabled measurement unit selection. You may now choose between different sets of measurement units in several categories, which affects how various on-screen values are displayed.
  • Overhauled the following PFD elements:
    • Autopilot Display
    • Airspeed Indicator
    • Altimeter
    • Radar Altimeter
    • Minimums Display
    • Wind Data Display
    • Angle of Attack Indicator
    • Navigation Status Bar
    • NAV/DME Information Bar
    • Bearing Information Bar

Fixes

  • [PFD] The "barber pole" speed strip on the airspeed indicator now appears at the correct speeds.
  • [PFD] Fixed a regression in v0.4.2/Sim Update 3 that caused the altimeter's baro setting display to not always display all four significant digits in "IN HG" mode.
  • [PFD] Fixed the scale of the Angle of Attack Indicator. Zero AoA is no longer in the middle of the scale. The top of the scale now theoretically represents the critical (stall) AoA, and zero on the scale represents the zero-lift AoA.
    • The scale for the TBM930 is based on the values found in the targetperformance.cfg file.
    • The scale for the Longitude is somewhat arbitrary since no references could be found, but should be at least in the ballpark of a "correct" scale based on empiric performance data gathered from within the sim.
    • The scale is not adjusted for differences in configuration (e.g. flaps) or mach speed.
  • [PFD] The "Auto" display mode for the PFD Angle of Attack Indicator in the G5000 now functions properly: when selected, the AoA indicator will be displayed if the landing gear are down or if flaps are set to any setting other than fully retracted.
  • [PFD] For the Longitude: The PFD altimeter is now synced with the same altimeter used by the autopilot (which is also synced to the standby altimeter). This will fix the issue of the autopilot appearing to hold at an altitude different from the selected altitude if the PFD and standby altimeter baro settings are not the same. This change has the side effect of rendering the standby altimeter baro knob unusable, since the standby altimeter is now slaved to the PFD altimeter.
  • [PFD] For the Longitude: the joystick above the PFD displays can now be used to increase/decrease the range of the PFD Inset Map.
  • [NavMap] The flight plan renderer now correctly draws the turning "transitions" into approaches which the sim's default autopilot flies when directly sequencing from the last leg before an approach into the first leg of the approach would result in a greater than 90-degree angle turn.
  • [GTC] The backspace button in the frequency entry pop-up window is no longer broken.
  • [GTC] Speed Bug settings are now properly synchronized across different touchscreen controllers.
  • [Misc] Loading/activating an ILS/LOC approach will automatically load the approach frequency into the nav radio. The exact behavior of this function depends on whether the G3000 or G5000 is being used, whether the selected autopilot/CDI nav source is FMS or NAV, and whether the approach frequency was already loaded into the nav radio.
  • [Misc] When flying an ILS/LOC approach, the selected autopilot/CDI nav source is FMS, and the approach frequency is loaded into the active frequency field of NAV1 or NAV2, the system will automatically switch the nav source to NAV1/NAV2 when the following conditions are first met: the next active waypoint is the FAF and the plane is within 15 NM of the FAF, OR the next active waypoint is past the FAF.
  • [Misc] Added the missing default reference Vspeeds for the Longitude. Note that these speeds are the published real-life values; performance in the sim may differ.

Known Issues

  • [Compatibility] Using this mod with the WorkingTitle GX mod may result in various flight planning bugs, such as blank waypoint entries in the GTC active flight plan page and avionics freeze when initiating a Direct To to an approach waypoint.
  • [PFD] Citation Longitude: the standby altimeter baro knob does not function properly. The standby altimeter is now slaved to the PFD altimeter (so changing the PFD altimeter baro setting automatically changes the standby altimeter's as well).
  • [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] Traffic is temporarily disabled. This feature will be added back in a future release.
  • [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...
Read more

cj4-v0.11.3

16 Mar 19:42
eaee441
Compare
Choose a tag to compare

Working Title CJ4 v0.11.3

Welcome to the Working Title CJ4 v0.11.3. Bug fixes! This release is all about working through some backlogged bug fixes.

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.

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.

Charts Integration

Charts in the CJ4 are powered by Navigraph - special thanks to the team at Navigraph for their support with API integration. In order to use the charts in the CJ4, you need to have a subscription that includes charts - https://navigraph.com/products/subscriptions. If you have a subscription, all you need to do is select the NAVIGRAPH line in MOD SETTINGS in the FMC and that will launch your web browser and ask you to log in to your Navigraph account - from there an access token will be issued. These tokens do time out from time-to-time, so if you're prompted by the aircraft, or if you ever encounter difficulties loading charts, please go back to this option and resync your account. Details on using the Charts capabilities are in the user guide.

Please note that occasionally the Navigraph token can time out; this especially happens if you do not exit the sim via the main menu. If that happens, please use MOD SETTINGS to refresh your Navigraph token and make a change to your flight plan, such as going DIRECT TO your current active waypoint - this will refresh the chart link.

Changes

  • Fixed bug with Pilot Waypoint storage that could cause errors for users adding waypoints to the data store for the first time
  • Fixed missing STAR transition legs when selecting a VFR runway for landing instead of a published approach
  • Fixed a bug with the autopilot update loop that could occasionally cause LNAV or VNAV to stop responding
  • Made adjustments to LNAV turn anticipation in certain turn types
  • Fixed bug that prevented the correct hold entry type from being updated when changing inbound course and turn direction
  • Fixed bug where AP dives to pre-select altitude when VNAV is disabled while in PATH mode
  • Fix behavior when a flight plan change causes PATH recalculation while in PATH mode - will now go to ALT and attempt to re-arm PATH

⚠️ Known Issues

  • PTCH mode will not level off at an altitude and it can have some quirky behaviors. This is currently a sim AP issue.
  • 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 the new REPAINT_README.md file included in the docs folder of the Github repository.
  • 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 here
  • 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.

cj4-v0.11.2

13 Mar 19:57
Compare
Choose a tag to compare

Working Title CJ4 v0.11.2 - HAS BEEN REPLACED BY v0.11.3

https://github.com/Working-Title-MSFS-Mods/fspackages/releases/tag/cj4-v0.11.3b

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.
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.

Charts Integration

Charts in the CJ4 are powered by Navigraph - special thanks to the team at Navigraph for their support with API integration. In order to use the charts in the CJ4, you need to have a subscription that includes charts - https://navigraph.com/products/subscriptions. If you have a subscription, all you need to do is select the NAVIGRAPH line in MOD SETTINGS in the FMC and that will launch your web browser and ask you to log in to your Navigraph account - from there an access token will be issued. These tokens do time out from time-to-time, so if you're prompted by the aircraft, or if you ever encounter difficulties loading charts, please go back to this option and resync your account. Details on using the Charts capabilities are in the user guide.

Please note that occasionally the Navigraph token can time out; this especially happens if you do not exit the sim via the main menu. If that happens, please use MOD SETTINGS to refresh your Navigraph token and make a change to your flight plan, such as going DIRECT TO your current active waypoint - this will refresh the chart link.

Changes

  • Implemented charts dark/night mode (activated when panel lights are off or at full [daytime mode] and are otherwise night mode)
  • Added ability to store up to 20 pilot waypoints (IDX->DATABASE)
  • Added ability to type pilot waypoint idents in LEGS, DIR and FPLN pages
  • Fixed Standby Attitude Indicator and Emergency Light Switches
  • Add Emergency Light CAS Message
  • Fix co-pilot audio panel
  • Fixes for TOD problems, including showing a TOD when in an approach and missing when in cruise
  • Fixed VNAV FPTA error that sometimes could cause LNAV to stop responding
  • Added CHECK SPEED message that will show when your speed is >20kts than the current restriction (remember speed constraints are not automatically loaded from nav data and must be manually entered)
  • Further enhancement of terrain colors for the TERR map option; adds curve points above and below aircraft based on aircraft AGL altitude.
  • Cleanup of some small FMC bugs, including missing Working... messages for some screens.
  • Improved duplicate detection methods when importing flight plans (fewer duplicates will flag)
  • Removed 'select waypoint' page being triggered during an import if there are no exact duplicates
  • Refined TOD rounding on MFD in VNAV WINDOW

⚠️ Known Issues

  • PTCH mode will not level off at an altitude and it can have some quirky behaviors. This is currently a sim AP issue.
  • 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 the new REPAINT_README.md file included in the docs folder of the Github repository.
  • 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 here
  • 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.

g3000-v0.4.2

10 Mar 00:30
Compare
Choose a tag to compare

Working Title G3000

Latest version: v0.4.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.4.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.1.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.3 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.

Release Highlights for v0.4.2

Now compatible with game patch 1.14.5.0 (Sim Update 3).

Fixes

  • [PFD] Fixed regression where PFD softkey functions related to changing inset map settings were not working as intended.

Known Issues

  • [Compatibility] Using this mod with the WorkingTitle GX mod may result in various flight planning bugs, such as blank waypoint entries in the GTC active flight plan page and avionics freeze when initiating a Direct To to an approach waypoint.
  • [PFD] (Vanilla issue) Co-pilot PFD softkeys are nonfunctional in the TBM 930.
  • [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.

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.

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 font (designed by Christian Robertson), licensed under Apache 2.0.
  • This mod uses the d3-array, d3-geo, and topojson libraries.

cj4-v0.11.1

10 Mar 18:29
da9c7de
Compare
Choose a tag to compare

Working Title CJ4 v0.11.1 - HAS BEEN REPLACED BY v0.11.3

https://github.com/Working-Title-MSFS-Mods/fspackages/releases/tag/cj4-v0.11.3b

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.

Charts Integration

Charts in the CJ4 are powered by Navigraph - special thanks to the team at Navigraph for their support with API integration. In order to use the charts in the CJ4, you need to have a subscription that includes charts - https://navigraph.com/products/subscriptions. If you have a subscription, all you need to do is select the NAVIGRAPH line in MOD SETTINGS in the FMC and that will launch your web browser and ask you to log in to your Navigraph account - from there an access token will be issued. These tokens do time out from time-to-time, so if you're prompted by the aircraft, or if you ever encouter difficulties loading charts, please go back to this option and resync your account. Details on using the Charts capabilities are in the user guide.

Here's a video demoing the Charts functionality: https://www.youtube.com/watch?v=bZNqV-aCzGk

User Guide

The User Guide has been updated: https://docs.google.com/document/d/1qzxPMTSQRkvau8QOi7xUqNvjx9rbww_qHlso5AT5OnI/

Changes

  • Fixed problem with FP SYNC option.
  • Addressed problems displaying VNAV TOD in certain circumstances.
  • Removed INOP tooltip from chart joystick.

⚠️ Known Issues

  • PTCH mode will not level off at an altitude and it can have some quirky behaviors. This is currently a sim AP issue.
  • 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 the new REPAINT_README.md file included in the docs folder of the Github repository.
  • Autopilot modes cannot be triggered via keybindings 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 here
  • 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 handflying the approach with the given lateral and vertical guidance.
  • The Standby Attitude Indicator switch is reversed in the model, so down (off) turns the SAI on and vice-versa; this will be addressed in a future update.