18 hours ago, Zangoose said:

I had a similar issue but I found out it was because I had an old version of the TDS GTN installed which caused this issue. Updated it and it all worked as normal again. Not sure if you have any similar addons installed.

 

18 hours ago, vgbaron said:

That was it!   Thanx for the heads up.  🙂 

I’m confused, why are you all using this with the Kodiak? It comes with G1000 NXi integration. Why are you using the GTN750? I don’t even see that listed on the TDS website as an aircraft it is integrated with?

15 minutes ago, B777ER said:

 

I’m confused, why are you all using this with the Kodiak? It comes with G1000 NXi integration. Why are you using the GTN750? I don’t even see that listed on the TDS website as an aircraft it is integrated with?

We aren't using the TDS with the Kodiak - Simply having one of the older versions of the TDS GTN that had the bug caused a confliction with the G1000NXI so regardless of the plane that uses the G1000NXI, it would cause the issue with the autopilot.

TDS fixed it with an update and if you then updated that the confliction with the G1000NXI was resolved. 

Edited October 26, 20223 yr by Zangoose

I keep seeing new posts and thinking it's a NEW update. Doh!

 

And no, I don't have a lot to do. ...😁

Edited October 26, 20223 yr by Ron Attwood

40 minutes ago, Zangoose said:

We aren't using the TDS with the Kodiak - Simply having one of the older versions of the TDS GTN that had the bug caused a confliction with the G1000NXI so regardless of the plane that uses the G1000NXI, it would cause the issue with the autopilot.

TDS fixed it with an update and if you then updated that the confliction with the G1000NXI was resolved. 

Ahh, gotcha. Thanks

I get no nosedive if I disengage autopilot before full flaps, just as before, so they haven't fixed that issue.

7 minutes ago, Ixoye said:

I get no nosedive if I disengage autopilot before full flaps, just as before, so they haven't fixed that issue.

I do get a nose dive every time I disconnect the AP... since I bought it!

I once asked about it on their Discord and they all acted like I'm the only one experiencing that and like they don't have a clue what I'm talking about. It left a sour taste in my mouth, otherwise it's a great plane but with an obvious bug not many developers could go away with. 

5 hours ago, Tomaz Drnovsek said:

I do get a nose dive every time I disconnect the AP... since I bought it!

I once asked about it on their Discord and they all acted like I'm the only one experiencing that and like they don't have a clue what I'm talking about. It left a sour taste in my mouth, otherwise it's a great plane but with an obvious bug not many developers could go away with. 

I think they've finally acknowledged it on the official forums but they didn't say when a fix can be expected.

They are an odd organization that seems to praise themselves for their attention to detail and reality, even having real Kodiak test pilots on the program, yet this last release had a number of issues that were immediately noticed by everyone, making you wonder what kind of testing they actually do.

Edited October 27, 20223 yr by Virtual-Chris

5 hours ago, Ixoye said:

I get no nosedive if I disengage autopilot before full flaps, just as before, so they haven't fixed that issue.

How can you not get a nosedive, when everyone else gets it??

 

40 minutes ago, Bobsk8 said:

How can you not get a nosedive, when everyone else gets it??

 

By disengage autopilot before engaging full flaps.

5 hours ago, Virtual-Chris said:

They are an odd organization that seems to praise themselves for their attention to detail and reality, even having real Kodiak test pilots on the program, yet this last release had a number of issues that were immediately noticed by everyone, making you wonder what kind of testing they actually do.

Don't know what to think wrt the Kodiak test pilots. It is hard for me to believe the test pilots where happy with the pitch sensitivity. Even after running the pitch axis through FSUIPC7 and the MSFS sensitivity settings, the pitch is still to twitchy. A retired pilot friend who flew C421s, King Airs and B727s among others, says the pitch axis is just not realistic in his judgement.  Really spoils the fun of flying the Kodiak for me. Sure which they would fix it.

And sure wish I could talk to the Missionary Bush Pilot for a few minutes!   😀

Al

Edited October 27, 20223 yr by ark

Makes me wonder why this isn't fixed yet, given that this issue was pointed pretty much from the beginning. 

1 hour ago, Ricardo41 said:

Makes me wonder why this isn't fixed yet, given that this issue was pointed pretty much from the beginning. 

I had the same thought, I have parked it in the hangar again waiting for the next update.

Edited October 27, 20223 yr by Ixoye

10 hours ago, Ixoye said:

By disengage autopilot before engaging full flaps.

I  usually disengage AP at 500 feet agl, you can't wait to put flaps down, until you get lower than 500 feet, that would be an unstablized approach. 

Hello gents,

To clarify some frequently asked questions:

-Nose drop with AP off. There is a bug with flap autotrim that brought this back to life. It seems fixed but will take some testing to ensure it does not rise again. We are also re-tuning flaps so this will take some time to get out.

-Speed burn on approach and idle power: Sorry to say that, but I have grown tired of explaining this one. On idle, as soon as the prop hits 11.4 degrees, the drag is immense. This was adjusted using airspeed figures from a Kodiak pilot who provided them. Before that, a Porter pilot was also telling me that there wasnt enough drag and you could notice that on a steep approach it was impossible to slow down below 70-75kts until April 2022, when we adjusted it as it is today.

It was also hard for me to believe until I rode an ATR and noticed that on the flare I could tell when the pilots idled the engines by the noise and me feeling like I hit a brick wall.

Now, when does it hit idle pitch? If your engine is underspeeding (below 1900rpm Np), when you idle the prop will go to 11.4 in a few moments. At that point you will notice the airspeed burning off quickly.

We are working on this but it is quite a bit of work and flight testing and we don't feel like issuing another hotfix after a patch is the right course of action.

Now to answer to a comment by VirtualChrisM, who pretty much described us like a weird cult and -to my biased eyes- seems to have the Kodiak in his sights here and on the MSFS forum: it is an adequate description, but not for the reasons you have in mind. First of all, when we do something we dig into it and we want to have a reason to be proud of the product.

Trust for bug reporting goes like this for us: Type rated pilots>data & POH>Pilots>Testers>Customers. A task created by a report must be Specific, Measurable, Attainable, have someone Responsible to do it and be Time-bound. S.M.A.R.T.

The customers will catch glaring errors that devs and testers who have tunnel vision -by definition- cannot see. They also provide us with countless cases of RTFM or people who have problems unrelated to how the plane works to sift through and few will be specific to a problem, even rarer to get data. Many use MBP videos as reference, but who can tell us if the trim rogging on his plane is out of whack? We had this dilemma before the initial release and solved it. A random person actually said it jokingly over at MSFS forum and I explained how we were able to work around the problem, simply because we were lucky to have hard data and the factory behind us. One can see why there is a lot of "noise" in customer feedback and it is always taken with a pinch of salt.

To move a report up the trust chain someone needs to provide data, expertise or something unique.

Examples of non-pilots who helped us?

>Some customers offered to test our hotfix code with their TCA throttle, as we didn't have a tester with one on the team. This helped us fix the throttle problem in a day, which would otherwise take 1-2 weeks.

>Another customer provided a video timestamp from MBP where we could analyse the OAT, altitude and engine settings and see what's up. No, we can't see all his videos or even one full video whenever one sends it. We have seen quite a few but there aren't enough hours in the day and at some point we need to produce.

So, we are definitely a group of nerds -a cult one might say- and far from perfect. But there is method to the madness and we are happy to accept contributions through our own venues and using hard evidence. Non-constructive criticism is worth less than no criticism.

Edited October 27, 20223 yr by A320_SX ALX
Grammatical correction.

On 10/26/2022 at 1:58 PM, Ixoye said:

It still drops the nose heavily when AP is disengaged for me, and below 90 Kias full flaps it fall like a stone on final and it's very twitchy to control, it's not fun to fly at all.

Don't use full flaps. You can land the KODI even with "lower" flaps very effecient. Even Kodiak pilots are not always using full flaps. 

And I'm not even sure if this is related to KODI only. The Aerosoft Twin Otter also behaves like this if you put flaps on 37. And also there landing with 20 and 30 is possible without issues even on short runways.