I did try the exact same procedure as shown in the video on the WT CJ4, with the same unfortunate results. I also did mention that in the video. 

6 minutes ago, Andreas Stangenes said:

I did try the exact same procedure as shown in the video on the WT CJ4, with the same unfortunate results. I also did mention that in the video. 

Interesting sorry I must have missed that!

 

You should post it in their discord server you will get a quicker response there.

 

https://discord.gg/Fa6w2xK

5 hours ago, Andreas Stangenes said:

I did try the exact same procedure as shown in the video on the WT CJ4, with the same unfortunate results. I also did mention that in the video.

I'm not totally sure why you weren't able to get this to work in our CJ4. The raw sim navdata (which is what we read from for our custom flight plan manager) has these fixes in the procedure description. This is what I get punching up that arrival:

As I've mentioned in prior posts, the stock sim NavBlue data is actually really good, it's just that the in-sim flight plan system doesn't load every leg type. But we don't have any such limitation, since we use our own.

-Matt

6 hours ago, fppilot said:

How does it work?  Is it merely manually entering the flight plan into the mod units in MSFS?  Or can a flight plan be imported into it?  And does it work with each of their mods?  The web search I just completed seemed to refer to the just to the CJ.

Our flight plan manager is a rewrite of the MSFS default flight plan manager, which is a utility that sits behind the instrumentation in the aircraft code that interprets flight plan data, provides for drawing the map, navigation guidance, etc.

It is modular to some extent and can be deployed in other aircraft. We intend to migrate it into the Garmin units and the FBW team is incorporating, with appropriate modifications, it into their project as well.

It uses the in-sim navigation database, whether default NavBlue or add-on Navigraph, but it manages the plan differently to better allow for more procedure types, transitions, etc. This is how we've been able to add things like holding procedures, vector legs, flight plan discontinuities, enroute and runway transitions, custom waypoints, etc into the CJ4 FMS - and how we will add missed approach procedures sometime "soon".

The FMC provides users the option to load a game flight plan built in the world map, to directly import an OFP from simbrief or to manually program the FMC. There is also an option to 'sync' the plan from the FMS back to the game, so as you modify your plan, in-game ATC can keep up with the changes. This doesn't work perfectly since we have more legs and procedure types than the game ATC knows/about understands, so it's more oriented towards those that use Vatsim, IVAO or Pilotedge, but we felt it was important to support the in-sim ATC engine as much as possible.

21 minutes ago, cwburnett said:

We intend to migrate it into the Garmin units and the FBW team is incorporating, with appropriate modifications, it into their project as well.

Will wait patiently as this sounds great!  I am immersed totally in GA multi-engine prop and turbo prop,  I am currently doing most of my schedule in FSX SE with RXP, VATSIM, and AS16 until refinements arrive for MSFS.

@MattNischan thank you for your reply. I will try again in the cj4. It is not the airplane I am most accustomed to, so I will not exclude user error 🙂 I will report back. 

Update: I dont know why it wasnt working earlier, but I did in fact get it to work properly now! Thank you so much for solving this huge issue, Matt and the rest of the CJ4 team 🙂 

Edited January 8, 20215 yr by Andreas Stangenes