Fartherbranch55 Posted February 8 Share Posted February 8 I can also confirm that TOGA works fine achieving correct t/o power setting. Link to comment Share on other sites More sharing options...
sunnya Posted February 9 Share Posted February 9 Update 1.0.6 changelog doesn't have anything related to this issue and I can confirm problem still persists if throttles are advanced manually only. 1 Link to comment Share on other sites More sharing options...
matterno Posted February 9 Share Posted February 9 I can confirm the issue... started with 1.0.5 my observation is: I have a FLEX TO that has a target of 95% for example. On take off N2 reaches 95% then, but not N1... is that right? Should the target be for N1? Would be nice if you'd fix that. 1 Link to comment Share on other sites More sharing options...
SkySurfer87 Posted February 9 Share Posted February 9 (edited) On 2/8/2024 at 6:07 AM, JoshF said: How is your Bravo set up? I'm using one and haven't seen this Here's how mines currently set up. I engage reverse by pulling the reverser switches back and the throttles all the way down through the idle detent. Then just close the reverser switches to cancel REV thrust and bring the throttles back up to idle detent. Worked fine up until 1.05 update, now when I try to cancel REV using this method the number two reverser only closes halfway for some reason. When I bring the throttles back to idle, the reversers stay engaged and any forward movement on the throttles is in turn actuating the reverser levers as an axis. I have to jangle everything around for it to go back to normal operation. So something seems to be wrong I suppose. I've tried to recalibrate in the EFB along with reinstalling the plane entirely with no luck. Overall im absolutely loving this model.. Thanks. Tom Edited February 9 by SkySurfer87 Link to comment Share on other sites More sharing options...
Deleted Account Posted February 9 Share Posted February 9 Yes, we are still tracking this issue and it wasn't fixed for 1.0.6 as it was too close to release. For now please just follow the SOP of spooling the engines to 50% N1 and then pressing the TOGA button. 3 1 Link to comment Share on other sites More sharing options...
Elmeon Posted February 9 Share Posted February 9 On 2/8/2024 at 6:48 PM, ponpon said: Hello, Same issue here, manual full power is 86%, and even worse : After a 2hr flight and after landing, my throttle axis controlled only the reverse. It was impossible to join the parking. I didn't change the setup during my flight and I confirm that my reverse axis option was unselected on the calibration page. I did a couple throttle calibration, I had still the issue. Engines work 100% with A/T. Aircraft concerned : A300-600F / Joystick : T.16000 Same issue here, after landing I'm stuck with the throttle axis only controlling the reversers even if the "reverse on axis" option is unselected. I'm also pretty sure that before 1.0.5 when F2 when pressed 2 times the reverser were put in idle, now it's not working like that anymore. The only way to use control the throttles again is to press F3 and then they start to work again... Link to comment Share on other sites More sharing options...
Enr1 Posted February 14 Share Posted February 14 (edited) Same problem here from V1.0.5, I can't get above 86% power, risk stalling on takeoff, and will get the landing gear warning when I retract them because the power isn't correct for takeoff. EFB calibration shows the right "values"!!! Edited February 14 by Enr1 Link to comment Share on other sites More sharing options...
kevink817 Posted February 14 Share Posted February 14 (edited) 3 hours ago, Enr1 said: Same problem here from V1.0.5, I can't get above 86% power, risk stalling on takeoff, and will get the landing gear warning when I retract them because the power isn't correct for takeoff. EFB calibration shows the right "values"!!! First, V1.0.6 is available, i'd recommend you update to that if you can. Second, for takeoff - spool the engines to 40-50% and press the TOGA button. For convience, they've placed a TOGA click spot button on the panel in front of you to the left of the Auto-land button and outlined in orange. Edited February 14 by kevink817 Link to comment Share on other sites More sharing options...
Enr1 Posted February 14 Share Posted February 14 20 minutes ago, kevink817 said: First, V1.0.6 is available, i'd recommend you update to that if you can. Second, for takeoff - spool the engines to 40-50% and press the TOGA button. For convience, they've placed a TOGA click spot button on the panel in front of you to the left of the Auto-land button and outlined in orange. First read carefully, I wrote from and not with. I have V1.0.6 and the problem persists. Link to comment Share on other sites More sharing options...
kevink817 Posted February 14 Share Posted February 14 52 minutes ago, Enr1 said: First read carefully, I wrote from and not with. I have V1.0.6 and the problem persists. Did you hit the TOGA button? Link to comment Share on other sites More sharing options...
Enr1 Posted February 14 Share Posted February 14 TOGA button are you referring to the "Take Off/go-around switch" in the thrust levers? so it should be a temporary solution anyway until the next update? thanks I will try Link to comment Share on other sites More sharing options...
kevink817 Posted February 14 Share Posted February 14 1 minute ago, Enr1 said: TOGA button are you referring to the "Take Off/go-around switch" in the thrust levers? so it should be a temporary solution anyway until the next update? thanks I will try Yes, those are the ones I'm referring to. If YOU would have read carefully, I also explained there is one easier to reach on the panel in front of you: "For convience, they've placed a TOGA click spot button on the panel in front of you to the left of the Auto-land button and outlined in orange." Also, keep in mind that setting the throttle to 40 - 50% (and actually the FCOM states even up to 80%) and activating the TOGA lever is the normal operating procedure in the aircraft and not a "temporary solution". Finally, the devs are already aware of this and have explained above that they weren't able to get a fix in time for the 1.0.6 release. Link to comment Share on other sites More sharing options...
Deleted Account Posted February 17 Share Posted February 17 And I can also say that this bug is already fixed for 1.0.7 🙂 3 Link to comment Share on other sites More sharing options...
Recommended Posts