Jump to content
The simFlight Network Forums

jdriskell

Members
  • Posts

    63
  • Joined

  • Last visited

  • Days Won

    3

jdriskell last won the day on November 14 2024

jdriskell had the most liked content!

About jdriskell

  • Birthday 01/10/1937

Profile Information

  • Gender
    Male
  • Location
    Tacoma, Washington
  • Interests
    Computers, Simulated and Real Flying, Skiing

jdriskell's Achievements

Explorer

Explorer (4/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

3

Reputation

  1. So I fell back to the 2020 keyboard layout in the controls section. Everything works the way I had set it up in MSFS2020 except for various instrument views where I'm using ctl+shift+ what ever number I need. The rest of the assignments and axes are being managed thru FSUIPC. I'll work with this for a while. Jim
  2. I agree that view control has problems. FSUIPC controls some of the buttons some of the time but the assignments aren't consistent. I was initially using an old list of key assignments that turned out to be from MSFS2020. I'm now using the MSFS2024 key assignments which work sometimes. I think I'll try to map the essential buttons directly thru MSFS2024 into a blank configuration. I don't know why the developers decided to completely revise the key assignments. I'm a great believer in the old adage, "If it ain't broke, don't fix it." I'll let you know what I find. Jim
  3. I'm a long time FSUIPC user and have been very satisfied with its use in MSFS2020. I'm now starting to transition for MSFS2024. I've built blank configurations for my CH Yoke, Quad and Peddles. Many of the underlying FSUIPC assignments work but I'm having problems assigning views to the various buttons that I've always used. In some cases, the view buttons assigned under FSUIPC work but others don't. I've assigned some of the non-working previously assigned FSUIPC buttons directly under MSFS2024 control configuration. I'd like to hear of others experiences using FSUIPC in MSFS2024. Any hints or ideas will be appreciated. Thank, Jim Driskell
  4. Just an update. I removed the old quad and plugged the new one in. I didn't have to edit the .ini file. FSUIPC recognized all the button assignments but I had to re-calibrate the throttle axes. The new values are equal and smooth so dealing with worn potentiometer values is a problem of the past. But I got 18 years service out of the old CH Throttle Quad. Jim Driskell
  5. Hi John, Thanks for the quick reply. Your suggestions verify what I had thought so I'll give it a try. As usual, your support is par excellence. Jim Driskell
  6. Hi John, The mid-value is read when the throttle lever is at the neutral detente on CH Quad before its either advanced or reversed. The third lever's values are inconsistent with the other lever's values. Some my sim aircraft use direct inputs so the inconsistencies can be a problem. Additionally, the reverse thrust position on the throttle levers doesn't always work because I think thee is some dead areas in resistance when I move the throttle lever to reverse. I could replace all the potentiometers but that's a lot of work. So, I bought a new CH Throttle Quad. Since my old and new quads are the same, can I simply unplug the old quad and plug the new one in. I would reboot my machine, then remove the old one, reboot again to clear the assignments, the shut down an plug in the new quad and reboot. Will FSUIPC recognize the new one and accept the existing axes and button assignments? I've always labeled my CH controllers alphabetically after they have been discovered so I'm hoping to save some work. Of course, I'll re calibrate those axes on the Quad to take advantage of the new potentiometer values. Thanks for the advice, Jim Driskell
  7. I've been using the same CH throttle Quad and controlling it using FSUIPC for about 18 years. Both have served me faithfully thru the various versions of Microsoft Flight Simulator . But lately I think the potentiometer values in the Quad have changed enough that it's becoming difficult to calibrate. Currently I run MSFS2020 with FSUIPC controlling my CH Yoke, Pedals and Quad. Here are the values FSUIPC sees on the 6 throttle levers:             Max   Mid   Min Lever 1     14847 10663 -16384      Lever 2     14719 11313 -16254 Lever 3     15487  9232 -15604 Lever 4     14335 11313 -16384 Lever 5     14591 11053 -16254 Lever 6     14591 10272 -16384 With the exception of #3, the levers seem consistent. However, I would think the Max values would come closer to the Min values if the Pots weren't so worn. I can calibrate the various axes but the control between chosen levers isn't consistent. Should I expect more consistent values in a new quad? I'm thinking it's about time for a new one. Please advise. Jim Driskell
  8. Again thanks for jumping on the stoppage problem. I noticed it but when I saw the mention of problem on the forum I got the fix. Good work, Jim Driskell
  9. A brief note to thank your and Pete for your wonderful FSUIPC product. I've been using it for about 20 years and have found it superior for controlling my aged CH products. They are still working in spite of their aging POTS while FSUIPC irons out the bumps and jerks of the old systems. Keep up the good work! Jim Driskell
  10. 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
  11. Hi John, I tried another flight with the PMDG DC-6 with the same results, the CH Quad loosing control for Throttle 1 & 2. The only way I could control them was with the mouse. 3 & 4 continue to work. I'm attaching my .ini file and the really big .log file. I included throttle 3 & 4 for comparison. Sorry for the extra data. Jim Driskell FSUIPC7.ini FSUIPC7.log
  12. OK, I don't open FSUIPC very often if everything is working. Will be more observant. Jim
  13. John, Will do. MSFS starts FSUIPC and I don't usually read the splash screen but will do in the future. Jim Driskell
  14. 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
  15. 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
×
×
  • 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.