Jump to content

Bert Laverman

Members
  • Content Count

    128
  • Joined

  • Last visited

  • Days Won

    1

Bert Laverman last won the day on September 16 2020

Bert Laverman had the most liked content!

Community Reputation

34 Excellent

About Bert Laverman

  • Rank
    Flight Student - Solo

Recent Profile Visitors

1932 profile views
  1. Yesterday I received a reply from Honeycomb: There is no calibration procedure for the Bravo like the "Konami code" for the Alpha.
  2. 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?
  3. 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
  4. The driver wasn't installed anyway. Will try it on my work laptop and see what the calibration says. Bert
  5. I have noticed the following strange behavior: When I move the throttles slowly towards their highest position, I noticed the throttles in Prepar3D made a jump in the last bit of the range. Using FSUIPC and the Windows 10 Game Controllers calibration I have checked this, and the values reported are actually supporting this. When using FSUIPC I see the value skipping the last 3000 values (range is there -16383 to 16384), when using Raw Data (also shown when doing calibration in the Control Panel "Game Controllers" calibration) it is from somewhere in the 800 to the max value of 1024. (range is
  6. Ok, starting with the Prepar3D settings, you have a lot of devices in there, and (apart from the keyboard) they all define axes: A single Honeycomb set: Alpha Flight Controls {1900294B-0010-0001-A945-9A55E23F5B1E} Bravo Throttle Quadrant {1901294B-0105-0001-FA78-ED87325A89E3} Two sets of Saitek Pro-Flight controls: Set 1: Saitek Pro Flight Yoke {113A4BD0-42E4-11E8-8001-444553540000} Saitek Pro Flight Quadrant {862B1FF0-42E4-11E8-8002-444553540000} Saitek Pro Flight Rudder Pedals {BC
  7. Can you share your Prepar3D control mapping and FSUIPC config? The first is stored in "C:\Users\<yourusername>\AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls\Standard.xml", but there is also a button named "Export" in Prepar3D that you can use to make a copy. The "FSUIPC6.ini" file is in the installation directory of FSUIPC.
  8. David, generally the simulator is not that smart, unless the device explicitly names the axes for the intended purpose. Since the Bravo Throttle Quadrant only tells Windows that is has 6 axes, but provides no purpose for them, P3D will assign a default set, which usually includes (again) elevators, ailerons, rudder, and throttle. So it is always best to verify that whatever Prepar3D has chosen for you will match your intentions. Please note that Prepar3D will not provide aircraft-specific profiles, so if you set everything up for the 747 and then load a twin-engine jet, the as
  9. Scott, this does not sound like a problem caused by the PMDG profiles, as they only deal with the buttons and LEDs. Also, it helps if you ask such a question in a new topic with a matching title, rather than "hitching a ride" on a different topic. I just happened to still get notifications on this one, otherwise I wouldn't have known you added a new question to it. Now in your specific case, my first question would be if you bind the axes using FSUIPC or Prepar3D? I myself use Prepar3D for the rudder pedals, as most (if not all) aircraft use the standard "Rudder" axis for it.
  10. These are from the Prepar3D SDK. In the Windows Start Menu, do you have an entry called "Lockheed Martin" -> "Learning Center"? In it, choose the "Software Development Kit (SDK)" section, then at the bottom "References" -> "Variables" -> "Variables Overview". The "INT" key is for "internal" and can be used in the configurator. You can set values to them in a "Variable" entry, and query their content using a "Condition". Bert
  11. With the current version (2.1.0) this is possible. Please check you version in the configurator. Use "Actions" -> "Open Settings" -> "About".
  12. Ok, here's what I did: Download your file and rename it to something that does not clash with my current profiles, I used "Test - PMDG_NGX(u)_Yoke.json". Open the file with Notepad++, but any text editor will do. At the top, update the name in "SaveName" to exactly match the name of the file, excluding the ".json" extension: { "Version": 1, "Language": "DE", "SaveName": "Test - PMDG_NGX(u)_Yoke", "Data": [ Start the configurator and import the profile, using "Actions" -> "Open Settings" -> "Import Profiles" -> "Select File". After selec
×
×
  • Create New...