Jump to content
The simFlight Network Forums

cavaricooper

Members
  • Posts

    96
  • Joined

  • Last visited

Posts posted by cavaricooper

  1. 1 hour ago, John Dowson said:

    As you know what causes this issue, you just need to eliminate that. i.e this:

    Also check that you have an empty profile assigned in MSFS, or at least that you don't have assignments in both FSUipc and MSFS for the same buttons/axes.

    John

    John-

    You've got a bit of your Dad's genius in you mate! 

    That was the ticket.  With the "G" mapped in MSFS, and the Gear Up command REMOVED (I thought it was) and the "G" keystroke assigned to that lever with "Keypress not to be held" I'm fairly confident that I've got this licked.  Give me a few hours and I will confirm.

    Ta!

    C

  2. 11 hours ago, Pete Dowson said:

    So that lever is faulty, constantly sending button press/release notifications? Is Honeycomb going to fix that?

    And why are you assigning to a Key press (G) instead of the more efficient GEAR TOGGLE control? Or, better, GEAR UP / GEAR DOWN? Do these controls not yet work in MSFS?

    If you are referring to FSUIPC3 and FSUIPC4. I think what you refer to was actually a Sim code hack which will not be done in the 64-bit FSUIPC5/6 not can it be with FSUIPC7 being a separate process altogether.  And "Fix control acceleration" wasn't a "flood" prevention -- there was never any such thing. If a button is continually signally a change FSUIPC must obey its assignments. The facility you refer to just changed the time value in the sim which was being used to determine whether to accelerate or not. And it operated on controls (events) not keypresses.

    I think the fix has to be in the Honeycomb device. Have they explained why they have it repeating like that? I can only assume it is a production bug. 

    Pete

     

    Pete-

    I use a PFC Controls Cirrus Console II which I have completely re-wired with Leo Bodnar boards- there is NO HONEYCOMB involved.

    Toggle Results in the same behavior- as the Gear Up position is what keeps sending.  I therefore resorted to a "G" keystroke, and SELECTED Not to be held, however, that too does not resolve the issue.

    Do you have any thoughts on how I can use my HW, and still get one degree movement with mouse wheel clicks (without leaving the Gear Handle down as I do now)?

    Ta- C

  3. John-

    The topic was closed without resolution so I started another one-

    No, I use a PFC Cirrus Console II rewired with 2 Leo Bodnar boards. The Honeycomb video was merely for illustration.  My issue is that my Landing Gear Lever, when up, floods MSFS with the pressed switch command constantly.  That creates the 10 degree heading control problem. This despite the fact that I stopped using the right side (Gear Up/Gear Down) and went to a keystroke "G" (toggle gear) with the tick box checked specifically to obviate this issue. 

    Zt4M3zi.png

    In the older versions of FSUPIC it was possible to tick a box (on the Misc Tab I believe) to STOP THE FLOODING issue.  Could we please implement that again?

    I realize you are very busy, but I would ask that you please do not close this topic until the issue is actually resolved. My current solution (not desirable) is to leave the Gear Lever down, and press the keyboard "G"... wholly negating the HW.

    I appreciate what Pete and now you do for us all, and remain obliged.

    C

  4. Pete or John-

    HAPPY 2021!

    Lately (perhaps coinciding with the latest Sim update) I have been unable to tune my instruments (especially HSI/VOR CRS knob) in one degree increments.  It seems to default to 10. It's driving me absolutely batty!  I've checked my mouse settings and they are all set to 1 click not 3. Is there a solution I'm overlooking? 

    To add to the head scratching- on the ground I can tune 1 degree at a time.. but not airborne.  Baffled.

    I remember some sort of setting for something similar in FSUIPC for FSX or before... is there capacity for fixing this, or is there something simple I'm being a Git about?

    Ta- C

  5. To follow up... all my buttons stuck in the default controls menus except for Custom Cockpit Camera 9... Alt+9, so I assigned a second command for that camera to the Tilde key, and just mapped that in FSUIPC to the button I wanted. Presto- alles gut.

    Looking forward to FSUIPC’s growth, as it will represent the evolution in the SDK that all the serious aircraft developers are waiting on....

    Bring on the payware version... I’m ready 🙂

    C

  6. I know this is a WIP... however, I remember Pete discussing the possible ability to use button presses to control the camera (Alt+1, Alt+9 etc.) as a workaround.  I too would love this ability as the Control Mapping for this is still broken in MSFS.  Is this close to being implemented... atm all I get when I try and map Alt+9 is (null).


    Ta- C

  7. There are times (when flying using PSX with MSFS only as a camera platform) that I need to disable ALL my in game controls.  Then, when I am flying MSFS, I need them back (at least for the X-Box controller I use for camera manipulation).  Is there a quick and easy way to do this reliably?

    Ta- C

  8. John-

    I’m very glad to read this. Whilst MSFS2020 looks like it will move the goal posts, your Dad’s (?) program has allowed an entire microcosm of development, not the least of which is LINDA. For HW aficionados, FSUIPC is the sauce in the recipe!

    I look forward to whatever you come up with, as soon as you are able to. Should I be able to assist you with testing, do reach out.

    Best- Carl

  9. Pete-  just one more user, grateful for your work, and ready for v5. With all my PFC stuff, converted to USB with LEO Bodnar cards, I'm basically grounded without your incredible software (I have multiple .ini files for each throttle configuration).

     

    Fingers x'ed for a smooth development process and transition.

     

    Best- Carl

  10. After banging my head on the Simconnect wall due to an interaction with the new version from EZCA I had to delete EZCA and go back to Mouse Look which is fine, as I am using P3d for visuals only atm. ALL I REALLY NEED IS TO DEFINE A FORWARD, RIGHT AND LEFT VIEW AND HOPEFULLY MAP THAT TO A JOYSTICK BUTTON. Is that possible????

    To get the mouse look I had to enable controls.... What now? I used to not tick enable controls and map everything in FSUIPC.... Does that now go back to default axis' or does the FSUIPC still override normal controls? I need my settings when I fly aircraft in P3d as I have multiple throttle quadrants and need the mapping.

    I am learning to use standard camera views and mouse look and it is a steep curve......

    Thanks in advance for any assistance provided

    Carl

  11. I have ordered 2 Leo Bodnar cards and am in the process of converting my serial PFC Cirrus Console II and Rudder Pedals to full USB versions.  Once that happens, I THINK I will not need Pete's PFCHID module, as it will then be a compliant USB device...... is that correct?  I would very much appreciate responses from those who are ACTUALLY USING Leo Bodnar cards.... I am going to install the BU8036X for the Flight Console (including yoke and TQ) and the BU8036A for the rudder pedals separately.  Also, and connecting/programming advice- AGAIN- from those actually using Leo Bodnar cards.

     

    Thanks!

     

    Carl

  12. Chris-

     

    I fly PFC as well.  My stuff is all older (Serial) however, my fsuipc.ini files ought to work for you just fine- you just won't need the pfcfsx.ini stuff.  

     

    Drop me a PM with your email and I will send them over.  FYI, being mostly a dolt, I use separate .ini files for each quadrant I have (5) so that axis and buttons all work correctly regardless of which quadrant I am using at the time.  

    I know this is all possible within a single fsuipc.ini file- but it evades me.....

     

    Carl

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