Andydigital

If you haven't made any button assignments in FSUIPC already then the [buttons] section wont appear in the ini file. Just copy and paste the below to the end of the ini file. [Buttons] EliminateTransients=Yes

Yeah i've just tried it too on FSX with Acceleration and 4.233 all parameters function correctly. You are entering them as x31f4 param x00, x31f4 param x01, x31f4 param x02, etc aren't you?

Look near the top of the forum index page in the Announcement section for "FSX DOWNLOADS and UPDATES" or "Other Downloads etc".

Did you buy the correct version? maybe you bought a key for version 4 (FSX>) rather than version 3 (FS9<).

Tick the Reverse Axis box for the toe brakes and all should be well.

You shouldn't have to disable the yoke in FS9 totally, just assign your other buttons and axes in FSUIPC as you are doing now, and make sure no buttons other than the POV switch are assigned in FS9 and make sure you Add "EliminateTransients=Yes" to the main [buttons] section in the FSUIPC.INI file if you haven't already. Better still if you can, return your Yoke to the retailer you bought it from for a replacement, the random button issue is a known fault and all retailers have supposed to have been made aware of this. If you dont have any luck with your retailer get in contact with Saitek directly and they will try to replace it directly for you.

Leave the POV switch assigned in FSX rather than use FSUIPC, the POV switch isn't usually affected by the random button issue.

Some of these serial to usb adapters have a nasty habit of creating a new com port every time they are plugged in, maybe this is why he is seeing such high numbers. This info isn't from personal experience its just something i've picked up from various other forums over the last 12 months or so regarding problems with this type of device.

You might want to look at the thread listed below it may help you. viewtopic.php?f=54&t=66828 Andy.

I've had this problem appear on XP as well and the only way to stop it from happening again was to reboot the machine. Make sure all control devices are plugged in and active before launching FSX, as plugging in a device after FSX has started is when FSUIPC seems to stop responding on the Buttons/keys page. PS you gotta love the RealAir SF-260, i rarely fly anything else anymore. Hmm thinking about it does it do it on every plane or just when using the SF-260 i've not investigated it that much really.

Not if you use the same USB port it wont, if you plugged into a different USB port it automatically reinstalls the drivers and that profile file.

I believe FSUIPC can already do the shift function, but its a complicated matter that will require you to study the Advanced manual that is in the Modules folder along with FSUIPC.dll

The below is taken from the official Saitek forum. I had the mode switch set as position: 1 2D cockpit view 2 3D Virtual cockpit view. 3 External Locked spot view. In my opinion there are enough buttons on the yoke as it is without the need for 3 shift keys as well. As it turns out i sent mine back to the shop eventually for a refund because i wasn't happy with having defective goods i.e. i had the random button activation issue on my yoke. Thanks to Pete he added some code to FSUIPC to remove the issues caused by Saiteks faulty goods, but unfortunately it doesn't help with other games and sims that don't have FSUIPC. Saitek actually admitted just a few days ago that they couldn't fix the issue with a driver update, and that is was some problem with the firmware on the yokes control board, hence me sending it back for a refund. Oh one last thing apparently they have fixed the firmware now on the new yokes, but i'm not getting my hands burnt again for a while yet :wink:

Cant help on the first problem but i had problems with NOD32 version 2.7 but i've now upgraded to the ESET smart security and don't have anymore problems. If you have a current subscription for NOD32 2.7 you should be able to upgrade to version 3 for free, i'm fairly certain you shouldn't get anymore FSX crashes with NOD32 V3, which is also in the ESET Smart Security suite .

It doesn't matter in vista whether the account holder is Admin or not you have to right click on the program file and select the option to run the program with full administration rights. Sorry if you already know this but i wasn't sure from your replies whether you knew or not. MS in the ultimate wisdom decided not to give administrators full administration rights unless you turn UAC off, or whatever its called.

Just delete or rename the FSUIPC4.dll in the modules folder, there is no uninstall program. the default location of the dll in windows XP is: *:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules * being the drive where FSX is installed.

Ok thanks Pete will do.

Just to let you know Pete this seems to be doing what i want it to do and i haven't had any problems with it so far. I haven't been able to get on FSX as much as id have liked, but still it seems to have done the trick. I didn't have to change the pollinterval either which was a bonus. Thanks again Pete. regards, Andy.

Wow quick work Pete thanks. Does EliminateTransients=Yes have to be put it the sections for aircraft specific buttons as well? Edit: It's ok Pete i think i've figured out the answer for myself, no its not needed in the aircraft specific sections. I can press buttons fast enough so as not to get an action from them, but you have to be really fast :lol: seems to be just right at these setting. Now i just need to do lots of testing to see if its long enough to stop the transients. Again thanks for you time and effort so far.

Yes it definitely needs to ignore the button activation for a certain amount of time, whether this is 50ms or not im not sure, that figure is just a guess. Looking at the spike appearing in the control panel for the yoke it does appear to be very brief. Holding the button to activate a function is fine by me. The buttons are all separate, even the rocker switches are actually 2 separate buttons when looked at in the control panel. They are "on" when held and off as soon as you release them. There is one switch called a mode switch which works in a different way, it has 3 positions and it holds a different button "on" constantly until you move it to another position, then it holds that new button "on" constantly, etc.... i.e. position 1 button 15 held on, position 2 button 16 held on, position 3 button 17 held on. Yes a INI file only option would be fine for me and i dont think it matters that its blanket coverage for all joysticks. As long as people are aware that a button has to be held to activate it i'm sure that would work fine. Being selfish i could say that i only need it for version 4 as I'm using FSX, but i do know that people using FS9 are having the same problem too so version 3 would be highly appreciated i'm sure by those users. I'm not currently a WideFS user (probably in the distant future) so this would not be important to me, but surely if someone has one of these jokes (oops i mean yokes) then surely they can make sure its connected to the PC running the main FSUIPC module saving you alot of extra work. Thanks Pete its greatly appreciated, this yoke is very good its just a shame the first manufacturing runs haven't been properly tested for EMC.

I've seen your control spike elimination function and wondered how difficult it would be to add this function for joystick button presses as well. The reason this is needed is because of the new Saitek Pro flight yoke system. A significant number of users are having problems with random button presses been activated when moving the yoke axis, be it elevator or aileron. Lots of test's have been done by myself and others on the official saitek forums but all saitek say is to return the yoke for a replacement, well that's next to impossible as these things are so popular they are on back order nearly everywhere, and the replacements a lot of people have received exhibit the same fault. It appears the offending axis is sending some kind of spike to the control board which sets off a random joystick button activation as well, they are completely random as to how soon and how often it happens. Someone wrote in a thread today that this maybe fixed in a driver update so that it ignores these random button activations. The trouble is though Saitek seems very slow in everything they do and aren't prepared to deal direct with customers to replace faulty goods. Finally im getting to the bit where you are involved Pete sorry to ramble on. Would it be possible for you to add some kind of code to FSUIPC to ignore any button presses of say less than 50ms or something like that. If its a big job then forget it don't worry about it we will have to wait for an official fix. But if its not too difficult to implement then maybe an option to switch the function on or off, and maybe also a option to change the delay before it accepts it as a valid button press. Thanks Andy. ps there are quite a few people with the problem so it may be some potential new customers for you :wink:

No he's not replying because he has a life outside of FSUIPC.Give Pete a break he will be with you a soon as he can, i'm sure. Besides its after 8pm here in the UK he's probably having a well earned rest now.

This version certainly doesn't have the severe stutters i had in the previous version of the beta. I did a flight from Newark KEWR to EGCC Manchester today and i didn't see any severe windshift or stutter.