Guys,I have talked about this problem in th former thread I made: "A question about Aerosoft manhattan". In this topic, I described a problem I had where, out of nowhere, my FPS was cut in half at least. This happened in all of the FS world, so it couldn't have been a scenery issue. A tproblem with one of the textures also seemed unlikely, because, as you'll soon read below, the problem also happened in a more or less clean installation (no extra textures installed at all - no REX, no GEPro, no third party scenery or texture files). After five reinstalls, I found what caused the problem: FSUIPC. More specifically: FSUIPC's settings.How did I find the culprit? Simply because, in one of the enw reinstalls, I dragged and dropped all FSUIPC related stuff from an old FS2004 install to the new one. Suddenly, FPS dropped considerably in all of the FS world. It was thus not a scenery issue! Then, when I removed FSUIPC completely, FPS was again as good as always. Then I reinstalled FSUIPC using the installer, so that I had a fresh, clean FSUIPC install - the FPS were good! So, the trouble must have been not with the module itself, but something else - its settings.Now here is what made me nervous: the onl thing I had changed in the settings, were stuff related to my new Saitek controllers. Would this whole episode mean that I can't use them anymore? And so I came to a theory. It occured to me that sometimes I'd unplug my Saitek gear in favor of my old joystick. i'd do this, for example, when checking out a new scenery and not wanting to plug in my whole Saitek setup, I'd use my old joystick. The joystick covers everything in one single apparatus, and since I anyway fly the default Cessna to check out scenery, I really didn't need all the Saitek gear. But it's exactlky here where I found the problem lies.See, here's the point. I think FSUIPC gets confused, in a way, when you unplug your hardware and replace it with something else. FSUIPC will look for the hardware but won't find it, and in its constant search of trying to process non existant joystick axes, it will ultimately make your FPS collapse. And that's exactly what I found. Here's the theory I had: FSUIPC's settings are specific for my hardware setup, meaning that if Use a different setup temporarily, then FSUIPC will flip out. This ahs several consequences:1) When I unplug the Saitek gear, the FPS should drop (because I now have a settings file incomptible with the current plugged in hardware).2) When I unplug the Saitek gear but plug it in before starting FS2004 once again, FPS should be normal (because FSUIPC settings and hardware match).3) When I unplug the Saitek gear, but move in a CLEAN FSUIPC settings file, FPS should be restored to normal (because, although I have different hardware, the currently loaded settings file does not hold any settings related to the currently plugged-in hardware)Without wanting to sound arrogant, I apeared to be correct on all accounts, and thus the conclusion seems clear: FSUIPC needed to have a settings file loaded that works with the hardware currently plugged in. I now have two settings files: a clean one, which I use in conjunction with the joystick, and one that holds the settings for my Saitek gear. That one I, evidently, use in conjunction with the Saitek yoke and throttle quadrants. I have had no FPS problems anymore ever since, as long as I remember to swap the settings files depending on the gear I'm gonna use.So why do i post this here? For two reasons:1) I'm very curious to know if other people have the same weird FPS issues I described;2) because I think this is an important find that could help people in the future. Really, I do not want to sound arrogant, but I feel good about this (I guess it's that standard dopamine shot that you receive when you solved a problem that ahs been bugging you for some time). it took me several days, but I finally cured my headache. I hope this knowledge can help others clear theirs!

Hi BenjaminMany thanks for posting this here.I've not had this problem myself, but you never know ! If I do get it then I'll know where to come !David

Guys,I have talked about this problem in th former thread I made: "A question about Aerosoft manhattan". In this topic, I described a problem I had where, out of nowhere, my FPS was cut in half at least. This happened in all of the FS world, so it couldn't have been a scenery issue. A tproblem with one of the textures also seemed unlikely, because, as you'll soon read below, the problem also happened in a more or less clean installation (no extra textures installed at all - no REX, no GEPro, no third party scenery or texture files). After five reinstalls, I found what caused the problem: FSUIPC. More specifically: FSUIPC's settings.How did I find the culprit? Simply because, in one of the enw reinstalls, I dragged and dropped all FSUIPC related stuff from an old FS2004 install to the new one. Suddenly, FPS dropped considerably in all of the FS world. It was thus not a scenery issue! Then, when I removed FSUIPC completely, FPS was again as good as always. Then I reinstalled FSUIPC using the installer, so that I had a fresh, clean FSUIPC install - the FPS were good! So, the trouble must have been not with the module itself, but something else - its settings.Now here is what made me nervous: the onl thing I had changed in the settings, were stuff related to my new Saitek controllers. Would this whole episode mean that I can't use them anymore? And so I came to a theory. It occured to me that sometimes I'd unplug my Saitek gear in favor of my old joystick. i'd do this, for example, when checking out a new scenery and not wanting to plug in my whole Saitek setup, I'd use my old joystick. The joystick covers everything in one single apparatus, and since I anyway fly the default Cessna to check out scenery, I really didn't need all the Saitek gear. But it's exactlky here where I found the problem lies.See, here's the point. I think FSUIPC gets confused, in a way, when you unplug your hardware and replace it with something else. FSUIPC will look for the hardware but won't find it, and in its constant search of trying to process non existant joystick axes, it will ultimately make your FPS collapse. And that's exactly what I found. Here's the theory I had: FSUIPC's settings are specific for my hardware setup, meaning that if Use a different setup temporarily, then FSUIPC will flip out. This ahs several consequences:1) When I unplug the Saitek gear, the FPS should drop (because I now have a settings file incomptible with the current plugged in hardware).2) When I unplug the Saitek gear but plug it in before starting FS2004 once again, FPS should be normal (because FSUIPC settings and hardware match).3) When I unplug the Saitek gear, but move in a CLEAN FSUIPC settings file, FPS should be restored to normal (because, although I have different hardware, the currently loaded settings file does not hold any settings related to the currently plugged-in hardware)Without wanting to sound arrogant, I apeared to be correct on all accounts, and thus the conclusion seems clear: FSUIPC needed to have a settings file loaded that works with the hardware currently plugged in. I now have two settings files: a clean one, which I use in conjunction with the joystick, and one that holds the settings for my Saitek gear. That one I, evidently, use in conjunction with the Saitek yoke and throttle quadrants. I have had no FPS problems anymore ever since, as long as I remember to swap the settings files depending on the gear I'm gonna use.So why do i post this here? For two reasons:1) I'm very curious to know if other people have the same weird FPS issues I described;2) because I think this is an important find that could help people in the future. Really, I do not want to sound arrogant, but I feel good about this (I guess it's that standard dopamine shot that you receive when you solved a problem that ahs been bugging you for some time). it took me several days, but I finally cured my headache. I hope this knowledge can help others clear theirs!

HelloYou may like to read page 28 of the Fsuipc user guide entitled "keeping track of multiple control devices"and the use of Autoassignletters=y.this will help if you tend to move controllers around different usb ports.A read of Page 26 will also be a great timesaver for you when correctly set up.

Mad dog,Thanks for mentioning. I had read it when I initially began to use FSUIPC several weeks ago, but I must confess I didn't quite get it and din't spend much time on it. While I was trouble shooting, and whenI ultimately discovered what was making my FPS drop, I thought I should probably re-read that passage. it could spare me the FSUIPC.ini swapping I have to do now. Another reason i didn't really look at it, was that my hardware was correctly recognized by FSUIPC. joystick still worked well after unplugging the Saitek hardware, so I assumed I didn't have to meddle with letters and such. Seems I was wrong! Tell you what: I'll try out the letter-naming thing and see if it makes the FSUIPC.ini swappinbg completely unnecessary. I do not think, however, that reading that passage would have helped me solving my troubles because it took three days to find out the problem was with FSUIPC... Of course, had I used the letter-naming stuff, I might not have ahd those problems at all.

Mad dog,Thanks for mentioning. I had read it when I initially began to use FSUIPC several weeks ago, but I must confess I didn't quite get it and din't spend much time on it. While I was trouble shooting, and whenI ultimately discovered what was making my FPS drop, I thought I should probably re-read that passage. it could spare me the FSUIPC.ini swapping I have to do now. Another reason i didn't really look at it, was that my hardware was correctly recognized by FSUIPC. joystick still worked well after unplugging the Saitek hardware, so I assumed I didn't have to meddle with letters and such. Seems I was wrong! Tell you what: I'll try out the letter-naming thing and see if it makes the FSUIPC.ini swappinbg completely unnecessary. I do not think, however, that reading that passage would have helped me solving my troubles because it took three days to find out the problem was with FSUIPC... Of course, had I used the letter-naming stuff, I might not have ahd those problems at all.

HelloReading the passage would have helped because then you would not have had the problem in the first place.The setting for assigning letters to controllers would have discovered your controllers as you plunged them in and ran the FSim.The real power comes with the Profiles, once set up for each aircraft type setting up a new aircraft is just a couple of mouseclicks and all of your assignments are ready for that addon and will be loaded automatically as you load each aircraft from that point on.No need to be swapping the ini files around, but dont worry the documentation is good but there is a lot of it and it takes a few readings before some things fall into place.You will still be finding things that Fsuipc can do for you even after using it for years.

I'm not so sure, actually. The problem I was having was dramatic FPS loss after disconnecting a device that had button assignments and axis calibrations done in FSUIPC, no problems with mis-assigned buttons and the like upon reconnecting a device in a different USB port. Anyway, I can't test it out: the [JoyNames] section of the FSUIPC.ini doesn't list any GUIDs for some reason. I have posted a thread about it in the FSUIPC support forum and I'm waiting for Pete to reply.Until that time, though, my setup works just fine and I'm content. I'm simply happy that I managed to find out what the problem was and how to solve it. I'll certainly look into AutoAssignLetters, but first I'll have to hear from Pete why no GUIDs are being listed in [JoyNames].

If you use FSUIPC for all joystick assignments then you probably have in FS the setting to disable joystick control. If so, there would be no joystick section needed in FS9.cfg I would imagine.For the joystick control in this case FSUIPC would be the interface from the Windows joystick driver output and drive the FS aircraft directly bypassing the FS axis assignments and sensitivities. The Win driver output is what you see on the Gaming Options applet in control panel.Unless there is something special in the Saitek driver software just use the standard Win drivers since probably FSUIPC can perform the same tasks and this would avoid conflicts.

Hey Benjamin. I let FSUIPC take total control of the joystick and I do not have the Saitek software installed. No problems here.Are you using the Saitek software for any reason (such as for different modes)?

I let FSUIPC take total control of the joystick

That's exactly the way to go. Except for Airsimmer A320.

So... you guys think that the Saitek drivers might be intefering with FSUIPC? That doesn't seem logical... If that were the case, then they should be interfering always, right? Not only when the Saitek related FSUIPC.ini file is loaded when the Saitek hardware is unplugged. Besides, for as far as I can see, the Saitek software seems to be only active when the Saitek hardware is actually plugged in (tray icons appear). When I unplug it, the tray icons also disappear, suggesting that they are inactive and thus cannot interfere with any FSUIPC operations.altstiff: I do use the Saitek software for the modes, yes. I love it. I'm not sure I want to give it up, it's too comfortable... I'd rather take the minor effort to swap an ini file than to stop using the Saitek software...ronzie: I do not use FSUIPC for all joystick assignments, simply because I don't see the need for that. So, switching of the joystick/Saitek hardware in FS won't work for me. I only use FSUIPC for the stuff that FS can't reliably do by itself or stuff that FSUIPC does better/offers more options for. The Throttle quadrant configuration is one such thing. Reverse thrust, for example, can only be done the way I want it via FSUIPC. Also the calibration of the spoiler lever has always proved problematic in FS, so I find it much faster and easier to do that via FSUIPC. For the rest, everything I need assigned, is assigned via FS (the hat switch for example) or via the Saitek software: the Saitek software is simply set up in such a way that a key press is forwarded on to FS, and in FS this key press is translated into an action (so mode 3 of button E on the yoke produces "G" for gear extention and retraction, for example). Do note that I only use the Saitek software for the yoke, not for the throttle quadrant. I simply do not see the need to have FSUIPC do everything. Pete also very much says not to do so if it's not really necessary; it will only complicate things if you're not sure what you're doing.Rafal: out of curiosity, why doesn't it work for the ASA320?The bottom line is that I'm happy the way it is right now. Of course, it would be best if ini swapping wasn't necessary, but if that's the way it is, then that's the way it is. I'll put it this way: I'm sufficiently pleased with how it is that I don't feel motivated enough to change it. I will meddle with the GUIDs and letter assigning, see what that does. Other than that, I think I'll leave it all the way it is. It works too good to start changing stuff bigtime...

I only use FSUIPC for the stuff that FS can't reliably do by itself or stuff that FSUIPC does better/offers more options for.

From my experience I can say that if you assign and calibrate you controllers via more than one setup (e.g. FSUIPC, default, and the hardware extra software) you are going to have conflicts and problems.Also remember that even if you want to use one of the setups only, the other can automatically detect the controllers too and cause counteractions or noise at least. So you may want to make sure you set them in one and disable in the others.

out of curiosity, why doesn't it work for the ASA320?

The AS A320 developers have programmed the flight controls in such a way that operating the elevator and ailerons axes (read: your joystick) requires assigning and calibrating in the FS9 menu and cannot be done via FSUIPC (the axes won't work).BTW: Since you suggest FSUIPC is the culprit (though I admit I've never ever heard of FSUIPC having anything to do with FPS loss), have you reported your problem at Pete Dowson's support forum? He's a great guy and will probably write you back quickly.

I have no duplicate assignments. Stuff that is set in FS is not set in FSUIPC, and vice versa. Also, the buttons programmed in the Saitek program are not programmed in FS nor in FSUIPC. Any conflict is thus avoided. In short, I have two buttons programmed in the Saitek hardware (so that I can use them across multiple modes and thus have 6 buttons in 2), I have the reverse hrust set in FSUIPC, and the calibration of the spoiler lever was also done in FSUIPC, but all other assignments are done via FS itself. This includes the Spoiler, thrust and flaps levers. So, that way, I'm sure FS will not start bothering me with automatic asignments of the throttle quadrants. I have seen that this does not always work reliably due to the standard Windows calibration, however. Therefore, the spoiler lever had to be calibrated in FSUIPC. The others didn't have to be calibrated there, though. They worked fine out of the box.I have not mentioned the FPS loss in the FSUIPC forums. I might, though... Maybe he has some help to offer. Still, I'd actually like to wait for the GUID thing to start working. I'll try that first.