Is it maybe possible that the startup procedure is incorrect?
-
Thank you @Black-Square for your post, I understand your concern and think it speaks for you that you want to provide your customers with products that are effortless to configure and use.
That example you are linking is something that is seen all over the MSFS community and I think is inevitable. Increased complexity and realism will always increase the chance of people running into issues, your products are certainly not the only ones. But what is the alternative? Keep systems arcade-ish just so that no one will ever get stuck during setup? This is of course heavily exaggerated, but I think there's no need for you to shy away from complex stuff because of people running into issues. That's what the community is here for... and your FAQ, and your manuals, and YouTube, there's so many places where people can and will get help. And in the end, when it also works for those who had encountered issues, they will enjoy the increased realism just as much.It's the nature of the game with MSFS. If you want complex stuff on an open eco-system, then sometimes it takes a bit of effort to get things going. And remember, people complaining after not reading manuals or FAQs are ALWAYS just a loud minority.
-
@Black-Square Thanks for shedding some light on the complexity of the issue, I fully understand compromises had to be made. I am pleased you are feeling confident to implement more realistic startup procedures in future products, maybe even as updates to current ones that need it. Your already excellent products will get even better. Have a great weekend.
-
@Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket
Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code. Of course this spawned several hours of other code edits, adding more Lycoming behavior, and testing, but it was still easier than I expected.
This had the byproduct of allowing me to implement the delay between mixture cutoff and engine shutdown that many have been asking about for a long time.
It's surprisingly easy, so long as everyone is okay adopting the mixture control bindings of my turbocharged aircraft. (It works with the native bindings, so I'm not sure why people continue to struggle occasionally.) If they revolt, I will send them your way
Kidding, of course.EDIT: I cannot tell you how fun it is starting the engines this way that I am so familiar with from the real world
-
@Black-Square Wow Nick, this is absolutely incredible news!
I cannot thank you enough for diving into the code right away and making this happen.The fact that a simple shower thought solved the axis interception problem with just six lines of code is amazing! And getting the realistic engine shutdown delay as a bonus feature is a dream come true for all realism-minded pilots.I’m so glad you are having fun starting the Lycoming engine the proper way now. It’s going to be a massive improvement for the Commander 114 and it really shows why Black Square is top-tier. Bring on the angry hardware users, we’ve got your back! Thank you so much again for listening to us. I can't wait for the update! -
@Black-Square Fantastic news you figured it out so soon already! I hope you didn't leave the water running too long
Like I said earlier, it will make the Commander 114 even better and more immersive than it already is. Thank you for listening to our feedback, your support is much appreciated. -
@Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket
Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code. Of course this spawned several hours of other code edits, adding more Lycoming behavior, and testing, but it was still easier than I expected.
This had the byproduct of allowing me to implement the delay between mixture cutoff and engine shutdown that many have been asking about for a long time.
It's surprisingly easy, so long as everyone is okay adopting the mixture control bindings of my turbocharged aircraft. (It works with the native bindings, so I'm not sure why people continue to struggle occasionally.) If they revolt, I will send them your way
Kidding, of course.EDIT: I cannot tell you how fun it is starting the engines this way that I am so familiar with from the real world
@Black-Square said in Is it maybe possible that the startup procedure is incorrect?:
It's surprisingly easy, so long as everyone is okay adopting the mixture control bindings of my turbocharged aircraft. (It works with the native bindings, so I'm not sure why people continue to struggle occasionally.) If they revolt, I will send them your way
Kidding, of course.Nick, I should really know the answer considering I own just about every single one of your aircraft, but the native Mixture Axis/Mixture X Axis bindings map to the K events you need, yes? I don't think I've had any issues making use of them previously, but I haven't looked too closely at whether they're using K events or the A var you specifically say not to use.
-
@Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket
Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code. Of course this spawned several hours of other code edits, adding more Lycoming behavior, and testing, but it was still easier than I expected.
This had the byproduct of allowing me to implement the delay between mixture cutoff and engine shutdown that many have been asking about for a long time.
It's surprisingly easy, so long as everyone is okay adopting the mixture control bindings of my turbocharged aircraft. (It works with the native bindings, so I'm not sure why people continue to struggle occasionally.) If they revolt, I will send them your way
Kidding, of course.EDIT: I cannot tell you how fun it is starting the engines this way that I am so familiar with from the real world
@Black-Square That's awesome man!!! Looking forward to it!
-
@jasmits Sorry for the late reply to your question, i have talked with my Aircraft mechanic for you. You are actually 100% correct about the "why"! The Lycoming Bendix system is a continuous flow system, so it floods the engine immediately on "Rich" before the engine catches. Continental's system is engine-driven and RPM-dependent, which is why it doesn't flood during start. Spot on!
-
@Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket
Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code. Of course this spawned several hours of other code edits, adding more Lycoming behavior, and testing, but it was still easier than I expected.
This had the byproduct of allowing me to implement the delay between mixture cutoff and engine shutdown that many have been asking about for a long time.
It's surprisingly easy, so long as everyone is okay adopting the mixture control bindings of my turbocharged aircraft. (It works with the native bindings, so I'm not sure why people continue to struggle occasionally.) If they revolt, I will send them your way
Kidding, of course.EDIT: I cannot tell you how fun it is starting the engines this way that I am so familiar with from the real world
@Black-Square said in Is it maybe possible that the startup procedure is incorrect?:
@Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket
Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code.
Must be a special kind of water supplied to your place!
Thank you, well done sir, appreciate your efforts massively! I just went ahead and bought the Commander, even though I'm still waiting for that Virpil yoke that seems to take forever to arrive on the market
