Project Airbus – Talk

But here is my question. Recently, I always fly the a380 almost everytime i fire up fsx. It is really good model that i always record and then watch my flights to see it majestic beauty especially when landing. Now when it comes to cruising at ideal cruise level, it always comes to my mind that &qu...

Edit the panel.cfg:

[fltsim]
alias=vasfmc_panel_a320

Google for an utility called Windows Installer Clean Up - with this tool you should be able to remove the installation informations of FSX, and this should fix the installer problem.

You can try to change the n1_correction_factor value in the a320(a320-project-airbus).cfg file in the vasfmc\aircraft_data folder.

You have to install FSUIPC, because without FSUIPC you will have problems with vasFMC. Have you tried to install the actual version of FSUIPC? Have you updated FSX with SP1 or SP2?

OK, that's an easy one to correct. Thanks, but the speed control is still a problem. Any suggestions about the settings values? I've tried it with both a/thr = vasfmc and FS9 but still get he same problem Really hard to say what's wrong - a few things could be the reason. If possible post a screen ...

The original panel was/is from Ken Mitchell - go to the AVSIM library and search for ab320km_panel.zip, and maybe also for km320upd.zip. You will find the sound files in the first zip, but you will have to add the dsd_xml_sound2 gauge to the panel.cfg to play the sounds, and there could be conflicts...

to add to the frustrations I now have a new problem. In the standalone version both the PFD & ND displays are lost when FS9 becomes active. The image in both windows is replaced with "ATT" in red. If I kill FS9 the PFD and ND come back to normal. The PA Airbus with the VASFMC panel su...

Very strange thing: there is something wrong with the scale part of the displays (gauges), because the correct x:y is coupled with the resolution of FS; only in a 4:3 resolution the displays will draw correct. I have tried a few tricks, but nothing seems to fix this problem.

Should be no problem though - post your [Window00] section of the panel.cfg.

Have you ever read the vasFMC docs?

You have to change the structure of the datas, and you have to rename the new cof file to wmm2005.cof. If you want to have the corrected file, send me a PM.

It seems that you have installed Adobe Air, because the air file is handled as an Installer Package - uninstall Adobe Air, and I guess that it will work.

Thank you!

Have you checked the Advanced Stuff section of the vasFMC documentation?

awesome!

Thank you guys!

I guess that the needed VC textures are missing in the texture folder of the ANA livery. Compare the texture folder of the ANA livery with a working livery, and you will see the difference. Missing files are: cabin_l.bmp cabin_t.bmp floor_l.bmp floor_t.bmp glass_cabin.bmp pax_t.bmp paxt_l.bmp VC_A38...

Regarding your HUD problem: I don't have this HUD gauge, but the entry in the panel.cfg seems to be wrong. With gauge65=jg_hgsa, 301,0,302,311 you do not call the subgauge, you call only the gauge name itself, and so FS is not able to find the subgauge. I am not 100% sure about the real subgauge (HU...

As for point 8: I have fixed the flickering - it was caused by a very small text box problem in the EWD, which caused an overlay problem in the SD. I cannot attach a file here in the forums though, but if an Admin or Mod could contact me via email, I could send him the corrected ecam.xml.

I don't know exactly when the last gauge update was released, but I think it was in June or July. The vasFMC website is gone, so all download links from there are also gone, but maybe someone has uploaded the files to one of the big flightsim sites.

What do you mean with "the newest version of vasFMC", do you mean v2.1 or the latest gauge update which was available in the vasFMC forums? With the updated gauge the lockups and CTDs should be gone though.

As for point 3 you have to play with the flap_limit_power setting in the gear_warning_system section of the aircraft.cfg. I would start with a value >25, this should work fine with flaps <=2, for flaps 3 and FULL you have to use a higher value, or you can disable the gear warning if you set gear_war...