7 hours ago, DJJose said:

The key is your approach speed. If you are too slow you will not be able to flare properly.

I use blue line with full flaps all the way to the numbers, I cut the power and raise the nose and touch down on the mains.

Easy does it!

That's why I do (and posted): I stay at the blue line almost up to touchdown.

6 hours ago, MrBitstFlyer said:

Keep the power in on approach.  At the same time you start pulling the nose up to flare, slowly reduce the power.  You don't need to be at blue line all the way to the runway.  Just reduce the power to achieve landing speed but don't go to idle.

The tendency to bank on landing suggests you are too fast at touchdown.

Yes, it does feel like I am going too fast but... I just watched this video...

2 hours ago, Bobsk8 said:

Real 310 Pilot flies Milviz 310R.

...and this real world C310 pilot stays on the blue line and only cuts throttle a little JUST before touchdown: his speed is around 100 at that moment. When I do that, I can't keep in centered on the runway. Well, maybe it just takes practice.

45 minutes ago, Bert Pieke said:

Good find indeed, but after applying the changes, with target altitude set, trimmed in climb, engaging the AP starts up with ROL / VS / 0 fpm.  Does it capture current pitch for anyone?

Hi Bert,

Having tested more, I think you're right, the AP is still engaging with a VS of 0, which results in a nose down to level (not correct).

I wonder if Milviz are using some custom code here, as the default MSFS code should hold current pitch, with a DEFAULT_PITCH_MODE value of 1.

I have found a workaround but it's not ideal and will only work if you use keyboard commands for AP:   I've set the same key that I use to engage the AP to also engage the MSFS command "Flight Director Pitch Sync".     Eg. I use the key 'X' to engage my AP, so that is now double binded to both AP ENGAGE and FLIGHT DIRECTOR PITCH SYNC.   Now, when I engage the AP, it does indeed hold the current pitch.

 

Edited May 7, 20224 yr by JYW

28 minutes ago, tup61 said:

2 hours ago, Bobsk8 said:

Real 310 Pilot flies Milviz 310R.

...and this real world C310 pilot stays on the blue line and only cuts throttle a little JUST before touchdown: his speed is around 100 at that moment. When I do that, I can't keep in centered on the runway. Well, maybe it just takes practice.

If you reduce power and flare at the same time your speed will reduce for the touchdown and you'll find the rollout will be better.  Stall speed is around 72knots so all you want to avoid is chopping the throttle, just come back gently on the throttle as you flare.

I'd recommend using this excellent KAP140 mod: GitHub - FS2020-USER-TESTER/KAP140-MOD-PACKAGE

28 minutes ago, Ohmsquare said:

I'd recommend using this excellent KAP140 mod: GitHub - FS2020-USER-TESTER/KAP140-MOD-PACKAGE

Have you had a chance to test with the c310?

2 hours ago, JYW said:

Hi Bert,

Having tested more, I think you're right, the AP is still engaging with a VS of 0, which results in a nose down to level (not correct).

I wonder if Milviz are using some custom code here, as the default MSFS code should hold current pitch, with a DEFAULT_PITCH_MODE value of 1.

I have found a workaround but it's not ideal and will only work if you use keyboard commands for AP:   I've set the same key that I use to engage the AP to also engage the MSFS command "Flight Director Pitch Sync".     Eg. I use the key 'X' to engage my AP, so that is now double binded to both AP ENGAGE and FLIGHT DIRECTOR PITCH SYNC.   Now, when I engage the AP, it does indeed hold the current pitch.

 

I kept a back up copy of the file just in case. We need to test the mod.

1 hour ago, MrBitstFlyer said:

If you reduce power and flare at the same time your speed will reduce for the touchdown and you'll find the rollout will be better.  Stall speed is around 72knots so all you want to avoid is chopping the throttle, just come back gently on the throttle as you flare.

I agree, however it depends on the length of the runway. For short field approaches, YES. For normal approaches, I can maintain blue line all the way to the numbers and still touch down gently on the mains with plenty of room to spare. Obviously, in the real world, that's why a checkout is required and many hours of experience for insurance to cover you.

37 minutes ago, Ohmsquare said:

I'd recommend using this excellent KAP140 mod: GitHub - FS2020-USER-TESTER/KAP140-MOD-PACKAGE

Interesting, I was about to code an autopilot helper for this plane.. lets see how well this works..

Just now, Bert Pieke said:

Interesting, I was about to code an autopilot helper for this plane.. lets see how well this works..

Let us know if you like it. 😀

22 minutes ago, DJJose said:

Have you had a chance to test with the c310?

Not thoroughly but so far I haven't noticed any issues with the C310 and it seems to work as advertised. 

4 minutes ago, Ohmsquare said:

Not thoroughly but so far I haven't noticed any issues with the C310 and it seems to work as advertised. 

Awesome! Looking forward to checking this out and thanks again for the link.

1 hour ago, Ohmsquare said:

Not thoroughly but so far I haven't noticed any issues with the C310 and it seems to work as advertised. 

Just installed it and my problems with the autopilot have disappeared.. highly recommended!

5 hours ago, JYW said:

I have found a workaround but it's not ideal and will only work if you use keyboard commands for AP:   I've set the same key that I use to engage the AP to also engage the MSFS command "Flight Director Pitch Sync".     Eg. I use the key 'X' to engage my AP, so that is now double binded to both AP ENGAGE and FLIGHT DIRECTOR PITCH SYNC.   Now, when I engage the AP, it does indeed hold the current pitch.

I tried that, and it does not work reliably for me.. however, the above mod does..  😉

Can I bind my AP controls in the 310 to my Bravo? 

Im using Axis and Ohs but I cannot find a script for it anywhere. 

36 minutes ago, Bert Pieke said:

I tried that, and it does not work reliably for me.. however, the above mod does..  😉

 

Dumb question...purchased this plane last night and love it so far despite the high speed 100 knot abrupt landings.  (This model version rolled out in 75’ and so did I!)

But my retractable landing lights while casting light don’t look nice and bright white on the lights/lenses like the Chancellor or 146 or others??

I also had a heck of a time getting my autopilot to even turn on and activate but traced the issue to my Shift Z mod...hit shift Z a few times and bingo a working autopilot.