I think the VC is also excellent and I particularly appreciate the variety of internal and external views which are offered. Overall, I'd give it 9/10 considering the amazing complexity of the systems.

 

 

The VC looks great to me too. Im on a 30" Dell Ultrasharp at 2560x1600 with a Geforce 670 and Kostas Inspector settings. I use Trackir and like my pilots eye view zoomed in pretty close to try and get the displays as close to life size as possible, and its looking great so far. If I zoom the VC way out as if Im standing in the door then yeah the hand drawn aspect of it stands out, but I never fly standing in the door. Shade for FSX is also helping to add some additional depth to the VC for me.Took the NGX off my system last night, just really kind of bored with it. This is new and refreshing, and will due till the FS Labs version comes out for myself.

 

I use the Saitek TPM throttle and the Bus throttle works perfect with it out of the box with stock FSX assignments. Also the landing gear lever and some of the lighting switches on my Saitek switch panel work with it too stock out of the box. The MCDU works perfect on the iPad. I have not ove into the systems yet, but so far Im stoked. Gonna take it slow though as TacPak just landed too on my system and Ive got 500 pages of Wiki to read on that as well :blink: So far Im pleased with this Bus :Applause:

Thanks

 

I'd be very interested to hear what others get for this. Just put the 320 on the runway and load the 'ready for takeoff' option. No other setup - just that, then firewall the throttles with your hardware.

 

I haven't tried using the pre-defined ready for takeoff state, but in the cold and dark procedure flow, the system automatically sets a rather high default flex temperature, which would account for the low N1.

 

If you don't want to use the default flex temp, you may enter a lower value on the INIT page, which should give you more available thrust at the t/o throttle setting.

Some of these snap reviews and rants are so embarrassing.

 

Rants???

 

Some people have bought a new flightsim toy and they're comparing notes about it on a flightsim forum.

 

Why's that embarrassing to you?

ND problem...Instead of displaying information about my next waypoint, it has data about the first one I flew...any ideas?

 

http://i.imgur.com/ruwPq.png

 

Bump.

Try the official support forums?

Bump.

 

Know problem that's being worked on...check the offical support forums.

What is your flex temperature? I believe the FMC automatically sets flex, this might be the cause of your low N1. BTW, you shouldn't firewall the throttles in an Airbus, you need to set the throttle lever to the proper detent

Every *attempted* ;-) flight thus far has been out of San Diego, so I'm pretty sure that's not the issue. N1 at 85% is NOT enough at KSAN even with 1/2 load!

I flew into WSSS last night with the A320, massive tropical storm, had to perform a missed approach and tried a second time. It was great fun! I am an MCE user, for those who have it, the aircraft works with voice control already as most of the commands for it are the same as the previous A320X, I could even get engine start and changes to the system displays via voice control.

Very handy when the cockpit is swaying so wildly I could not put the mouse cursor on a button to press it! Looking forward to that Hotfix, but so far am enjoying this bird.

 

woops sorry if it's a stupid question or maybe already answered earlier in this thread, i read most of it but probably not everything, also most of you have probably have good specialized flightsim hardware and dont really care about this kind of issues.

 

i was maybe interested in buying this aircraft but after reading around it seems it will not work if you have only a 'simple' joystick with only 2 axes (which would already be used for aileron and elevator control) and or a gamepad because, for some reason, the throttle system is very different from any other addons available today and require a dedicated axis (to my limited knowledge i think even more complex addons than AirbusXt would work without that limitation).

 

i saw also there is a file in the library to allow throttle control by button, but once again i think it requires fsuipc registered which i don't have either (yeah i know it's only xxx $, but it all sums up hehe)

 

is that true or did i misunderstood the issue ? i'm not that much into that technical stuff

 

i would appreciate any information about this, don't want to buy something i would not be able to use. Thank you in advance

 

take care and happy xmas to everyone !

Every *attempted* ;-) flight thus far has been out of San Diego, so I'm pretty sure that's not the issue. N1 at 85% is NOT enough at KSAN even with 1/2 load!

 

Whether you are at KSAN or not won't matter. The FLEX temperature isn't the actual outside air temperature... it is a performance setting in the FMS... the same setting which on a Boeing aircraft is known as "assumed temperature".

 

In other words, you are instructing the engine performance management system to "assume" that the outside air temperature is much hotter than it actually is, in order to force a reduced thrust takeoff.

 

By default, the Aerosoft Extended Airbus will automatically set the FLEX temp to 67 degrees C, unless you, the pilot, set it to a lower number.

 

When you start on the runway threshold using the "Ready for Takeoff" situation file, BEFORE advancing the throttles, open the PERF TAKEOFF page in the MCDU and check the number adjacent to FLEX TO.

 

I'll bet you'll find it is set to "67". If so, enter a lower figure... say "30" on the scratchpad and press the line select key next to the FLEX TO prompt. This should give you pretty close to maximum available thrust for your takeoff, so that you'll get airborne properly, instead of sliding nose first through the MCRD parade ground!

Whether you are at KSAN or not won't matter. The FLEX temperature isn't the actual outside air temperature... it is a performance setting in the FMS... the same setting which on a Boeing aircraft is known as "assumed temperature".

 

In other words, you are instructing the engine performance management system to "assume" that the outside air temperature is much hotter than it actually is, in order to force a reduced thrust takeoff.

 

By default, the Aerosoft Extended Airbus will automatically set the FLEX temp to 67 degrees C, unless you, the pilot, set it to a lower number.

 

When you start on the runway threshold using the "Ready for Takeoff" situation file, BEFORE advancing the throttles, open the PERF TAKEOFF page in the MCDU and check the number adjacent to FLEX TO.

 

I'll bet you'll find it is set to "67". If so, enter a lower figure... say "30" on the scratchpad and press the line select key next to the FLEX TO prompt. This should give you pretty close to maximum available thrust for your takeoff, so that you'll get airborne properly, instead of sliding nose first through the MCRD parade ground!

This is some interesting stuff, Jim! The only issue I am encountering is with the "reverse thrust" effectiveness, it only reaches 31%. Moreover, there seems to be little to no effectiveness. Do you have any ideas on increasing or bettering the effectiveness ?

This is some interesting stuff, Jim!

 

I don't know if that default 67 degree FLEX temp is something you would see in a real Airbus, or is just specific to this initial version of the Aerosoft aircraft. I tend to think the latter. I've seen some comments on the Aerosoft forum that even if you do select a lower flex temp during MCDU setup at the gate, that is sometimes will change back to 67 degrees during taxi, so I'd advise re-checking the settings on the TAKEOFF PERF page before taking the runway.

 

Just purchased it last night, and haven't had a chance to do more than a couple of quick test flights as of yet. The aircraft has a few quirks in this first release, but it's head and shoulders above any other FSX Airbus that has come to market so far. That will undoubtedly change when the FSL product comes out.

 

Not sure about the reverse thrust effectiveness issue, or how that might be changed. Probably a question for the developers forum.

 

As I do with any new add-on I buy for FSX I've been doing my initial test flying from the 15,000 foot runway at the Southern California Logistics airport. (KVCV) I was once stationed there in real life when it was still George AFB, so its my favorite testing ground. I actually haven't tried using reverse thrust on the aircraft yet... no need on that long runway!

Seems like I can't control my rudders with my previously working controls with the Airbus X?

 

With my Attack 3 joystick. I've set my left and right buttons to yaw the rudder left and right accordingly. With the Extended, the rudders seem to be held down centralized.

 

I thought it may be the auto rudder but it's turned off in settings>realism. And I've even tried to toggle the auto rudder on and off in flight.

 

I'm still unable to steer the plane to taxi. Anyone having this problem?

I wonder how many bugs the FSLabs offering will ship with. It's even more complicated so would have thought it might have even more problems initially. Not sure how performance will suffer for that extra detail either. This may end up being the good mid-way point.

This is some interesting stuff, Jim! The only issue I am encountering is with the "reverse thrust" effectiveness, it only reaches 31%. Moreover, there seems to be little to no effectiveness. Do you have any ideas on increasing or bettering the effectiveness ?

 

I think this coincides with the Auto Brake problem I reported! What I discovered is the Auto brakes do engage, but will disengage if thrust reversers are used.