Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello 

Is it possible to disable a ditected device in FSUIPC,

I have an issue one of my device which is ditected by FSUIPC, its blocked all the buttons I assign in FSUIPC,  

when this device is unplugged before I start P3D and then I plug in the device all the buttons work just fine,  so that's why I would like to know if this is possible to disable a certain device in FSUIPC

this the information I see in FSUIPC log file

     219 Device acquired for use:
      219    Joystick ID = 5 (Registry okay)
      219    5=Razer Orbweaver Chroma
      219    5.GUID={04F942D0-3954-11E7-8010-444553540000}

 

 

FSUIPC5.log

Posted
1 hour ago, johnliem said:

I have an issue one of my device which is ditected by FSUIPC, its blocked all the buttons I assign in FSUIPC,  

Is it a Joystick type of device, with buttons or axes you can assign?

In what way does it "bloack" buttons. Do you mean FSUIPC still finds and assigns the other buttons, but thay don't work, or do you mean the other devices aren't found?

1 hour ago, johnliem said:

this the information I see in FSUIPC log file

     219 Device acquired for use:
      219    Joystick ID = 5 (Registry okay)
      219    5=Razer Orbweaver Chroma
      219    5.GUID={04F942D0-3954-11E7-8010-444553540000}

I think that was one of the devices known to cause problems and which were eliminated. If it isn't then I think maybe it is masquerading as a joystick device?

You attach a log showing a good session which does not feature the extract you show above at all, so it is really of no use at all.

Please do four things:

1. Try with FSUIPC 5.103e, now available in the Download Links subforum.
2. Supply a log showing the problem, NOT one showing everything good.
3. Also show the FSUIPC5.Joyscan.csv, which is a concise summary of the scanning results.
4. Download HidScanner from the Download Links "Useful Additional Programs" thread, run that, and supply its log too, please.

Pete

 

 

 

Posted
Is it a Joystick type of device, with buttons or axes you can assign? it is a keypad only key see picture.

 

 

In what way does it "block" buttons. when this keypard plugged and then I start the P3D all the buttons I assign to in FSUIPC do not working anymore, except from the button from the Yoke, but when I unplug this device and start the P3D , there is no problem as logicly that FSUIPC does not detect it. 

 

FSUIPC does not  finds and assigns the other buttons, and they don't work, 

 

I think that was one of the devices known to cause problems and which were eliminated. If it isn't then I think maybe it is masquerading as a joystick device?

You attach a log showing a good session which does not feature the extract you show above at all, so it is really of no use at all.

 

1. Try with FSUIPC 5.103e, now available in the Download Links subforum. I downloaded it and still the same issue
2. Supply a log showing the problem, NOT one showing everything good.
3. Also show the FSUIPC5.Joyscan.csv, which is a concise summary of the scanning results.
4. Download HidScanner from the Download Links "Useful Additional Programs" thread, run that, and supply its log too, please.

 

 

 

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

HidScanner.log

 

orbweaverchroma.jpg

Posted

But these details show that even with the Orbweaver connected, FSUIPC still rcognises and assigned these devices:

      157 -------------------------------------------------------------------
      172 Device acquired for use:
      172    Joystick ID = 4 (Registry okay)
      172    4=Saitek Pro Flight Yoke
      172    4.GUID={04F9B800-3954-11E7-8012-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=Saitek Pro Flight Quadrant
      172    3.GUID={4667AD50-4C6F-11E7-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 5 (Registry okay)
      172    5=Razer Orbweaver Chroma
      172    5.GUID={04F942D0-3954-11E7-8010-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 0 (Registry okay)
      172    0=Saitek Pro Flight Rudder Pedals
      172    0.GUID={04EB1200-3954-11E7-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=Throttle - HOTAS Warthog
      172    1.GUID={04F34F60-3954-11E7-8006-444553540000}
      172 -------------------------------------------------------------------


There's not going to be any change if that device isn't there or added later.  Even the assigned Joystick numbers look the same as those used in your assignments, though with so many devices I think you should enable JoyLetters so that your assignments still work even if the Joystick numbers change.

You say:

1 hour ago, johnliem said:

FSUIPC does not  finds and assigns the other buttons, and they don't work, 

What do you mean by "the other buttons"? Are you saying some assigned buttons work and some don't? 

Are you testing with a default aircraft, or the PMDG? Test with default.

Just looking at your default assignments, you have buttons assigned to joystick IDs 1, 2, 3, 4 and 5. (See the list of devices above to see what they are). You don't have a Joystick ID 2, but i see you have alternative assignments in any case:

2=P2,18,K119,10     -{Key press: ctl+F8}-
3=P1,1,K119,10     -{Key press: ctl+F8}-

15=P4,7,K73,24     -{Key press: alt+I}-
16=P4,6,K85,24     -{Key press: alt+U}-
17=P2,15,K85,24     -{Key press: alt+U}-
18=P2,17,K73,24     -{Key press: alt+I}-

52=P5,2,K188,8     -{Key press: ,<key}-
53=P5,3,K190,8     -{Key press: .>key}-
70=R2,14,K188,8     -{Key press: ,<key}-
71=R2,16,K190,8     -{Key press: .>key}-

except for these:

31=R2,10,K104,8     -{Key press: Num8}-
32=R2,12,K98,8     -{Key press: Num2}-
33=R2,13,K100,8     -{Key press: Num4}-
34=R2,11,K102,8     -{Key press: Num6}-
72=P2,4,K67,24     -{Key press: alt+C}-

Do the axis assignments work okay? You've only mentioned buttons.

Pete


 

Posted

Hi Pete

Thanks for your quick reply 

But these details show that even with the Orbweaver connected, FSUIPC still rcognises and assigned these devices:

I did not say that Orbweaver not recognise by FSUIPC , but this Orbweaver cause all the buttons do not work, that is why I was asking if it is possible that FSUIPC will not detect the Orbweaver.

 

There's not going to be any change if that device isn't there or added later.  Even the assigned Joystick numbers look the same as those used in your assignments, though with so many devices I think you should enable JoyLetters so that your assignments still work even if the Joystick numbers change.

How can I enable JoyLetters?


What do you mean by "the other buttons"? Are you saying some assigned buttons work and some don't?

yes, only the button from the yoke still working when Orbweaver is connected 

 

Are you testing with a default aircraft, or the PMDG? Test with default.

I test with default aircraft and  the PMDG

Just looking at your default assignments, you have buttons assigned to joystick IDs 1, 2, 3, 4 and 5. (See the list of devices above to see what they are). You don't have a Joystick ID 2, but i see you have alternative assignments in any case:

yes I have some alternative assignments in this case

 

Do the axis assignments work okay? You've only mentioned buttons.

only the axis work okay with the Orbweaver

Posted
30 minutes ago, johnliem said:

How can I enable JoyLetters?

There's a chapter on this in the User Guide.

30 minutes ago, johnliem said:

only the axis work okay with the Orbweaver

So no axes or buttons get through if the Orbweaver is connected, except for those on the Orbweaver? That's really very strange.

What about if you go into the FSUIPC options, Buttons or Axis assignments tabs, and select the "reload" button? Do they work then?

And what happens when you connect the Orbweaver later, instead of having it connected at the start? Everythng carries on working pus the Orbweaver?

Are all the devices connected to separate USB sockets on the PC? Or are they on a hub? A powered hub?

Can you check in the Windows Device Manager that power management is disabled (i.e. no power saving) on each USB hub or other USB devivce which has that tab (it'll be in the device properties if it is there).

37 minutes ago, johnliem said:

I was asking if it is possible that FSUIPC will not detect the Orbweaver.

But if it doesn't detect the Orbweaver then your assignments to it (Joystick ID 5) won't work. I see no assignments to any axes on it, but you said the axis works on the Orbweaver.

If you don't intend to use it, why connect it in any case?

Pete

 

Posted

HI Pete

sorry to make you confuse I should say that only the axis work  okay   when the Orbweaver is connected, because I use the axis assignment from my Rudder. so in this case I do not  have any issue with axis assginment only with the buttons  when the Orbweaver is connected,, and the Orbweaver is a keypad which has not axis at all

 

 

What about if you go into the FSUIPC options, Buttons or Axis assignments tabs, and select the "reload" button? Do they work then?

 when the Orbweaver is connected, as I do not have an issue with axis they work  and again when  when the Orbweaver is connected I reload for button, there is no reaction when I press any button ( when the Orbweaver is connected,) eventhough there are no the buttons work , I still can use the Orbweaver as a keypad.

 

 

 

And what happens when you connect the Orbweaver later, instead of having it connected at the start? Everythng carries on working pus the Orbweaver?

when Orbweaver  connected later there is no problem with the buttons.  

 

 

Are all the devices connected to separate USB sockets on the PC? Or are they on a hub? A powered hub?

they are connected to separate USB sockets on the PC, and I have treid to connect the the Orbweaver to a diffrence socket on the PC already, but no luck.

 

 

Can you check in the Windows Device Manager that power management is disabled (i.e. no power saving) on each USB hub or other USB devivce which has that tab (it'll be in the device properties if it is there).

well, it is maybe the answer of this issue, I check as you asked me to do about the power management and it was enable and after I disable it see printscreen, it works ;-)  all the buttons work  with the Orbweaver connected.

 

I will give it a go if I hope this really work, if you do not hear anything about this, it means it is over, solved.

 

really apprciate it your support and help to solve this silly issue,  thanks Pete. 

 

1.JPG

Posted
1 hour ago, johnliem said:

I should say that only the axis work  okay   when the Orbweaver is connected, because I use the axis assignment from my Rudder. so in this case I do not  have any issue with axis assginment only with the buttons

FSUIPC uses DirectInput to read the data from the devices. Each joystick-type device supples both Button and Axis states tgether. They cannot be separated.  So if FSUIPC can see the axes it can see the buttons -- unless some other software or driver is preventing this.

The axes you have assigned are on all of the other devices, Saitek Rudder, Yoke and Quadrant, and the HOTAS Warthog, so if all those axes are working there's no way FSUIPC can not see the buttons without some other interference in DirectInput, which seems very unlikely.

1 hour ago, johnliem said:

the Orbweaver is a keypad

No buttons? It seems t be telling DirectInput that it has 24 buttons, and 6 axes (RUVXY and Z), here:

Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255

So how are these assigned? 

It sounds like there's some software being run for the OrbWeaver which is seriously interfering with everything else. Do you know about any software? Howdo you configure this "keypad"?

1 hour ago, johnliem said:

well, it is maybe the answer of this issue, I check as you asked me to do about the power management and it was enable and after I disable it see printscreen, it works ;-)  all the buttons work  with the Orbweaver connected.

I will give it a go if I hope this really work, if you do not hear anything about this, it means it is over, solved.

Sorry, that seems to be contradictory. You say: "it works ;-)  all the buttons work  with the Orbweaver connected" but then "I will give it a go if I hope this really work"! Which is the truth? It works or you hope?

I'm not sure about that "Power Options" picture you showed. Maybe it is different in win10? The USB power management I'm talking about is in Device Manager, in the "Universal Serial bus controllers" section, and in the Properties (right click) for each entry described as a "Hub".

Did you also try what I asked, i/e:

What about if you go into the FSUIPC options, Buttons or Axis assignments tabs, and select the "reload" button? Do they work then?

Pete

 

Posted

 

No buttons? It seems t be telling DirectInput that it has 24 buttons, and 6 axes (RUVXY and Z), here:

Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255

So how are these assigned? 

I am not sure about this because why FSUIPC detect as you mention above , because when I open FSUIPC and go to buttons and I press any key on the the OrbWeaver there is nothing ditected by FSUIPC, and I do not assign anything in FSUIPC with the the OrbWeaver, the reason why I want to be able to use the the OrbWeaver  because every button which I assgined in FSUIPC as you can  see in the ini file, I assgined them with a hotkey in FSUIPC like for example Shift+ K for a button. so nothing assgined  with the Orbweaver.

 

so the OrbWeaver has it own software indeed, its called Razor Synapse. via this software I can assign every hotkey I made in FSUIPC via the the OrbWeaver keypad, instead of pressing the button on my joystick or my yoke. *

It sounds like there's some software being run for the OrbWeaver which is seriously interfering with everything else. Do you know about any software? Howdo you configure this "keypad"? see *

 

Sorry, that seems to be contradictory. You say: "it works ;-)  all the buttons work  with the Orbweaver connected" but then "I will give it a go if I hope this really work"! Which is the truth? It works or you hope?

it is not a hope but it works fine now.

 

I'm not sure about that "Power Options" picture you showed. Maybe it is different in win10? The USB power management I'm talking about is in Device Manager, in the "Universal Serial bus controllers" section, and in the Properties (right click) for each entry described as a "Hub".

sorry about the power option, I was miss understood about it, see print screen, it is the situation at the moment I do not changed any.

 

what I changed only like the first pirntscreen of the power option.

 

 

 

Did you also try what I asked, i/e:

What about if you go into the FSUIPC options, Buttons or Axis assignments tabs, and select the "reload" button? Do they work then?

 

when the first state that did not work, by doing as you asked me to do into the FSUIPC options, only Axis assinments works, not the button,

 

but now all the buttons are working. 

 

 

 

 

1.JPG

Posted
31 minutes ago, johnliem said:

I am not sure about this because why FSUIPC detect as you mention above , because when I open FSUIPC and go to buttons and I press any key on the the OrbWeaver there is nothing ditected by FSUIPC

But the reason for that is presumably the same reason that there's no button seen on anything else.

32 minutes ago, johnliem said:

so the OrbWeaver has it own software indeed, its called Razor Synapse. via this software I can assign every hotkey I made in FSUIPC via the the OrbWeaver keypad, instead of pressing the button on my joystick or my yoke.

So you aren't worried about not seeing buttons after all? I am really confused now.

If you want to test for button recognition, thy closing down that Razer software before loading the sim.

34 minutes ago, johnliem said:

It is not a hope but it works fine now.

So, problem solved?

Not that it matters now, I assume, but the picture from Device Manager you posted shows the Human Interface Devices section expands. That is NOT the Universal Serial bus controllers section, which oddly enough is actually called Universal Serial bus controllers!!!

Pete

 

 

 

Posted


I am not sure about this because why FSUIPC detect as you mention above , because when I open FSUIPC and go to buttons and I press any key on the the OrbWeaver there is nothing ditected by FSUIPC

But the reason for that is presumably the same reason that there's no button seen on anything else.


so the OrbWeaver has it own software indeed, its called Razor Synapse. via this software I can assign every hotkey I made in FSUIPC via the the OrbWeaver keypad, instead of pressing the button on my joystick or my yoke.

So you aren't worried about not seeing buttons after all? I am really confused now.

 

as it is solved now and Not that it matters now just to make it clear about the button, I think you are  still confused about it ,  again Not that it matters now

the issue was really when I still have the issue when the Orbweaver is connected, all the buttons I assigned from the Joystick and the yoke, they did not work(when the Orbweaver is connected ). it has nothing to do with the buttons of the the Orbweaver what so ever.


It is not a hope but it works fine now.

So, problem solved? yes it is solved now.

again thanks Pete

 

cheers

Johnliem.
 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.