If you use FSinn, I would also suggets to run it as administrator, do not start FSinn from the FSX menu. And check on what Kevin said, that is important too.

Then what's ivao usa all about?

Its a good question, cause looking at the traffic levels over there IVAO usa cant be very busy. They get far less traffic than what I get on the north pole on vatsim!

Edited February 1, 201214 yr by Sekstifire

I agree

I use FSINN with VATISM, with no issues when running the NGX, so it certainly is a config issue for the warnings etc(the only problem i get is more likely to get OOM errors when on VATSIM)Now , as you say that you are able to take off with no warnings when not using an online client it does sound as if there is maybe a keycommand issue maybe, what I mean is that maybe keys/joystick buttons etc that you are using are also mapped maybe to your online client(sB or FSINN) and thus they are maybe overriding or changing settings on the aircraft when you use them. So for example perhaps you have your trim adjust set to a key that is duplicated and thus when you either type or use it its adjusting the trim also, hence being outof trim by the time you come to take off hence the horns and crash on rotate.You dont arm the spoliers in the NGX, they will automatically come on should you do a RTO, in the MD11 and 767 you do. you only need to arm them when landing in the NGX, people are carrying over practices from other aircraft and the 767 is very very different from the NGX.other things to look out for when taking off if you use seperate throttles for your engines, is that when you apply takeoff, that both engines are spooling up to the same amount, you can end up with one engine either spooling up wrong or spooling down if your controlers are not congigured correctly, this will cause a horn, and autothrotle to disconnect.regards the flap settings - takeoff flaps will vary depending on a number of things, including SOPS. on average most departures out of reasonably long runways, on a average temperature day, with average load could take off with flaps1 - however some company SOPS specify minimum flaps for take off as being flaps 5. That said a short runway with, different load, and temps etc, could require a flaps 15 or even 20 for departure. So there isnt a "Correct" flap setting as such.So quick things to look forAre your flaps set to somethingIs your trim in the green band (often around 5)are both your engines spooling up to same amount when TOGA selected.Spoilers are down and not autoarmed.Doors closed.Generators and Yaw Damper onParking brake off, and chocks off.

Did you install FSCopilot first? If not, you need to.Whats wrong with that? I use 10 almost all the time without an issue.

sure did and i can see the controllers freg and i get atis and weather but they cant seem to hear me. I went to the area to set up your ptt switch but still no joy

May I give You one triteness advice:AviateNavigateCommunicate

You dont arm the spoliers in the NGX, they will automatically come on should you do a RTO, in the MD11 and 767 you do. you only need to arm them when landing in the NGX, people are carrying over practices from other aircraft and the 767 is very very different from the NGX.

You don't need to arm speedbrake for takeoff in any Boeing, 767 included. It's an Airbus and Douglas thing. If you're not getting a config warning by doing so on the LDS 767 that's all well and good, but an RTO will work just as well if you don't.

The warning which was triggered was pretty sure the takeoff warning. So something wasn't set to takeoff configuration. As you're talking about having problems to control the aircraft maybe you forgot to set your flaps. When flying my first few VATSIM flights I also forgot some tings because of the high workload. That'll change when you get used to VATSIM with the time.I don't beleave that your problem is caused by the VATSIM software. You surely only forgot to do something which was relevant for your takeoff. Try it a few times more, maybe it'll wort better then.

+1 sounds very much like no flaps and then also stallingIan