Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/23/2024 in all areas

  1. Hi, I'm looking for a command to "press" the ALT button on the transponder (GNS-Version). DataRef came up blank, at least I didn't find a way to change the mode. I'm ok with a lua-solution. I also have a question regarding the GPSS-Roll-Steering Button (GPSS/HDG). Is it intended/realistic behaviour, that I can't change it and don't have an indication, unless I already have the AP active in HDG-mode? Lastly, GPSS behaviour: If you follow a flight plan and do a "direct-to", the GPSS turns even before your "accept" by pressing the "enter" button. Is that correct?
    1 point
  2. My sincere apologies for making any inference that you were not being proactive toward the development of the MU-2.
    1 point
  3. I know how you feel Mike....I felt a similar sting reading your comments on Toto's Discord a while back, insinuting a simple swap from your work to mine would "make eveything OK" and I was just too lazy to do it....and clearly my defensive posture resulted in a harsh turn of phrase above..which doesn't make it right. At the end of the day though, we get the customer support emails (a much larger contingent than is present on forums) and as such, I have a broader perspective of my customer base ...and enough experience in this market to know that your changes would result in making several customers happier, but also several more disappointed and I have to answer to those folks. I'm sorry if it stung a bit. What we're dealing with here is a "philosophy of development" given known limitations in 'modeling methodology'. For a good while I've watched us aircraft devs "put in the numbers" and complain to Austin when things don't perform right. But at the end of the day, these are just a big collection of numerical models and approximations, some better than others depending on lots of factors. So as aircraft devs with 'approximate models' in many places, we've always had to determine "which numbers to prioritize" given the state of X-Plane's flight/systems models. If, for example, you prioritize "accurate blade angles and engine parameters per handbooks" but the plane's performance is off in some regime because X-Plane's 'black box models' are off or too generic in places ....then you have to ask yourself, "can a user see the blade twist angles of the flight model? ..... or can a user more easily see the "off-nominal performance" and you make your decision about what to prioritize and compromise. If I said, "I'm putting in all the accurate numbers and will wait for X-Plane to 'come to me' and perform correctly before I release the product....well..you can imagine how that will go, so my philosophy is different. Numerical compromises and fudges are required for more balanced performance across the envelope in my experience. Indeed you have put in a crazy amount of accurate info into Plane-maker, and I do appreciate your work and it won't go to waste. It is not a simple swap and deploy because as you've noted, the X-Plane models aren't perfect so some numbers will have to change to accomodate the ground regime; however, your work is a wonderful springboard that I do respect and will simply have to look at parameter by parameter and gauge the effect against their impacts in a broader range of regimes. I hope I can strike a balance that satisfies enough. -tkyler
    1 point
×
×
  • Create New...