Jump to content
The simFlight Network Forums

Collserola

new Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Collserola

  1. No, the problem this definitely resolved and everything works perfectly. I think that with my limited English I 'm complicating things for you. What I was treating to say in this paragraph is only for information. The cuestion is that if you program incorrectly as I did (xxx.xx instead of xxx, xx which is correct and works), pressing the joystick button on the settings screen of Temspeek appear F12 (only in that case with settings and set), but later on the standard process it doesn't work. Again, thanks to your help, everything works perfectly. My issue satisfactorily solved. Thanks a lot and have a nice weekend. Alberto
  2. Hi Pete Many thanks for your quick answer (only 30 minutes). My problem has been solved with your sugestion. The solution was to change the dot (.) for the comma (,). As you say in your message and in the documentation. As for the message about the key CTRL is because that my first choice was this key, but I read that sometimes this key gives problems and I decided to change it by F12 without changing the comment. Finally, with the option of xxx.xx point (correct is xxx, xx) the F12 key can be programmed on Teanspeak by pressing the joystik. But only that, afther the program can not react to the press or release of the button. Again thank you very much. Alberto
  3. I have a problem with WideFS and push to talk and abusing the kindness that shows this page, I would like to ask for help. I'm using two PCs. One works: FSX, IvAp and Fsuip4 and WideServer. The other Ivap, WideClient and TeamSpeak2. I configured both computers to program a button on my joystick Saitek for use as push to talk through the F12 key. Once started both computers, with the indication of WideFS connected in both. If I start TeamSpeak2 with “sound settings” and selecting “set” for to tell to the program which key corresponds to the push to talk, pushing the button of the joystick, the answer of the program is F12. Perfect, this is what I wanted. From here begins the problem. If I select Activate local test mode, pressing the joystick button, TeamSpeak does not respond (the green light keeps off or ranges and you cannot hear what is said in the microphone). I do not understand what is happening. WideFS passes the F12 key properly from Server to Client since I can program the key chosen from the joystick, but then pressing the button does not open the microphone. Data: FSUIP4, Buttons + Switches: KEYSEND 1-255(WideFS) Parameter 1 KEYSEND 1-255(WideFS) Parameter 2 WideServer: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerIPAddr=192.168.1.195 Port=8002 Window=3,405,798,564 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Protocol=TCP ; ----------------------------------------------- [user] Log=Errors+ Keysend1 = 123.16;means Press left CTRL key Keysend2 = 123.24;means Release left CTRL key UseSendInput = Yes; ; =============================================== [sounds] Path=F:\fps$YWIDE\WideFS\Sound\ Device1=Controlador primario de sonido Device2=USB audio CODEC Device3=Realtek HD Audio output Apologize for my poor English and thank you very much
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.