Goran_M

There could always be some kind of rogue key or button assignment that could override what we're doing in the TBM, but there is no way for us to find it. An easy way would be to delete the contents of your preferences folder and restarting the sim. However, this will delete all your key, button and axis assignments. But it is definitely the most effective way to determine the cause.

According to Ben Supnik, beta 10 has some confirmed issues with it, so we'll ignore this one.

Disconnect all hardware. Go through a normal start up, and while on the ground, put the throttle in flight idle and slowly increase power using the mouse. After letting go, if the throttle stays where it is, this confirms the problem is with you hardware calibration and assignments. If it DOES keep moving back with hardware disconnected, then please post your log so we can further diagnose, as this is not something that should be happening.

https://discord.gg/ep5M9q

Can you post a log.txt file so we can take a look.

It doesn't work in 11.50 yet. It's being worked on.

This is definitely not normal behaviour. Did you check the maintenance manager for any damage? Do you have some kind of hardware that could be overriding the trims? As a last resort, you could try deleting the contents of preferences folder and re-calibrating, but this a rather drastic step. Also, we ask that you don't compare the TBM to other aircraft. Reason being, for example, the pocket rocket has a completely different autopilot to the TBM. The TBM requires the AP Trims switch to be turned on before the Autopilot will work. Regardless of the AP button being pressed on the Autopilot panel. There is a lot of code behind each system on the TBM, and much of it works outside of the X-Pane envelope. You're more than welcome to join the Hot Start discord. There may be someone who has experienced the same thing as you have, who may be able to help you. https://discord.gg/nW4pkw

Ah, ok. Well, to clear up any confusion, that is my post. But yes, as stated, the big upgrade to version 2 will be a paid update, but heavily discounted. There was a compatibility update made to bring the Saab up to working in X-Plane 11. The update we're working on now, is yet another free update to fix some further issues.

There is something seriously wrong with your install and this log file. In over a decade of making add ons, I have never seen a 21MB log file. The biggest I've seen is maybe 5 or 6MB. Most of the time, they range in size from 50kb to 200kb. I'll forward this to Saso and see what he has to say about it and what he thinks is going on.

https://discord.gg/BU2UP7

The update has some flight model fixes, which addresses some of these issues.

Yes. I need to use the word "imminent" more conservatively. We'll have more information in the very near future.

Can you steer using the mouse and tiller?

Are the engines running and is the aircraft moving?

Ok. Here's the official word. The big update will be a paid update for current customers, but it won't be full price. It will have more features than the current version that is available in the store. It will have more systems modelled (working circuit breakers being 1 of them, as part of a newly coded electrical system. However, this is dependant on us getting our hands on the electrical schematics) 100% new art assets. (3D mesh, PBR textures, lighting) Improved flight model (The flight model is likely the only thing that will not be done from the ground up.) If you can find out where you got this information, I would be very interested in visiting this site and finding out more about the person saying these things.

We were in touch with navigraph over several weeks. From what I understand. steps were being taken, but release day was coming, and we didn't want to hold up the release while waiting for navigraph. So the X-Plane navdata was implemented.

Some of the graphical elements don't work in the TBM under Vulkan. It's something that is being worked on. An update shouldn't be too far off to fix these issues.

Am I correct in assuming you're using 11.50? If so, can you confirm this is only happening in Vulkan? Can you also check to see if it's happening in 11.50 under OpenGL? (uncheck the Vulkan option in your graphics settings.)

It definitely needs to be there. Reason is, due to the unique shape of the throttle pattern, (the "h" pattern), if someone was in low idle, and didn't know it, and then tried to go into reverse, they would inadvertently move the throttle from low idle to fuel cut off. And vice versa (if they were in high idle and thought they were in low idle, and wanted to go to fuel cut off, they would instead go to reverse thrust.) Even if we made it an option to toggle it on or off, there would be people who would simply forget to toggle it back on when needed. All things considered, it's best to have it intermittently appear (only when using the throttle.)

Anything to do with air traffic. I think World Traffic from Just Flight works with the TBM without crashing. They reached out to me about 1-2 months ago and asked for a copy of the TBM to somehow code their AI so it doesn't crash when run with the TBM. I haven't heard any problems with their version of traffic. X-Life WILL crash with the TBM, as will the default AI traffic.

It's not supposed to be there constantly. Only when using the throttle. Are you saying it's there 100% of the time while in VR?

Excellent.

"I did a little research and found that version 2 will be required to run with Vulkan and this will be treated as a new product rather than an upgrade from X-Aviation." V2 will be an upgrade. Not a new product.

Correct.

You're telling me. Something must have changed that caused this to happen. The only other thing I can think of, which will reset everything, is to delete your preferences folder contents. You'll lose all your calibrations, but it's an opportunity to really narrow it down.