Jump to content

Bert Laverman

Members
  • Posts

    137
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Bert Laverman

  1. 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
  2. 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.
  3. Can you provide your Controls definition and, if you have FSUIPC installed, your FSUIPC.ini or FSUIPC6.ini?
  4. 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...
  5. The Honeycomb configurator is only concerned with buttons, switches, knobs, and LEDs. The Axes you should configure in P3D/MSFS or FSUIPC. Bert
  6. 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
  7. 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
  8. Yesterday I received a reply from Honeycomb: There is no calibration procedure for the Bravo like the "Konami code" for the Alpha.
  9. 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?
  10. 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
  11. The driver wasn't installed anyway. Will try it on my work laptop and see what the calibration says. Bert
  12. 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 -1024 to 1024) Because this happens in the raw data, I am unable to use the last bit of my throttle range. I have reset any calibrations, but this did not help. Anyone an idea? Bert
  13. 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 {BC87B5F0-3C9E-11E8-8003-444553540000} Set 2: Saitek Pro Flight Yoke {0BAC06A3-0304-0000-0000-000000000000} Saitek Pro Flight Quadrant {0C2D06A3-0202-0000-0000-000000000000} Saitek Pro Flight Rudder Pedals {076306A3-0101-0000-0000-000000000000} A collection of Thrustmaster controls: Thrustmaster Virtual Game Controller (root) {E2F999D0-3CA1-11E8-8006-444553540000} Joystick - HOTAS Warthog {44B0B930-3C9B-11E8-8001-444553540000} Throttle - HOTAS Warthog {59940370-3C9B-11E8-8002-444553540000} Two sets of Airbus controls: Set 1: T.A320 Pilot {FF6DAA20-7443-11EB-8002-444553540000} TCA Q-Eng 1&amp;2 {E5819E00-7443-11EB-8001-444553540000} Set 2: T.A320 Pilot {0405044F-0200-0001-D6B5-020000000000} TCA Q-Eng 1&amp;2 {0407044F-0200-0001-F752-B14FE92FAAAA} Anyway, Prepar3D seems to have assignments for both your Honeycomb devices. For the Bravo, the assignments are: <SimControls.Map> <Name>Bravo Throttle Quadrant {1901294B-0105-0001-FA78-ED87325A89E3}</Name> <Axis> <AxName>XAxis</AxName> <Index>0</Index> <AxEvent>AXIS_THROTTLE1_SET</AxEvent> <AxScale>-127</AxScale> <AxNull>1</AxNull> </Axis> <Axis> <AxName>YAxis</AxName> <Index>1</Index> <AxEvent>AXIS_SPOILER_SET</AxEvent> <AxScale>127</AxScale> <AxNull>1</AxNull> </Axis> <Axis> <AxName>ZAxis</AxName> <Index>2</Index> <AxEvent>AXIS_FLAPS_SET</AxEvent> <AxScale>-64</AxScale> <AxNull>64</AxNull> </Axis> <Axis> <AxName>RxAxis</AxName> <Index>3</Index> <AxEvent>AXIS_THROTTLE4_SET</AxEvent> <AxScale>-127</AxScale> <AxNull>1</AxNull> </Axis> <Axis> <AxName>RyAxis</AxName> <Index>4</Index> <AxEvent>AXIS_THROTTLE3_SET</AxEvent> <AxScale>-127</AxScale> <AxNull>1</AxNull> </Axis> <Axis> <AxName>RzAxis</AxName> <Index>5</Index> <AxEvent>AXIS_THROTTLE2_SET</AxEvent> <AxScale>-127</AxScale> <AxNull>1</AxNull> </Axis> <POV> <Index>0</Index> <Down>PAN_VIEW</Down> <DownRpt>1</DownRpt> </POV> </SimControls.Map> So, you have Spoilers, four throttles, and flaps assigned here. Now FSUIPC: [JoyNames] AutoAssignLetters=No 2=Saitek Pro Flight Rudder Pedals 2.GUID={BC87B5F0-3C9E-11E8-8003-444553540000} 0=Bravo Throttle Quadrant 0.GUID={2E5C74B0-8D85-11EB-8001-444553540000} 1=Alpha Flight Controls 1.GUID={3C1332B0-8D85-11EB-8002-444553540000} FSUIPC knows about your rudder pedals and the two Honeycomb devices, the Bravo being device 0, the Alpha device 1, and the rudder pedals device 2. The axis assignments are: [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=1R,256,D,5,0,0,0 -{ DIRECT: PropPitch }- 4=2X,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 5=2Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 6=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- So, FSUIPC does Aileron and Elevator on the Bravo ("0X" and "0Y"), Throttle and PropPitch ("1Z" and "1R") on the Alpha, and Rudder with Toe-brakes ("2R", "2X", and "2Y") on the Saitek Pedals. So, you have double assignments, and they are indeed in conflict. Quickest way out is to remove the FSUIPC assignments, as they do the wrong thing. (Aileron and Elevator on the Bravo, Throttle and PropPitch on the Alpha) Just remove the 7 lines assigning axes in the "[Axes]" section. The lines for the Rudder Pedals are duplicates from the Prepar3D definitions anyway, so you don't need those either. I do not know how the current assignments got into FSUIPC. Now for the way forward: if you want to use FSUIPC's profiles to have aircraft-specific assignments, then start by removing the assignments in Prepar3D, and re-assign them in FSUIPC. This takes a bit more work and puzzling, but will allow you to use the middle two axes for the 737 throttles, and the middle four on a 747. However, this has nothing to do with the Honeycomb Configurator. Cheers, Bert
  14. 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.
  15. 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 assignments will possibly again not match your expectations. FSUIPC is often used to add this flexibility. Cheers, Bert Laverman
  16. 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. If you're using FSUIPC, are you perhaps using profile specific assignments? Then maybe the FSUIPC profile for the NGXu was lost and you need to assign them again. Cheers, Bert Laverman
  17. 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
  18. With the current version (2.1.0) this is possible. Please check you version in the configurator. Use "Actions" -> "Open Settings" -> "About".
  19. 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 selection, tick the box in the list and "Import Profiles". In the "Profiles" list I selected the profile. Now, when I tilt the yoke forward so I can see the buttons, and select the "MASTER BAT" switch, and choose "Master Bat ON", I can see your assignment fine. What version of the configurator do you have installed? Mine says he is version 2.0.0 ("Actions" -> "Open Settings" -> "About"), but the download was "AS_HONEYCOMB_P3DV4_V2.zip", containing a "AS_HONEYCOMB_P3DV4_V2001.exe", so I guess I have 2.0.0.1. Since the Aerosoft site is a bit weird in its download behavior for these files, if you can't download the latest let me know, I'll attach a copy here. Page to download it from: https://www.aerosoft.com/en/hardware/flight-simulation/throttles/2568/honeycomb-bravo-throttle-quadrant?c=835 Bert
  20. Ok, that is an important clue: The apps are very sensitive to the syntax of the file. Can you share it?
×
×
  • Create New...