XST

That makes total sense. Just wondering because I use the TBM a lot. Thanks!

Hi, I tried this plane in XP 12 and it just CTD. Are there any plans for an update soon? Thanks!

Same here... Fresh install in XP 12 Folder and a quick test... it seems to work normally, of course a deep test and longer fly needs to be done to check all the functionality, but so far so good. Happy to have extra aircraft to the default ones in XP 12!!! Very good job thanks!

Any one tried to install this aircraft on XP 12? Works? Any expected update for XP 12 soon? Thanks!

This is four or five beers or a dinner for two in a not-very-expensive restaurant. Two hours of joy. Instead I buy this plane and the joy last for another 10+ years. Expensive? I think is cheap, very cheap!

The first test with this second update was simply great. I couldn't go through the whole list of previous bugs but I did the most important ones and everything works well and smooth. So far so good. Very good job!!!

@Ch.Cole ok, understand, thank you!... I will play a bit more with it after the new update then... so far I stay with legacy.

@Ch.Cole I use legacy one, but I tried the modern method and I had the same issue. I think the problem is that the plane 3D cockpit lever stops correctly to prevent to enter accidentally in beta range, but you may continue moving your joystick throttle lever... so when you click (execute) the lift command, the plane lever goes to where your joystick lever is... so if you accidentally moved it to the lower position then plane goes to full reverse. In other words, prevents accidentally beta ranges but then you have to pay attention to your joystick lever position or it goes full reverse... so one way or the other the "accidentally" option is there... honestly I don't see the advantage of this method unless you have a joystick lever with a physical lever stop, so then you don't need this method either. Of course, maybe I was using it a wrong way too.... so I decided to go old school legacy.

Enjoy your trip... that is important too! Thanks!

Same here... happy to help and looking forward to have this great aircraft working well... this is totally normal in new developments and the developer doing great both technically and communicating. This is how great things are done. Congrats!

Since an image is worth a thousand words, let me add some images to show what I'm experiencing: 1. Flight idle position on ground keeps torque somewhere between 38-40%... It doesn't go lower. 2. Pressing beta toggle in that position torque goes to 30%... it is OK... but there is no range to handle a torque between 31 %to 37%. Its like a dead zone. 3. Throttle lever all the way up test... no words.... 4. Since min torque in flight range is 38-40%... I pressed beta range to go lower... not trying to do inflight reverse... just trying to lower the 40%... then it goes to 0%... same action on ground goes to 30% but on air it goes straight to 0%. Lever is in the beta limit not in the reverse range... Summary: 1. Full throttle is very overpowered. 2. No way to go lower than 38% torque on flight range unless pressing beta... then dead zone in 31%-37%, this happens only on ground. 3. If beta button is pressed on air (inflight) to go lower than 38% torque... it goes straight to 0%... this doesn't happen on ground. Don't hesitate to ask for any clarification if needed. This aircraft is going to be great... just a bit of tuning to be done. Thank you!!!

Just observations, not sure if this is right or wrong, using in legacy throttle mode: 1. In flight range, throttle never goes under 40% in lower position and in higher position goes all the way up till Torque % label... 150/160%? is this right? 2. All the way down to 40% again, when sim/engines/reverse_toggle pressed, it sometimes starts under 40% so beta can be handled from 39% torque to 0 with the throttle lever. But sometimes it goes to 0 directly and no way to go through the beta range.... not found a rule or reason of why this sometimes happen. I'm not sure but in previous version torque was much lower than 40% just in the limit of the flight to beta range... and not that overpowered in the top high throttle position. Just observations, I'm not a real pilot so maybe above way is the right way to work. Thank you for such an amazing progress!

I did flight again after re-staring XP and suddenly worked again ... I will pay attention to the GNS mode just in case. Thank you

Hi, I tried ILS approach in a couple of airports and did not work. GS never captured. I tried the same airports with other planes and worked. Anyone having similar problems?

Update: sim/flightmodel2/wing/flap1_deg[0] dataref Works and gives the right information I want to show, it seems to work well in all other planes. So I think is better to change this on my side. We can consider this problem solved. Thank you very much for all of your help.

I always think that the best way to go is to stay with what the real plane does... to keep it realistic. Even if that is bothering or slow for us as simmers. Do we know which is the increment in the real plane? I could not find it. Editing the .obj file is always an option for those willing to speed it up. Also, there are some free FWL scripts or tools to manually type the bug value... that is always a shortcut for simmers without breaking the integrity of the aircraft realism. Just my two cents opinion... of course.

Tom, thank you very much for your post! I'm also a developer (instrument trainers) and home cockpit builder. I mainly focused on glass cockpits but also gauge ones. We both are on the same side. I 100% understand that you have urgent matters and priorities so, as a developer, I will never ask you to jump into minor things like this one unless you see an easy way to solve it. Let me check alternatives on my side first and I will let you know shortly what the results and options are... I may have alternatives to sim/cockpit2/controls/flap_ratio that may work now and if so, there is no reason to bother you on this. I first asked this because it was working in v1 of this aircraft but fully understand that you had to override this for a realistic behavior. Will get back on this as soon as I explore some alternative ways and I'm pretty sure we will get to a good solution. Thank you very much for such a great work on this plane.

Good! I will remove curve settings on next update. Thank you!

I understand that sometimes aircraft developers needs to use custom datarefs for specific or complex functions for a particular plane. Autopilots win on this. But I still don't get why standard datarefs are not used for regular easy normal functions and controls. For example, brakes, flaps, trims, landing gear, and so on... simple standards that doesn't change from one plane to another. This problem only affects to home cockpit builders or instruments trainers, which is not a small percentage of the simmers. In my opinion worth to take in mind. By customizing each and every dataref in each and every aircraft, it just makes so complicated to keep up the settings for instrument trainers or home cockpits, sometimes almost impossible. If there are X-Plane standards (dataref and commands), and I'm just talking about regular common controls working equal in all the planes... why to over complicate this making all dataref names different? And again, all datarefs mentioned on this post were working great in the v1 of this same aircraft... reason enough to at least, comment this on this forum. Always from the constructive point of view, far of a big complain. Still a great aircraft!!!

Hi, is not a problem of using an axis, I don't use axis for flaps, I use the flaps button up / down a notch in the Saitek panel. And it works perfect! The problem is related to the display. As a home cockpit I use several kind of displays to show where the flaps are... then I don't have to move the 3D view down to see where the lever is. Just watch the value of the display in my home cockpit. The different displays I have use sim/cockpit2/controls/flap_ratio to display the flap position, In all the planes I have in XP 11 I had never a problem with this dataref. Even the v1 of this aircraft shown this correctly. And this is why I point to this.

Parking brake works: sim/flightmodel/controls/parkbrake but standard joystick mapping for P. Brake don't act.

Hi, In V1 sim/cockpit2/controls/flap_ratio dataref was working properly, seems not to be mapped in v2. I think is very important to map standard dataref and commands, at least for main autopilot and control functions, since most of the market hardware instruments for home cockpits use them. Not all allow dataref customization. Not sure if all are possible to map but just in case I will keep reporting them. I'm a home cockpit builder and this is such a great plane for it. Thanks!

Solved. The axis curve configuration was not stored correctly. I fixed it again and not works. Sorry for inconvenience.

Landing V2: torque doesn't go lower than 60. Then beta and reverse. Makes me difficult to control normal speeds for landing with min torque at 60... it is not happening to me in v1. Am I doing something wrong? Thanks!

Hi! Can't wait to buy v2!!! BTW: I own v1 and I didn't receive any discount coupon yet, I guess it will come sometime today before the sale starts, right? If coupons were already sent please let me know because I did not receive mine. Thank you for such amazing plane and work. Looking forward to it!!