Working Title CJ4 v0.10.1
Welcome to the Working Title CJ4 v0.10.1. This hotfix is for pressing issues we did not catch during our QA.
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.
Default Livery Conflicts
The alternate default liveries that now ship with MSFS are not compatible with the CJ4 yet at this time. They currently ship with panel.cfg files that do not include our FADEC module. Please use the standard livery or a known compatible 3rd party or community livery.
- Correct missed lift adjustment in FM leading to incorrect stall speeds
- PFD should no longer allow any preset but NAV1 when nav-to-nav is armed and the active nav source is FMS
- PFD should automatically set the preset nav source to NAV1 when nav-to-nav-is armed
- Corrected stuck CHECK LOC TUNING scenarios where addon navdata is incorrect
- Change navaid datablock to “LOC” from “ILS”
- Fix VNAV not leveling off at constraints during a climb
- Alt alert cancel on ALT knob push
- VNAV Setup page should no longer display CRZALTCELL
- Fixed issue where VNAV state would become corrupted when capturing a preselected altitude while in VPATH.
⚠️ Known Issues
- PITCH 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. You must uninstall them or remove their panel.cfg from the livery folder. This is a limitation of the Asobo livery system.
- 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 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 handflying the approach with the given lateral and vertical guidance.
- If for whatever reason, you find that VNAV is not behaving as expected, try and turn it off and on again.