Hi,I've been using the FSUIPC feature of programming a yoke button to press a key in the keyboard in such a way, that one of the buttons equals Scroll Lock, which is setup in RW to be the PTT button.This configuration has worked without a hitch for months, but recently after I re-installed FS2002, some problems have surfaced.The problem is that the keypress doesn't activate everytime I push the PTT button in my yoke. It's as if it worked whenever it feels like. It has begun to interfere with online flying since I have to repeatedly check that I'm transmitting... because many times it just isn't.Anyone have any clues ?regardsTerops. yes I have the FSUIPC configured as before, it's the same INI-file and module I had in my previous installation. Also, the yoke button doesn't have any double assignments (if even possible).

and you're 100% sure that +Scroll lock doesnt have a function within FS now that you've reinstalled it?

Tero,You took the post right off my fingertips. I used to use the keysend command because of running RW over on my laptop but since getting the new system, I have reverted back to running voice on my second sound card on the primary pc. What I have noticed is, not only does this problem occur with the PTT button, but also with the buttons that toggle the AP (z) and the autothrottle (shift ?? I forgot). The problem is most likely to happen when I am in very demanding scenery areas like Alaska running mesh terrain, Alaskan Docks scenery, Offshore Ships traffic, cloud layers, sliders to max, you get the picture. I believe, but cannot confirm, that the slice of processing time that FSUIPC gets is cut significantly when the frame rate is running well below the target.Anyone else having ideas about this, your thoughts or ideas would be welcome.MikeB

Tero (Mike),I have the same experience!Note that I am using CH Control Manager in which I have defined my PTT flipper switch as a DirectX button.First I used the keysend definitions in WideServer.ini to signal PTT to RW at my second PC, that worked fine until I upgraded to DirectX9.0. Then I could grap the RW channel but was not able to release it. I remained using DirectX9.0 but switched to using the FSUIPC button functionality at the button page (in setad of the keysend definitions in Wideserver.ini). That worked well, but after a few months I suddenly noticed that it no longer worked.... I also noticed that it looked like the FSUIPC button definition was gone. After you redefine it, it sometimes works again..Could this not beeen introduced by the latest FSUIPC version?Personally I don't think it has to do with dense scenery, like Mike is suggesting, because I have this problem at the gate in the cockpit.Regards,Nicohttp://www.nicokaan.nl/

Don't know if this will help, but I don't have a problem using my joystick button as PTT for Rw on second PC.I do not have a CH yoke I use the Saitek X36 combo without their programming s/ware.The missile launch button is used as RW PTT and is configured via the 'Butons' tab in FSUIPC. I use the 'keysend 1-255 (widefs)' control with parameters 1 & 2 for 'pressed' & 'release' and corresponding entries in wideclient.ini (KeySend1=RWon, KeySend2=RWoff). Make sure 'ActionKeys=Yes'.If your set up is similar then I can only think that there is a problem with the CH interaction and FSUIPC.BTW I am using the latest version of FSUIPC 2.975 (or 6)HTH