Thanks for the prompt reply Paul. The problem has been sorted. It was the Microsoft Sidewinder Force Feedback software that had control of the button I had assigned even though I had zeroed it within FSX. Thanks again for your help.
Denis----- Original Message ----- From: "Paul Reynolds" <paul@xxxxxxxxxxxxxxxxxxx>
To: <jhb@xxxxxxxxxxxxx> Sent: Thursday, September 06, 2007 2:37 PM Subject: [jhb] Re: Remote Teamspeak
Hi Dennis, Yup t'was I who cribbed someone elses work and adapted it for use with FPI initially then IVAO/Teamspeak latterly. I take no credit for this, the original version of this method was distributed with an earlier version of WideFS but dropped when VatSim updated their voice software. I have e-mailed Peter Dowson so I can credit the original author but he cannot recall who it was. I do however use it with Peter Dowsnon's support. So, your problem. Answering your question, the keysends can go in the same [user] section as your Run1 lines though I would list them first. Now let's try and troubleshoot the PTT set. Have you closed down the WideClient.ini file, stopped and restarted WideClient so the keysends become active? If so then check through the following: Are the WideClient.ini lines consistent and gramattically correct? i.e. [User] Keysend1=123,16; Press F12 Keysend2=123,24; Release F12 UseSendInput=Yes Run1=... Assuming these are OK From within FS, open FSUIPC from the Modules menu and goto the Buttons + Switches tab. Press the joystick button you intend to use as your PTT button. If you get no response, then it is because the button has been assiged through either the FS Control Assignments or external management software. If this is the case, you will need to track this down and free up the button. If you get a response, then assuming you configured it following myinstructions, on the Right Hand Side, under Control sent when button pressedit should read: KEYSEND 1-255 (WideFS) In the Parameter box below this it should read: 1 The tick box Control to repeat while held should be ticked. The Control sent when button released should read: KEYSEND 1-255 (WideFS) The Parameter box below should read: 2 If any of these are wrong, that is probably the source of the error.Should there still be a problem, Other possible causes include the firewall not letting WideFS data through; Interferance from Active Sky? Your PC notaccepting F12 as a default key? I hope there's enough there to track down the problem.If not then it'll need some thinking about, I think I've covered most of theobvious here. Paul -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of Denis Ripley Sent: 06 September 2007 20:37 To: JHB_Airlines Subject: [jhb] Remote TeamspeakMy grey matter lets me down on occasion but I think it was Paul that gave us the directions for remote operation of Teamspeak. If so, this is directed tohim. I have gone through the set-up procedures, right upto the part where the pop-up window asks you to press a key on the joystick, then nothing. The pop-up window remains and does not disappear.Question. Should the extra lines that are added to the WideClient.ini file be added to the already present [User] heading(I have ActiveSky listed under[User] and Run1) or should they be under their own [User] heading? Apartfrom this area of uncertainty, everything went as written on the tin but itdoesn't work. Have you(or anyone for that matter) any idea what might be wrong? I am also having trouble running IvAp v2 from a remote computer but I will save questions on that until after I get Teamspeak working. Denis -- No virus found in this incoming message. Checked by AVG Free Edition.Version: 7.5.485 / Virus Database: 269.13.7/992 - Release Date: 9/6/2007 8:36 AM
