Jump to content
The simFlight Network Forums
Pete Dowson

Volunteers with multiple devices needed to test improved device detection

Recommended Posts

13 minutes ago, DaveG said:

I've just tried 4.964e & it doesn't recognise my 2 Thrustmaster MFD panels ( they're just a collection of buttons really). Going back to 4.964 they're seen and work fine although they're not listed in the "joystick device scan" section in the FSUIPC log. HIDScanner sees the 2 MFDs OK.

The logs don't show me enough information I'm afraid.  Please check the first message in this thread where it explains how to modify the INI file first to provide more logging.

I really want to make this work correctly in all cases, so I do appreciate such testing. If you could please re-run the test with 4.964e after enabling the extra logging it will be most useful. I'll only need the LOG from that.

Pete

 

 

Share this post


Link to post
Share on other sites

Oh, another question.

Is the 4.964 INI file different to the 4.964e one?

I see that the MFD devices aren't recognised in the scan at all, in either version of FSUIPC, so I don't see how their assignments could work. It is during the scan that their DirectInput handles are obtained, and tabulated against ID number, so that they can be scanned. There's no other way they will be seen. The scan is an essential part of the process, it isn't just there to provide information in the Log file.

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete, I think the ini was from the 4.964e one. Been swapping back and forth and lost track a bit!

I'll mod the ini with the extra logging and report back shortly.

 

edit: Log now attached.

FSUIPC4.log

Share this post


Link to post
Share on other sites
Just now, DaveG said:

I think the ini was from the 4.964e one.

Yes, I know it was (it says so in the fiile). But I don't understand how it could possibly have worked in 4.964 either, because the Joystick Scan for 4.964 doesn't list the MFD devices either.  Without being recognised in the scan the devices won't be opened and so cannot be used -- at least, not by FSUIPC. Do you perhaps still have then assigned in P3D?

4 minutes ago, DaveG said:

I'll mod the ini with the extra logging and report back shortly.

Thanks. It would be useful to rerun, with the extra logging too, with 4.964 as well, and check that the assignments ARE in fact working, that all 4 devices ARE seen in the Buttons & Switches or Axes tabs in FSUIPC. I'd also like to see the INI from 4.964, because things are just not making sense at present.

The problems I am trying to address with the changes here are NOT that any devices aren't being seen, but that the Joystick IDs aren't being sorted and corrected properly for those folks using Win8 or Win10 with installed joystick devices which somehow don't get assigned an ID. Previously I was having to recommend such users used the "JoyIDs" program to assign their own IDs so that FSUIPC would see them. These FSUIPC changes do that for you -- choosing numbers not already in use, and enforcing numbers already assigned in case something else has changed them (like JoyIDs can).

Pete

 

 

Share this post


Link to post
Share on other sites
57 minutes ago, DaveG said:

OK, here's the log from a 4.964 run.

Aha! Right. In that scan it sees all 4 devices! In the initialising scan but not when doing the Joystick ID scan. 

The main thing I see is that the MFDs are VID_044F&PID_B351, and VID_044F&PID_B352, and in the second loop they appear, thus:

Checking: \\?\hid#vid_044f&pid_b351#8&31a00d26&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Checking: \\?\hid#vid_044f&pid_b352#8&1c5fe7ed&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Yet the registry doesn't cough up the details that you get for the Warthogs.contains

It will be very interesting to see the fuller log for 4.964e. The two loops are now combined into one.

Pete

 

Share this post


Link to post
Share on other sites

I've peered through the code, and the only thing I can see which will make this difference between 4.964 and 4.964e is that the usage identification returned for those MFD devices is not one I recognise as a Game Controller. I've searched the Microsoft DirectInput data on-line and I've added some more usage checks into 4.964f for you to try for me.

Unfortunately I still cannot guarantee this will work correctly, but at least with some extra logging I've added I'll know why. Unfortunately HidScanner doesn't include the very information I needed for this -- an oversight, evidently.

So I'd be most grateful if you would kindly download FSUIPC4964f_TEST.zip and test that for me. Please show me the LOG no matter what the result it. Please back up your INI file first.

Thanks,
Pete

 

Share this post


Link to post
Share on other sites

Thanks for your continued work on this Pete. I won't be able to test until this evening though, I'm afraid. 

Share this post


Link to post
Share on other sites

Pete,

 

Back from skiing I tested the 4.964f Version with my WIN 7/64 bit OS and P3D 3.4. Everything worked as before and my devices are recognized. Also the order of entries in the INI file has not been changed anymore:

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Yoke
0.GUID={35A598E0-AAF5-11E1-8002-444553540000}
1=TQ6
1.GUID={317A1330-B07D-11E1-800C-444553540000}
2=Saitek Pro Flight Quadrant
2.GUID={7EC7D4F0-B1C3-11E1-8001-444553540000}
3=Saitek Pro Flight Rudder Pedals
3.GUID={35A598E0-AAF5-11E1-8001-444553540000}
R=Saitek Pro Flight Rudder Pedals
Y=Saitek Pro Flight Yoke
T=Saitek Pro Flight Quadrant
G=TQ6


249 ---------------------- Joystick Device Scan -----------------------
249 Product= Saitek Pro Flight Rudder Pedals
249    Manufacturer= Saitek
249    Vendor=06A3, Product=0763 (Version 1.0)
265    Assigned joystick id 3 (Registry okay)
265    GUID= {35A598E0-AAF5-11E1-8001-444553540000}
265 Product= Saitek Pro Flight Yoke
265    Manufacturer= Saitek
265    Vendor=06A3, Product=0BAC (Version 3.2)
265    Assigned joystick id 0 (Registry okay)
265    GUID= {35A598E0-AAF5-11E1-8002-444553540000}
280 Product= Saitek Pro Flight Quadrant
280    Manufacturer= Saitek
280    Vendor=06A3, Product=0C2D (Version 2.0)
280    Assigned joystick id 2 (Registry okay)
280    GUID= {7EC7D4F0-B1C3-11E1-8001-444553540000}
280 Product= TQ6
280    Manufacturer= GoFlight
280    Serial Number= 00080 7
280    Vendor=09F3, Product=0200 (Version 2.0)
280    Assigned joystick id 1 (Registry okay)
280    GUID= {317A1330-B07D-11E1-800C-444553540000}
280 -------------------------------------------------------------------

Rgds

Reinhard

 

Share this post


Link to post
Share on other sites
3 hours ago, DaveG said:

4.964f seems to work OK here. Only a quick startup to see if things were recognised

Thanks. The log shows why the previous versions didn't get the MFDs:

      312 Checking: \\?\hid#vid_044f&pid_b351#8&31a00d26&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      312    Usage=5, UsagePage=1, =Game Controller
      312 Product= F16 MFD 1

Up till now all the joystick type devices I've seen the Usage number for have been 4, not 5. I extended to allow 5 as well as a result of researching these on the Internet. I think the numbers were extended quite recently.

Anyway, I've released FSUIPC 4.964f as a general interim release now.

Thanks for your help!

2 hours ago, aua668 said:

I tested the 4.964f Version with my WIN 7/64 bit OS and P3D 3.4. Everything worked as before and my devices are recognized. Also the order of entries in the INI file has not been changed anymore:

Good. Thanks for the confirmation!

Pete

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • 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.