Hello,

 

Could someone please help with a good merge for the Project Airbus and IFDG to use the Wilco Panel.

 

Thanks In Advance

 

 

Mark Oxley

Mark, I prefer using Project Airbus' FDE to Wilco's. My "merge" is limited to a few key areas:

 

1. Replacing PA's flaps.0 section with Wilco's one. However, the lift and drag scalars in this section should be kept at 0.0. This is only so that the panel stops thinking that flaps are incorrectly set.

 

2. Adjust the 1503 and 1504 tables in the airfile so that the N1 cap is removed (this is specially helpful in the A319).

 

3. The PA A321 is way too underpowered... that's because someone wrote an incorrect thrust value in the CFG file. Replace it with the correct one (you may find the value in Airliners.net or Airbus).

 

I'm currently at work, so I don't have access right now to my FS files. I've never tried merging iFDG, the repaints I need are already in Wilco or PA.

 

Hope this helps.

Hi Luis,

 

Thanks for the info.

 

If possible could you post the changes or send me the file.

 

Thanks again for you help

 

Kind Regards

 

Mark Oxley

Mark, these are the values for the A320:

 

Default 1503 and 1504 values:

 

Table 1503 (Low Mach CN2 vs throttle and IAP ratio):
0.000000 1.000000 22.570000
0.000000 58.500000 71.145510
0.250000 82.500000 82.500000
0.420000 85.847763 85.854828
0.550000 88.293106 88.283646
0.700000 91.196724 91.186569
0.800000 93.384369 93.420059
0.900000 95.564835 95.546463
1.000000 96.900000 98.056023

Table 1504 (High Mach CN2 vs throttle and IAP ratio):
0.900000 1.000000 4.000000
0.000000 80.734420 81.380000
0.250000 82.259689 82.310852
0.420000 83.758583 83.801346
0.550000 85.764839 85.813637
0.700000 88.593903 88.622635
0.800000 91.045898 91.019493
0.900000 93.607498 93.652138
1.000000 96.683311 96.804893

 

And these are the modified ones:

Table 1503 (low Mach CN2 vs throttle and IAP ratio):
0.000000  1.000000   22.570000
0.000000  58.500000  71.145510
0.250000  83.372678  83.372678
0.420000  87.373355  87.380545
0.550000  90.347811  90.338131
0.700000  93.897803  93.887348
0.800000  96.545367  96.582265
0.900000  99.203991  99.184920
1.000000 101.000000 102.204936

Table 1504 (high Mach CN2 vs throttle and IAP ratio):
0.900000   1.000000   4.000000
0.000000  80.734420  81.380000
0.250000  83.129825  83.181529
0.420000  85.247048  85.290571
0.550000  87.760708  87.810642
0.700000  91.217892  91.247475
0.800000  94.127741  94.100442
0.900000  97.172118  97.218458
1.000000 100.774143 100.900869

 

A318 and A321 should have similar values. Hope this helps. Take into account that this was done only for CFM engines, I haven't tried with IAEs.

Mark, I prefer using Project Airbus' FDE to Wilco's. My "merge" is limited to a few key areas:

 

In general that is not a god idea! Complex system models are generally tied to their FDE's Using a different FDE can result in anything from the flight computer calculating the wrong values, to unexpected erratic behavior! When merging a model to panel with complex systems, you should merge model to panel, not the other way around. Replacing only, the contact points, lights, exit and in some cases the view section of the replacement models aircraft.cfg file (In this case the PA A320) should be replaced into the complex models aircraft.cfg file (In this case the Wilco a320). This will ensure the aircraft behaves the same as it was designed to.

Agree with Tom. Also, don't forget the tail hook and folding wings section of the PA config... If it has it. This is often used for extra animations, like cargo doors.

and after all the merging tricks, it suddenly crashed to desktop whenever ending a flight (in windows 7 64)... no cures until now

and after all the merging tricks, it suddenly crashed to desktop whenever ending a flight (in windows 7 64)... no cures until now

Almost always I get a CTD when ending a flight, in both Win7 32 and 64 bit editions. I don't know if it's just placebo, but if I turn off the FD and leave the aircraft with only external power, the chances of getting a CTD are reduced.

 

In general that is not a god idea! Complex system models are generally tied to their FDE's Using a different FDE can result in anything from the flight computer calculating the wrong values, to unexpected erratic behavior! When merging a model to panel with complex systems, you should merge model to panel, not the other way around.

This is how it should be, and this is the way to go if you'd like to keep using the load manager and fuel planner. But knowing Wilco's vol.1 FDE (which had to be tweaked anyway).... I just "broke the rules" and I'm satisfied with the results. For vol.2 you have to do it as it should be done; a simple alias would not work (or at least not with Posky, I'm not sure Overland), the FBW could not keep with the aircraft.

 

Now that I think about this, I should pay more attention to the values in the MCDU to see if there is too much difference between the predicted and actual (FS) values. Last time I ended up arriving 50 mins later in a 5-hour flight with an A319. I'll try again with the stock Wilco FDE.

 

For Mark, this is how the merge should be done:

http://www.flightsim.no/ubbthreads/ubbthreads.php?ubb=showflat&Number=426245

Thanks for all the advice.

 

Luis, thanks for the link you sent me, I will give it a go over the weekend and post the results.

 

Thanks again for all the help.

 

Mark Oxley