Mack,Do you have the registered version of the FSUIPC?Scott

Yep.

Hmmm... the two people that have the upgrade merge working have the registered FSUIPC. Do you think this accounts for anything?Scott

Hmmm... the two people that have the upgrade merge working have the registered FSUIPC. Do you think this accounts for anything?Scott

It might have something to do with it. Hard to tell. I don't recall having anything specific set in FSUIPC that would make a difference, I only ever registered it to support Pete's development of it and left it "as is". I don't think any add-ons ever required that FSUIPC be registered for them to work properly, I don't think it should matter in any way here.

I have no idea what it could be then. I have the same problem on a totally different computer with a different yoke on it. So I don't think it is hardware related. I wonder if it conflicts with another add on or something.Scott

There is plenty of other people with the same problem I have found searching the forums. And their queries are just ignored by the development staff. The FSUIPC settings seem to be pretty confusing so I'm going to have to read up on it but I doubt it will help. It didn't help other people. Scott

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

Alright last stab at the cat here.Replace the Wilco model with the PA one. You need to use the wilco.air file and cfg data.The only thing from the PA cfg you need to use is the contact points and Lights. That's it.I can even send you my data later.But I've found changing or mixing general flight data screws alot of things up.I can't see a registered FSUIPC being the golden fix here so I think it's something in the merge.

Well guys,I appreciate all your help but for some reason my problem is directly related to the virtual cockpit. If there is no virtual cockpit then there is the problems. I found this out because I was tired of the virtual cockpit in the wilco models hogging up all the frame rates so I took them out with the hex editor. The throttles act the same with the wilco models as they do with the merge. So for some stupid reason, my upgrade ties itself to a virtual cockpit. I'm stuck.It must be my version of the upgrade if you guys don't have that problem. Because it is not a hardware issue because I have tested it on two different computers with two different yokes.Scott

Hello Everybody,I gave up on this topic for awhile but I am eager to get back into the airbus and do not want to fly with a virtual cockpit I don't use and the hideous models of wilco. Is there any reason the logic of my throttles would be tied to a VC? And why is no one else seeming to have this problem. I know my problem is tied to the VC because when I take the VC out of the actual wilco model I get the same phantom throttle effect on the ground and in the air. So why would this be the case with my version of eric marciano's upgrade but nobody elses? Any Ideas?Scott

Hi there,I believe that the throttle is tied to the gauges that are in both the 2d and VC panels, because I got throttle surging not only when I removed the VC, but when in the 2d cockpit, but fullscreen mode (eg; hitting W to go to the minipanel, and using the solo PFD w/SHIFT-6). That's my preferred view for take off and landing (don't find either the VC or 2nd w/full panel gives you a proper perspective for landing) so, finding the update did little else to improve the package, I simply removed it and ate the $40-odd bucks I paid for it. I've heard that some people have got it to work, while others not at all. For me it doesn't work, and there are no plans to change it (AFAIK after some emails to ERIC).I only bought the update in all honesty in hopes that it would solve the CTD I often get after landing at an airport, while turning off the runway. It was a problem a number of people got, but was supposedly patched later. I'm all patched up but still get it... so I've never really had a reliable version of the Airbus Volume 1 on my computer, ever (despite the considerable outlay of $$).I rarely, if ever, fly it anymore - just like most of my Feelthere aircraft.Hope this helps in some small way...- daniel

Daniel,I have heard of this problem and it was quite frequent. Some patches would fix it but then the next patch would ruin it again etc. The thing is that is weird about it is: when I run the latest patch from wilco I don't have this problem. I believe it is 3_c, and then as soon as I install the patch I get the problem that I read a lot of people having with the surging throttle. I also get it in 2D as well (but never the cockpit screen) only wing view or W mode. It is just frustrating that his update would bring me the fatal surging throttles. Even though the update only fixes minor things, it still definitely makes it more enjoyable (MCDU wise especially). Scott

What I find a little annoying was the fact the Eric told me that no one else was having the problems I was having, so it was me and there was nothing he could do to fix it (so, end of story for me). But I'm finding out more and more that that is not the case, and there are actual problems with his upgrade. And it is an upgrade, not an update, because we had to pay for it. So, for me, I take an aircraft I paid for that never worked properly, add a payment for an upgrade that doesn't work, and... add in the fact that - given the fact that the upgrade is not a Feelthere product - the little support you could get for the airbus volume 1 from the Feelthere forums (none of which ever helped me much anyway...) is now completely gone.This was never a really, super-complex aircraft to begin with (not 100% of the systems simulated, and only an approximation of fly-by-wire) so I could never figure out why the thing never worked properly (before the upgrade). The folks from Feelthere would disagree with me, I know, and say their support is great and the product works 100% for the majority of people. So I guess it's just me... and the other people scattered around these forums. - daniel

There is plenty of people with the problem we are having. They are just silenced by the feelthere forums. Feelthere and wilco are notorious for leaving things unfinished and handing off the problems to other people (wilco). Wilco is just as bad. While the airbus is nothing too spectacular compared to other complex sims out there it is still the best airbus you can fly around at the moment. What gets me is some people had the problem during the 2nd update, some during the 3rd, and then there is me with it only occuring with the eric marciano's upgrade. Why it is so scattered I have not a clue. It's almost like everyone has a different product even though everyone has the same version. My problem I think is the mistake of having the throttles somehow tied to the panel and do not work properly unless you are looking at the panel (2D etc.) Scott

Same problem here, after the Marciano update... Any news? Solutions? The wilco external model is horrible....Thomas