September 14, 201312 yr Every time I start up the plane for a flight, after the engines are started the engine generators wont ever kick in. The overhead switch lights remain illuminated off and I have the eicas messages to go with it. Is there something I'm missing here or is this part of the simulation? Help please!!! Jimmy Nestor
September 14, 201312 yr Are you using a default state like cold and long, or are using using a custom saved state? Ash KeelsonLIAN LI DK-02 Desk/Intel Core i7 6700K Skylake 4.0 ghz/ H110i Liquid Cooler/ ASUS Extreme VIII/ EVGA GTX 1080 8GB/ 32GB G.Skills DDR4 RAM/ Intel SSD 1TB/Samsung 1TB/ Crucial 150GB/Windows 10/Prepar3D v3.3
September 14, 201312 yr They take a minute or two to kick in, its not instant like on most planes and the same goes for the bleed and packs. Alex Jevdic KORD/KHOT/KPWKA<380 love at first flight
September 14, 201312 yr Author I'm using a custom state and yes I know they take a minute or so. They never kick in. Would my panel state be the cause d'ya think?? Jimmy Nestor
September 14, 201312 yr No idea since I never had that problem. Alex Jevdic KORD/KHOT/KPWKA<380 love at first flight
September 14, 201312 yr Wow! I just posted this as I didn't see your problem. See mine, I have an example (on video) of what happens. At least I think it's the same issue as my left GEN light never goes off while waiting. http://forum.avsim.net/topic/420650-engine-1-freezing-after-startup/ Sorry if it's not the same. Sounds close. PHIL CHIMBOLO "Flight Simming for 40-years" Intel Core i7 3970X 3.50GHz (OC @ 4.20GHz) | 32GB RAM | Windows 10 Pro 64-bit NVIDIA GeForce GTX 1070 8GB | Four Monitors | GoFlight Pro Yoke GoFlight TQ6 Advance Throttle | CH Rudder Pedals | TrackIR 5
September 14, 201312 yr Author It's both engines for me. Also when I advance the throttles nothing happens. No movement of the plane nor N1 indication on the EICAS! Jimmy Nestor
September 14, 201312 yr Cant explain the n1 indication but have you removed the chocks at all I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
September 14, 201312 yr Author I should mention hydraulic C2 fault light is on and both engine bleeds stay off also!! Jimmy Nestor
September 15, 201312 yr I have exactly the same problem. I follow the start-up process as per the Tutorial but the main generators never come on line. Also, the throttles move but the engines do not spool-up! Having been trying turning stuff off that could be interfering (eg FSUIPC, Ezdok, etc.) but to no avail so far. USing the preset panel states doesn’t help either!
September 19, 201312 yr Author Any more feedback on this would be great. The only way I can get it to work is if I go to the map through the menu and raise my altitude above ground level, then the engines start by themselves and everything works fine. After this I park the aircraft at the gate and cycle through many startup/shutdowns in every different panel state and it starts up just fine every time. Maybe it has something to do with the initial loading of FSX itself??? Just to clarify, I load FSX with a default aircraft. Jimmy Nestor
September 19, 201312 yr I am having the same problem. After starting the simulation in the cold and dark saved panel state, the main engine generators never come on. The engines are running, but the pneumatic engine bleed valves never open either. Additionally, the engines will not respond to any throttle movements. They remain in idle. The thrust anticipation arcs move along with the throttles, but engine RPM never moves. It seems as though this problem only occurs when starting the simulation from a cold and dark panel state.
September 19, 201312 yr For me I found I couldn't get N1 movement if I started the flight sim with a cold-and-dark airplane (I put the Cessna 172 as the default flight but it wasn't running). If you press CTRL-E when you're hung like this does it make the engines respond to thrust levers and the gen's kick in? I ended up re-saving my default flight to a running/avionics on 172 and haven't run into the problem since.
September 19, 201312 yr Guys, are you using any sort of external hardware that links to your fuel or mixture axes? For me, during beta, I had my fuel valves were mapped to some buttons in the FSX controls screen which prevented the engine from starting successfully and it would exhibit everything you talked about in your post. Hope that helps. Regards,Robert Szarek
September 19, 201312 yr Author I can confirm that the CTRL-E method works but only for the left engine. I assigned TAB-E to the command "starters all(on/off)" and that got the other engine going. The "battery/avionics on" default panel state on the 172 wont work for me either! EDIT!!! CTRL-E now works for both engines. Jimmy Nestor
Create an account or sign in to comment