xkoote

Yes, i noticed. You will actually have to start her up and depart. It is the only way to actually test the LVAR's. Thanks John.

Hey John, seeing that you now have the 727. Did you maybe map the autopilot controls already? If so, can you share the presets? e.g. Autopilot On/Off, turn knob inc/dec, VS inc/dec etc etc.. If not no big whoop, I'll get around to it.

Noted John. Thanks!

John, I followed your instructions to a tee. I searched the Lvar, and found it using the Developer Mode. I noted its name and also its value (0-100). With that I had the 3 requirements to build the preset. Now to be honest, I have a difficult time remembering all the help I get from this forum as I only need to apply the recommendation once, and it will work forever ;-). So, some parts of the description went over my head. 🫳😮‍💨 But I did notice that the example had the same values I had. And so, I copied the ...$Param... part and created the following in the MyEvents.txt B727 Spoiler Axis#$Param 16384 + 327.68 / 0 max 100 min (>L:FSS_B727_SPOILER_LEVER_STATE, Number) I then reloaded the presets and assigned it to the axis I wanted. WORKS LIKE A CHARM !!! Cheers and thank you!

Hello John, I have had a few tough days at work. I have just opened this post again to see if I can map the spoiler. With regards to the fuel levers, I have edited my "MyEvents.txt" with the following; B727 Fuel Control 1 Run#1 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_1,number) B727 Fuel Control 1 Cutoff#0 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_1,number) B727 Fuel Control 2 Run#1 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_2,number) B727 Fuel Control 2 Cutoff#0 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_2,number) B727 Fuel Control 3 Run#1 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_3,number) B727 Fuel Control 3 Cutoff#0 (>L:FSS_B727_PDSTL_FUEL_CUT_OFF_3,number) I then mapped these to the appropriate buttons using the Preset function.

Hey John, it seems that he simply did it in axis and oh's where he could simply map this to an axis. But I will first read up on how to do it here, get it done, then find out again how he did it. Thanks.

Thanks John. I will read up

So a good mate sent me a message saying that he got it to work by assigning the axis to "EVT_LEVER_SPOILER_1" which seems to be an event ID. I can't see a way to do this in FSUIPC.

Hello, for some reason, even though I can map ALL the airplane's axes, it will not accept the spoiler axis. I have tried the FSUIPC axis and the 2 possible "Direct to Sim" axes. The spoiler handle does not move. I know it is probably an FSS coding problem and not an FSUIPC problem. But I thought I would ask anyway to see if you might have a workaround to try or test. A fellow user mentioned that he used SPAD to "make a custom axis pointed at the 727 spoiler handle position LVAR". Assuming I can find that LVAR name, can I do that in FSUIPC too. Can you maybe tell me how that is done or point me to the correct portion in the manuals? Thanks, Xander

Well, I tried a flight today. But the MD-11 has its own WASM crash issues. Anyways, in the 3 hours a had it in SIM I had 0 issues. Including the presets I made. They all worked. Subsequent sim session with circuits flown all as well was good. Hopefully this one can be marked fixed 😉

Understood. I'm doing a flight today with all my presets reactivated. Hopefully it will last throughout.

Thanks John. Downloading now. To be fair. I did one flight in the Dc-6 and one in the MD-11 (Yes, I'm Douglas at heart 😉 ) and I got no crashes. Will test this out tomorrow on my next bout. Xander

John, thanks as always for your support. I have been flying the MD-11 on and off and first noticed this behaviour when switching from the .12b you gave me which introduced extended ControlNumbers prior to the official SU15 release. I thought it was due to the MD-11 being in beta and having some issues. Today after a long time, I needed to edit my PMDG DC-6 due to a new joystick and associated Windows joystick ID's. In the process of doing this I noticed that the preset button assignments that worked just before, stopped working. Must have been around 30 minutes in. All the events of course were still present in the updated events text file. e.g. PMDG DC6 cowl flap operation. After I changed these binds from presets to straight out Rotor Brake codes, they worked fine. Testing my other preset based buttons however stayed inoperative. I will post in due time if you don't mind as I always want to make sure I am not jumping to conclusions. I will then send my ini files for the program and the DC-6, the WASM log as describes above and WASM ini and lastly the FSUIPC7.log. Thanks as always, Xander

Unfortunately, after glancing through this exhaustive post (and with build 13 of FSUIPC and SimFX installed) I have the same issue of Preset assignments dropping out mid-session. Native commands keep working, rotor brakes as well. I will have to read up on this post and see if I can get it sorted. Will post back if nothing changes after some additional flights with the appropriate logs. Xander

John, was too excited so I tested it, and it works like a charm!! Thank you so much 😉