Caravan Professional

See this post and please follow the test mentioned in the post. https://community.justflight.com/topic/10241/fs-2024-vanilla-turbine-failure-with-no-blacksquare-failure/11

Thank you for the video. That's always so helpful. Indeed, it appears that the native autopilot will use the rudder regardless of the yaw damper settings. I should be able to just zero out the PID constants to eliminate it, but I will have to try it and make sure there are no adverse effects. Thanks for letting me know!

@C525B thanks for the recommendation on the ram air vents. i had made that discovery early on when messing around with stuff in the cockpit. i didn't make any changes to the audio i uploaded. i wouldn't even know how to go about doing that. i had included the other samples more for me to hear them side by side and less about, "this is what i think this plane should sound like". i wasn't clear about that intent. and I only used a very small handful of ftsim's sounds as i felt they missed more times than they hit as well. the engine sounds for me are much less about prop noise and more about the overall depth of the sound. this soundscape lacks the bassy resonance you hear with any gas powered engine. to me it sounds like a desk fan and takes away from an otherwise enjoyable experience in a plane i've always enjoyed flying in the sim. like i said, i have no experience in a plane with a pt-6 let alone the caravan and i know sounds are subjective but i am disappointed with how thin they sound (along with a couple of other particulars that i've mentioned prior). anyhow, looks like i am part of a very small minority of people who don't love the sounds so i'll just drop it. thanks again for the recommendation.

It's a stroboscopic effect. This comes up with just about every one of my aircraft, so it's not just you

@Black-Square said in Bankrupt: @slod That would be great. I sure hope that's the real world behavior, because trying to circumvent that behavior would open a can of worms. And here I thought I was slow to this one... I took at least a few hours off after the release just working on Twin Commander minutiae to clear my head. Hi Nick, thinking about it , when you first engage the autopilot you have the manually press the 'arm' button, so using your 200ft example you'd probably blow through your selected altitude if you weren't really quick! One quirk of the unit is that when in 'alt hold' if you select a new altitude and enter 'vs' mode the unit automatically 'arms'. I'm not sure if that happens when selecting a new altitude or when entering 'vs' mode but I'll check next time for the fun of it. You're proposed work around is more than enough though! You can see why anyone with enough cash goes for a digital autopilot! Cheers

It's been happening midflight. Just did some testing on the ground to clarify what's going on, what's actually happening is the engine controls are momentarily going to zero and back again when i connect a device (in this case my headset to charge). Considering it happened when I was testing it on another aircraft too, It looks like it may actually be a bug in the sim rather than with the addon. My apologies

Looking at the code, the only thing that could cause that behavior in the Caravan is if either the Elevator Trim, or Autopilot Actuators circuit breakers are pulled. Any hardware that is possibly assigning these electrical circuits might interfere, but it's unlikely this would happen without you knowing what you assigned in 3rd party binding software. This would also be possible with the Analog Caravan, and it's also possible that any circuit breaker failures have carried over to the Caravan Professional, since I used the same namespace for the failures. Other than that, I would be left suspecting something on the hardware level, since I haven't received any reports of this before. I am happy to help here, but it might also be worth contacting Just Flight support, as they deal with many aircraft, not just mine, and may have seen this behavior before. Sorry that you've been dealing with this since the Analog Caravan! Hopefully we can get it fixed for you quickly!

@RISCfuture Perhaps the Caravan specifics in this thread might interest you.

@NixonRedgrave That's what I'm here for I'm glad to hear you're enjoying them, and please let me know if you ever have any other questions. You know where to find me!

@Tadeus72 said in Where is the wear?: although a failure is going over to the next flights if you don't fix it. That's a good point, too. You could not repair the aircraft until every system has failed, which be quite an entertaining challenge to see how far you could get. @steveonatorer said in Where is the wear?: Just sad to see it being advertised as such. The quoted sentence has a specific meaning, its not about being stated unclearly. I understand how you interpreted that sentence, but the meaning was that failures of each type are possible, rather than all failures being capable of all types. I sometimes find it difficult to fit descriptions of all the features in my aircraft into my advertising, especially when various marketplaces impose character limits. Although it's not what we're talking about here, the MSFS Marketplace administrators have actually re-written my descriptions, often choosing words and phrases that I would never use! Sorry you feel like the description was not adequate. When system descriptions in my manuals have been confusing in the past, I always ask my users how they would rewrite them for clarity, so please feel free to share your thoughts.

You sir are amazing. Look forward to V1.1

Oh, I forgot there was another post related to this. Here is what I posted elsewhere after some work last night: This turned out to be a little more work than I was expecting, but I've fixed it, and improved the climate control system after a consult with one of my Caravan pilots too. As usual, thanks for the little nudge in the right direction to improve my aircraft

@MiRexer wow, do I feel silly not looking over my shoulder at the seating.

@qqwertzde said in state.cfg settings: the covers are now in place, but the chocks are still missing. This has been discussed numerous other times, unfortunately. The aircraft loading sequence in MSFS 2024 is terribly confused, with the aircraft being thrown up and down while the terrain is loading, while temperatures and wind are loaded from the camera position in low earth orbit. This means that aircraft is still moving so much when it's loaded that the chocks are automatically disengaged. I haven't found a fix for this yet, because I was hoping that Asobo would fix some of these significant regressions from MSFS 2020, but it seems like that's becoming very unlikely.

Just wanted to let you guys know that I was working on this last night. Here is the post from another thread: I think I was able to arrive at the optimal solution with only some small edits to the code. I also improved some other small things in the KAP140 while I was there. The only thing I'm not sure about relates to the behavior of the real world unit. If you engage the autopilot when you are already within 200ft of your selected altitude, the vertical speed will be zero, and it will capture the selected altitude. All things considered, this is a very small tradeoff in my eyes, compared to what is sometimes required to circumvent the native autopilot. It's always amazing when you implement some of these small things, and you can immediately feel how much more intuitive they are. Thanks, guys! An addendum for this thread: The capability to display "PIT" mode still resides in the KAP 140, but you should not see it during normal operation. I've left it there more as a debugging tool, since errant autopilot modes are my best tool for diagnosing GPS addon issues.

@Ratman This turned out to be a little more work than I was expecting, but I've fixed it, and improved the climate control system after a consult with one of my Caravan pilots too. As usual, thanks for the little nudge in the right direction to improve my aircraft

Ah, thanks for letting me know. There is a flag I remember somewhere like, "DO_NOT_APPEND_UNIT_ID", which might be responsible. I'll double check later.

@Black-Square said in Avionics selection, can it be made sticky?: This is just related to the currently bugged state saving, I believe. There are ways to set it permanently, if you really want, and I can figure out a solution for you. You can scratch this off your to-do list.. I did not realize that I had to select this for each variant separately.. Seems to be working now!

https://community.justflight.com/topic/10189/no-internal-sounds/20