Jump to content

Bert Laverman

Members
  • Posts

    137
  • Joined

  • Last visited

  • Days Won

    1

Bert Laverman last won the day on September 16 2020

Bert Laverman had the most liked content!

1 Follower

About Bert Laverman

Recent Profile Visitors

2254 profile views

Bert Laverman's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

37

Reputation

  1. Hi Bert,

    Im a newbie so i apologize for a stupid question. I run pmdg 4.5 i purchased the honeycomb alpha, hooked it up, downloaded. Opened configurator, activated pmdg, went to "download profiles" downloaded 737ngxu in my aerosoft account. Downloaded a json file?, windows would not open so I downloaded a json app to open. Opens as a text file?

    cannot save to the sim to activate, watched a few vids but they seem to bypass this part, go straight to opening the file?. What am I doing wrong here?

     

    Thanks from a very annoyed purchaser of these products

    1. Bert Laverman

      Bert Laverman

      Martin, there is actually a support forum for this at https://forum.aerosoft.com/index.php?/forum/245-hardware-and-os-discussions-suggestions-and-insights/.

       

      You said you downloaded the profile, but did you activate it in the Configurator? When you run Prepar3D, in the Add-on menu, do you see an entry for the AFC Bridge?

       

      Cheers,

      Bert Laverman (not an Aerosoft or Honeycomb employee)

  2. Eduardo, so far, 99% of the time this turns out to be an actual double configuration. When you connect a new device, or sometimes a known device on a new USB location, Prepar3D will see it and give it "default" assignments. If, at the same time, you are using FSUIPC for this, you'll end up with confusing double assignments. A similar problem may happen on the button side, where a set of default bindings can conflict with either FSUIPC or the Honeycomb Configurator. Cheers, Bert Laverman
  3. Ok, it looks like Throttles 1 through 4 are also in FSUIPC: [JoyNames] AutoAssignLetters=No 0=Saitek X52 Flight Control System 0.GUID={B2573D10-CB2D-11EA-8001-444553540000} 2=Mad Catz Pro Flight Combat Rudder Pedals 2.GUID={B257B240-CB2D-11EA-8009-444553540000} 1=Bravo Throttle Quadrant 1.GUID={BE0377C0-A8D9-11EB-8001-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=1X,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 1=1Y,256,D,0,10,0,0 -{ DIRECT: Throttle2 }- 2=1Z,256,D,0,0,11,0 -{ DIRECT: Throttle3 }- 3=1R,256,D,0,0,0,12 -{ DIRECT: Throttle4 }- So, if you have them in the Prepar3D Controls, then it looks like that is your problem.
  4. Can you provide your Controls definition and, if you have FSUIPC installed, your FSUIPC.ini or FSUIPC6.ini?
  5. Yes, if you installed the X52 drivers, it may conflict with some aspects of other controllers. I noticed the X52 driver will disable e.g. Saitek Flight Info Panels. That caused me to immediately de-install them, so I have not tested what they did vs the Alpha. My Bravo is not at home at the moment...
  6. The Honeycomb configurator is only concerned with buttons, switches, knobs, and LEDs. The Axes you should configure in P3D/MSFS or FSUIPC. Bert
  7. Not to be too simplistic about this, but have you asked the SimHanger guy? I have not viewed/used his video so I can't comment on its ionstructions. Bert
  8. The levers requiring "reverse" to be on is normal, but having one lever move two engines sounds like you have multiple definitions. Where do you have the exes defined? In P3D or FSUICP... or could they happen to be in both? Bert
  9. Yesterday I received a reply from Honeycomb: There is no calibration procedure for the Bravo like the "Konami code" for the Alpha.
  10. Yes, on my laptop from work, which definitely has never been used with game controllers before, shows the same behavior: 0 to 823, and from there it immediately skips to 1023 and holds that value during the last segment. Is there a Honeycomb device calibration for the Bravo?
  11. Additionally: the Alpha and Bravo are both connected via a USB 3.0 hub. I just saw the remark in a different thread about the Honeycomb devices having trouble with USB 3.0. Could this be related? Also, there is a calibration built-in inn the Alpha, but I see no such procedure listed in the Honeycomb KB for the Bravo? Bert
  12. The driver wasn't installed anyway. Will try it on my work laptop and see what the calibration says. Bert
×
×
  • Create New...