Jump to content
The simFlight Network Forums

jdriskell

Members
  • Posts

    54
  • Joined

  • Last visited

Posts posted by jdriskell

  1. Hi John,

    Thanks for getting back to me.  I re-scanned the throttles in the DC-6 Axes.  They are now working.  PMDG updated the DC-6 twice recently so I think the update disconnected the link between FSUIPC and the model.  The reason you only found to poorly scanned throttles 1 & 2 is that I did this early on but now I generally scan and calibrate them within the various subsections specific to the particular airplane.  The PMDG DC-6 accepts Throttle input direct, not calibrated.  The DC-3 has the Duckworth enhancement that uses a preset Duckworth special  connections.  The PMDG 737 uses the standard scanned and calibrated throttle input.  Apparently the standard is "no standard!"

    Thanks for your time and help.  Your customer service is tops!  Say "Hello" to your dad.  As I mentioned, I've been using FSUIPC since the early days and think it's the superior method for controlling flight controls.

    I'm attaching my current .ini file for information is you have time to look at it.

    Jim Driskell

    FSUIPC7.ini

  2. Flying PMDG DC-6 in MSFS that requires direct throttle input via FSUIPC 7 ver 7.3.24.  Engine runup and take off is fine.  Reducing power to 30" for cruise is works.  But further reducing power for descent below 30" only works on engine 3 & 4.  Can manually reduce throttles 1 & 2.  input from my very old CH Throttle Quad has no effect on 1 & 2.  I can increase power on 1 & 2 above 30" 

    Checking FSUIPC values: 

    Throttle          1          2            3          4

                      14719  15615    14335   14719

                    -16254 -15604 - 16384 - 16234

    Lots of variation here but the quad has been working until just now.  any ideas why half of the system would quit?  I'm attaching the last log file for what it's worth.

    Maybe it's time for a new Quad.  Thanks,

    Jim Driskell

    FSUIPC7.log

  3. Hi John,

    I had 7.3.20 installed but upgraded today to 7.3.24.  Make lots of difference and easier to use with the pesky lvars.  I corrected the spelling of $Param on added your suggestion for parking brake controls and now everything works as advertised.

    Thanks again for your prompt help.  As I mentioned before, I'm a long time user of FSUIPC and plan to continue.  There is so much power built into the system but I've only scratched the surface. 

    My complements to the Dowsons.

    Jim Driskell

     

  4. Hi John,

    I'm still struggling with the lvar concept.  I'm using an old CH Throttle Quad what shows its age.

    Max and Min Values for the Throttles and Mixture levers are:

    T1 - 15615, -15604 = 31219

    T2 - 14335, -16384 = 30729

    M1 - 14591, -16254 = 30773

    M2 - 14591, -16384 = 30975

    Myevents.txt file contains the following:

    DuckWorks_DC3_Throttle1#$Parm 31219.0 / 0.5 + (>L:DUCKWORKS_THROTTLE1_SET)
    DuckWorks_DC3_Throttle2#$Parm 30729.0 / 0.5 + (>L:DUCKWORKS_THROTTLE2_SET)
    DuckWorks_DC3_Mixture1#$Parm 30773.0 / 0.5 + (>L:DUCKWORKS_MIXTURE1_SET)
    DuckWorks_DC3_Mixture2#$Parm 30975.0 / 0.5 + (>L:DUCKWORKS_MIXTURE2_SET)

    I got this format from a previous entry in forum dated 6/23/2023 with a conversaton with Andre92.

    I bound these lvars to the throttle and mixture axes, checked select for Preset and Send to FS as normal axis but they have no effect on the throttles within the Duckworks Enanced DC-3 aircraft within the sim.  What an I missing? Probably my numeric parms.

    In addition, the Duckworks Enhancement also uses the lvar "DUCKWORKS_PARKING_BRAKE_SET."  I sent the lvar to 0 but am unsure how to define the lvar within the myevents.txt file.  Suggestions?

    Your documentation refers to a subset within the .ini file titled "[LvarOffsets].  Is this necessary when the system already has lvars listed and available?

    Thanks in advance for your help.  I've been using FSUIPC ever since your father and I were young enough to learn new tricks. But I beginning to think that learning new ways of attaching flight controls to actions within the simulation is leaving me in the lurch.  As they say, "if it ain't broke, don't fix it." 

    Jim Driskell

     

  5. Apparently the Duckworks enhancement for the MSFS DC-3 has it's own throttle and mixture labels for controlling these axes.  They are called;

    DUCKWORKS _THROTTLE1_SET

    DUCKWORKS _THROTTLE2_SET

    DUCKWORKS _MIXTURE1_SET

    DUCKWORKS _MIXTURE2_SET

    Can FSUIPC control these axes and if so, how?

    Thanks,

    Jim Driskell

  6. Hi John,

    Another weekend, but has Micamber said, "Things are looking up."  I think I understand why I was having so much trouble with the missing Throttle Quad in the scan and the pesky xBox controllers impinging on my FSUIPC install.  After getting a clean scan for FSUIPC and MSFS described above, I decided to re-install the Steam version of FSX since I have a lot of time and money invested in that old system.  Bad idea!  The registry conflict reappeared as evidenced by the missing Throttle Quad when I installed FSUIPC  4.997 into FSX - Steam.  So I uninstalled FSX and Steam and the problem is gone.  I get a clean scan with MSFS and FSUIPC7 so something within the Steam version is the problem.

    I'll stick with MSFS. 

    Jim

  7. Hi John,

    Another note for follow up.  I removed Steam and FSX from my machine.  The xBox conflict disappeared giving a clean FSUIPC scan.  Maybe the previously deleting the Steam version of MSFS left some trash somewhere, fooling the FSUIPC scan.

    I installed the Microsoft Store version and so far everything look OK.  I'm attaching the scan file for your information.

    What do you think about adding the xBox reg entries back on my machine, or should I let sleeping dogs lie?

    Jim

    FSUIPC7.JoyScan.csv

  8. Hi John,

    Worked as advertised.  I did find the UserCfg.opt file previously but wasn't certain that I should delete all the video card entries.  Now looks like everything is working.

    Your (and previously your father's) sense of customer service is a bright place in what is a rather confused world.  Great work!!

    Now I need to get FSUIPC controlling MSFS and I'll be done.

    Thanks again, and take the rest of the day off!

    Jim

  9. Hi John,

    I found an entry in the UserCfg.opt file pointing to the Steam MSFS Content directory, "InstalledPackagesPath "G:\MSFS Content" and removed it.  Reinstalled FSUIPC7 and got the same result, looking for the Steam edition.  Steam has been giving me problems since the start, so I uninstalled all of Steam and will try installing FSUIPC7 again later today.

    I've attached the files for your review.

    Jim

    InstallFSUIPC7.log UserCfg - Copy.opt

  10. Hi John,

    Hate to keep bothering your but I've got a new problem.  I dumped the Steam version of MFSF, installed the Microsoft Store version, installed FSUIPC7 but the new installation keeps looking for the old steam version, wanting to install it when I start FSUIPC7,  Uninstalled FSUIPC7 using the uninstaller with the package, rebooted and reinstalled it but it's still looking for the steam version which isn't installed.

    Thanks in advance for your help.

    Jim

  11. Hi John,

    I think I know what caused the conflicts between the CH Throttle Quad and the xBox virtual controllers on my new Dell XPS 8950 Win11 machine.  I don't know why!

    I setup Steam and the Steam FSX system first.  When I first ran FSUIPC4, i got a clean FSUIPC4.ini file which I've attached.  Sometime later, I installed the Steam Microsoft Flight Simulator system.  Then I started having trouble.  The description of the Throttle Quad disappeared.   I don't know if the xBox and xBox Game Bar were installed then, but I think they are causing the problems. 

    I talked to CH Products.  They haven't heard of this problem.  I've lodged questions on AVSIM about the hardware conflict but haven't gotten any feedback.

    In any event, I'll go ahead with what I have and let you know how it works.

    Jim

    FSUIPC4.ini.org

  12. Hi John,

    Tried the JoyId program, switched the Throttle Quad to #3, reran FSUIPC4 and got basically the same result as indicated by the attached files.  Switched the id back and will go ahead without the name as you suggest.  I will identify the three CH controls as Y, Q and P as I've always done and see how they work.

    I the problem must be with the xBox app on my Win 11 box.  I've never used this app before and don't plan on using it now.  Maybe I'll uninstall it.

    Have you encountered this problem before?

    Thanks for your help.

    Jim

    FSUIPC4.log FSUIPC4.JoyScan.csv FSUIPC4.ini

  13. John,

    I did a search of the Registry looking for VID_28DE&PID_11FF which I think represents the xBox controller.  Can't find that value anywhere but when I reinitialize FSUIPC4, I get the same results, missing CH Throttle Quad name and the obvious conflict.  The log and scan still pick up the xBox controller.  I guess I could spring for another manufacturer's throttle quad but I'd rather try fo fix this problem.

    Jim

  14. Hi,

    Maybe a small problem but vexing.  New Win 11 machine. Installed Steam versions of FSX and MSFS.  Long time user of FSX, new to MSFS.  Problem is FSUIPC.ini files in both FSUIPC4 and FSUIP7 do not display the name, "CH THROTTLE QUADRANT" with the associated GUID.  Windows sees my CH Yoke, Pedals and Throttle Quad.  .ini files append USB to the recognized products.  Can I just plug in the missing name for the associated GUID since the GUID numbers seem correct?

    Attaching, scan, logs and .ini files from both installations.  Please advise,

    Thanks,

    Jim Driskell

    FSUIPC7.log FSUIPC7.JoyScan.csv FSUIPC7.ini FSUIPC4.log FSUIPC4.JoyScan.csv FSUIPC4.ini

  15. I have a Dell 8500, Win 10 running FSX-Steam and FSUIPC 4.976 licensed version.

    I have been using CH products for many years with few problems.  About three years ago, I had to replace my CH Rudder Pedals because the old set (in service for about 10 years) decided to stop working properly.  I think one of the control modules on the circuit board malfunctioned.  I bought a new set which have functioned properly until recently. I started to notice that I had lost directional control on landing and couldn't hold direction during the takeoff roll.  Viewing the aircraft from the rear and moving the rudder pedals, I see that I get full left rudder, the rudder at rest is slightly left and full right rudder only produces a slight right rudder.  I control all my addons with FSUIPC and have not changed the calibration for a couple of years.  I suspect the CH Rudder Pedals are malfunctioning.  Sometimes I can abruptly release the pedals which seems to rectify the problem but it returns almost immediately.

    I think it's time for a new set but I'd like your evaluation.

    Jim Driskell

  16. I have been spending a considerable amount of time flying the FSX-Steam version of PMDG's wonderful DC-6.  As with all my simulated aircraft, I control the DC-6 with a licensed copy of FSUIPC ver 4.9.74.  So far, I only have one problem with the DC-6 and I don't know if it has anything to do with FSUIPC so I thought I'd ask about the problem here.

    When flying an ILS approach, on course and intercept altitude,  the aircraft starts a momentary climb of about 500ft/min when intercepting the glide slope before stopping and losing the glide slope rather than pitching down on the glide slope.  Could FSUIPC have anything to do with this.  PMDG claims that the DC-6 will intercept and follow a glide slope if setup properly.  I think I an flying the intercept properly the the results are wrong.

    I'll update my copy of FSUIPC to the latest version but I like any ideas that anyone might have concerning this problem.

    Thanks,

    James M 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.