sn.ave

USB PnP relies not just on the USB source, but also the device using it - so what is true for the USB port (hot plugging, no problem) turns out to be less than 100% correct when you use it to plug in a device. I've encountered problems with soundboards (not sound cards, but external things like mixing desks, mood controllers, synths and amps) as well as ordinary hardware like sticks and yokes. It also can be triggered by turning on a powered hub that was running in passive mode. It can be anightmare troubelshotoing these things, but with FS it is at least easy touse FSUIPC and zero/zero settings like replacing the .cfg file to remove the software from the equation! :lol:

What may also have happened is that you now have multiple joystick entries in the FS9.cfg. No amount of messing with the port can supplant a rename of the FS9.cfg ot FS9.cfg.OLD and a reboot of the sim to make a new one. You've got a pretty pickle because you haven't been quite as methodical as you might have been in thinking about what the implications are of plugging-in a new stick... but it's quick to fix. Watch out that any specific settings you have in the FS9.cfg will be lost, so if you use this method to experiment with, then the Final Solution will be to copy the new joystick settings from the new cfg to the old manually, and remove all the old ones. Because EVERY USB port on every USB hub has a separate address, you may also have created yet one more joystick setting for the cfg rather than replacing the old. You should avoid plugging and unplugging devices into USB hubs while the system is `live` if possible, as it can also cause problems, especially through Hubs! Hope this helps.

Probably with very good reason. FS exaggerates the effects of off-centre weight distribution so many (most) aftermarket addons `cheat` by placing the tanks closer to the centre line than they might be if one were to calculate the position.

We really do seem to be approaching an age where the assumption of personal responsibility is being abrogated in the face of abject stupidity. :roll: The purpose, reason and methodology of FSUIPC - both 3 and 4 - is written in BIG LETTERS in the readme and documentation - which may be freely downloaded and analysed at the potential users leisure. Suffice to say, you'll look bloody silly complaining about an addon that used to work perfectly in FS9 and now doesn't work at all in FSX if you don't understand the need for and the purpose of, FSUIPC... :wink: And that's before you get to the added features as Bill says. :lol:

Lots of reasons. Same as FS9.

I would also suggest you look at the FS9.exe. Right mouse click on the FS9.exe in the main FS folder and click on Properties, then click on the Version tab. If the version is anything other than 9.1.0.40901 You do NOT have the current FS9.1 upgrade patch installed and this can also cause numerous problems with addons. Ensure you have installed the FS9.1 patch from the MS website.

Before you do that, turn the Yaw Damper off when on the ground. Does that help?

No pint necessary. I dealt with something similar just recently which reminded me when I saw your post! :lol:

It is my understanding that FSUIPC supercedes most CH CM settings, rendering it superfluous. By `most` I mean that certain of the button selections can exists away from FSUIPC, but that the calibration performed within FS is controlled by FSUIPC.

Roy, There should be only one copy of FSUIPC.dll, it should be in the `Modules`folder within the main FS file structure, and nowhere else. Do a computer search on FSUIPC.dll and delete every reference you find. Now, go to http://schiratti.com/dowson.html download FSUIPC again, and unzip it. Place ALL the files directly in the `Modules` folder, then restart Flight Sim. That way you must have version 3.65 and can't have any `rogue` older versions installed. Report back...