Jump to content
The simFlight Network Forums

macwino

Members
  • Content Count

    117
  • Joined

  • Last visited

Community Reputation

0 Neutral

About macwino

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://
  1. Thomas, I'll have PFC check out the controller. In the meantime, I'll manually configure the detents as shown in the User Guide. Interestingly, I checked and the PMDG 747-8i's flap detents, and they are similarly structured, but the bottom detents are somewhat further apart and it never caused me a problem. Thanks again for your assistance, Robert
  2. Hi Thomas, As you requested, attached is a copy of my fsuipc6.ini as it pertains to the PMDG 737 NGXu. Please remember that in the fsupc GUI the Flaps pane indicates that there are 9 detents for the Flaps and that the increments are 4094. I don't see where this information is set forth in the ini settings. Thanks for your assistance. Robert Robert's fsuipc ini for PMDG 737 NGXu.pdf
  3. I have a problem with my hardware flaps lever and the PMDG 737 NGXu in P3Dv5. I am using fsuipc 6. I am using a PFC USB TQ which has a flaps lever that is assigned and calibrated through fsuipc. The problem is that the detent settings are grossly uneven. For instance, the range of motion for Flaps 1, 2, 5, 10 and 15 takes up more than 4/5 of the lever’s entire range of motion. This means that Flaps 25, 30 and 40 are squeezed into the last 1/5 of the range of motion. It is almost impossible to set Flaps 30 because with the limited range of motion you almost always go from Flaps 25 to Flaps 40 instead. We’re talking about almost infinitesimal movement of the lever in this lower range between flap settings. Fsuipc indicates that there are 9 detents for the lever and that the increments are 4094. In all the years I’ve used fsuipc and the PMDG 737, I’ve never encountered this problem. There’s always been a sufficient space between flap settings so that the correct setting could be attained without making micro adjustments. Any thoughts on what might be the problem here and how I might fix it? Let me be clear. My lever does not have physical detents. It is a smooth flowing lever and has always relied on fsuipc’s ability to determine the number of detents and separate them accordingly over the lever’s range of motion. Thanks for your assistance. Robert
  4. I let this go for a day and tried the install again. This time it worked and I was able to get to the setup screen. I've no idea what might have caused the problem, but it's now fixed. Thanks for your assistance. Robert
  5. Hi Simon, Thanks for the prompt reply. I was hoping you'd encountered this issue before and had a quick fix. Guess not, so here's some more info. The cfg files are identical, which is strange and makes no sense. I also checked my 2 exe and 2 dll files in both locations to see if something had been added but they hadn't been changed by the STB installation or the failed launch. When this sort of thing happens that's where I usually find the problem. But not this time. I did not set STB to launch with p3d as I don't always use it. I just did the installation and then tried to launch P3D to make sure all was okay, a process I always follow after installing an add-on. Exactly what would I disable in the STB-DS addon.xml found in My Documents assuming it's created on installation and not on the first launch? Robert
  6. I have recently installed P3Dv5 including HF2. After running P3D for a few weeks without a crash, I decided to install STB Data Server 5.0.2020.17800. Following this installation, I could no longer launch P3D. The application would hang before it got to the flight setup screen. If I uninstall STB, the application still hangs on launch. The only way I can get P3D to launch again is to replace the Prepar3D.cfg file with a backup I always create before installing any new software. I have tried the STB installation twice over a few days with different copies of the installer. and both times I got the same result. Your assistance will be appreciated. Thanks. Robert
  7. Good point. Indeed, I'm currently using your built-in utility for this purpose with my Saitek TQs and had forgotten that. I appreciate that whether I were to use fsuipc or your built-in utility, either should theoretically work with the PFC turboprop TQ. I was simply looking for some reassurance from someone who has actually been able to setup the detents with this particular hardware. PFC's sales department has been very discouraging in this regard. Essentially, they've told me to use X-Plane if I want to use their TQs. Due to their stiff restocking fee, I was hoping to get some further actual user feedback before taking the plunge. Thanks for your input. Robert
  8. I would like to know if anyone has experience using the PFC USB turboprop TQ with the Real Air Turbo Duke v2 and the Majestic Q400. I am most interested in learning if you've been able to use fsuipc to program the detents built into the TQ for the beta range on these planes. Thanks, Robert
  9. Pete, thanks for clarifying this for me. While awaiting your response, I ran across your Profiles in Separate Files announcement and think I will give it a try. It is a feature that may make the conversion process worthwhile for me. Thanks again for the support. Robert
  10. Pete, thanks. Now, one more question, since you brought up the Profile facilities in fsuipc a few posts back. I’ve been reluctant to implement this feature because I go way back with fsuipc, and have stuck with using the “aircraft-specific” facilities for each plane in my hangar, which has worked well for me—though a bit tedious when changing hardware. Now that I’m about to change my yoke, pedals, joystick, and TQ, it may be time to reconsider the Profiles facilities you introduced several years ago. I appreciate that a single set of assignments for levers can work for a defined type of aircraft, e.g., single engine prop, twin engine prop, twin engine turbo, twin engine jet, etc. But what I’ve been concerned about—and what has prevented me from pursuing implementation of fsuipc’s Profile facilities—is how do I handle the unique characteristics of the various planes within these broad categories. For example, how do I use different slope settings for different aircraft within the same broad category such as twin engine jet? Do I have to setup a new profile for each jet aircraft, based on my default jet profile, and then edit it to include my slope settings for that particular aircraft if it doesn’t follow my default slope settings? Similarly, how do I customize different button commands for each plane’s popup windows within a broad category? I use my yoke buttons to popup 2D windows using the Shift+n commands. But each plane usually has different popups and different Shift+n assignments for these popups. So, again, do I have to setup a new profile, based on the default profile for that particular type of aircraft, and then edit it to include the specific button settings for that particular aircraft’s popup windows? Or is there a simpler way to accomplish this customization? If not, then, for me anyway, there seems to be no advantage to using Profiles. Thanks for your assistance. Robert
  11. Pete, thanks for this important info. Let me make sure I understand what you’re saying about the PMDG and Airbus aircraft. I think you’re saying that I won’t be able to assign fsuipc’s reverser axis command (in the pull down command list on the left side of the axis assignment window) to the dedicated reverser levers on the PFC USB TQ. Instead, I will have to use P3D’s F2 key command. Here’s how I would anticipate utilizing this F2 command. Please let me know if this is what you have in mind. I would go to fsuipc’s Axis Assignment window and move the TQ’s dedicated reverser lever for Throttle 1 to select it. Then, in the right side area of the fsuipc window, I would setup a range for the upper part of the lever and assign it to the Throttle 1 Cut command in the pull down list. Then, I would setup a second range for the lower part of the lever and assign it to the Throttle 1 Decr command in the pull down list and have it repeat if found to be necessary. Then, I would repeat this process for the Throttle 2 reverser lever using the Throttle 2 commands. In this way I can utilize the PFC USB TQ’s dedicated reverser levers as though I’d assigned a reverser axis command to them. Am I on track? Thanks, Robert
  12. In that case, here's what I'm most concerned about: 1. Will the PFC USB turboprop TQ work with the Real Air Turbo Duke v2 and the Majestic Q400? I am most interested in the ability to use fsuipc to program the detents built into the TQ for the beta range. 2. Will the PFC USB two-engine enhanced jet TQ work with the PMDG 737 and 777 and the Aerosoft Airbus? I am most interested in the ability to use fsuipc to program the TQ's dedicated reverser levers. Thanks, Robert
  13. Thanks, Pete. I very much appreciate your prompt input. Now, I'd like to hear from anyone who is actually using the PFC USB TQs, and learn if they have any tips for setting them up with fsuipc. No one seems to post about this, and perhaps that indicates that it's really trouble free, which I hope is the case. Thanks, Robert
  14. Before investing in the PFC jet throttle quadrant with dedicated reverser levers and the PFC turboprop twin engine throttle quadrant with detents for the beta range, I wanted to make sure that others have been able to get these TQs to work properly in P3D v3.1 using fsuipc in Windows 7. PFC sales isn’t terribly helpful, and they stress that they do not support P3D and profess a buyer beware attitude. I suspect that their USB TQs will work just fine with P3D but they don’t want to be bothered with supporting the required fsuipc configuration. In this regard, there is an October 2014 post in the Avsim forum that indicates that they should work. See http://www.avsim.com/topic/449386-pfc-throttle-quadrant-not-working-in-p3d-v23/. I was hoping that Pete (who I think uses the serial version of PFC hardware but who may have some experience with the USB TQ devices) or some others who actually use the PFC USB TQs might be able to give me some reassurance. Any assistance will be greatly appreciated. Thanks, Robert
  15. Peter T, thanks for posting this solution. I'm sure it will be helpful to others who might experience this problem. It parallels somewhat my own experience that I never documented here because I couldn't be sure what I'd done exactly and I also felt it was probably a one off. I gave up on my TQ and arranged for Saitek to send me a new one. I can't remember now whether they sent me a PS2 or a USB replacement, but I believe it was USB. I unplugged my PS2 TQ and plugged in the new one. I never messed with the Device Manager at all. But even with the new TQ I still had the same problem as before. So I planned to return it, removed it, and plugged my old TQ back in. Lo and behold, FSX and fsuipc both suddenly recognized the axis on my original TQ that had been giving me the problem. Thanks, Robert
×
×
  • 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.