halfur Posted December 28, 2023 Share Posted December 28, 2023 Hi, I'm seeing the following issue with the A300F: With the starter running and after opening the fuel valve the engine spools up as expected at first. Then, once it is reaching idle, N₂ jumps to around 109%-110% immediately (no noticeable delay, no gradual rise, it jumps from 58% to 110% in a few frames). N₁ then starts following, rising to 99.9% over a few seconds, while N₂ settles down to 102.8%. Throttle levers are in idle. I'm using a Honeycomb Bravo throttle, I've tried resetting and recalibrating the throttle, the EFB also shows the correct position. I've checked for bindings which might cause issues but didn't find any obvious culprit (the oft troublesome Honeycomb Bravo avionics / lights toggle switches are all unbound e.g.). The needle in the N₁ gauge indicating the lever position is also at about 20%. Moving the throttle lever changes the needle, but the engine doesn't react, the only action the engines seem to react to is cutting off the fuel again. Any ideas what might be causing this, any obvious mistakes on my end, or any input bindings I should check? I've also created a quick screen recording to show the issue in action: https://youtu.be/frkLyqXagdM (full resolution will be available once YouTube has finished processing, but I think the issue can be seen even in 360p). Let me know if there's anything else I could provide to help. Link to comment Share on other sites More sharing options...
Alexair Posted December 28, 2023 Share Posted December 28, 2023 Hi Halfur, Just watched your video. Everything is working fine on my side. For me it look like a binding issue (throttle, GA mode, autothrottle, etc.). I guess you already checked all of that huh ? Link to comment Share on other sites More sharing options...
Deleted Account Posted December 28, 2023 Share Posted December 28, 2023 If you are on our Discord, there is an extensive thread about it where they got it fixed. https://discord.com/channels/535246634448191499/1190011180731871272 Link to comment Share on other sites More sharing options...
halfur Posted December 28, 2023 Author Share Posted December 28, 2023 That link only leads me to the rules channel unfortunately. I haven't seen a relevant thread about this issue so far, which channel is it in? I'd have expected it in #msfs-community-support, but I don't see it. Link to comment Share on other sites More sharing options...
Deleted Account Posted December 28, 2023 Share Posted December 28, 2023 yep, should be in there. Link to comment Share on other sites More sharing options...
Solution halfur Posted December 28, 2023 Author Solution Share Posted December 28, 2023 This post was recognized by iniBuilds! halfur was awarded the badge 'Great Support' Found it. I guess the role for accepting the rules hadn't synced yet, I didn't see any threads in the channel younger than a month. Restarted discord and found the thread. So as a summary for all those who don't want to use Discord (I'm leaving the server immediately after as well): Setting the Honeycomb Bravo selector switch for the autopilot variables to IAS causes this issue, so as a workaround one can select a different position and not use the selector until it's fixed. 1 Link to comment Share on other sites More sharing options...
Recommended Posts