mryan75

Just to report back, this works wonderfully. I thought I would have to adjust the speed, but with the stock 172 in MSFS2024 it works perfectly with your settings. I assume I can use the same setup (as shown in post 2 of this thread) to set up the trim button on the Honeycomb Alpha? As I have electronic trim in my real plane I would really like to have both set up concurrently, the Alpha trim button and the Bravo wheel. Once again, thank you for your help.

That's really odd, it's the one that was included with my download. I don't see another anywhere. But in any event, swapping those and deleting the axis did the trick. It moves rather slowly so I will have to adjust the speed, but it works. There's just so much lag in the trim in MSFS that it's impossible to handfly GA aircraft with any consistency. Thanks very much for your time, John.

Correct, it's the speed brake axis that is controlling the trim. When I move that axis it shows: Joy A#, Y Axis#. Send direct to FSUIPC calibration. "ElevatorTrim". When I move the trim wheel itself, in Axes Assignments it shows nothing at all, and in fact it doesn't cause any indication in any of the "Assignments" sections when I roll the trim wheel. Assignments in MSFS 2024, I have nothing set to elevator trim for the Bravo. The sim recognizes the trim wheel as buttons 22 and 23, and there is nothing assigned to either the trim wheel or the speed brake axis (I'm using the Asobo 172 G1000 to set this up, that's my trim wheel guinea pig). My ini and the lua file I'm using are attached. Thanks so very much, John. Rotaries.lua FSUIPC7.ini

So I got kind of a funny result, @John Dowson. I copied the trim wheel settings you cited in the above thread, with my Bravo being A; under Buttons I have: And strangely enough, the first slot of my Bravo now acts as the trim wheel. In other words, the furthest left of the 6 axes, what would be your left throttle in a twin engine piston configuration. That lever now acts as the trim axis rather than my trim wheel. No conflicting settings in the sim. I say the result is funny as the axis works PERFECTLY. It's exactly what I want, just the wrong "thing" controls it. Suggestions?

It's buttons in each direction, I found that out yesterday evening. Thanks again to you and to @John Dowson, your reply below should set me straight. Thank you both!

Do I need to use the rotaries.lua file to get my Bravo trim wheel to work in FS2020/2024? It recognizes other axes but not when I rotate the trim wheel. I may actually use your initial suggestion with a increase/decrease button on my Alpha yoke, I use electric trim in real life and would prefer it in the sim actually. Ideally what I'd love to have is gross trim using the wheel and fine trim using the buttons, so I can make large changes and then fine tune.

I am very grateful for your reply, @ark1320, thank you!

I greatly appreciate this explanation! Would I be able to se it to the trim wheel on my Honeycomb Bravo? Or is there an axis assignment that does the same thing? I think I actually had that set up in the early days of FS2020. Many thanks again for the assistance.

Hi all, The default trimming in MSFS 2024, like 2020, is awful. If you spend a 10-minute flight handflying a GA aircraft you will spend ten minutes trimming it, back and forth, back and forth. It's really annoying. There used to be a program for FSX called realtrim, and you could set a button that you could set your airspeed with your yoke, press the button, release the yoke pressure and your airspeed would remain where it is. (Or you could say it would hold that pitch attitude, whichever). Is there anything like this in FSUIPC, any way to mirror this behavior? There's an MSFS setting called "Set trim", and it apparently does... nothing. I tried binding it to a key, tried binding it to a button, you press it and absolutely nothing happens. I didn't try using the log to check. Or would setting up my trimming in FSUIPC mitigate or eliminate this sloppy trimming in MSFS 2024? Thanks!

Gentlemen, I'm wondering if there is a way to create a custom command (key bind) to remove all of the covers in the walkaround nonsense in MSFS2024. I just went into the sim and removed the covers from the 172 and saw these events in the log: 401187 InputEvent received: UNKNOWN_COVER_PITOT=0.000000 (param=';FLOAT64') 401296 InputEvent received: UNKNOWN_COVER_PITOT=0.000000 (param=';FLOAT64') 403093 InputEvent received: UNKNOWN_COVER_STATIC_PORT=0.000000 (param=';FLOAT64') 403265 InputEvent received: UNKNOWN_COVER_STATIC_PORT=0.000000 (param=';FLOAT64') 411593 InputEvent received: UNKNOWN_COVER_ENGINE=0.000000 (param=';FLOAT64') 411687 InputEvent received: UNKNOWN_COVER_ENGINE=0.000000 (param=';FLOAT64') Not sure why there are two events for each cover, but how would I go about binding all of these to one key? I tried Key Assignments - custom Control and entered the number preceding the event, but that doesn't work. Any help would be considered divine intervention at this point. Thanks, Mike

I just created a super-quick log so you could see the log itself. This is like 2 seconds' worth of data.

FSUIPC7.log

Okay this is kind of odd. I created an Event log, which is too big to upload, and I think the reason is because it is just a constant stream of the following. If I open the console you see this, moving so fast you can't even really read it. So something odd is going on. So far as I know I don't have any of these events set up with FSUIPC. The "ELECT_FUEL_PUMP2_SET" event is me pressing the button on my Bravo (to no avail), the rest of it is just this endless stream of events. 3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789500 *** EVENT: Cntrl= 67053 (0x000105ed), Param= 0 (0x00000000) ELECT_FUEL_PUMP2_SET 3789531 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789531 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789594 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789594 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789656 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789656 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789719 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789719 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789797 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789797 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE 3789859 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF 3789859 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF 3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE 3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE 3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE 3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE

Thanks John, I appreciate your thoughtful responses and your time, as always. I will try a few things and see if I can figure it out.

And FYI, I tried it in the Baron, and the fuel pumps work fine. Still no go in the Islander. I cleaned up the .ini file per your comments above, got back in the Islander, and tried to set up the fuel pumps. Nada. So then I got in the Baron to test it, and with the settings that had not worked in the Islander, the fuel pumps in the Baron worked just fine. So I'm guessing it is specific to the Islander. FSUIPC7.log FSUIPC7.ini

Hi John, Thanks for your time here. Just to confirm, should I delete any button command that has "P65" in it? Those are virtual buttons? I removed the ones you noted above, but I have more of them in my ini file, and I want to be sure I'm cleaning it up fully: So essentially I should delete all of the ones with P65 and recreate the actions with the actual button? I will wait on your answer before doing that, and then I will test in the G58.

FSUIPC7.logThis is the log of me trying to set the buttons, along with my updated .ini file. I deleted the lua scripts, then deleted the virtual button presses, and tried to create new button presses. They seem to register in the .ini file, but nothing happens in the sim when I press them. I've tried toggles, I've tried the on/off's. I can't get the Avionics masters 1 and 2 to work, either, for that matter, but I'm guessing the same thing is wrong in both cases. FSUIPC7.ini

Thanks for the response, John, I have made the updates re: the lua files and will make the changes with the buttons and see how we do. Will report back. Thank you!

Sure John, thank you!FSUIPC7.logFSUIPC7.ini

Hi all, I've just gotten an updated piston twin airplane, and most of the buttons on my Honeycomb Bravo did not need updating. But the fuel pumps don't work (they did with the previous version of the plane). What's odd is that when I'm in FSUIPC7 and flip the fuel pump switch up and down, there is a phantom button activation exactly at the midpoint. They button I am moving is button 65 1 & 2 (1 is up, 2 is down). As I flip the switch up and down, in the middle, two buttons are activated: D133 and D134. I have nothing else bound, nothing else assigned to this button in MSFS itself. What gives? Also, the button that I'm trying to use (65 1 & 2 for the fuel pump) does not work. Thanks!

Many thanks, John!

Sorry for the confusion, now I get it. I was looking for the axis under Send direct to FSUIPC Calibration, rather than Send to FS as Normal Axis. Now I see Anti Ice Gradual Set Eng1, and I can assign it and it works! One little issue is that it only uses the bottom half of the range of the Bravo axis. In other words, the lever all the way down is correctly carb heat on, but as I push the lever up, it goes to full in (ie carb heat off) only halfway up the axis. Not really that big a deal, but it would be great if it used the full range of the axis.

Hi John, I genuinely tried doing this, following your instruction above and using the manual, to no avail. I activated the logging for Axis Controls, opened the logging console and moved the lever. It registered. I then went into the axis assignments and moved the axis I want to use, that seemed to have registered. I used Send to FS as Normal Axis. Then on the right side of the Axis Assignments panel I selected Anti Ice Gradual Set Eng1. I tried different ranges, from -16384 to 16384, and also using smaller ones, but I get no movement visually of the carb heat lever, and I turned on the engine and tried to use it in case maybe it just doesn't show an animation, but the action itself works, and I get nothing. The lever doesn't move, and the carb heat doesn't open and close. Here is the relevant part from the ini file, and the file itself is attached. I would greatly appreciate any help you could give me. [Axes.GA Single] RangeRepeatRate=10 0=BX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=BY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=AX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 3=AY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 4=AR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 5=DX,256,D,4,0,0,0 -{ DIRECT: Throttle }- 7=DZ,B,-16384,16383,67012,0 -{ Entering=ANTI_ICE_GRADUAL_SET_ENG1 }- 8=DR,256,D,6,0,0,0 -{ DIRECT: Mixture }- FSUIPC7.ini

Many thanks, John! I figured out a workaround the other day, but this sounds much better. Will report back.

Hi all, I know I have an account here, but I can't get the password reset email. Anyway, has anyone figured this out? To clear a few things up: you can get carb ice from around 20 degrees C down to -5 degrees C. Flying around at -20 degrees C will not produce carb ice. In real aircraft it is an axis. If you have a carb temperature gauge you would use it to bring the carb temp above freezing. If you don't have a carb ice gauge (and most small piston singles don't), you would put it full on if you suspect carb ice. Either way, I'd like to map the carb ice setting to an unused axis on my HC Bravo just because it's more realistic to have it as an axis, even if I only really get full on or full off. That's fine, I just do want an axis. Though maybe one has come to being for carb ice in MSFS since this thread was last active. I don't see any way to set carb ice at all in FSUIPC7. Any help would be appreciated.