TBM 850

I think using another aircraft's engine sound is not that trivial, not to talk about the licensing issues.

However it was just confirmed that @Black-Square will cooperate with Boris Audio Works to create a custom sound set for the Turbo Duke. I hope that the TBM can benefit of this afterwards, because the current sounds are the only major downgrade for me on this excellent product.

@vojkd Thanks, that looks amazing. Unfortunately I am too lazy to do this manually. An fully automated option is the TBM Performance app on iOS/Android.

Ahh, I didn't see that post. No worries, it's not the end of the world.

Was the manual override lever set, or are you now using it? The latter is an issue, if so.

What I don’t get is: I don’t have that sound. Never heard it. I know is should be there but for me there is nothing. Begs the question, what other sounds am I missing that would enhance the simulation? We know the engine sound could be better but on my end it seems the sounds are just dull, which I know should not be the case. I am the one not having missing least this sound piece?

Maybe your friend's fuel pump is about to fail :)
You could have a look at the file SimObjects\Airplanes\Asobo_TBM930\sound\sound.xml in the TBM 850 package, there seems to live the definition for fuel pump sounds.

I had a similar issue the other day and I suspect they're related. I often load a .flp file into the map so the GPS is preprogrammed, but I've seen it not work on first load.

I have also seen the same happen in the 414 (and going back to the menu and reloading into the same plane fixes it) so I don't think it's TBM specific; it's either related to the fact that both have not been updated to use the WT avionics natively, with everything that comes with that, and rely on the marketplace pointer, or it's part of the regression that the WT stuff seems to have undergone with the recent SU.

@schultenh oops, didn't realize the gauge markings went high to low.

I have searched Google already and have not found what I was looking for. Maybe there is a way to derive the dimensions from the 3D model but I don't see how to do that.

I think I've answered these before in various threads, but I will put all my answers here for safe keeping:

Sun Visors - They are not visible from the outside in all my airplanes. There was an issue with the Blender exporter when I was learning all this that made the draw order not behave correctly, so the visors would flicker horribly. This may have been fixed since. I'll look into it.

Starter does not get damaged - I'm looking at my code right now. 120 seconds is the hard cutoff to disconnect the starter. Starter performance will begin to degrade after 60 seconds. Other of my aircraft have more sophisticated starter temperature simulation. I forget what my reasoning was for not implementing this in the TBM.

Altitude selector ARM - Limitation of the native autopilot. Nothing I can do without implementing my own autopilot controller, which would conflict with the many hot-swapping GPS options I provide, since many of them already implement a custom autopilot.

High Bleed Torque - Not easily done, even with the many circumventions I've made around the native turboprop simulation. I could fake it, but then it wouldn't really affect engine performance. I made some notes on a possible way to do this that I will revisit for the Turbine Duke.

WX display on the HSI - I have to do this for the Starship, so once I figure it out there, I will bring it back into the TBM. I like to start big new features like that from scratch, so that way I don't break things that are already working.

These are the expressions I use in FSUIPC to handle trims. They account for electric power (so they even stop working when you pull the respective fuse) and for the AP/Trims switch. And you can change the rate at which the trims move to suit your taste. Can be adapted for use in other software like Spad, etc.

Created with help from other forum members here https://community.justflight.com/topic/5517/trim-key-bindings-work-when-they-shouldn-t

The calculations could be probably simplified, but are the result of iterative development till I got something that worked and stopped there :)

BSTBMElevatorTrimInc#6 (A:1:CIRCUIT CONNECTION ON:5, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:ELEVATOR TRIM PCT, Percent) 163.83 * 32 + 16383 min (>K:ELEVATOR_TRIM_SET) } BSTBMElevatorTrimDec#6 (A:1:CIRCUIT CONNECTION ON:5, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:ELEVATOR TRIM PCT, Percent) 163.83 * 32 - -16383 max (>K:ELEVATOR_TRIM_SET) } BSTBMAileronTrimRight#6 (A:1:CIRCUIT CONNECTION ON:6, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:AILERON TRIM PCT, percent) 0.1 + 163.83 * 16383 min -16383 max (>K:AILERON_TRIM_SET_EX1) } BSTBMAileronTrimLeft#6 (A:1:CIRCUIT CONNECTION ON:6, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:AILERON TRIM PCT, percent) 0.1 - 163.83 * 16383 min -16383 max (>K:AILERON_TRIM_SET_EX1) } BSTBMRudderTrimRight#6 (A:1:CIRCUIT CONNECTION ON:7, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:RUDDER TRIM PCT, percent) 0.2 + 163.83 * 16383 min -16383 max (>K:RUDDER_TRIM_SET_EX1) } BSTBMRudderTrimLeft#6 (A:1:CIRCUIT CONNECTION ON:7, Bool) (A:ELECTRICAL MAIN BUS VOLTAGE:6, Volts) 12 > and (L:BKSQ_AutopilotMasterSwitch) 0 > and if{ (A:RUDDER TRIM PCT, percent) 0.2 - 163.83 * 16383 min -16383 max (>K:RUDDER_TRIM_SET_EX1) }

@Lemny said in Outside temperature display jumps back:

This confirms again that Celsius is the only „true“ measurement system.

You might be on to something, was wondering what is the meaning of that true/false for a temperature unit variable.
Though I would rather consider Kelvin to be the ultimate unit of temperature measurement, but Celsius is getting close, has the same step size, with only slightly shifted start :)

This should improve with my overhaul to state saving that will come with the Dukes, btw. The most essential features, like the radio state should be loaded before the flight ever initializes. If everything works well, I will bring this back into the TBM in a major update I have planned.