Todd Moore

No, it wasn't tail strikes. I had been activating my A/P before taking off. That was the cause of the warnings.

I was engaging the AP prior to takeoff, just as I did with the 737 NGX. When I stopped doing that, I no longer get the warning light or horn.

Neither.

It's the aircreation trike at Friday Harbor. I just disconnected the AP and pressed the reset, and that cleared it. #####.

I have taken off with flaps 20, and flaps 15. I put that in my ref page each time. Both times I get the warning light and horn, and no EICAS message. My takeoff speeds are correct, and I set the plane up according to the manual. This is really boggling my mind. For my latest flight, the warning horn did not reset after I passed TA. In fact, it would not reset at all for the entire flight. This is driving me mad.

It is the main red warning light, and I get a constant warning horn. The panel state that I load is cold and dark, and I use FS2Crew to configure the cockpit from the start. When I take off, the trim is in the green.

I have no idea how to select a different panel state. What the heck is that?

If I have the wrong takeoff configuration, I get the warning light the moment I put my throttles forward. This didn't happen until I was in the air, twice in a row.

I am getting a warning light on takeoff, and there are no messages telling me what the warning is. I thought it was an anomaly so, I restarted my sim, and took off again. It still gives me a warning and I cannot reset it! It did reset, but it would be nice to know what may have caused it. I had my flaps set to 15, and the warning didn't start until after I had lifted off. It reset some time after I reached transition altitude.

I just tried to install the 777 version, and it gave me an error saying that the majestic dash 8 has not been installed. Why on earth would it say the dash 8 is not installed when I am trying to install the 777? #####...over?

I entered a route from JFK to DEN, normal stuff. On ascent, the VNAV would not stay connected, and I could not connect it for the rest of the flight.

My VNAV keeps disconnecting. Any idea what would cause this?

My voice command will not recognize the word 'on.' It thinks I am saying 'armed.' I have run the speech recognition software twice for the computer for it to recognize my voice, to no avail.

I have a high end Alienware Aurora. I have the skeleton issue all the time, not matter what livery I am using.

When will there be liveries and support for the 777? I don't see anything on your website with anything concerning the 777.

Every time I try to run the livery manager, it crashes. What am I supposed to do now?

I think that must have been it. I made sure to complete everything on the PERF INIT page for the flight I am starting now, and it is not giving me any troubles.

I have been putting the route, sid and star in correctly now for almost a hundred flights. It has only now begun to give me troubles.

Normally, when start my flight, I engage the VNAV and the LNAV, if it will connect, before I even push back from the gate. Of late, the VNAV disconnects shortly after I push the button. And, once I am airborne and the autopilot has been engaged, I will try to press the VNAV again, and it still disconnects. Not cats were involved..(grin)

I am having difficulties with my VNAV. I try to engage it, and it disengages after a few seconds. I ran the maintenance feature on the FMS and that had no effect. Any ideas?

Disregard, I figured it out. I ran the maintenance on the FMC, and it cleared up.

I cannot keep my vnav connected. Please help.

Ah, I misunderstood that. I thought it was the current OAT at ground level.

I have posted about this once, but I have gotten no responses. I have read some responses on this before, but I didn't get a definitive answer from those posts. When I enter the current temperature in my FMC, if it is not a negative value, the arrival times go nuts. What can I do to prevent this from happening?

I have posted about this once, but I have gotten no responses. I have read some responses on this before, but I didn't get a definitive answer from those posts. When I enter the current temperature in my FMC, if it is not a negative value, the arrival times go nuts. What can I do to prevent this from happening?