Andre92

Hello John, Thank you, once again, for your help. Copying the supplied code into myevents.txt didn't work initially, but i played around with it and came up with a working solution. The lines in myevents.txt now look like this: DuckWorks-DC3_Throttle1#$Param 32768.0 / 0.5 + (>L:DUCKWORKS_THROTTLE1_SET) DuckWorks_DC3_Throttle2#$Param 32768.0 / 0.5 + (>L:DUCKWORKS_THROTTLE2_SET) DuckWorks_DC3_Throttle#$Param 32768.0 / 0.5 + s0 (>L:DUCKWORKS_THROTTLE1_SET) l0 (>L:DUCKWORKS_THROTTLE2_SET) DuckWorks-DC3_Mixture1#$Param 32768.0 / 0.5 + (>L:DUCKWORKS_Mixture1_SET) DuckWorks_DC3_Mixture2#$Param 32768.0 / 0.5 + (>L:DUCKWORKS_Mixture2_SET) DuckWorks_DC3_Mixture#$Param 32768.0 / 0.5 + s0 (>L:DUCKWORKS_Mixture1_SET) l0 (>L:DUCKWORKS_Mixture2_SET) I use a Honeycomb throttle and it generates values from -16384 to +16384. So by dividing with 32768, it outputs values -0.5 to +0.5. The +0.5 converts to range 0-1. This works for me. Thank you very much for your help. Kind Regards, Andre

Hello, The Duckworks DC-3 Mod uses custom LVARs to control Throttle and Mixture. i'm trying to control the LVAR L:DUCKWORKS_THROTTLE1_SET, with a hardware Axis. I've tried using a LVAROffset to write to Offset 0XA000 [LvarOffsets] 0=L:DUCKWORKS_THROTTLE1_SET=UB0xA000. And then assigned an axis to the Offset. Problem is that that Axis generates values from 0 to 100. The LVAR used by Duckworks needs values from 0.00 to 1.00. I've tried making a LUA script to convert the value send by /100, but had no success. Edit: I've tried assigning the LVAR directly to the Axis and then convert the output from the Axis. This works when converting to 0-100 3=LV,256,F,M25:2,0,0,0,*-0.0030518, +50 -{ TO SIM: Macro DC3: L:DUCKWORKS_THROTTLE2_SET set }- but not when multiplying with 0.000030518. 3=LV,256,F,M25:2,0,0,0,*-3.0518e-05 -{ TO SIM: Macro DC3: L:DUCKWORKS_THROTTLE2_SET set }- And the same when assigning an Offset. Could anyone help me getting this to work? Kind Regards, Andre

Disregard.... Reinstalled FSUIPC and somehow it is working again... Hello John, For some reason the auto lua loading [auto] on fsuipc startup stopped working. Looking at older backups it all worked fine and the lua's were started after the wasm load. I can't remember changing anything that could mess this up. Could you pls take a look at my ini and log files to see if something is wrong? Kind Regards, Andre FSUIPC7.logFSUIPC7.ini

Sorry and thanks for your help. Have a nice weekend, André

Hello, For the Flyingiron Spitfire, i've made the Authentikit Replica Spitfire Grip with a Brake lever (working as an Axis). On the Spit, if you use Rudder and pull the brakehandle, only the side where the Rudder is pushed, gets brakepressure. This doesn't work in MSFS currently. When i have the Brakelever programmed to the Brake axis. brakes are always applied evenly to both sides (as expected), so i would like to program a conditional state, where the Left brake axis is used when Left Rudder input is given, and vice versa. What would be the best way to program this? Kind Regards, Andre

No solution, but just would like to add that i have the same problem with the Winwing Airbus stick. Regards, André

Thanks John, I played around with the scaling function and did get the axis to work only on the lower part of the throttle. Still need to experiment a bit more with this. I think i prefer the steering tiller function of fsuipc. This way i can set up a fairly large deadzone in the middle, which i prefer. Have a nice weekend! Andre

I use the a button for the fuel levers. The honeycomb throttle has a detent at the bottom part of all throttles/axis which triggers a button. 125=PL,24,C66587,68801 -{ROTOR_BRAKE}- 126=UL,24,C66587,68801 -{ROTOR_BRAKE}- 127=PL,27,C66587,68901 -{ROTOR_BRAKE}- 128=UL,27,C66587,68901 -{ROTOR_BRAKE}- It looks like this in my ini file (Buttons section), where L is the letter assigned to my Honeycomb throttle on my setup. Andre

Don't know if this helps you but here is my experience so far: With the PMDG 737, in the FMS>PMDG>Simulation you can select the Nosewheel steering to be controlled by Rudder only OR Prop1 axis and Rudder. With this 2nd option, you assign your tiller axis to the prop1 axis and this only controls the tiller (as in the RL aircraft). Unfortunately when you assign this through FSUIPC, you will have to use PROP_PITCH1_AXIS_SET_EX1 and not the Direct FSUIPC calibration. Which means (to my knowledge), that you can't calibrate the Axis, only reverse it. Another way to use your Tiller is to use the 1st option in the PMDG Menu (Rudder only) and then assign your Tiller through FSUIPC with DIRECT FSUIPC Calibration. This way you can calibrate your Tiller axis. The downside is that it does not correctly simulate moving the PMDG 737 Tiller, but basically controls the Rudder. I use my Warthog Throttle for the tiller with Airliners, and use the Direct FSUIPC calibration. This way i can only use the part of the axis up till the Afterburner detent, calibrate it with a fairly large deadzone in the middle and use slope to smoothly transition the steering. This works quite nice with the DC-6 and the CRJ, but very abrupt in the 737. Kind Regards, Andre

So had some spare 30 minutes to try again. The Throttle 1 Dec (and #2) does work. I believe you have to add a parameter (not 0), for it to work. I've now set it up on my Honeycomb Throttles to have a single Throttle 1 dec when the reverse levers are pulled, this gives you idle reverse. When pulling the throttles through the detent, Throttle 1 dec is pressed repeatedly, so you get full reverse. This allows you to choose between idle and full reverse. When the reverse lever is released Throttle 1 cut stows the reverser. I programmed the fuel lever (idle cutoff) on the detent of axis 2 and 5. On press and release of the detent button they are toggled. André

Hello, Struggling with the 737 as well..:-) The reverser works for me when i assign it on an Axis as described above (direct to FSUIP Calibration). Setting a button to Engine 1 dec does not work for me (which normally works on other planes). I will experiment some more when i have the time. The fuel lever / idle cutoff can be toggled through the Rotor brake function. Fuel lever 1 is 688 Fuel lever 2 is 689. To assign a toggle function for this, assign the Rotor Brake to a button with the parameter 68801 or 68901. The 01 means left mouse click. You can download an Excel file with all the event numbers here: https://forum.pmdg.com/forum/main-forum/pmdg-737-for-msfs/182499-737-lvars-simevents-etc-list Kind Regards, Andre

Hi John, I've corrected the lua files and will take a look at setting an offset condition directly to the assignment when i have more time, this evening. Thanks for your help! Andre

That worked great! Thank you John, also for taking the time to write such a detailed answer. I've made two small lua files to read the offset and turn the tailwheel on/off depending on the state. Works like a charm. They are attached here, in case someone else wants to use them. (Place them in the fsuipc directory and assign them through the FSUIPC Interface) Andre MilvizPC6_Tailwheel.zip

Hello, I am trying to assign a button to the Tailwheel lock for the Milviz PC-6. On the Hubhop site of Mobiflight i found the following code: (A:TAILWHEEL LOCK ON, Bool) 0 == if{(>K:TOGGLE_TAILWHEEL_LOCK)} Can i use this for FSUIPC as well? If so, how? Sorry for the noob question, but i'm more and more confused with MSFS way of implementing events A: K: L: H:....? 🙃 Regards, André

It’s simply a quick way to align the Heading bug and only has effect on AP / FD guidance if the hdg roll mode is active. This could be used when flying in nav mode and ATC instructs to maintain hdg. You press the hdg sync and then activate the hdg roll mode. Or when handflying rawdata, you can use it to quickly align the hdg bug with a simple press (f.e. after localizer intercept). Kind Regards, Andre

Yes, but it also activates the heading (hold) function of the AP/FD system. Some Aircraft have a Heading Sync function where only the Heading bug is aligned, but no Hdg mode is activated. (F.e. the TBM 930 or CRJ).

Hello, I couldn't find a standard function in Fsuipc to sync the Autopilot heading to the actual heading (Heading Sync). So i made this little lua script. I took the conversion from true to magnetic from the provided sample plugin display vals.lua. Place this lua in your Fsuipc folder and assign it to a button. You will find it under lua Hdg_Sync in the assignments list. If there is a simpler or more elegant way to get this function working, please let me know. Kind regards, Andre HDG_Sync.lua

Hi John, That works! Thank you for help! Cheers, Andre

Hello, Noob question: I want to control the Left, Nose and Right Landing lights of the Aerosoft CRJ, with a single switch. Their respective LVARs are: 1=L:ASCRJ_OVHD_LDG_LEFT=Set 2=L:ASCRJ_OVHD_LDG_RIGHT=Set 3=L:ASCRJ_OVHD_LDG_NOSE=Set And i can control them seperately, but how can i set them with one switch? I tried the multi-line macro from the advanced users manual, but then also saw that this doesn't work wit Lvars. Kind Regards, Andre

Hi John, With the updated Exe it works. I used the compound button programming to condition the opening of Canopy and Frame door. Thank you! I hope you have a lot of fun flying the Spitfire. Cheers, Andre

Oh wow, very nice! If you have a VR set. Try it with that, it really comes to life in VR. And be careful with the Boost on Take-off. I usually start with only 0 Boost till the tail comes up and then slowly increase to 6-8. I'm fiddling around and building simulators as a hobby and have now started to build a Spitfire Pit with the Authentikits DIY controls https://authentikit.org/ Andre

Thanks John, I did try the Offset Float 64 Set/1000 just now, but except for the Offset values changing, no change in behaviour. The Set function normally behaves fine. I use it f.e. to change the Radiator function between Open/Auto with Parameter 0 and 1. But no rush on this. It's really not that important to get this working. I can toggle the door and the unlock is just an extra. I will try to write a LUA file, just for the learning experience. 🙂 Thanks for your help and Kind Regards, Andre

Just tried the L:AIRFRAME_DOOR=Set function again. It does work, but partial. No matter what parameter is set, the AIRFRAME_DOOR value is always set to 0 when i assign this function to a button.

Ok, had some time to play around: I added [LvarOffsets.Spit] 1=L:AIRFRAME_DOOR=F0x66FC to the fsuipc.ini and assigned the Offset Float32 Set/1000 to a button with Offset x66FC and Parameter 100. - The Offset is changed to 0.1 when i press the button but the door is not unlocked. - Also tried Parameter 1000, so the Offset is changed to 1, but also no response. Than i had the Offset value displayed (in the FS Window) to see if it's working at all. - When i unlock the door by clicking on the mousespot for it, the Offset value is also changed to 0.1 (so it seems to be correctly connected to the AIRFRAME_DOOR LVAR) - When i assign a button directly to the LVAR L:AIRFRAME_DOOR=Set, with Parameter 0 or 1, the Offset is changed accordingly, but the door is also not responding. - When i assign L:AIRFRAME_DOOR=Toggle, the door is opened and closed (and the Offset changed to 0 and 1) when i press the button. - When i set the LVAR AIRFRAME_DOOR through the FSUIPC UI /addons/WASM/Set Lvar, it works (also with 0.1) and the Offset is also responding accordingly. -Changing the AIRFRAME_DOOR LVAR by Mouse click, Set LVAR (FSUIPC UI) or the L:AIRFRAME_DOOR=Toggle function, works. -Changing it through the Offset or the AIRFRAME_DOOR=Set (neither 0, 1 or 0.1) function does not work. -Changing the Offset, does not change the AIRFRAME_DOOR value, changing the AIRFRAME_DOOR does change the Offset. Am i doing something wrong here? Otherwise i'll try the 2. Option you suggested. (Will have to dig into the LUA Programming a bit 🙂 ). Thank you for your assistance. Kind Regards, Andre

OK thanks, I'll download the latest FSUIPC version and try this with Offset 66FC tonight. Andre