Jump to content
The simFlight Network Forums

Dougal

Members
  • Posts

    1,454
  • Joined

  • Last visited

Posts posted by Dougal

  1. First off, this is not a request for support, it's simply a HELLO and a thank you!

    It feels great to be BACK in here after years of being 'on the dark side' in XP11 and without FSUIPC.

    I gave up on Microsoft sims some years ago when I defected to XPlane, but now I have FS2020 installed and can once again return to my trusty companion that is FSUIPC, and have it do all things properly:-)

    I nearly fell off my chair when told I could buy this again for FS2020:-)

    Pete Sir, you have been around for as long as I can remember. You and I probably don't like to remember just how many years that is:-)

    Returning to FSUIPC is like 'coming home' for me, and even better to see John's name there also!

    GREAT to be back! And thanks to ALL concerned in keeping this truly GREAT product alive and kicking.

    • Like 1
  2. Found the fault Pete!

    HARDWARE!!!  Most unusual.

    There's something wrong with the main USB ports on the motherboard.  Thankfully, whatever the issue, its only affecting the main ports, and not the extra onboard ports.  I had to update the BIOS to accept a new i7 7700k chip, and now realise, that's when my problems all started.  Trouble is of course, I can't roll it back as then the chip isn't supported.  I've contacted Asus, but you know what they're like at implementing stuff on older boards (Z170).

    Some things will work correctly on those USB ports, but not all.  Thats why it was hard to track down the issue.

  3. Yea Ha!  I can now use FSUIPC to control all my aircraft once again!

    Frustratingly, it ended up requiring a COMPLETE re installation of Windows and P3D to cure the problem.  I ‘THINK’ the problem was within the Windows USB control environment.

    It really isn’t until one has to do without it, that you realise just how important FSUIPC is.

    Ho Hum….  Now I just have reinstall all my addons……

  4. Hi Pete

    Sorry about that.  I had the answers done and thought I'd done a 'copy & paste' but obviously forgot the 'ctrl-V' ;-)

    The problem is spread evenly between the two quadrants. Not 3 axis as I first thought, but four; axis 1 & 2 on both units. They are both USB (not PS2) and independent of each other; each being plugged directly into a separate motherboard USB port. No hubs in use.

    The issue is both in the calibration and axis assignment tabs.

    Within FSUIPC, the same levers always act exactly the same way, behaving just like the pots themselves are damaged.  They definitely are not.  They’re almost new, and function perfectly outside of FSUIPC which doesn’t make sense does it.
     

    Never thought to keep the old ini file:-(  and only keep backups of C (Windows) and D (Data), so no FS backup.  Need another HDD for this.

  5. This is really strange.  I’m still having this issue and not able to use FSUIPC at all for assigning or calibrating the Saitek USB throttle axis.  No problems with joystick axis.  This all started after a Windows and P3D reinstallation.

    I have two USB (3 axis) throttle quadrants.

    All controllers are disabled within P3Dv4.

    There are no conflicting commands within FSUIPC.

    Three of the six axis will not operate smoothly. As you said before Pete, they ‘act’ just as if there are conflicting assignments, but there are not.

    When assigning, calibrating and using the quadrants outside of FSUIPC, they’re fine, with no jumping around.

    I’ll attach the log and ini files again just in case you can see something I can’t.

    I’m pulling my hair out with this as I’ve never experienced anything like it before.

    FSUIPC5.ini

    FSUIPC5.log

  6. Hi Pete

    Yeah it does doesn't it.  If disable them completely, I have to set up a way of using the HAT switch I don't like.  All my previous installations I've done this way but I guess the latest P3D doesn't like it.  Still, I'll go that route and see what happens......

    joy.cpl is the app in the windows10 system for calibrating controllers.

    I hear Stoke got it pretty bad with the winds last week.  Is all well?

    PS  Thanks for replying on sundays;-)

  7. Been off flight sim for some time and now finished reinstalling all my flightsims; P3Dv4, X-Plane 11 and DCSWorld etc.

    Having major issue trying calibrate or use my two Saitek throttle controls, using FSUIPC5 in P3Dv4. If they weren't almost new, I'd say the pots are dirty.  That's just how they're behaving within FSUIPC.

    They calibrate and operate smoothly and perfectly in Windows10, using 'joy.cpl'.  There's also no issue using them directly in P3D, or the other flightsim programs, but once I disable the axis within P3D and attempt to calibrate with FSUIPC, they jump around and become unstable:-(

    I normally setup numerous profiles in FSUIPC, which is why I use it.

    It's also a new Windows 10 (x64) installation.

    No Saitek drivers are installed.

    This is a new one to me, so if anyone have any idea what might be going on, I'd be most grateful.

    log attached

    FSUIPC5.log

  8.  

    Yes, the current release (4.69 or later) does. Obviously it needed updating for completely ne FS versions in order to find the correct Scenery.CFG file. Maybe you are using an old version? 

     

    Take a look at the first few lines of the log, "Runways.txt". That'll tell you the version you were using AND the place where the scenery.cfg file was being read from. For example:

     

    Make Runways File: Version 4.69 by Pete Dowson
    Reading  SCENERY.CFG ...
     CFG file being used is: "C:\ProgramData\Lockheed Martin\Prepar3D v3\SCENERY.CFG"
    
    Don't forget you must install and run the program from the FS folder itself. That's how it works out where to get the CFG file from!
     
    Pete

     

    Ooops!   Thanks Pete.  I'd downloaded the latest, then promptly threw it away and was trying to use the old one (sheepish look).  Just think of all that spare time you'd have if it wasn't for people like me;-)

  9. Hi Dougal,

    to copy the file to the correct folder exists so far no tool for working in a network.

    Try the following workaround.

    Search the file scenery.cfg in C:\Program Data\Lockheed Martin\Prepar3D v3\ or similar.

    Copy this file to the folder where Prepar3D v3 was installed.

    Run the Database Manager.

     

    Volker

    Looks like this worked Volker, accept I renamed it to scenerycfg.fsc

    Just running the DBM now, which i never managed before. Will report back.

  10. hi

    I am new to this forum but a Spad user, it's an unusual problem.

    Dougal you are using a very old version of FSUIPC. 4.6 install the latest version 4.9. Also the saitek drivers per device. Did you uninstall/re-install Spad into the new location.

    With FSX running do the devices appear on separate tabs within the spad interface screen, Spad should also show if FSUIPC is connected

    JM

    Hi and thanks for responding

    I see from my log, that FSUIPC version, is 4.6a, although I was sure I updated recently.  Have restored a backup though, so that could be why.  Will download latestb and retry, though I don't think it's actually an FSUIPC issue.

     

    Separate tabs do indeed show for each panel when its running.  The issue, is that sometimes, like about 2 minuits ago;-) SPAD simply doesn't launch

  11. What I think is probably very bizarre, is that according to log below, surely SPAD opened without issue.  And yet, the drivers failed to launch or inisialise the Saitek devices:

    ********* FSUIPC4, Version 4.60a by Pete Dowson *********
    Reading options from "F:\FSX\Modules\FSUIPC4.ini"
    Trying to connect to SimConnect Acc/SP2 Oct07 ...
    User Name=removed
    User Addr=removed
    FSUIPC4 Key is provided
    WideFS7 Key is provided
    Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)
    Module base=61000000
    Wind smoothing fix is fully installed
    DebugStatus=255
          375 System time = 14/02/2015 04:30:22
          390 FLT UNC path = "\\MAINPC\Flight Simulator X Files\"
          390 FS UNC path = "\\MAINPC\FSX\"
          640 F:\FSX ADDONS\OpusFSI\FSISERVER.exe
          765 LogOptions=00000000 00000001
          765 SimConnect_Open succeeded: waiting to check version okay
        23806 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
        23806 Initialising SimConnect data requests now
        23806 FSUIPC Menu entry added
        23853 \\MAINPC\Flight Simulator X Files\737 Default at VHHX.FLT
        23853 \\MAINPC\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR
       107204 System time = 14/02/2015 04:32:09, Simulator time = 11:49:21 (04:49Z)
       107204 Aircraft="Boeing 737-800 Paint1"
       126158 C:\SPAD\Spad.exe
       127297 Advanced Weather Interface Enabled
       189604 \\MAINPC\FSX\SimObjects\Airplanes\PMDG 737-700NGX\B737-700.AIR
       190587 Aircraft="Boeing 737-700NGX PMDG House"
       282175 Sim stopped: average frame rate for last 91 secs = 14.7 fps
       501559 Sim stopped: average frame rate for last 27 secs = 16.2 fps
       682957 Sim stopped: average frame rate for last 25 secs = 16.5 fps
       740162 Sim stopped: average frame rate for last 35 secs = 16.3 fps
       977752 Sim stopped: average frame rate for last 33 secs = 14.4 fps
       981449 \\MAINPC\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR
       981449 Weather Mode now = Custom
       981449 \\MAINPC\Users\Dougal\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
       995879 System time = 14/02/2015 04:46:57, Simulator time = 11:53:25 (04:53Z)
       995879 *** FSUIPC log file being closed
    Average frame rate for running time of 247 secs = 15.7 fps
    Memory managed: 112 Allocs, 111 Freed
    ********* FSUIPC Log file closed ***********

  12. If there's no error logged for its loading, then no error was reported by Windows when FSUIPC asked for it to be run. So as far as FSUIPC knows it was successful. Are you sure it isn't still running invisibly? Maybe it isn't fully closing from before. Use Windows Task Manager to check the running Processes.

     

    Another thought. Maybe it needs to be run when FSUIPC and FS are ready. Try adding the READY option.

     

    One last check -- make sure the [Programs] section "at the end of the INI file" (as you say) is the ONLY [Programs] section!

     

    Pete

    Hello Pete

    Definately not running when it happens.  Checked the task manager straight away, as I have that issue often with Mozilla Firefox.  Would love to know what stops some programmes  exiting properly, as its a right royal pain.

    I digress.... Will try your other suggestions....

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