New screenshots today showing the main ND/MCDU issue... However, I can see what for me is a big issue too: fuel consumption. 1200 KG during takeoff is absolutely irrealistic.

 

I hope this will be corrected during the next weeks with the ND/MCDU issues as well :good:

never mind ;-)

Me personally, I rather they take their time to make sure it is done right. What is wrong with that? Man, people need to chill-out a little..lol I know it is not possible, but I want a bug-free addon, so to me Aerosoft is doing the right thing here. Please, take all the time you need Aerosoft. In the end, you will have an excellent product.

 

My two cents on this matter.

Please, take all the time you need Aerosoft. In the end, you will have an excellent product.

 

My two cents on this matter.

 

+1

 

Dirk.

Okay, now as they decided to include the aileron/elevator droop they should now try make the position lights at the right place and not somewhere in the wings behind the real light.

 

Then it looks really awesome.

 

 

*do someone of the beta-testers know if they'll make the A321 sharklet? Or maybe the A320 IAE sharklet aswell?

*do someone of the beta-testers know if they'll make the A321 sharklet? Or maybe the A320 IAE sharklet aswell?

 

There was a poll over on the Preview thread at Aerosoft if there should include an A321 sharklet model, and a lot of people had their say, but as for the results.....unknown.

 

Unfortunately a lot of people said no, mostly because they did not read the original post where it strictly told them that creating the new model would not inhibit release in any way. Either way, we'll see I guess, I'm hopeful for it as well.

Maybe someone who is involved with the development of the Aerosoft Airbus can help me?

 

I've been following the development of this add on and would love to buy it but I think I'm right in saying that you must have a hardware throttle? I use an Xbox 360 controller at the moment and it works just fine for my NGX etc. Is it true that I won't be able to use it for the A320?

 

If so, can you explain why? I'm not complaining, I'd just like to understand the processes that you've used that make the throttle different.

 

Thanks in advance...

Maybe someone who is involved with the development of the Aerosoft Airbus can help me?

 

I've been following the development of this add on and would love to buy it but I think I'm right in saying that you must have a hardware throttle? I use an Xbox 360 controller at the moment and it works just fine for my NGX etc. Is it true that I won't be able to use it for the A320?

 

If so, can you explain why? I'm not complaining, I'd just like to understand the processes that you've used that make the throttle different.

 

Thanks in advance...

 

System requirements from here: http://forum.aerosoft.com/index.php?/topic/58780-airbus-x-extended-preview-part-3-new-images-updated-features/

 

System requirements for FSX/P3D (please note the controller, with a throttle axis, and mouse with mouse wheel are absolutely needed)

• Microsoft Flight Simulator X (SP2, Acceleration Pack or Gold Edition), Lockheed Martin Prepar3D
  
• Windows XP, Windows VISTA, Windows 7 all fully updated, (64 bit version highly recommended)
  
• 3.0 GHz processor (Dual Core processor or equivalent system recommended)
  
• 2 GB RAM (4 GB recommended)
  
• Mouse with mouse wheel
  
• 3D Graphics Card with minimal 512 MB (2 GB recommended)
  
• Control unit (joystick) with throttle and rudder control
  
• Download-Size: 1 GB
  
• Installations-Size: 2.2 GB
  

 

So yes, you will need a throttle axis. The reason being how the FADEC is modeled, and it not using the default FSX method.

Kyle,

 

Will you be able to have FSX controllers disabled in FSX and all the controls via FSUIPC, even if it means sending the axis directly to FSX? It's basically the same thing.

There was a poll over on the Preview thread at Aerosoft if there should include an A321 sharklet model, and a lot of people had their say, but as for the results.....unknown.

 

Unfortunately a lot of people said no, mostly because they did not read the original post where it strictly told them that creating the new model would not inhibit release in any way. Either way, we'll see I guess, I'm hopeful for it as well.

 

Thank you. That means we have to wait and then we'll see.

I've pre-ordered this baby months ago and looking forward on the release date.

I'm a Boeing guy and

that PMDG B737NGX which i've mastered..... gets boring sometimes.

I want to test my skill on this new Airbus shark.

 

Kin M

Kyle,

 

Will you be able to have FSX controllers disabled in FSX and all the controls via FSUIPC, even if it means sending the axis directly to FSX? It's basically the same thing.

 

Word Not Allowed, do you think that could be a way around using the A320 with the Xbox360 controller?

Re the A321 with sharklets. If I remember correctly, Mathijs said that it won't be in the initial release because he would have to use the modeller from the twin otter project. So rather than slow that project down, it would be done for SP release.

Kyle,

 

Will you be able to have FSX controllers disabled in FSX and all the controls via FSUIPC, even if it means sending the axis directly to FSX? It's basically the same thing.

 

Yes, I have done and tested that.

Maybe someone who is involved with the development of the Aerosoft Airbus can help me?

 

I've been following the development of this add on and would love to buy it but I think I'm right in saying that you must have a hardware throttle? I use an Xbox 360 controller at the moment and it works just fine for my NGX etc. Is it true that I won't be able to use it for the A320?

 

If so, can you explain why? I'm not complaining, I'd just like to understand the processes that you've used that make the throttle different.

 

Thanks in advance...

 

Well, since you politely asked unlike some of the other people, I will take the time to explain.

 

FSX has default throttle axis and only one channel for throttle.

 

The Airbus has throttle "detends" as they call it, so in order to properly simulate the throttle detends we need two channels for throttle (One for user throttle - INPUT, the other for the ATHR to control thrust - OUTPUT). The question is where do we get the channel? The answer is we intercept the channel. However, with this, unfortuanely we loose compatibility with the keyboard keys.

 

I am still investigating ways to implement keys, but that is extremely low priority, so don't hold your breath.