Goran_M

The only thing I can think of is that you have 1 button or key press assigned to 2 functions. I can safely say this is not a bug because this is the first time I’ve seen this happen in 2 years since the TBM came out.

Go into maintenance manager and check trim linkages. You likely had a tail strike, or the the aircraft dropped on loading and damaged them.

Can you try disabling AI traffic and see if that has any effect?

There's a lot going on here. You have a lot of buttons assigned to various functions, and also a lot of damage on the TBM is being recorded. I can understand you having problems, but to really nail this problem, you need to disconnect everything except your mouse and keyboard, reload the sim nd the TBM, and then use the mouse to maneuver the power lever. If you can confirm that it functions correctly, without any hardware connected, then the problem lies in the hardware calibration. The only way to know for certain, is, as I mentioned, to disconnect all hardware except mouse and keyboard. This part of the log also is cause for concern, because with damaged components, especially this many damaged components, many systems will not function correctly...

You mentioned that you tried the TBM on a demo version of X-Plane. Can you try again and post a log file from that?

Whenever the power lever goes to full power on its own, it's because of some kind of assignment. Do you have something that sets takeoff power getting activated on other add ons? Any other scripts that might be doing something to set full power?

Looks like you have some kind of script or key assignment that retracts the landing gear when power is turned on.

Either Gizmo is not installed, or the TBM is not activated.

position yourself in the cockpit and press CMD (numpad number) to assign a position. Then when you went to move to that position next time, press the numpad number only. As for the sound, not sure what that could be. Check the audio panel and make sure something on there isn't turned on.

Keen eyes. I'll add it to the whiteboard, but no promises for the next update.

All annunciators have been re-textured for the update.

The navdata you should be using is for XP 11.00 and above. If you use 11.50, you will get the ILS bug (which is fixed for the next update)

Correct. What you're seeing on the G1000 display is what would be seen on any aircraft, default or payware, that uses the default G1000 display.

In that case, you might be better off sending an email off to Laminar and asking if something went wrong in an update. The TBM uses the default moving map and all navigation code for the displays. If the navdata isn't updating correctly, it is definitely something that they did.

Not released yet. We'll announce it here when it is available. Ilias is posting regular development updates so you can keep track of what is going into it. Current owners of the DC3 will receive a significant discount. Quite a lot of work has gone into it, including new model and textures, and quite a large amount of code.

I need the log.txt file out of the X-Plane root folder.

Check your maintenance manager.

Disconnect your throttle quadrant and any other hardware, as well as removing any lua scripts, then try it just using the mouse and a key press to toggle thrust reverse (for going into beta). If this works, then the problem lies in your calibration or some rogue script. Please post back results.

Une mise à jour est en cours d'élaboration et est presque terminée.

One of the reasons lua scripts can be a blessing and a curse.

I'm afraid not. And those sections can only be accessed on the ground with the engine shut down.

That means your pressure vessel is damaged, and that can't be repaired. Make sure you dont make any tail strikes or when you load the TBM, make sure it doesn't "drop" on the tarmac.

Found a few things. When in sim, check the maintenance manager and make sure nothing is broken. The TBM900_log.txt file is showing some things as failed or worn, and this may have an effect on the throttle. If you find anything damaged or broken, repair them and try again.

Ah, hold up a minute. So am I right in assuming you're using the F5 and F6 keys by holding them down while in the different ranges, without letting them go when the power lever reaches it's limits? If you press F5, while in the high idle range, to bring the power lever to the bottom of that range, but you keep the button pressed AFTER it reaches the high idle position, X-Plane will read that value as zero, instead of the mid point. So when you drag it over to low idle, because of the value X-Plane has recorded (zero), it will snap the power lever to cutoff. If you were to use hardware, and you brought the power lever back to high idle, you would need to bring the hardware throttle to about half way only. Bringing it back all the way will have the same effect if you were to then move the power lever to low idle. It would snap to cutoff. So, in case I don't make any sense, if you're at full power, press the F5 key until you reach high idle. Then STOP. Don't keep the button pressed. Then drag the power lever over. It should stay at low idle. This will also work in reverse. Moving from START to low idle by pressing F6, do not keep it pressed longer than it takes for the power lever to reach low idle. Hope this makes sense.