Jump to content
The simFlight Network Forums

jdriskell

Members
  • Posts

    54
  • Joined

  • Last visited

Posts posted by jdriskell

  1. I got the Douglas C-47 Beta V3.14 sim to respond to FSUIPC throttle input, but only after I first loaded the old DC-3 airways Virtual Airline sim which always responds to its FSUIPC controlled inputs.  I shut down the old DC-3 sim and reloaded the Beta version and the throttles started working.  I found that I could then redefine the throttles in FSUIPC a couple of different ways.  Either way worked.  But when I shut down FSX-SE and restarted it, the Beta version had the same problems unless I loaded the other DC-3 version first and then ended its flight before reloading the Beta version.  Don't know what is going on because every other sim works properly.

    Since then, I have turned off power management on the USB connections as recommended by Pete Dowson and I'll redefine the controls as  "Send to FS as Normal axis" and report back on my findings.  The only other sim that I've had to do this to is the PMDG DC-6/C-118.  Every other PMDG model uses FSUIPC as the calibrator.

    I'm also beginning to think my CH Throttle Quad may be getting a little long in the tooth as it's over 10 years old.  the third and fourth lever don't calibrate equally.  This is not the problem here, but it's vexing.

    Thanks for the input,

    Jim Driskell

     

     

  2. I use FSUIPC in conjunction with FSX-SE to control all my aircraft from the PMDG models to the stock aircraft without issue.  I have a set of CH Rudder Pedals, Yoke and Throttle Quad.  FSUIPC controls every aircraft properly except Manfred Jahn's Douglas C-47 Beta V3.14.  I have defined separate prop, throttle and mixture controls in FSUIPC as "Send direct to FSUIPC for Calibration"  for each CH throttle lever.  Prop and mixture controls work properly but the throttle controls do not seem to interface with the sims throttles so they do not move from idle cutoff.   What am I missing?  Can I track these assignments via a log to determine the problem? 

     

    Thanks in advance for your help.

     

    Jim Driskell

  3. I run the db builder after every navgraph update.  Hervé Sors' worldmag.bgl dated 12/31/18 has been applied.  So I guess I'll just try to work with what I've got.  I still don't understand why the Seattle Sectional says the V4 course is 104° and the various FSX/add-on systems are different, but if I accept FSX/etc everything should work.

    Thanks,

    Jim Driskell

  4. How does FlightSim Commander take magnetic declination into account?  I live near KSEA whose declination is about 15.61° E.  I fly FSX-SE and have applied Hervé Sors latest magnetic declination corrections. 

    I built a flight plan from KSEA to KBOI via V4 using Flight Sim Commander Version 10.0 Rev 5 Build 06.03.2018.  The first leg of the flight plan from SEA to YKM shows a course of 108-110° magnetic.  The Seattle Sectional Chart shows V4 as constant 104°.  FSTramp shows a course of 105°.  The sectional chart is correct, so how do we explain Flight Sim Commanders course of 108°?

    Is it possible to update Flight Sim Commander to use the correct magnetic declination variables?

    I love Flight Sim Commander but I don't like to use erroneous course information.

    Thanks in advance for your help.

    Jim Driskell

  5. I recently rebuilt my machine, installed Windows 10 and FSX-SE and upgraded to FSC 10.  I built a flight plan between two airports but FSX-SE doesn't want to read the plan.  In looking at the plan, it seems to be in simple format, not in the  "Ace XML" format that previous plans built with older versions of FSC an other flight planing systems.  I'm probably overlooking something simple but I can see what it is.  I'm attaching a sample.  Please advise. 

    Thanks,

    Jim Driskell

    KMWHKPDX_C-118.pln

  6. Thanks for the responses.  I'm familiar with FSUIPC and think I've assigned the various axis correctly, but?  The problem is that nothing is stable during flight and things seem to get worse as time passes.  Anyway, controls are disabled in FSX and I don't use the CH Control programs.

    I've attached my FSUIPC log file and the .ini file.  Thanks in advance for your help,

     

    Jim Driskell

    FSUIPC4.ini

    FSUIPC4.log

  7. I recently did a clean install of Win10 on my machine.  I also did a clean reinstall of FSX Gold on a SSD.  After loading FSGenises, Ultimate Terrain, and ORBX NA PNW, I'm now having control problems.  Previously I controlled everything with FSUIPC4 very smoothly but for some reason now elevator and aileron inputs from my CH Yoke go crazy.    The installed DC3 Airways DC-3 can not be controlled unless I activate the autopilot at takeoff.  Then a few minutes later I loose control of the aircraft as it begins to wander from its course settings.  I also tried the default Beech Baron and it was as squirrelly and uncontrollable.  The slightest input for either elevator or aileron on the CH Yoke causes the aircraft to loose control.  I also have CH's Rubber Pedals and Throttle Quad, both which seem to work properly.   I've had great success with in the past with FSUIPC but now I'm stuck.  

    I did have a couple of errors loading FSX and the Acceleration Package, but I thought I worked thru them and the installations completed and the applications asked for the registration keys.  Maybe not?  As it stands now, the sim is unusable.

    I've attached the FSUIPC4.JoyScan.csv file in case the file discloses a problem.

    Thanks in advance for any suggestions and help with this mess.

    Jim Driskell

    FSUIPC4.JoyScan.csv

  8. Apparently my CH Throttle Quad has become noisy.  Inputs from the first two levers, QX and QY, jump around when the levers are in the full closed position.  The other four levers seem to provide smooth inputs.  I've tried recalibrating both levers in FSUIPC but they remain noisy.  I finally recalibrated all the levers using the detent position as fully closed which seems to eliminate the noise.  I'm wondering if anyone on this list has had a similar problem.  Could this problem stem from a voltage issue at the USB port and if so, how could l verify this?  Should I try another USB port and if I did, would I have to recreate all my A/C specific profiles because of changing letters/numbers sensed by FSUIPC.

     

    Maybe it's time for a new throttle quad since I have had this one 6-8 years.

     

    Thanks in advance for any information.

     

    Jim Driskell

  9. Hi Volker,

     

    I uninstalled and reinstalled FSC again yesterday following the instructions (I always install stuff "Run as administrator).  I turned off UAC as soon as I got this new machine.  I installed it in its own directory on a SSD drive (i:\ drive) that's used exclusively for FSX.  My system an other stuff is on my c;\ drive.  Previously I had installed FSC in the root directory of FSX.  I think this may have been the problem but don't know why.  So far I haven't had any more problems but will let you know if I do.  I'll be out of town for a couple of weeks so I won't have a chance to really shake out the system until I return.  Thanks for your help.

     

    Jim Driskell

  10. I have a similar problem with an apparent malfunction in my throttle quad.   I'm using the latest version of FSUIPC to control the the inputs from my CH rudder pedals, yoke and throttle quad to my various simulations running in FSX under Win 8.1.  All the throttle axes work smoothly except for the Y axis.  No matter how I calibrate and re-calibrate the Y axis on the throttle quad, inputs are not smooth across its range of movement.  The input of this axis jumps around.  Small movements cause large inputs compared with the other axes.  The Y axis creates variable inputs even when it's fully closed.  I suspect that the potentiometer of this axis is bad but I'm not sure how to verify this or how I go about correcting the problem without buying a complete new throttle quad.  Any ideas will be appreciated.

     

    James M Driskell

  11. Hello,

     

    I'm running:

     

    1. FS X
    2. FSUIPC* / WideFS version 9.321
    3. FS Commander and Database Manager version and build used:  9.5.1 w/hotfix dtd 4 May 2014

    4. Navgraph AIRAC Cycle 1405
    5. Download version from your website
    6. Operating System - Win 8.1

     

    About every other time I start FSCommander, the system rebuilds the data base and creates a new FSCDbManager icon.  Although this action doesn't seem to affect anything, it's bothersome and time consuming.

     

    Any ideas?

     

    Jim Driskell

  12. Volker,

     

    Here's more information on my system:

     

    1. FS X, FS2004(FS9) or Prepar3D (Version) .... FSX
    2. FSUIPC* / WideFS version used .... 4.931
    3. FS Commander and Database Manager version and build used ... Vers 9.5 net( Build 14 March 2014

    4. Which provider and period of the AIRAC Cycle 1404
    5. Aerosoft version or download version from our website .. download today
    6. Operating System (Windows 7/8 32/64, Vista32/64, XP, 2000) ...  Win8.1

     

    Tried again to enter the key, both while FSCommander was running standalone and while FSX was running.  Didn't work either time.

     

    James M Driskell

  13. Same thing happened to me.  I installed the demo version, updated the database and started the program.  It looks good so I paid for the program today but the system rejects my registration information.

     

    Win 8.1, FSX with acceleration pac, latest FSUIPC version for FSX, Navgraph cycle 1404.

     

    Thanks for the help.

     

    James M Driskell

     

     

  14. Hi Pete,

     

    I decided to install the latest version of FSUIPC to see if this helped the problem.  I was running 4.9.2.9 and now I'm running 4.9.3.1.  Seems that the problem has gone away.  I'm now able to assign additional axes and calibrate them although I have to tell FSUIPC to ignore the axis when I'm scanning a particular lever.  I also wonder why my yoke, throttle quad and rudder pedals are defined twice, once by letters and then by numbers. I'm attaching my .ini for your review.

     

    I've attached the log file as a zip file to reduce its size.

     

    Thanks for your help.  I guess I owe you some of The Macallan. :cool:

     

    Jim Driskell

     

    Here's the .ini file.

     

    [General]
    UpdatedByVersion=4931
    History=F0X94W9CYH4WGFS9KE7S5
    InitDelayDevicesToo=No
    MouseWheelMove=No
    MouseWheelTrim=No
    MouseWheelTrimSpeed=1
    JoystickTimeout=20
    PollGFTQ6=Yes
    BlankDisplays=No
    FixControlAccel=No
    FixMachSpeedBug=No
    DeleteVehiclesForAES=Yes
    AutoScanDevices=Yes
    VisibilityOptions=No
    OneCloudLayer=No
    CloudTurbulence=No
    CloudIcing=No
    GenerateCirrus=No
    SuppressCloudTurbulence=No
    MaxIce=-4
    MinIce=-4
    UpperWindGusts=No
    SuppressWindTurbulence=No
    SuppressWindVariance=No
    WindTurbulence=No
    TurbulenceRate=1.0,5.0
    TurbulenceDivisor=20,20,40,40
    SuppressAllGusts=No
    MaxSurfaceWind=0
    WindLimitLevel=200
    WindDiscardLevel=400
    WindAjustAltitude=No
    WindAjustAltitudeBy=2000
    SmoothBySimTime=No
    WindSmoothing=No
    WindSmoothness=2
    WindSmoothAirborneOnly=Yes
    PressureSmoothness=0
    TemperatureSmoothness=0
    DisconnTrimForAP=No
    ZeroElevForAPAlt=No
    ThrottleSyncAll=No
    WhiteMessages=No
    ShowPMcontrols=No
    SpoilerIncrement=512
    MagicBattery=No
    RudderSpikeRemoval=No
    ElevatorSpikeRemoval=No
    AileronSpikeRemoval=No
    ReversedElevatorTrim=No
    ClockSync=No
    ClockSyncMins=5
    ClearWeatherDynamics=No
    OwnWeatherChanges=No
    TimeForSelect=4
    LoadFlightMenu=No
    LoadPlanMenu=No
    PauseAfterCrash=No
    BrakeReleaseThreshold=75
    SaveDataWithFlights=No
    ZapSound=firework
    ShortAircraftNameOk=Substring
    UseProfiles=Yes
    EnableMouseLook=No
    AxesWrongRange=No
    TCASid=Flight
    TCASrange=40
    AxisCalibration=No
    DirectAxesToCalibs=No
    ShowMultilineWindow=Yes
    SuppressSingleline=No
    SuppressMultilineFS=No
    AxisIntercepts=No
    DontResetAxes=No
    InitDelay=0
    GetNearestAirports=Yes
    OOMcheck=Yes
    WeatherReadFactor=2
    WeatherRewriteSeconds=1
    CustomWeatherModify=No
    SimConnectStallTime=1
    LuaRerunDelay=66
    Console=No
    UseMidMouseBtn=Yes
    UseSystemTime=No
    NewInterceptTextMenu=No
    DelayedMouseLookZoom=No
    LogAxes=Yes
    Debug=Please
    LogExtras=x200008
    LogButtonsKeys=Yes
    FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
    SimConnectUsed=10.0.61259.0

    [JoyNames]
    AutoAssignLetters=No
    Q=CH THROTTLE QUADRANT
    Q.GUID={095DF3F0-9E0A-11E2-8002-444553540000}
    P=CH PRO PEDALS USB
    P.GUID={095DF3F0-9E0A-11E2-8001-444553540000}
    Y=CH FLIGHT SIM YOKE USB
    Y.GUID={095E1B00-9E0A-11E2-8003-444553540000}
    0=CH THROTTLE QUADRANT
    0.GUID={095DF3F0-9E0A-11E2-8002-444553540000}
    1=CH PRO PEDALS USB
    1.GUID={095DF3F0-9E0A-11E2-8001-444553540000}
    2=CH FLIGHT SIM YOKE USB
    2.GUID={095E1B00-9E0A-11E2-8003-444553540000}

    [buttons]
    ButtonRepeat=20,10

    [AutoSave]
    Next=1
    Interval=60
    Files=10
    SaveOnGround=No
    AutoSaveEnabled=No

    [GPSout]
    GPSoutEnabled=No
    Port=COM0
    Speed=4800
    Interval=2000
    PosTo6Decimal=No
    SimModeIndicator=No
    Sentences=

    [GPSout2]
    GPSoutEnabled=No
    Port=<none set>
    Speed=4800
    Interval=2000
    PosTo6Decimal=No
    SimModeIndicator=No
    Sentences=

    [WideServer]
    WideFSenabled=Yes

    [sounds]
    Path=I:\FSX\Sound\
    Device1=Primary Sound Driver
    Device2=Speakers (Realtek High Definition Audio)
    Device3=Realtek Digital Output (Realtek High Definition Audio)

    [Profile.PMDG 737 NGX]
    1=PMDG 737-800NGX PMDG House Winglets
    2=Boeing 737-890NGX Alaska Airlines Winglets

    [buttons.PMDG 737 NGX]
    0=PY,5,C65752,0
    1=PY,4,C65570,0
    2=PY,6,C65759,0
    3=PY,7,C65758,0
    4=PY,0,C65860,0
    5=PY,8,C65861,0
    6=PY,9,C65791,0
    7=RY,10,C65607,0
    8=RY,11,C65615,0
    10=RY,2,C66278,0
    11=RY,3,C66279,0
    12=RY,32,C66416,0
    13=RY,34,C66416,90
    14=RY,33,C66416,45
    15=RY,35,C66416,135
    16=RY,36,C66416,180
    17=RY,38,C66416,270
    18=RY,39,C66416,315
    19=RY,37,C66416,225
    20=PY,1,K83,8

    [Axes.PMDG 737 NGX]
    RangeRepeatRate=10
    0=QZ,256,D,9,0,0,0
    1=QU,256,D,10,0,0,0
    2=PX,256,D,7,0,0,0
    3=PY,256,D,8,0,0,0
    4=PZ,256,D,3,0,0,0
    5=YX,256,D,1,0,0,0
    6=YY,256,D,2,0,0,0

    [JoystickCalibration.PMDG 737 NGX]
    AllowSuppressForPFCquad=Yes
    ExcludeThrottleSet=Yes
    ExcludeMixtureSet=Yes
    ExcludePropPitchSet=Yes
    SepRevsJetsOnly=No
    ApplyHeloTrim=No
    UseAxisControlsForNRZ=No
    FlapsSetControl=0
    FlapDetents=No
    ReverserControl=66292
    Reverser1Control=66422
    Reverser2Control=66425
    Reverser3Control=66428
    Reverser4Control=66431
    MaxThrottleForReverser=256
    AileronTrimControl=66731
    RudderTrimControl=66732
    CowlFlaps1Control=66162
    CowlFlaps2Control=66163
    CowlFlaps3Control=66164
    CowlFlaps4Control=66165
    SteeringTillerControl=0
    MaxSteerSpeed=60
    Aileron=-15557,-275,262,15597
    Elevator=-15521,-431,417,15550
    Rudder=-15859,-131,131,15993
    LeftBrake=4644,16190/16
    Throttle1=-16384,-16384,-16384,16246/32
    Throttle2=-16384,-16384,-16384,16246/32
    RightBrake=4644,16190/16


    [Profile.C-47]
    1=DC3-NH1

    [buttons.C-47]
    0=PY,5,C65752,0
    1=PY,4,C65570,0
    2=PY,6,C65759,0
    3=PY,7,C65758,0
    4=PY,0,C65860,0
    5=PY,8,C65861,0
    6=PY,9,C65791,0
    7=RY,10,C65607,0
    8=RY,11,C65615,0
    10=RY,2,C66278,0
    11=RY,3,C66279,0
    12=RY,32,C66416,0
    13=RY,34,C66416,90
    14=RY,33,C66416,45
    15=RY,35,C66416,135
    16=RY,36,C66416,180
    17=RY,38,C66416,270
    18=RY,39,C66416,315
    19=RY,37,C66416,225
    20=PY,1,K83,8

    [Axes.C-47]
    RangeRepeatRate=10
    0=QX,256,D,17,0,0,0
    1=QY,256,D,18,0,0,0
    2=QZ,256,D,9,0,0,0
    3=QR,256,D,14,0,0,0
    4=QU,256,D,10,0,0,0
    5=QV,256,D,13,0,0,0
    6=PX,256,D,7,0,0,0
    7=PY,256,D,8,0,0,0
    8=PZ,256,D,3,0,0,0
    9=YX,256,D,1,0,0,0
    10=YY,256,D,2,0,0,0
    11=YZ,256,D,29,0,0,0
    12=YU,256,D,30,0,0,0

    [JoystickCalibration.C-47]
    AllowSuppressForPFCquad=Yes
    ExcludeThrottleSet=Yes
    ExcludeMixtureSet=Yes
    ExcludePropPitchSet=Yes
    SepRevsJetsOnly=No
    ApplyHeloTrim=No
    UseAxisControlsForNRZ=No
    FlapsSetControl=0
    FlapDetents=No
    ReverserControl=66292
    Reverser1Control=66422
    Reverser2Control=66425
    Reverser3Control=66428
    Reverser4Control=66431
    MaxThrottleForReverser=256
    AileronTrimControl=66731
    RudderTrimControl=66732
    CowlFlaps1Control=66162
    CowlFlaps2Control=66163
    CowlFlaps3Control=66164
    CowlFlaps4Control=66165
    SteeringTillerControl=0
    MaxSteerSpeed=60
    Aileron=-15557,-275,262,15597
    Elevator=-15521,-431,417,15550
    Rudder=-15859,-131,131,15993
    LeftBrake=4644,16190/16
    RightBrake=4644,16190/16
    Throttle1=-16384,-512,512,16383/40
    Throttle2=-16383,-512,512,16383/40
    Mixture1=-16384,8192,8192,16383/8
    Mixture2=-16384,8192,8192,16383/8
    PropPitch1=-16384,0,512,16383/8
    PropPitch2=-16384,0,512,16383/8
    CowlFlaps1=0,16383/8
    CowlFlaps2=0,16383/8
     

    FSUIPC4.log.zip

  15. Ever since I had the misfortune to upgrade from Win 8 to Win 8.1, I have also been having problems assigning axes.  I had previously assigned the two center levers of my CH Throttle Quadrant as throttles for my PMDG 737NGX before I ungraded.  After I upgraded, I attempted to create a new profile for a C-47.  I couldn't assign any axes so I copied the 737 profile and tried to add the first two levers as prop controls and the last two levers as mixture controls.  I couldn't assign any more axes.  I did get around the problem by manually creating the axes using a text editor.  I was then able to calibrate the new axes and they seem to work fine.  Any ideas why I'm having problems with FSUIPC.  I did run FSUIPC with the edit lines in the .ini file.  The process generated a log file of over 8.5 G in size.  I've zipped the file down to 244K and can send it on if necessary.

     

    Thanks in advance for any help.

  16. I re-calibrated the controls and wound up with the following:

    Aileron=-15557,0,0,15597

    Elevator=-15521,0,0,15550

    Rudder=-15859,0,0,15993

    LeftBrake=-16384,16383/16

    Throttle1=-16384,-16384,-16384,16246/32

    Throttle2=-16384,-16384,-16384,16246/32

    RightBrake=-16384,16383/16

    The PMDG 373NGX seems to fly OK with these settings.

    Jim Driskell

  17. I'm having problems with the autopilot on my 737NGX engaging properly. I've read that the controls need to be in the neutral position in order for it to engage, so I re-calibrated my CH Yoke and Peddles in FSUIPC. Here's an extract from the .ini file:

    Aileron=-16380,0,0,16380

    Elevator=-16380,-144,-144,16380

    Rudder=-16380,-512,512,16380

    Aileron values look OK to me, but should the elevators and rudders have null values instead of the values shown for the center of the range. Also, why does the rubber have a minus and a plus value?

    Thanks in advance for the information,

    Jim Driskell

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