Real CL650 Pilot here with bugs/ request

[mtmurat]

The FMS and VNAV are superb. One thing I noticed (and I do this in the real plane), if one flies an ILS or RNAV with intent to circle, I like to build the visual approach to the intended runway of landing in a secondary flight plan. I switch to HDG/ ALT to begin the circle, then activate the SEC flight plan (visual), go Direct to the RX fix, then select Nav/VNAV, dial the Alt selector to zero, (adjust with VVS is above vertical profile) then the jet flies a picture perfect visual approach (one can assign speeds to the visual fixes also to let ARS handle that).

In Version 1.8, it will do this, BUT when activating it in this manner, VNAV does not work. The workaround is to build the Visual in the Active flight plan but don’t activate it until committed to circle- in this scenario it’s all there, VNAV and all. The benefit of doing it the first way is that the original approach then becomes Secondary and can be activated promptly in the event of needing the published Miss.

On the request front, can we start with the Altimeter in Baro?

I'm happy to answer real world CL650 questions or to beta test new versions. I have three copies on three machines- 2 Windows PCs and a M4 MacBook Pro.

I fly S/N 5911- technically a 60( but with the PL21 Advanced, HUD and triple IRS/FMS.

 

 

 

[skiselkov]

9 minutes ago, mtmurat said:

The FMS and VNAV are superb. One thing I noticed (and I do this in the real plane), if one flies an ILS or RNAV with intent to circle, I like to build the visual approach to the intended runway of landing in a secondary flight plan. I switch to HDG/ ALT to begin the circle, then activate the SEC flight plan (visual), go Direct to the RX fix, then select Nav/VNAV, dial the Alt selector to zero, (adjust with VVS is above vertical profile) then the jet flies a picture perfect visual approach (one can assign speeds to the visual fixes also to let ARS handle that).

Welcome. Let's work on refining the details here. The way you describe it, I don't see why it shouldn't work in the sim already, so there's probably some step you're doing that's missing. Let's build up a specific test case so I can analyze what's going on in detail:

• which airport
• what is the original STAR+approach+runway selection in the ACT FPLN
• what exactly do you have entered in SEC FPLN?
• exactly where do you switch to HDG/ALT and what are the heading & altitude you fly
• then the exact sequence of button presses or mode changes you do - when do you activate SEC FPLN, what changes do you perform to the activated flight plan?
• crucially - what exact sequence of button presses leads to VNAV not activating as you expect it to - what modes do you expect to see? What do you see instead?

Basically, I need an almost robotic sequence of steps, so I can repeat them on my machine and see the problematic behavior you're describing.

13 minutes ago, mtmurat said:

On the request front, can we start with the Altimeter in Baro?

Yeah, this has been on my pile of little things to fix for a while. I know the real avionics should default to inches of mercury rather than hPa, but I figured it's not a big deal for folks using persistent airframes (once changed with an airframe, it sticks).