Jump to content
The simFlight Network Forums

Sergio_

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by Sergio_

  1. 7 hours ago, Pete Dowson said:

    So the actual devices you have are:

    1 x Alpha Flight Controls
    2 x UnoJoy_Throttle
    1 x B737
    1 x MFG Crosswind V2

    Yes, right.

     

     

    7 hours ago, Pete Dowson said:

     what the "more details" were intended to be in the Log, but there's nothing useful there.  For some reason you are running a plugin called "comtest.lua" and have Lua log/trace enabled.

    Next step would be to get the log with that extra logging i mentioned so I can give you instructions on cleaning this stuff in the Registry.

    Pete

     

    I adderd this to the INI file, as you said.

    Debug=Please
    LogExtras=x200000

    What should I do next? Just run the Sim?

     

     

  2. 6 hours ago, Pete Dowson said:

    It would be interesting to see the files before the re-boot so we can see exactly which one changed its GUID.

    In the new files you provided things are slightly different -- the second pair with identical GUIDs is with "B737" instead of the Crosswind:

    MFG Crosswind V2      ID=4        {9EEBEF20-B521-11E7-8001-444553540000}
    Alpha Flight Controls   ID=4        {9EEBEF20-B521-11E7-8001-444553540000},

    B737                                 ID=0        {7BFCBC30-96D6-11EA-8001-444553540000}
    Alpha Flight Controls   ID=0        {7BFCBC30-96D6-11EA-8001-444553540000}

    The common factor in this is, then, "Alpha Flight Controls". Very odd that Windows keep re-assigning it AND gives it the same GUID as something else.

    I can provide detailed instructions, or even a little .REG file to remove them automatically, if you get me a log with more details. To do this add these lines to the [General] section of the INI file:

    Debug=Please
    LogExtras=x200000

    The log will then give me the full pathnames in the registry.

    Pete

    Ok, deinstalled them all again, and connected one by one, all devices are recognized by FSUIPC, didn't reboot yet.

    Here are the new ini, without reboot, and the new Log with more details.

     

    Greets

    Sergej

    FSUIPC6.rar

  3. Ok Pete, I did everything again, step by step, I deinstalled all the HID devices in the Device Manager, and all the drivers and it's the same.

    As long as I don't reboot, all controllers are recognized, after the first reboot, one is missing again.

    Do you know, where the HID Devices are placed in the registry? Maybe I can delete them manually.

    I ran Windows 10.

    I attached the new ini files.

     

    FSUIPC.zip

  4. I have similar Problem with FSUIPC6 and P3Dv5.

     

    I have 5 devices, but one of them is always not recognized by FSUIPC, I think this is the one with the highest ID.

    I tried averything in the last couple of weeks, but I can't get it to work.

    The last thing I tried was these steps you mentioned earlier:

    -------------------------

    1. Replace the complete [JoyNames] section in your FSUIPC4.INI file with just this:

    [JoyNames]
    AutoAssignLetters=Yes


    So far you haven't made many assignments to any devices, but be prepared to make them again as the numbers may change (probably will), and now you'll see letters instead.

    2. Now use the Windows Device Manager or Settings and remove all those devices. If the option to remove their drivers too, agree and let it happen. You may need to repeat this several times for the multiple entries looking the same.

    3. Unplug all those USB devices.

    4. Reboot the PC.

    5. Start the sim, then when it is all ready, plug the devices back in,  one at a time, leaving the Simple Solutions ones till last, and checking access each time in FSUIPC.  

    If there's still a problem, please supply those three files again.

    The more drastic solution is Registry Editing, which it may come to. But let's see.

    ---------------------

     

    After that, all devices was recognized by FSUIPC, but after the windows reboot, one is missing again.

    They are all listed in the FSUIPS.ini but one is not warking when I try to calibrate it in FSUIPC.

     

    Here are the 3 Files you need, in a .zip

     

    Hope for some help,

    Best regards

    Sergej

    FSUIPC.zip

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