Working Title CJ4 0.8.3 - Open Beta - RNAV, LPV, VNAV, FADEC - v1.12.13.0 compat

Discussion Hub Aircraft
,
1

Working Title CJ4 v0.8.3 - OPEN BETA - added 1.12.13.0 compatibility + fix for dolphin dance

Welcome to the Working Title CJ4 v0.8.3 OPEN BETA.

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.

Remarks to flight plan synchronization between the Game and FMS

Our recommendation is to keep FP Sync off.
You can still ā€œfileā€ your flight plan to ATC by entering it in the world map of MSFS and it will remain visible to ATC/VFR.

To then load the plan into the FMS you can either enter it manually or use the FPLN RECALL (GAME/SB) option in IDX ā†’ PAGE2 ā†’ ROUTE MENU

Due to the increased accuracy and capabilities of the FMC managed flight plan, you may find that the sync to the game does not always work as expected or does not reflect the FMC flight plan.

KEY FEATURES

  • Added VFR runway approaches - in DEP/ARR you can now choose a VFR runway for landing and specify a runway extension waypoint to be added to the flight plan as far as 25nm from the runway. This allows you to ā€˜roll your ownā€™ LNAV/VNAV approach to any runway at any airport. Great for small/private fields! Microsoft Flight Simulator 2020.12.19 - 13.01.45.05
  • Fixed issue when resuming VNAV climbs and fixed issue when setting missed approach altitude during an RNAV approach with GP.
  • Adjustments to autopilot controller gains to address pitch oscillations

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.

Compatibility

  • Compatibility with MSFS 1.12.13.0
  • Removed old unused files that were causing a compatibility issue with WT Garmin units and the FBW A32NX

RNAV

  • Fixed an issue where GP would stop descending and capture an altitude when the altitude preselector was moved (i.e. to the missed approach altitude)
  • Fixed an issue where sometimes the active waypoint would sequence to the airport and take the plane off course on an RNAV approach.

MCP

  • Fixed an issue where the CRS would not accept input sometimes while not in LNV or NAV mode

PFD

  • Numerous fantastic cosmetic accuracy updates (contribution by TheFlieger)
  • FMS mach value now always shows only two digits
  • Updated BARO indications to show when STD has been set; updated BARO knob to always set STD pressure when pressed

MFD

  • Numerous fantastic cosmetic accuracy updates (contribution by TheFlieger)
  • Shows IGN indication on engine ignition during startup
  • Donā€™t show TOD marker on map when in Approach Mode

SAI

  • Fixed the baro setting rounding error

FMC

  • FPLN page will now properly accept airways following the departure fix
  • FMS will now continue to sequence even when the active nav source is not FMS
  • FMS will no longer sequence past the destination runway fix even if you fly beyond it
  • Fixed an issue where FPLN and LEGS would not show modifications unless the page was changed under certain conditions
  • FMC should now be able to continue to be used even on page error in most circumstances
  • LEGS page will no longer interpret entries of lower than FL500 as speed restrictions
  • LEGS order of AB restrictions should now be correct
  • FPLN now allows proper entry of 3 letter ICAO airport codes
  • FPLN selecting Origin or Destination will put the ICAO into the scratchpad
  • Visual approach (runway extension fix) capability added to the DEP/ARR page
  • Pressing LSK next to origin and dest will now copy ICAO to the scratchpad
  • FMC should no longer blackscreen when going to the ARR DATA page
  • FP Sync option will now actually be active when set to enabled
  • Added new option ā€œFPLN RECALL (GAME)ā€ to Route Menu to sync the flight plan from world map to the FMS

Flight Plan Manager & Import

  • Fixed an issue where game flight plans with blank ICAO legs would cause the plan to fail to load
  • Simbrief plans with 3 letter ICAO airports prefixed with K should now properly load
  • Fixed issue where some track-to-radial-intercept legs were being dropped from procedures
  • Changed behavior of FP Sync on flight start
  • When FP Sync is off: ATC/VFR plan remains but FMS plan is empty. Enter the flight plan manually or use the FPLN RECALL options

LNAV

  • Fixed issue where LNAV would get stuck in a swapping full left then right bank oscillation

Sound

  • Wind, Spoiler Drag and external engine sounds should now be played on the right audio bus so it doesnā€™t play during pause & volume can be adjusted.

Autopilot

  • Adjusted pitch PID gains to eliminate oscillation under certain conditions

:warning: Known Issues

  • Sync to the game flightplan (ATC/VFR Map) is very much work in progress and turned off by default. You can enable this feature in MOD SETTINGS on the FMC.
  • Some external applications that use the GPS/Flight plan SimVars may not function correctly or as expected.
  • 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.
  • TOD sometimes will flash on the PFD during an approach.
  • 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.
  • Sometimes when turning more than 90 degrees onto an approach segment, VNAV might give a NOPATH condition because it sees that you are too high. Engage FLC or VS and descend down and it should recapture the path.
  • Very long legs may display some constant cross track deviation on the map and course needles. The plane will still track properly towards the fix. This will be addressed later in the beta.
  • The FMS now builds turn anticipation into direct-to course projection. However, you will still encounter some overshoot beyond 90 or so degrees.
  • If for whatever reason, you find that VNAV is not behaving as expected, try and turn it off and on again.

:santa: Have fun! :santa:

45 Likes
2

Iā€™ve been waiting for this one! :heart_eyes: Canā€™t wait to try it out. Simply amazing work!

2 Likes
3

As i wrote on reddit: YES! IT IS OUT! I was following the progress since weeks on their discord. Also, new cool stuff is in beta for the G1000!

Guys this is a great great great job youā€™re doing. It is definitely an important feature of the entire game in my opinion.

4 Likes
4

This is fantastic news, especially since I just today decided I was going to give the CJ4 a shot, and Iā€™m a huge fan of the work you guys do in general.

This may be a dumb question, but is there any documentation like a POH, or checklists, or other things of that nature? I canā€™t program my way out of a wet paper bag, but Iā€™d be more than willing to collaborate with you to put out an instructional video or three, but in order to do so, Iā€™m gonna need at least some base line training materials so that I can learn to use it myself! But if that would be helpful, count me in as a potential volunteerā€¦

2 Likes
5

I am truly in awe of the talent this team has shown. To think that a few short months ago, we were all complaining about how poorly this aircraft was performing. Then, this team showed up and literally rewrote most of the code to make the CJ4 fly that would rival payware aircraft.

Thank you to everyone on this team for all the hard work, for all the improvements you brought to this popular biz jet and for making this sim a heck of a lot more enjoyable to play.

3 Likes
6

We welcome contributions and videos. There are a couple starter videos and a vnav document above, and more documentation is coming. There are also complete checklists available via the MFD.

1 Like
7

BRAV-freaking-O. You guys should get a bonus from MS/Asobo! lol

THANK YOU!!!

1 Like
8

Itā€™s works great when it works, but 2 CTD and overstressed plane while taxiing. Need serious work to get out of beta.

1 Like
9

would the VNAV fonction be easy to implement in other planes (like the g3000/g1000 works for different planes at once) or it wouldā€™ve to be added plane by plane ?

great job btw

10

These features will be making their way into the Garmin units over the next monthā€¦

7 Likes
11

Wow, so many awesome improvements! Iā€™m very excited, especially about the improved flight planning and new, more sophisticated autopilot.
Question: I just got some hardware for controlling the AP via SimConnect without having to use the mouse, so Iā€™m hoping support comes back for manipulating the AP via vars or keyboard shortcuts. Will yā€™all be able to get that working again, or is that an Asobo limitation you canā€™t work around?

12

Those donā€™t sound like aircraft code issues. Aircraft code canā€™t really cause a CTD the way the sim is structured. And we donā€™t have any control in the aircraft code over crash detection, taxiing behavior, or the like.

13

I just did a flight from Buffalo to Oshkosh and it is absolutely amazing great work

2 Likes
14

Doesnā€™t happen with .7 nor with any other plane. 100% 0.8 related so donā€™t dismiss it off hand.

15

I donā€™t think it was my intent to dismiss it, just explaining the scope of what the aircraft code has control over.

Can you provide a more detailed report or way we can reproduce the issue?

16

Just had a CTD - I donā€™t ever get CTDs and havenā€™t had them in previous versions of this mod.

EICK->EIDWā€¦ once about 2 seconds after take-off, once during climbā€¦ Not doing anything in particular at the time of CTDsā€¦ Just taking off during the first one. Messing around with cameras a little bit just before the second one, but it wasnā€™t triggered by any specific action, I donā€™t think. Iā€™d be happy to provide more details if you let me know what else you need.

17

Could this somehow be related to new sounds? And I didnā€™t even have VNAV enabled, soā€¦

18

Hard to say, weā€™ve been testing with a small group for a couple weeks and never encountered any CTDs, havenā€™t seen any reports from the folks on our discord server yet, but weā€™ve got these two reports now. It will be hard to trace if it isnā€™t repeatable, though ā€“ thatā€™s what sucks about CTDs, but this is also why we opened it up so we could find the bugs we havenā€™t found yet. As much detail as possible reported on GitHub would be greatly appreciated. Thanks!

19

Forgive my ignorance, but I am not too familiar with GitHub outside of downloading something from there, so any report would have to be here. But itā€™s basically two flights (same plan) that resulted in CTD. I then deleted the package and performed the flight with vanilla AC without any issues. So something definitely isnā€™t right, because I literally never get CTDs. Hard to say exactly whatā€™s causing it.

I am running a 10750 mobile processor with 16GB RAM (3200), RTX 2060 6 GB and a fast SSD. All of this running 1080p on Ultra everything. My mods are basically all WT packages, A320NX, and a bunch of payware scenery, bush trips, and payware aircraft.

1 Like
20

I have a question to the devs: were the game SDK recently updated to enable you to code the VNAV and other stuff? Are you in contact with Asobo? How your G1000 implementation will affect the Asobo one, since it is already scheduled that theyā€™re going to make an overhaul?