Ross McDonagh

+1 for this

The more they know people are having an issue-the better position they’re in to fix it... On that note... I’ve got this issue as well (plus no ability to squawk Charlie on vatsim and no weather radar)

Will do John I’ve got some stuff sorted for the moment but it needs work. I’ll post these when I can probably tomorrow. Thank you so much.

I have not used said facility but I will certainly take a look John thank you again.

The Honeycomb/Aerosoft Software seems to enable the LED’s for gear/annunciation panel on the Bravo-as seen in the video. It’s quite a bear and there’s only a 5 page manual! It has all kinds of LVAR’s and such. It seemingly auto assigns GEAR/FLAPS and it also seems the autopilot button. That brings me back to a new question: ..I’ve programmed the Autopilot button in FSUIPC-but because I can’t figure out how it works/how to set it in the honeycomb software, my FSLabs rotorbrake control code for Autopilot is HALF working-I press the AP button and it animates in the cockpit BUT the autopilot won’t stay engaged. I’ve checked all the assignments... The ONE thing I have assigned in P3D is the steering axis on my Thrustmaster Airbus sidestick Z axis-I use this for ground steering in every aircraft. I had made no assignments until I had the devices re-plugged in and perhaps that was due to them not going to the same USB ports? My rudder was assigned in FSUIPC to flaps and my left/right brakes were spoilers and something else. I’ve got the axes sorted. It’s onto the buttons at this point and trying to figure out how to make the shifted functions in LINDA work to adjust the rotary switches in each aircraft which I’m still not sure is totally possible.... Thanks as always for your help John I appreciate it very much I’m sure I’m not the only one trying to figure this out-I’ll keep messing around and see what I can bring back to the community.

Hello all, I’ve just moved into a new house and finally just about completed my setup (waiting on the TM Airbus Add On if it ever decides to ship) Previously I had a great setup going with the Honey alpha, CH Throttle Quad, Logitech Rudder Pedals and the TM Airbus Sidestick and Throttle... I used rotorbrake for the FSLabs and some custom control codes and keyboard bindings for the PMDG and TFDI Aircraft I use. (The CaptainSim 76 and FeelThere E Jets are another story altogether) Fast forward to me moving a few blocks up the street the day after my Honeycomb Bravo throttle arrived. I plugged in the Bravo and left the CH unplugged. My axes went nuts-flaps were assigned to brake pedals, spoilers to the rudder axis.... I deleted all axes and buttons in P3D but SOME functions of the Bravo work in the 737... Gear, trim and the CRS knob come to mind. I can’t get throttle 1 to work but throttle 2 does work. I’ve attached a video and my FSUIPC.ini My questions are: 1. Should I just delete the FSUIPC.ini and start from scratch with each aircraft? OR can I remove the CH Throttle assignments and go from there? 2. FSUIPC (and windows) don’t seem to recognize the rocker/toggle switches on the Honeycomb-Linda DOES recognize them but I’m trying to keep it fairly simple-I had a few issues trying to sync LINDA (which I previously had only used on the QW787 and Aerosoft A330) to sim with the 737 module 3. It seems the Aerosoft/Honeycomb software doesn’t play well with FSUIPC... When it was installed a few things were working and when I uninstalled the Honeycomb software-the gear and some other functionality stopped working. (but my throttle 1 started working again) Any ideas on this are welcome! This has been a 1-2 hour a day affair for the last few days. I’m anxious to get back in the air but it’s been a grind trying to get this to work. Lots of confusing stuff and I feel like I’m slowly getting there but need a bit of expert direction from the folks around here FSUIPC6.ini

Glad to see I’ve helped out a bit John

That still means I can send it as a custom control for FSUIPC? Thanks Pete. I appreciate the help. I had always used macros back in the 2D cockpit days. Looking forward to doing it right this time

After some spending some time researching/ learning after the help John and Pete gave me in my other thread here earlier in the week, I think I’m about ready to try and ditch the mouse macros to button controls that I was using as a solution to bind my autopilot controls to my honeycomb yoke switches. My question/issue in this is that with the A3XX series (or any Airbus) the autopilot controls are a momentary push/pull type of switch to select the desired mode. I am using the 4 rocker “switches” on the honeycomb yoke (and I intend on using the same type when my honeycomb bravo throttle arrives in the fall. See pics for what I mean Now instead of being actual switches they’re actually buttons which remain depressed/active so long as the position is up or down. For example if the switch is up, button 23 is continually “pressed” and if the switch is down, button 22 is continually pressed. With my current mouse macros, in one airbus (Aerosoft) it shows the animation of the autopilot/FCU switch shows permanently pushed or pulled in even though the autopilot mode activates as desired. Bearing that in mind, I found these parameters (offsets? Lvars? Both?) on the FSLabs Forums to send thru FSUIPC to my switches. The italicized text is copied from a thread over there All of these are as above (rotor_brake) commands: Alt(itude) Push (left-click): 71249 (mouse click), 71252 (mouse release) Alt Pull (rt-click) : 71250 (mouse click), 71253 (mouse release) Alt(itude)increase: 71261 Alt decrease: 71262 I can send the increase/decrease commands to my CH throttle switches (3 way switches-up/off/down no problem. What I’d really like to do and need guidance on is how to send Alt Pull/Push AND Mouse release while the switch remains depressed. So for instance when I select my switch up (thereby depressing button 23) I’d like to send the commands: Alt(itude) Push (left-click): 71249 (mouse click), 71252 (mouse release) In the same push as it were even though button 23 remains “on” I realize that I can’t send 71252 (mouse release) as a “control to send when button released” because “button 23” never becomes released so long as it’s in the up position. Any guidance would certainly be appreciated!

Ok John, I’ll hold off on the log. In the meantime, I’ll ask about control sets over in the forums. The head developer replied to my GPU hang issue so I’ve got some updating to do thanks so much for all your help!

Will do. With the great advice you’ve given I’m going to remove the 3 way switches and try to find out a way to turn the switch off and on. I can’t thank you enough for your patience with me. I recall Pete doing the same with a friend of mine when we first discovered FSUIPC way back when and my friend telling me how great it was and he put up a YT video which I came back to to make macros all these years later. My plan is going to be to clear out all the macros and try to get the LVARs setup. I found a list of LVAR and rotorbrake codes on the FSL forums but I didn’t see many of the specific controls I’m looking to program (mainly for the FCU/Autopilot) so I’m not sure if FSL uses an FS command or not.

I did indeed find and remove that. So the landing light (and taxi, strobe lights) is a 3 way switch on the A320. The landing light is retract/extend/on while the taxi light is Off/Taxi/Takeoff and the strobe is Off/Auto/On. Obviously the honeycomb alpha doesn’t have a 3 way switch. I was meant to setup button 21 for “down” and 22 for “up” but put the repeat on there so it would cycle thru both settings because on the honeycomb when the switch is up, the button remains pressed. How does one unassign a macro after it’s been made and how would I get you the log file?

Thanks John, I’ll give it a whirl. Of all things after my reinstall and deletion of the macros, I got a GPU hang climbing out of FlyTampa KBOS. I shut the computer down in disgust, then got mad at it, turned it back on, went to (of all places) FlyTampa Las Vegas (with pretty much everything turned up to 100%) and did a SID/STAR/visual flying around at night with no problems but some reduced frame rates. So I take it once I list the LVAR’s I should be able to see what controls are what inside FSUIPC and go on from there? I’ve now got the manuals in my phone (well most of them) so I’ll be going thru those today while I’m at work. I have all afternoon today to hopefully sort issues and then I’m really hoping to fly all day tomorrow.

John, attached are all the Macros I can see Please let me know if you need more. I would probably delete and restart the macro making particularly since I have to completely reinstall the FSLabs A320. Just want to get a fresh start on this. I've been waiting 11 years to fly this bird and finally have a system capable enough to do it, but it seems not without some headaches and heartaches first. A320 Test.MCRO.bakA320 Test.MCROTFDI 717.MCRO.bakTFDI 717.MCRODefault Test.MCRO

Adrem, thank you so much for the comforting words!!