Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

TBM still has a few issues.

Featured Replies

No big ones or I would have shouted harder about them in the beta period. A mod will come at some point I hope.

The doors can't be opened in VR.

During climb diff. pressure exceeds its limit and triggers a warning (can be overcome by clicking DUMP twice in quick succession).

No registration on the external model of the base TBM and all custom livery's that fallback on it.

Edited by Gerwil

  • Replies 31
  • Views 6.5k
  • Created
  • Last Reply

How about the interior panel lighting being terrible? It needs some dimmable panel lights for nite flying as now its either too bright (overhead on) or too dark (overhead off).

External taxi and landing lights do not cast outward/forward nearly enough to be useful from the cockpit at night. They need attention. I can't do any nite flights until it's fixed.

Also, not certain about this because I only did 1 quick flight thus far, post-patch...but I may have noticed the drag on final approach was wrong? Generally speaking, in these modern tbm's, you should be using about 25 torque or less once you're situated on short final, and with full flap you should be pointing nose down at least 3 degrees or more in order to maintain 85-90 kias. It might have just been me, or the weather or whatever else at the time where I wasn't paying full attention but I thought I remember the nose being very flat on final and needing alot more throttle...as if I was dragging it in, which is all wrong for this aircraft. Could have just been my error though so I'll need to try again.

Did a short flight today and had two noticeable issues with the "new" TBM:

1. A red door warning alarm in the CAS system during the entire flight, even if all the doors seemed to be closed (and locked).

2. Needed to cut the engines by closing the fuel valves in the center console panel. I couldn't place the throttle handle to the right to the cutoff position.

If some helpful pilot gives me a hand on was went wrong, I'll be very much appreciated.

Apart of this, the new G3000 is a wonder, and the aircraft is a joy to fly.

 

Edited by edpatino

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

1 minute ago, edpatino said:

Did a short flight today and had two noticeable issues with the "new" TBM:

1. A red door warning alarm in the CAS system during the entire flight, even if all the doors seemed to be closed (and locked).

2. Needed to cut the engines by closing the fuel valves in the center console panel. I couldn't place the throttle handle to the right to the cutoff position.

If some helpful pilot gives me a hand on was went wrong, I'll be very much appreciated.

 

 

Ed, dunno about #1, but for the stuck throttle handle not shutting down... if you have a hardware axis setup for props just reduce the props and the throttle handle in the tbm will move itself over to the right hand side of it's gate and then if you like, you'll be able to manually drag it down yourself to kill the engine.

3 minutes ago, hangar said:

if you have a hardware axis setup for props just reduce the props and the throttle handle in the tbm will move itself over to the right hand side of it's gate and then if you like, you'll be able to manually drag it down yourself to kill the engine.

Got it, will try it!.

Thanks!

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

As this has been my "go-to aircraft" for a couple of years (w/both aircraft and g3000 modded) and it has been performing beautifully with those mods I was curious to see how the recent updates affected performance.  I finally had an opportunity this morning and took her up:

1. The g3000 update by WT is marvelous.  Many more features are now operational and VNAV works well - it also did a decent job on my first RNAV approach test   Also, the nearest airport weather data is great to have and I'm sure there are many more features to discover!

2. The TBM aircraft, however, appears to have a number of issues:

  • Ground steering:  Really bad - could barely make turns unless down around several knots.  I went into the flight_model.cfg file and reset "max_castering_angle" so that it was identical to the mod's very nice steering response.
  • Torque: I'm not sure about this.  The TBM has never needed full torque to take off and climb, especially near sea level but now it seems to be on steroids?  With the mod I had a very controllable power level, but now I have to pull the throttle back a lot more after lift-off to come anywhere near the proper climb profile.
  • Trimming for climb is not responding well now.  As with most aircraft, the modded (and previous default versions) could be set in a 10% climb angle with a few seconds application of electric trim.  Now I trim and trim and trim and trim and get no response for a long time.  Eventually, she responded and I was able to get a proper climb, but this still required a lot of power reduction to keep her out of the red.  After the initial climb, power settings appeared to move into more standard response.  98-99% torque settings worked well and small increases were necessary as altitude increased (which is a proper response).
  • The aircraft handled well throughout the rest of the climb, cruise and initial descent.
  • Initial approach: using the recommended 35% torque which should have established a speed around 150 kts she settled in at 149 kts. 🙂  So far, so good.
  • Final approach: I set up for standard procedure, dropping gear and flaps TO, then pulling power to 22% and going to full flaps at the glide slope.  At this point things got really dicey, as my destination's current live weather gave me a 90° crosswind at 15 gusting to 21 kts - not an ideal situation.  I was forced to add power to maintain the 85 kt approach speed and the touchdown was not pretty.

It's going to take a few more flights under more standard conditions to see if the normal approach procedures produce a good landing.  Overall, I love the upgraded g3000, but the TBM performance mod seems to be much better for overall handling and special touches.

Items on the mod that work really well but not on the current default:

  • All of the doors
  • Interior and instrument lighting
  • Takeoff and climb power settings (still need to verify the default's settings for takeoff)
  • Trim response!!!
  • Final approach settings (need to be fair to the default here and do more testing)
  • Sunshades (don't work at all on the default)

As I must use the default version in order to get the new g3000, I'll spend a little more time with it.  However, if I find that the trim and power settings can't be brought into line, I'll return to the modded versions, which gives me a very nice aircraft and a good WT g3000 mod that has decent features, but can't do assisted VNAV.

Randall Rocke

To be clear: is this regarding the mod version or stock? Mod still working?

SAR Pilot. Flight Sim'ing since the beginning.

8 minutes ago, Flyfaster_MTN002 said:

To be clear: is this regarding the mod version or stock? Mod still working?

Stock... and yes this little mod still works.

Bert

2 hours ago, RandallR said:

 

  • Ground steering:  Really bad - could barely make turns unless down around several knots.  I went into the flight_model.cfg file and reset "max_castering_angle" so that it was identical to the mod's very nice steering response.

So it pulled hard left for you during taxi?  That's what it does for me.

Edited by Jeff Nielsen

Jeff D. Nielsen (KMCI)

https://www.twitch.tv/pilotskcx

https://discord.io/MaxDutyDay

VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro

5 hours ago, RandallR said:

Ground steering:  Really bad - could barely make turns unless down around several knots.  I went into the flight_model.cfg file and reset "max_castering_angle" so that it was identical to the mod's very nice steering response.

I agree, the ground steering is terrible. If your changes improved the ground steering, would you tell me where this file is located and what change you made?

Tom

3 hours ago, Jeff Nielsen said:

So it pulled hard left for you during taxi?  That's what it does for me.

Not for me - its steering response was quite poor and she couldn't make tight corners without pushing.

If she pulled on you while taxiing, was there a strong crosswind?

Randall Rocke

1 hour ago, tjrush said:

I agree, the ground steering is terrible. If your changes improved the ground steering, would you tell me where this file is located and what change you made?

Go to the flight_model.cfg file for the aircraft and change the castering angle.

In the original file you'll see:
---------------------------------
max_castering_angle = 3.14159265358979 ; Defines the maximum angle a free castering wheel can take (in radians).
point.0 = 1, -7.5, 0, -4.14, 720, 0, 0.52, 15, 0.327, 1.5, 0.9, 13, 13, 0, 0, 0, 4

Change the 15 to 60 so it looks like the below:

max_castering_angle = 3.14159265358979 ; Defines the maximum angle a free castering wheel can take (in radians).
point.0 = 1, -7.5, 0, -4.14, 720, 0, 0.52, 60, 0.327, 1.5, 0.9, 13, 13, 0, 0, 0, 4

-----------------------------------

Personally, I've found "60" to be a little too sensitive for my tastes so I use "50"

Randall Rocke

2 hours ago, RandallR said:

Go to the flight_model.cfg file for the aircraft and change the castering angle.

In the original file you'll see:
---------------------------------
max_castering_angle = 3.14159265358979 ; Defines the maximum angle a free castering wheel can take (in radians).
point.0 = 1, -7.5, 0, -4.14, 720, 0, 0.52, 15, 0.327, 1.5, 0.9, 13, 13, 0, 0, 0, 4

Change the 15 to 60 so it looks like the below:

max_castering_angle = 3.14159265358979 ; Defines the maximum angle a free castering wheel can take (in radians).
point.0 = 1, -7.5, 0, -4.14, 720, 0, 0.52, 60, 0.327, 1.5, 0.9, 13, 13, 0, 0, 0, 4

-----------------------------------

Personally, I've found "60" to be a little too sensitive for my tastes so I use "50"

Randall,

Thanks.  I don't know if 60 is the right number but, it's a lot better than 15. Thanks again. Maybe now I can stay off the grass.

Tom

Update - 2nd Flight:

Ground steering: the castering angle adjustment did indeed work and handling is good again.

Torque: It seems fairly accurate now that I've had another go.  The amount of throttle needed to achieve 95-100% is a little less than the mod but once I got used to it it's decent.  As altitude increases the response is similar and cruise performance is appropriate.

Trimming for climb: In my initial flight this was a concern.  This time I set the pre-takeoff trim to the furthest "up" position and it may have helped.  I was able to rotate smoothly and trim for a 10% climb without as much input.  (I was using a different livery this time to see if they were still compatible and there were no issues - I don't know if a change of livery from the default could have any affect on trimming but the response was a lot better).

Approach sequence: This time I had a mild quartering headwind (6 kts) so I was able to get a good feel on handling.  35% torque gave me around 150 kts again, so spot-on,  With gear down and full flaps she maintained around 85 kts at 22-25% torque - very good!  10% torque at flair, then idle just above ground with about 5% nose-up gave me a nice touchdown.  Well done, WT!  (However, I got the atrocious "mini-hurricane" bug and got thrown all over the place in the 600-1000' AGL zone - the air became stable again at about 400' AGL.  Come on, ASOBO - get rid of this word not allowed!)

Lighting: I would recommend reducing the overhead lamp output a little - it's just too bright right now.  Also, don't have the instrument back-lights set to 100% at start-up.  Maybe put the dial around 50% so it's easy to make adjustments?

Sunshades: get these working - they're really helpful in the mod and can be moved all over (including the sides)

Doors: It's nice to be able to open and close the doors but the cargo door Close button needs to be activated.  It's way too clumsy to have to move a camera outside to grab the handle - simply share this function with the button and you're good.

I shot the Scottsdale RNAV RW03 approach and the g3000 did a fantastic job - spot-on all the way.  Really well-done WT!  Make some small adjustments with the aircraft and I'm a happy camper.

Edited by RandallR

Randall Rocke

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.