July 30, 20214 yr Nearly every take off recently has given me problems not reaching full thrust on take off. When I remember I usually go from full thrust then back to idle before take off but even this doesn't seem to prevent problems where the cure is to madly go back and forth with the thrust several times during take off to eventually get the desired result. I am not sure if others have found this too or is it just my Thrustmaster Hotas is cream crackered? I have checked the settings in MSFS and none of my preferences seem to have changed. AMD Ryzen 7 5800X on ROG CROSSHAIR VIIl DARK HERO (AM4), Asus ROG Strix GeForce RTX 3080 V2 OC and 32 GB Vengeance Pro Ram 3600MHz. DELL Alienware AW3420DW 3440x1440 and DELL U2414H
July 30, 20214 yr Run windows calibration and see what that shows. David Murden. MSFS • Fenix A320 • PMDG 737 • MG Honda Jet • 414 / TDS 750Xi • FS-ATC Chatter • FlyingIron Spitfire & ME109G • MG Honda Jet • • Fenix A320 Walkthrough PDF • Flightsim.to • DCS • A10c II • F-16c • F/A-18c • F-14 • (Others in hanger) • Supercarrier • Terrains = • Nevada NTTR • Persian Gulf • Syria • Marianas • • [email protected] All Cores HT ON • 32GB DDR4 3200MHz • RTX 3080 • TM Warthog HOTAS • TM TPR • Corsair Virtuoso XT with Dolby Atmos® • Samsung G7 32" 1440p 240Hz • TrackIR 5 & ProClip •
July 30, 20214 yr Author 1 hour ago, Nyxx said: Run windows calibration and see what that shows. Had to look that up as I have never used it before, will let you know if any difference. For those similarly ig_norant as me it is: Just press the WIndows key and R key to get up the run dialog box and then type joy.cpl and click on ok You will the see a list of your controllers Click on the one you want to calibrate and press properties AMD Ryzen 7 5800X on ROG CROSSHAIR VIIl DARK HERO (AM4), Asus ROG Strix GeForce RTX 3080 V2 OC and 32 GB Vengeance Pro Ram 3600MHz. DELL Alienware AW3420DW 3440x1440 and DELL U2414H
July 30, 20214 yr Be aware that there is an issue with the latest patch for the sim whereby if you use the mouse to look about, it inhibits the signal from your controller. This means there could be a scenario where you are taxying, you push the thrust up a little bit but happen to be looking around with the mouse as you do so. What then can occur is your thrust lever was move to perhaps 20 percent, but the sim is still reading it as not having moved because you were using mouse look at the time you moved your throttle, so it never got the signal that you moved the throttle and it therefore thinks it is at zero when it's actually at 20 percent of its travel. So when you push the throttle up to full, it actually only reads as going to maybe 80 percent because of that previous signal being inhibited. To get around that, you can take the throttle down to zero, then back up to full and it will effectively recalibrate its movement on that flight. They need to sort this one out to be honest, but so long as you are aware it can happen, you can work around it. Alan Bradbury Check out my youtube flight sim videos: Here
July 30, 20214 yr Author 50 minutes ago, Chock said: Be aware that there is an issue with the latest patch for the sim .......... Many thanks for that, it could well be the explanation I was seeking as the hotas has only done 140hrs work so I was hoping it was not yet ready for the great graveyard in the sky 🙂 AMD Ryzen 7 5800X on ROG CROSSHAIR VIIl DARK HERO (AM4), Asus ROG Strix GeForce RTX 3080 V2 OC and 32 GB Vengeance Pro Ram 3600MHz. DELL Alienware AW3420DW 3440x1440 and DELL U2414H
.thumb.png.83ed92937c65d8d19c5d8b24b791cc3f.png)
Archived
This topic is now archived and is closed to further replies.