Jump to content
The simFlight Network Forums

Navigation

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by Navigation

  1. Good day Pete, I just got a quick question here about alierons and the nosewheel on the PMDG NGX. My situation is I’ve disabled all controls in Prepared and set up my yoke to control the alierons and I sent it as FSUIPC calibration. Now when I’m taxing and I turn my yoke to check the alierons the nosewheel turns too. Is this normal or not. 

     

    Thanks

  2. 2 hours ago, Pete Dowson said:

    So far all the logs I've seen for this problem have shown no joysticks, so it looked the common factor.

    So, can you show me you log with the joystick previous connected, please? With the DEbug=Please etc options added to the INI.

    BTW I've now tested on a Microsoft Surface Pro 4 on Win10 with no joystick devices, and I get no problems. So it isn't something in Win10 specifically.

    Pete

     

     

    Ok will do as soon as I can I'm busy today but tonight I'll send it thanks

  3. 1 hour ago, Pete Dowson said:

    Your problem is not related to this thread and a HidScanner log is not needed! Please see your own separate thread.

    This one is for P3D crashes on loading, at the Splash Screen, which occur only when FSUIPC5 is registered, and, it seems, only for those folks with no joysticks whatsoever.

    Pete

     

    I'm using a joystick Pete Thrustmaster Hotas X but I've tried with it hooked up and disconnected 

  4. 45 minutes ago, grapeno1 said:

    pcssundahl you have to send the FSUIPC5.log after you try installing FSUIPC5 with your reg key. the one you sent was the log from installing without the key.

    Navigation go to the first page of this forum, at the top you will see Download links. then find Useful additional programs. you can find the HidScanner there.

     

    No luck for you still grapeno1?

  5. 3 hours ago, Pete Dowson said:

    Please don't keep sending my my own program (the DLL). It is just a waste, and I already have a copy of my own program, believe it or not!

    The LOG shows similar to grapeNo1's, ending with

          140 ---------------------- Joystick Device Scan -----------------------
          203 Product= <not readable at this time: maybe device disconnected?>
          203    Vendor=0CF2, Product=9010 (Version 1.1)
          219 -------------------------------------------------------------------

    Can you please run HidScanner too, as I asked him, and show me its log? It might prove useful to see if there are similarities.

    Pete

     

    OK Pete here you for HidScanner results see attached

    HidScanner.log

  6. 49 minutes ago, Pete Dowson said:

    Please don't keep sending my my own program (the DLL). It is just a waste, and I already have a copy of my own program, believe it or not!

    The LOG shows similar to grapeNo1's, ending with

          140 ---------------------- Joystick Device Scan -----------------------
          203 Product= <not readable at this time: maybe device disconnected?>
          203    Vendor=0CF2, Product=9010 (Version 1.1)
          219 -------------------------------------------------------------------

    Can you please run HidScanner too, as I asked him, and show me its log? It might prove useful to see if there are similarities.

    Pete

     

    How do I find HidScanner

  7. 1 hour ago, Pete Dowson said:

    Ah, now that log IS different. Your earlier log was NOT from a crashed P3D. This new log terminates early on, after a very very short Joystick scan:

           93 ---------------------- Joystick Device Scan -----------------------
           93 Product= <not readable at this time: maybe device disconnected?>
           93    Vendor=8087, Product=0A1E (Version 2.0)
           93 -------------------------------------------------------------------

    What joystick type devices do you have connected?  

    Once I have narrowed down the place where it stops I can add more detailed logging ot identidy it exactly. It's an iterative process and I need your help. 

    I am still hoping for corroborative log information from Navigation!

    It certainly won't be very soon at all unless you help. Where's your LOG and INI files with 5.101a?

    The process of nailing this will be me getting information from you then asking you to try things. If nobody is going to help it won't get fixed. i cannot fix things here without help when there's no problem here. And as you say, there seems to just the two of you!

    Thanks,

    Pete

     

    Ok I'm off work now so as soon as I get home and get my PC fired up I'll post my files another hour before I get to post

  8. 3 minutes ago, Navigation said:
    42 minutes ago, grapeno1 said:

    I dont know, and Pete has to deal with me and I dont know anything about computer files.

     

    3 minutes ago, Navigation said:
    42 minutes ago, grapeno1 said:

    I dont know, and Pete has to deal with me and I dont know anything about computer files.

    What type of Joystick do you have I have the Thrustmaster hotas X

  9. 19 minutes ago, Pete Dowson said:

    Ah, now that log IS different. Your earlier log was NOT from a crashed P3D. This new log terminates early on, after a very very short Joystick scan:

           93 ---------------------- Joystick Device Scan -----------------------
           93 Product= <not readable at this time: maybe device disconnected?>
           93    Vendor=8087, Product=0A1E (Version 2.0)
           93 -------------------------------------------------------------------

    What joystick type devices do you have connected?  

    Once I have narrowed down the place where it stops I can add more detailed logging ot identidy it exactly. It's an iterative process and I need your help. 

    I am still hoping for corroborative log information from Navigation!

    It certainly won't be very soon at all unless you help. Where's your LOG and INI files with 5.101a?

    The process of nailing this will be me getting information from you then asking you to try things. If nobody is going to help it won't get fixed. i cannot fix things here without help when there's no problem here. And as you say, there seems to just the two of you!

    Thanks,

    Pete

     

    I won't get to post mine until later today but I will as soon as I can Pete

  10. 20 minutes ago, grapeno1 said:

    When I install FSUIPC5 into P3Dv4, and enter my Registration. Then try to run P3Dv4 it shuts down.

    Then I un-install FSUIPC5. and run P3Dv4 it runs fine.

    Then I install FSUIPC5 into P3Dv4 and when it asks to Register and I click NOT NOW. It installs the unregistered version of FSUIPC5 and P3Dv4 run's fine.

     

    Same issue for me why are we the only two with this problem is what I'd like to know 

  11. 3 hours ago, Pete Dowson said:

    I still have no FSUIPC5.LOG or FSUIPC5.INI file! The Windows crasgh is NOT in FSUIPC at all.  

    What does, where?

    In the Modules folder, next to FSUIPC5.DLL.  You may see it as "configuration details" if you have Windows set to hide filetypes from you.

    If there is no INI file then you have never yet run FSUIPC, registered or unregistered.

    No, that is the Install log as it clearly says. The FSUIPC5.LOG is the run-time log, next to fSUIPC5.DLL in the Modules folder. It records what FSUIPC5 is doing when it is running. It may be cabelled as a Text file if you have Windows set to hide filetypes from you.

    If theree is no FSUIPC5.LOG file there then, again, FSUIPC5 has not been run, registered or unregistered.

    I'm afraid I have no useful information so far.

    Pete

     

    Ok will report back

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