FSUIPC keeps forgetting button settings

[p0pster]

Hi Peter,

I have a strange problem after installing FSUIPC 3.50.

I have assigned the DEL key to teamspeak to be able to talk.

So I assigned button 0 on my joystick to the DEL key using FSUIPC.

This should be OK and has always worked for me before using 3.50.

However after installing V3.50 FSUIPC keeps forgetting the button assignments. Going back to V3.48 doesn't solve the problem.

In the .ini file I can see the assignment which looks correct.

[buttons]

1=H1,0,K46,8

However pressing button 0 on my joystick won't allow me to talk (as if its not assigned to the DEL key).

My keyboard is set to US International.

I don't understand what can be wrong.

Do you perhaps know why it won't work?

Kind regards,

Greg.

[Pete Dowson]

So I assigned button 0 on my joystick to the DEL key using FSUIPC.

This should be OK and has always worked for me before using 3.50.

However after installing V3.50 FSUIPC keeps forgetting the button assignments. Going back to V3.48 doesn't solve the problem.

It isn't FSUIPC "forgetting" a key assignment then. As you say, the assignment is still there. And there's been no changes in 3.50 in this area. Maybe TeamSpeak is not picking up the key press?

I notice you've programmed the button to be "held" -- this may cause Windows to generate repeats -- it would normally generate repeat keypresses after a delay if a key is held down. Perhaps that is the problem? I don't know how Teamspeak works with these things -- this is why, for Roger Wilco, AVC and SB3 we changed to a direct command, sent straight to the program. It is a pity Teamspeak didn't offer similar facilities.

You may be better off checking the option not to hold the key, and simply pressing it once to talk, then again when you've finished.

Another problem of course may be that TeamSpeak it cannot see keystrokes sent to FS.

Incidentally, one way of proving whether FSUIPC is in error or not is simply to assign the keypress (Del == Numpad Decimal to FS) to some easily recognisable function in FS's own keyboard assignments, and then see if your button operates that correctly. This is certainly how I test these functions -- I don't have all the applications to test with, and certainly not TeamSpeak (sorry, I don't fly on-line, yet. Maybe when I have more time to actually fly! ).

Regards,

Pete

[p0pster]

Peter,

Thank you for your help!

The problem was solved by reinstalling teamspeak.

Everything is working fine again.

Regards,

Greg.

[Pete Dowson]

The problem was solved by reinstalling teamspeak.

Everything is working fine again.

Ah, good! Thanks for letting me know.

Pete

[SDICKENS]

Hi there

That's strange !

I have also had the same problem with Teamspeak since installing 3.50 ?

I'll re-install today and see if that cures it.

Stu

MAC-184

http://margaritaair.com/

[SDICKENS]

Hi Pete

I've re-installed teamspeak as the other chap did but i still seem to be getting a problem with both the keyboard assigned teamspeak button and the button on the yoke i have also assigned failing after a short while.

They both completely stop working and the only way to clear it is reboot teamspeak.

The keyboard button works fine without FS9 running and doesn't seem to fail at all.

This has only been happening since installing 3.50 so i replaced it with version 3.48 this evening and haven't had any problems at all?

Any ideas what has changed to cause the new version to cause a conflict ?

Its got me beat! :shock:

Best Regards

Stu

[Pete Dowson]

... getting a problem with both the keyboard assigned teamspeak button

You mean actually using the keyboard? Unless you've programmed that in FS or in FSUIPC for something, neither will be stopping TeamSpeak getting it. In any case I would assume TeamSpeak must capture it beofre anything else gets it, i.e. as a Hot Key?

This has only been happening since installing 3.50 so i replaced it with version 3.48 this evening and haven't had any problems at all?

Any ideas what has changed to cause the new version to cause a conflict ?

No, sorry, none at all. Anyway, I'll need more explanation about exactly what you mean by "getting a problem with [both] the keyboard assigned teamspeak button".

The button actions in 3.50 are really the same as they've always been. I don't understand why you get a difference.

You can check that the button assignment itself works quite easily by assigning it in FS to some function you can recognise. This is how I test it. The actual method used to send the button hasn't changed, so your experience is really weird.

There's also some extra logging (see Logging page) which you can enable to check button actions. Can you switch it on and let me see the results in the FSUIPC Log please? Keep the test short.

Pete

[SDICKENS]

Hi Pete

Within Teamspeak itself I have the large 0 button on the Numeric keypad set for "push to talk"

When I have FS9 up and running I have also assigned a button on the CH yoke to mimic this command through FSUIPC.

When I am flying I can use either to transmit, what evers most convienent at the time.

Never had any problems with it and its all worked fine.

I installed 3.50 just after you released it a few weeks back.

Everything seems to work fine for a while , then for no apparent reason both the keyboard push button and the yoke push button won't activate the transmit in Teamspeak. The only way i can get them working again is to close Teamspeak and re-start it.

I removed and re-installed Teamspeak as the other chap did hoping it would resolve the issue but it didn't.

I don't appear to have any problems when FS9 isn't running, THe keyboard Teamspeak button works fine, but when I have Flight sim running this problem is occuring intermitently. Sometimes it works fine for 30 mins before failing, sometimes it packs up in 10- 15 mins.

The only thing I have knowingly changed was the FSUIPC version so like I say i re-installed 3.48 last night and it worked fine all evening. Could well be just a coincidence I know bit its got me beat as to what it is.

I'll put 3.50 back in this eve and activate the logging

As this is intermitent it could be a long log file. What i will do is set a stopwatch going as i activate both which might at least give us a elapsed time if thats any help.

I'll mail you a log file over later this eve assuming i get a failure again.

Cheers for all your help Pete

Stu

[Pete Dowson]

Within Teamspeak itself I have the large 0 button on the Numeric keypad set for "push to talk"

...

Everything seems to work fine for a while , then for no apparent reason both the keyboard push button and the yoke push button won't activate the transmit in Teamspeak. The only way i can get them working again is to close Teamspeak and re-start it.

Quite honestly, all that certainly points to something going wrong with TeamSpeak. FSUIPC can in no way interfere with TeamSpeak seeing the keyboard directly, and the fact that it doesn't see the same key when pssed through FSUIPC isn't really relevant, as it is evidently just the same problem.

Furthermore, the fact that reinstalling Teamspeak "fixes" it temporarily also seems to show that it is something in Teamspeak's own settings which is getting changed or corrupted somehow. Neither FS nor, especially, FSUIPC, know anything about TeamSpeak. It is entirely separate and has no connection or overlap with anything FSUIPC does.

The only thing I have knowingly changed was the FSUIPC version so like I say i re-installed 3.48 last night and it worked fine all evening. Could well be just a coincidence I know bit its got me beat as to what it is.

Me too, since, as I say, there cannot really be any connection. Possibly a very small difference in timing, or real memory usage, due to the few differences between 3.48 and 3.50, but this is clutching at straws. Nevertheless, if you load TeamSpeak before FS, try it loading after, or vice versa, just so they get different real memory allocations.

I'll put 3.50 back in this eve and activate the logging

Please don't bother. Now that I understand the use of the keyboard directly also fails, it explains very clearly why FSUIPC's button programming does too -- after all, all it is doing is seeing your button and sending the NumPad 0 keypress which is being ignored in TeamSpeak just as it is when you press it directly.

One thing though. Can you try another keypress instead, one NOT on the NumPad? Maybe it is related to the Num Lock setting on the keyboard?

Regards

Pete