Whiskey-Tango-Foxtrot???

[Malcolm Street 74]

So last night I was mucking around with my P3Dv5 configuration, which included adding some new scenery, one of them a freeware Wichita airport package from the AVSIM library.

Once I had everything happily set up via SimStarter, I fired up P3d, only to find that the throttle axis was playing up.  I'd move the throttle lever on my CH Yoke full forward, and the throttle in the sim would go to full and then immediately spring back to idle.  Spent about half an hour to no avail, so went to bed.

This afternoon spent 3.5 hours doing nothing else but trying to get it working.  I tried everything under the sun, including installing FSUIPC (full version) and trying to set up the throttle through that, of course turning off the controllers in P3D.  The throttle worked fine within FSUIPC but didn't move at all in the sim.

After still more research and mucking around I decided the next step, as per LM's debugging guide, was the nuclear option - delete all the generated files.  

And when I restarted P3D afterwards, and said no to every add-in load request, lo and behold the throttle worked normally and I had a nice little flight around Fort Randolph.  Decided to have a look at Wichita and once again it all looked fine.  Decided to try loading the Wichita freeware in sim and as soon as I did that... the throttle again kept springing back to idle and I nearly crashed the plane in the ensuing engine stoppage.  Disabled said freeware and the throttle worked fine again!

Can anyone tell me how on earth a basic scenery file can trash a control axis in the sim???

 

[edpatino 1,980]

2 hours ago, Malcolm Street said:

Once I had everything happily set up via SimStarter,

If I were you, I  would try to test it without that SimStarter. I tend not to use those gadgets and try to get things as simple as possible, as they potentially introduce additional points of failures or malfunction.

Cheers, Ed

[MDFlier 2,031]

If I had to guess, I'd say it added something to one of your config files (exe.dll, xml.dll, etc.) that does not work. When it dies, it is probably preventing the rest of the stuff in whichever file it is in not to run. Are there any drivers or programs for the CH yoke loaded when you start the sim? Check the file that launches it to see if the scenery added anything. 

In my Unix support days, I would always ask customers when the last time something worked properly. They would almost always say, "It worked yesterday and we haven't changed anything since then.". At which point I would do a do a directory listing of their system and filter out all of the files modified since yesterday. I'd always see a bunch of new files somewhere, and ask them, "What about package xyz that got loaded last night at 7PM?". 

My point with that was, go to the P3D folders that hold config files (Appdata, Program Data, etc..) and use the modified date to see which files got changed when you installed that scenery.