![]() I can still manually deploy the spoiler whenever I want, although only between fully retracted or fully deploy. That’s why I remove the Spoiler from the axis and use this binding instead. The Spoiler axis position of your lever will always override the Auto-spoiler, so the autospoiler never deploys. Because if you set them to use the Spoilers Axis like in the default profile, while you can still control how much or how little spoiler you want to deploy. But the positive side is that the Auto-spoiler will work. The drawback in here is that it would either go between 0 or 100. then if I want to deploy, I can deploy full at the FULL position. I set it up this way so the spoilers can be armed at the first position and disarmed and retracted at the RET position and at the 1/2 position. Generally though, I don’t use the Default profile for my Spoilers configuration. But I tested this on the FBW A32NX aircraft. I tested it using the Default profile, and the Speedbrakes/spoilers and Flaps work just fine for me. So we’re using the virtual buttons that you’ll trigger when you move the throttle to full reverse to trigger the decrease throttle command which will actually bring the engines to reverse thrust. ![]() The theory is if it’s already registering the 0% point as IDLE, pressing the decrease throttle ‘should’ bring to Reverse. But I think we can use the Virtual Button 12 and 16 as a workaround by assigning them to Decrease Throttle. It’s not a solution, and your throttle is still clearly having an Axis problem. In that case, I think you can apply the same workaround in MSFS. When you pull your throttle to full reverse, not only that the axis should become 0% or empty green bar, but it’s also activating the virtual button 12 for throttle engine 1 and virtual button 16 for throttle engine 2. Unless… the other sim is NOT using your Throttle Axis for the reverse, but instead it’s using your virtual Button 12 and 16. But I would think that even on IDLE position you would still have the issue. Which might explain why other sims can still receive a full reverse thrust. Because clearly, based on both of your screenshots, the hardware is actually feeding both sims as Full Reverse thrust (because it’s an empty green bar). I think the issue is not about why you’re not getting reverse range in MSFS… But most likely why are you not getting the IDLE thrust. Why can other simulator work with the reverse range? IDLE position should have it filled on the 2 bar level. It shouldn’t be empty like in your screenshot on the IDLE position. It’s even more unacceptable that the same problem happened “twice” from a different hardware connected in the same way to your PC.įeel free to take my screenshot on what it “Should” look like for the Idle position and show it to the Thrustmaster support. If they can’t find it as an issue, I think that’s an unacceptable excuse, since you would have sent them this evidence to tell them, “Here’s IDLE, here’s Full Reverse” Why are both the green bars empty? The green bar should fill up 25% or 2 lines per detent position in the throttle quadrant, just like in my screenshot. ![]() Your screenshot of it is clearly showing an obvious problem coming from the thrustmaster control panel. Shifting the blame to MSFS as the problem is an unacceptable excuse since the Thrustmaster Control Panel is “THEIR” software coming from their driver and their own tool. But if the issue already comes from the thrustmaster driver software, it’s not a fair accusation if they see it’s the sim’s issue. Then yes, it is an issue on the sim side. If the Hardware is correct, and the driver/software is showing the correct input, but MSFS behaves differently. MSFS just takes whatever it is being input to it. Either on that Software, or the hardware itself on the previous step. It doesn’t matter what MSFS is doing, if the input itself is already wrong on the driver/software level, then it’s already wrong from the start. Because the way that input flow works is Hardware → Driver → MSFS. ![]() I’m actually surprised that Thrustmaster couldn’t find a hardware, firmware, or calibration problem about this. I had a new and a old quadrant and both have this problem in the thrustmaster panel and MSFS. I was talking to the thrustmaster support and they can’t find a problem in the hardware or software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |