Jump to content

Archived

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

viper1740

Engine does not respond to throttle

Recommended Posts

Ok so I started my engines and my #1 engine will not respond to throttle. I tried restarting the engine as well as the CTRL+E (1 & 2) and it does not work. Any ideas? Also unless I start with starting my #2 engine my #2 will not start if I start with starting my #1 engine. **EDIT**For some reason when I pressed CTRL+E (1,2,3,4) it worked. Hope this helped.


Jakub Wesolowski

Share this post


Link to post
Share on other sites

Are you following the start up checklist in the documentation? I don't believe the ctrl e works correctly. A couple of screen shots of the upper panel, main panel and throttle would help.


George Morris

 

Boeing777_Banner_BetaTeam.jpg

Share this post


Link to post
Share on other sites

Cool I did not know you could have the Hydraulics on the Bottom Display unit like that while the rest of the info was on the top display. I usually move all the info to the top before takeoff but had to switch between Hydraulics and other info. Never knew you could have both at the same time.


Paul Deemer

Share this post


Link to post
Share on other sites

So your engines are running and you have the a/t enabled so depending on how you have your options set up everything looks fine? Turn off A/T to manually control the engines. We need a little more clarification on what the problem is?


George Morris

 

Boeing777_Banner_BetaTeam.jpg

Share this post


Link to post
Share on other sites

I want to say there seems to be a delay in the throttle response from the time you turn on the engines (something I'm not used to) This has happened to me again when I was taking off LAX not too long ago. I tried the CTRL+E function like I have stated before and no response. So as of right now, that's all I have.


Jakub Wesolowski

Share this post


Link to post
Share on other sites

Jakob, I have experienced exactly the same problem. Only the other day in fact. A workaround for me was to save the flight and then reboot FSX and load the flight again. This seemed to work, which suggests that there may well be an intrinsic issue somewhere along the line.


Howard
P3DV4.5, MSFS2020, MSI Mag Z490 Tomahawk MB, i7-10700 CPU @ 5ghz, Nvidia RTX3090 GPU, 32gb RAM@3200Mhz, SSD/2Tb+SSD/500Gb+OS, Western Digital 1Tb HD + Storage, Corsair 1000W PSU, Philips BDM4350UC 43" 4K IPS, PFC Yoke, MFG Crosswind rudder pedals, CPlight MCP, Virtual Fly TQ.



Banner_FS2Crew_Supporter.jpg

Share this post


Link to post
Share on other sites

It so happens that after I landed my FSX crashed so I had to reset, but it doesn't appear to be a problem anymore. I am still having an issue to start my number 2 engine first. If i start with my #1 engine, my #2 will not start. Is this a normal procedure?


Jakub Wesolowski

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    42%
    $10,670.00 of $25,000.00 Donate Now
×
×
  • Create New...