Need Help fsuipc not seeing stick bottons

[Roland Ives]

i in stalled a ssd 850 pro did all the migration and now have it as C: boot. fsx box is working well orbex, ezdok, asn and all the rest working fine. whill in a2a c182 i open fsuipc and go to botton key tab. fsuipc no longer sees joystick boorotn for assignment. Plese help with this. I flashed the firm ware in cougar HOTAS  and all is working fine. reinstalled fsuipc and it still shows me as registered but even after doing this fsuipc still dose not see joystick buttons. When i first started fsx box on the new drive it asked me for my key pass i entered it and all is fine with fsx but not with fsuipc all axis work fine in fsuipc even rotory dile i use for trim but fsuipc never sees the joystick bottons. once again please help . Thank you.

[Roland Ives]

Did I do or say someting wrong on this forum? I posted the above and have not yet gotten one sugestion of help. dose Pet Dawson read these posts?

[Pete Dowson]

Did I do or say someting wrong on this forum? I posted the above and have not yet gotten one sugestion of help. dose Pet Dawson read these posts?

 

My name is Pete Dowson, actually. And sorry, I just didn't see it. It arrived on my first day back from holiday and I had a big backlog.

 

You say FSUIPC sees the axes, but not the Buttons? Are these on the same device? If so then it must be a Windows driver problem, because the axes and buttons are read with the same call to direct input. However, FSUIPC can only handle the first 32 buttons.

 

The other thing which might interfere is any other driver or software you are running for this device. What was the flashing of the firmware for? Does this firmware process trhe buttons itself, perhaps? What does Windows see?

 

Please find and show me the JoyNames section of your FSUIPC4.INI file, in the FS Modules folder.

 

Pete

[Roland Ives]

Thank you for the responce and sorry for the typo Pete. The folowing is the joy sec of the ini //

 

[JoyNames]
AutoAssignLetters=No
1=Saitek Pro Flight Rudder Pedals
1.GUID={D66121A0-20A5-11E4-8001-444553540000}
2=F16 MFD 1
2.GUID={B70C2C20-3386-11E4-8001-444553540000}
3=F16 MFD 2
3.GUID={E1E1BFA0-3386-11E4-8002-444553540000}
0=HOTAS Cougar Joystick
0.GUID={F52B0320-16A1-11E4-8001-444553540000}
4=Razer Tartarus
4.GUID={2A247DE0-F8D3-11E4-8002-444553540000}

 

seems to me that 0= HOTAS Crugar Joystick should be on top of list but I don't know if it makes a defrance ?

 

I am not sure what the flash dose or dose not do in updating eeprom of controler. but windows sees the stick and ther buttons on it. all buttons that I am useing are on the stick and also the throtel. everything worked before ssd upgrade. though fsuipc says that fsuipc is registered to me with my email address, fsuipc is acting like it is not registered. one of the hats on the stick is used to lower and raise the flaps and works in a2a c182 and fsx but when i go to bottobs and keys and press the hat or any buttons on thw stick nothing happens. fsuipc dose see f 16 1 and 2 buttons but not the stick. I am going to move 0= Hotas to the top of liat and see if it helps.

 

Thank you

[Pete Dowson]

seems to me that 0= HOTAS Crugar Joystick should be on top of list but I don't know if it makes a defrance ?

 

No, the order isn't relevant -- it's the order detected, that's all.

 

though fsuipc says that fsuipc is registered to me with my email address, fsuipc is acting like it is not registered.

 

If it acted as if not registered, you wouldn't be able to go to the Buttons & Switches tab because it wouldn't be thjere! Besides which you said the axes were detected okay!

 

one of the hats on the stick is used to lower and raise the flaps and works in a2a c182 and fsx but when i go to bottobs and keys and press the hat or any buttons on thw stick nothing happens.

 

What button numbers does FS itself see for those? It sounds like they are out of range.

 

fsuipc dose see f 16 1 and 2 buttons but not the stick. I am going to move 0= Hotas to the top of liat and see if it helps.

 

The order in the list is completely irrelevant.

 

Pete

[Roland Ives]

I do not know how to tell what FS sees the buttons as? I used fsuipc to bind the hat to flaps inc up and down right and left. This hat still works in FS but in fsuipc button and keys it dose not apeare in the box and so can not be reasigned. nothing regards buttons on the stick can be re asigned as no buttons are seen. Also EZCA dose not see them either. What was bound before the move to ssd all work ok but now i can not make any new bindings for the stick only. when i did the migration and installed the ssd as c: through the bios I did not remove the original hdd from the system. it is now seen as F: by the OS and all files are still in tact. Do you think that some dll got stepted on in migration or some pointer got slamed in the registry? I am sure that i will not be the only one with this sort of problem as users more and more upgrade to ssd. An ssd migration page might be a good addition to the forum. Well thanks for you time and help it is much apreciated and i hope between the two of us things will come to a happy ending.  Also a spell ckeck would go a long way i am a EE and therfore dislectic and a very bad speller. great with numbers poor with letters. thank you.

[Pete Dowson]

I do not know how to tell what FS sees the buttons as?

 

If you assign in FS it tells you which button it recognised (it numbers from 1 to 32, FSUIPC numbers from 0 to 31). Have you never tried assigning in FS? Why did you switch to FSUIPC?

 

 I used fsuipc to bind the hat to flaps inc up and down right and left. This hat still works in FS but in fsuipc button and keys it dose not apeare in the box and so can not be reasigned. nothing regards buttons on the stick can be re asigned as no buttons are seen. Also EZCA dose not see them either

 

Hmm. Seems like a general problem with the device. You need to find out what FS recognises them as -- it may actually be a program associated with the device which is interpreting the button presses and converting them into FS controls -- there are Thrustmaster, Saitek and GoFlight drivers which do that. I don't know your device nor what you installed for it.

 

What was bound before the move to ssd all work ok but now i can not make any new bindings for the stick only. 

 

Er, that makes no sense. If FSUIPC doesn't see anything it cannot act on anything, no matter when they were "bound" (assigned?). I think you need to explain that much more carefully!

 

when i did the migration and installed the ssd as c: through the bios I did not remove the original hdd from the system. it is now seen as F: by the OS and all files are still in tact. Do you think that some dll got stepted on in migration or some pointer got slamed in the registry?

 

I don't think changing disks or the registry wil have anything to do with it. It will be all to do with the drivers or other software associated with the device. Try unindstalling it completely, drivers as well, then reinstalling but without any of its own assignment software.

 

I am sure that i will not be the only one with this sort of problem as users more and more upgrade to ssd.

 

SSD's are nothing to do with it. They are just disks. I've been using SSDs ever since they were rare and expensive. they are indistinguishable to other disks as far as all this stuff is concerned. You are chasing down a blind alley.

 

Pete

[Roland Ives]

I have assigned buttons ib FS before. i switched to fsuipc as a better system and it is. controls afe turned of in FS everything gos through fsuipc. i will assign in fs and get back to you.  i am using a thrustmaster hots courgar if that helps. thank you once again.

[Roland Ives]

in FSX when i assign one of the hat switches I get up= ctrl+F3, down= ctrl + F2, right = H, left = Shift H I do not get any numbers 1 to 32 or 0 to 31.

Fsx sees the stick buttons. in fsuipc key button tab Box PRESS Nothing Box Button nothing. I tried this with EZCA enabled and with EZCA disabled.

Thrusmaster Foxy sees all buttons and compiles and downloads to stick. I nolonger use foxy i have been total depending on fsuipc for all controlers rudder peddels, stick and trotel and f16 MFD 1 and 2. all are working in fsx and fsuipc except stick buttons.

[Pete Dowson]

in FSX when i assign one of the hat switches I get up= ctrl+F3, down= ctrl + F2, right = H, left = Shift H I do not get any numbers 1 to 32 or 0 to 31.

 

So, you have some (Thrustmaster?) software running which is reading the hat buttons ad converting them to key prresses long before any sother software like FSUIPC or FSX can read the actual button presses.

 

If you want to assign buttons in FSUIPC you have to remove that software. Or of course you can program the keypresses instead. 

 

Pete

[Roland Ives]

Hi Pete, your working on Sunday you need to take a brake you help is great but only 5 days a week be kind to your self. NO I do not use foxy or any apps with the hotas cougar. only the basic driver is in play. i tested the stick in foxy and FSX seperatly  only to make sure that the drivers are working as they should out side fsuipc4. if FSX sees the bouttons and foxy sees the bouttons and they would not if the drivers were crupted then it has to be someweare in fsuipc4 that the problems lies . if fsx sees the buttons and foxy sees the buttons and fsuipc dose not were elese can i look. Now the real trick is that fsx responds to stik buttons that were binded through fsuipc4 before the move but now fsuipc dose not see them for rebinding to something else.  IF fsx OR foxy AND fsuipc4 passes commands to the sim with controler shut off in fsx THEN drivers are good AND bindings are difined with fsuipc4 and passed only ELESE commands are NOT passed then drivers bad. IF buttons are not reassignable in button key subroutine THEN problem is in subroutine something is blocking. The cntrl F2 and F3 and the H and Shift H is what FSX is calling the buttons not the hardware or the drivers for the hadrwear.  Thank you Pete and take care.

[Pete Dowson]

Er, this is going in circles. Please read this slowly and carefully so you understand!

 

If the buttons result in keypresses then they are not seen as buttons, neither by FSX or FSUIPC. They are seen as keypresses. In FSUIPC you assign keypresses in a different tab, NOT the Buttons and Switches tab!

 

If there is no software running in the PC which is converting the buttons to keypresses, it must be in the firmware in the device.. In that case your device looks like a keyboard NOT like a joystick button device.

 

I really cannot help you further. You either need to assign the keypresses, or find out whatever it is which is converting the buttons into keypresses. I can't do that for you.  I don't know the hotas cougar nor this "foxy", but I suspect the device is programmable and retains its programming in its own memory. If so it would not matter if you weren't running this "foxy" at the time. The programming would still operate. If this is the case and you want the buttons to be buttons you'll need to reprogram it.

 

Pete

[Pete Dowson]

I just found this older thread where someone else had problems with Foxy programming and the Cougar:

 

http://forum.simflight.com/topic/60759-cougar-problem-with-the-new-fsuipc-450/?hl=cougar

 

Note this paragraph in the final message:

 

"The Thrusmaster Cougar were programmed through his software FOXY, with 2 files, one is Joystick controls, the other is Macros controls. The controls are downloaded into the ROM of the joystick through software, and emulation for FS or Windows is then made. For some strange electrical reason (component dead or ROM program delayed), the ROM does'nt give any command yet. As soon as I have disabled the emulation, I have seen all my buttons recognized from FSUIPC, and programmable through it. 

So I have all reprogrammed trough FSUIPC interface, and everything is allright to fly FSX, now. So thank you for your help one more time .

I have now to understand what is wrong with the memory of the joystick, perhaps to flah the ROM..., but nothing to do with FSUIPC. "

 

Pete

[Roland Ives]

Thank you Pete for finding that old thread. I turned emulation off and now all is fine. we understood that something was blocking Buttons and the answer in the old thread got it done. all is well with all fs and fsuipc4. thank you once again.