I have searched alot for this and found a few downloads that didn't work for me when i tried it before for Wilco panel and Overland model merge. I have tried this before and wasn't too good for me, anyone else use it? (it's on this page): http://www.flightsimworld.com/downloads/listfiles/aircraft-panels/1.htmlTo do this merge by myself, do you just use the same method as the Wilco-Project Airbus merge (which worked fine for me, but I just like the overland model a bit more)?Wilco-Project Airbus merge: http://www.airsimmer.com/support/index.php?showtopic=406

Any help with this one?I too am having problems merging the SMS/Overland A319/A320/A321 with the Wilco Panel and flight dynamics. Main issues appear to be contact points and lights, SMS aircraft without merged Wilco data are fine. As background I have successfully merged PA/IFDG Airbuses with Wilco A32x, POSKY A330/B77E/B77L/B77W with Wilco/PSS respectively and fiddled my PMDG B744 aircraft config to make it a B774ER for those long LAX-MEL MTOW runs!! In short I am not a beginner at this.Process followed (simpilfied):1. Copy Wilco Aircraft Config, Panel folder and Air file to SMS Directory2. Contact Points, Lights, Effects, Exits, Viewpoints, Tail hook, Wing fold sections of SMS aircraft file copied. Same sections removed from copied Wilco aircraft config.3. Added SMS details from 2 into copy of Wilco aircraft file. Result = SMS model, Wilco Panel, Wilco .AIR and merged Aircraft config (Contact Points, Lights, Effects, Exits, Viewpoints, Tail hook, Wing fold from SMS, everything else from Wilco)Problem is when the merged aircraft is loaded it just drops through the runway and lights are way above where the should be. For anyone who has this merge working, would you mind providing your contact points and light points from A319/320/321 IAE and CFM to me please?Any replies will be greatly appreciated.ThanksSteve

Hi,actually there is a person who is very good at merging panels. He did the A321 very very nice and no doubt one of the best merge out there and is continuing to do the A318/319/320 series. Check it out here,he is currently working on the A330/A340 series too if you are interestedhttp://nl.forum.ivao.aero/index.php/topic,162763.0.htmlHe also did the mega 777 merge too,very impressive!

In short I am not a beginner at this.

Then you should know that with 95% of all merges you'll need to edit light and contact points, Among other things.Out of all my merges, I don't believe I've ever not had to.

Hi,actually there is a person who is very good at merging panels. He did the A321 very very nice and no doubt one of the best merge out there and is continuing to do the A318/319/320 series. Check it out here,he is currently working on the A330/A340 series too if you are interestedhttp://nl.forum.ivao...c,162763.0.htmlHe also did the mega 777 merge too,very impressive!

Thanks for this Sk1nNy, very helpful.

Then you should know that with 95% of all merges you'll need to edit light and contact points, Among other things.Out of all my merges, I don't believe I've ever not had to.

Don't know what merges you have worked on in the past Geddy. With PA A318/319/320, IFDG A319/320/321 and POSKY A330, all with Wilco, the default contact points and lights from the freeware aircraft all work fine without modifcation. My understanding is that contact points and lights relate directly to the .mdl in the model folder. Therefore if you use a POSKY model, POSKY contact points and lights are required. SMS are the only models I have ever had issues with. Happy to be corrected with a constructive response instead of an "I know better than you" one.Steve

Contact and light points are edited via the aircraft.cfg.If your using the POSKY model with the POSKY cfg file you won't need adjustment. POSKY model with the PSS or Wilco cfg file will/should require some minor adjustment. The reason your falling through the tarmac is because these adjustments are needed.

Contact and light points are edited via the aircraft.cfg.If your using the POSKY model with the POSKY cfg file you won't need adjustment. POSKY model with the PSS or Wilco cfg file will/should require some minor adjustment. The reason your falling through the tarmac is because these adjustments are needed.

Thanks Getty. This makes much more sense to me, I think maybe you had misread my original post.Having downloaded andplayed around with the merge for the A321 that Sk1Nny linked above, I can now confirm the following about the SMS AIrbuses:

1. Wilco weights in the Aircraft config are in KG's, SMS are in Lbs. If you put the Wilco [WEIGHT_AND_BALANCE] section of the aircraft config file onto the SMS with SMS Contact points the aircraft falls through the runway. Presumably this would require a tweak of the contact points. Converting those exact weights from KG to Lbs and inserting in config results in no falling through the runway.
2. If you use the SMS [WEIGHT_AND_BALANCE] in the merge, everything works. ZFW's can be modified in Lbs via the aircraft config.
3. Using the principles learned above, I merged the A319/320 but Wilco FBW Autotrim fails to work while on approach and the bus seemed very overpowered. Using OPT CLB function I was getting in excess of 6000fpm climb rate below FL100 on the A319, 3000fpm at TOC (FL340). This for a 62 tonne A319 with massively reduced takeoff and climb thrust - not sure if this is truely representitive or not?

Content to upload my merged aircraft configs for the A319/320 if anyone wants them but I will stress they aren't perfect.Steve