What I have concluded is that the new gauge file is tied to the model file, and it will not accept any other model file.

Scott, I don't have the addon in question, but here are three suggestions:1) Did you keep the "title=" lines in the aircraft.cfg similar to the ones you had in Feelthere's aircraft? As an example, the title of the stock A320 IAE (the one with the Airbus colors) is this one (I hope I don't upset anybody for doing this):

[fltsim.0]title=Feelthere A320 IAE Airbus House

In your merged aircraft.cfg, put the title in a similar style, i.e., copy-paste the title and change the "Airbus House" bit for whatever you like. The "A320" and the "IAE" depend on the aircraft and engine, obviously. That's something I've learned not to overlook when merging aircraft panels and models. Gauges love to be tied to this line, I know PSS aircraft present this "problem", I don't know if Feelthere does so.2) If this fails, why don't you try to do a RFP-style merge? The Ready for Pushback 747-200 gauges are tied to the model (that's what I've read here), so when they want to merge it, they put the RFP's model file in the merged aircraft model folder. Therefore, in the folder will be 2 model files. What I want to say with this is just copy Feelthere's model file (for the IAE A320 is called A320IAE.mdl) and paste it into your, let's say, Project Airbus A320 IAE\model folder.3) I don't know in which order should this be, this is the most time-consuming one: Uninstall your Airbii, undo your merges, reinstall both Wilco Airbus volumes (1 and 2), install Eric Marciano's addon and finally do the merges.Hope this helps, let us know if so.Best regards from Colombia,Luis Miguel

Luis, You have been much help. I am going to try these things a little later today and I will let you know. Thanks for the reply buddy! :)Scott

Luis,I have done all the items on your list and unfortunately no luck. I thought putting the model file in the model folder would have done the trick but I guess not. The throttle on the ground is still uncontrollable and when in the air it drops to idle and will not hold speed or any throttle setting range. Again, everything works fine when your in the 2d cockpit, but as soon as you change to vc or outside view... problems. It's wierd. Thanks for throwing out some ideas though. Got any more? :( Scott

Anyone else have any ideas? There must be some people out there that are good at merges.Scott

Try doing a refined search Scott, Ive posted more times on various forums than I care to admit about merges.If it's a plain simple model merge not worrying about VC's it's relatively easy.Currently I run the PA/Wilco A318-A320 Merges.

But do you have Eric Marciano's upgrade? I used to have the merge working just fine too. But then the upgrade messed everything up. Works fine with wilco models but nothing else.Scott

I've been continuing work on this and it seems like the problem definitely is in the .gau file that lies in the panel folder. It seems like the throttle control does not act appropriately with any other model merged to it. It acts ok in the 2d view but none of the other views. Is there any way to read the .gau file to see what is different between the upgrade .gau file and then the regular wilco .gau file?Scott

But do you have Eric Marciano's upgrade? I used to have the merge working just fine too. But then the upgrade messed everything up. Works fine with wilco models but nothing else.Scott

I do actually.

Do you mind PM'ing me your panel.cfg and stuff you used to do the merge? Or tell me how you got it to work. I tried putting the PA model in the wilco model folder instead and do it that way but it still didn't work. Scott

One thing I have noticed is that a lot of people have had my same exact throttle issue. Fortunately I never had it without the upgrade, but then it became evident WITH the upgrade. So the upgrade kind of created the problem. I do not have a registered FSUIPC so that should not be the conflict, which it seems for everybody else it was. Without the registered FSUIPC (which I'm not going to pay 35 USD) for there is no settings besides some stuff for weather. So that should not be the problem right?EDIT: I also just found out that the throttle is totally dependent on the virtual cockpit with eric marciano's upgrade. This is why it doesn't work with the project airbus, which does not have a vc. I found this out because I deleted the virtual cockpit out of the original wilco model to save on frame rates and the throttle surges and acts inappropriately outside of 2d view just like with the merge. So this sucks. I don't like the virtual cockpit and we have to suffer having it hogging down on frame rates just so the d**** throttle acts the way it's supposed to. Scott

Hate to blow holes in your theory but.. I've removed all my VC's and still run the Wilco/PA Merge with the Marciano MCDU update.I do also run a registered version of FSUIPC.When doing your merge, You replaced themodel withing the Wilco folder, Which air file are you using. Which aircraft cfg are you using?

It's ok if you blow holes in my theory. Lol. I just want to figure this stupid thing out. I have done it three ways.1.) Take the contents out of the wilco panel folder and put them into two separate panel folders in the PA A320 for example. So there would be panel.iae and panel.cfm. Then I copy all the necessary things from the wilco aicraft.cfg to the project airbus aircraft.cfg (flaps, autopilot, engine data, reference speeds, flight tuning etc.) I have also added the model file from the wilco model into the PA model file just to see if it was tied to the feelthere.gau but it didn't work. I am using the feelthere panel.cfg (just copied it from the feelthere panel folder). I also copy and paste the FDE from the wilco model into the PA folder and use that one. One for each panel, iae goes to iae and cfm goes to cfm. 2.) The other way I have done it is I just added the project airbus model into the feelthere model folder and tried using it that way. That didn't work either (same throttle problem). 3.) I have also tried keeping the iae and cfm variants in seperate folders for the project airbus and that didn't work either. I have also tried everything that has been mentioned in this thread so far. I am using the Saitek Pro Flight Yoke System with throttle quadrant if that makes a difference which I doubt. It's just funny because before the upgrade my merge worked, after the upgrade... nothing. Not to mention after the upgrade I cannot remove the vc on the wilco model because the throttles start acting up. That's what made me think this is all tied to the VC. My merge works fine in the 2d view as I have mentioned many times. It's when I go into the vc view or outside view when things go to hell. I have seen others with this problem with just the regular wilco, and they also refer them to something being tweaked in the registered version of the FSUIPC, but I do not have that so it can't be the culprit... whew.Scott

You did the obvious step of reinstalling everything from scratch, right?Let's have a look at your panel and aircraft configs from the CFM version. Also, what's in your panel directory? Do you have all the files that should be there (gau & lsp)? What are their timestamps/sizes?

I have re-installed and started with a clean slate 3 or 4 times. I am going to go ahead and attach the panel and aircraft.cfg's. They are from the merged project airbus A320 cfm variant. My current set up at the moment is keeping the A320 IAE and A320 CFM in two seperate folders. For Example in the main aircraft folder there is Project Airbus A320 IAE and then Project Airbus A320 CFM. I have tried the other ways too, keeping them both in one folder and moving the model folder into the wilco folder. The list for my panel folder is:A320CFM_feelthere.gau time stamp: 4/4/2010 10:39AM (The reason for this is probably because I have done a fresh install today and have tried it again)A320CFM_feelthere.lsp time stamp: 12/19/2008 12:35PMMain_BG.bmppanel.cfg time stamp: 4/4/2010 10:39AM (I haven't made any changes to it that's probably just from the fresh install)panel.lsp time stamp: 06/23/2007 4:46AMZOOM.bmpand a thumbs file. The size of the Feelthere.gau is 18.6MB. The feelthere.lsp is 18.5MB and the panel.lsp is 9.20KB. Size of the panel.cfg is 9.45KBI had to copy and paste the .cfg's into a text file to upload because it would not let me upload a .cfg extension.Thanks,Scott

I've gone through all the files, they're the same as on my install. We do have some differences in our aircraft configs. I have the jet engine thrust scalar set to 0.95, as opposed to your 1.0 and a completely different airplane geometry section (I might have copied over feelthere's, can't be certain), here it is for your reference, if you feel like troubleshooting:[airplane_geometry]wing_area=1317.503wing_span=111.833333wing_root_chord=13.76wing_dihedral=3.298901wing_incidence=-3.5wing_twist=-1.600000oswald_efficiency_factor=0.745 wing_winglets_flag=1wing_sweep=25.0000wing_pos_apex_lon=16.813 wing_pos_apex_vert=0.70000htail_area=333.681htail_span=41.666667htail_pos_lon=-57.33688htail_pos_vert=6.500000htail_incidence=1.500000htail_sweep=0.000000vtail_area=231.424vtail_span=17.991665vtail_sweep=0.000000vtail_pos_lon=-54.51698vtail_pos_vert=19.915elevator_area=76.500000aileron_area=57.0rudder_area=56.200000elevator_up_limit=25.0elevator_down_limit=15.0aileron_up_limit=25.0aileron_down_limit=15.0rudder_limit=25.0elevator_trim_limit=13.5spoiler_limit=50.0 //35.0spoilerons_available=1aileron_to_spoileron_gain=1.5min_ailerons_for_spoilerons=12min_flaps_for_spoilerons=0same goes for our brakes, mine are set to:[brakes]toe_brakes_scale=0.86parking_brake=1Our panel configs are exactly the same. Those are the only differences I've spotted in our installs.If this doesn't help, then the only other explanation is that the problem is hardware or hardware-to-software related - something is commanding the throttles to idle. There's just no other probable cause that I can see.