Andre92

Thank you for your support! Kind Regards, André

Hi John, sorry for the late reply. I think i found the issue: I've had buttons assigned for time acceleration. 301=PG,13,Cx02000C1A,x0100 -{offset word set, offset 0C1A}- 302=UG,13,Cx02000C1A,x0400 -{offset word set, offset 0C1A}- 303=PG,12,Cx02000C1A,x9600 -{offset word set, offset 0C1A}- 304=UG,12,Cx02000C1A,x0400 -{offset word set, offset 0C1A}- When starting up FSUIPC, this would (sometimes) trigger fsuipc to continuously trigger the event: SIM_RATE_INCR continuously. Since i assigned a press and not repeat function, i don't quite understand what i did wrong here? You can see the event happening in the attached log file. After removing the above entries, the problem stopped. Kind Regards, Andre fsuipc.zip

Sorry for the late reply, i'm away from home flying. I'll be back home on Thursday and will add the requested lines to the ini file. The first supplied ini was from a session where fsuipc worked fine. Sorry, i had the memory leak initially, restarted without problems and then saved the ini. I increased "maxnumberofcustomevents" because inibuilds used to create an enormous amount of events when they initially released their A310 and later A300. I'll set it back to default. Kind Regards, André

The fsuipc.ini is in the first zip file. With 3D i mean when you've loaded into your flight. Sorry, that's an old habit from Falcon BMS days. We used 2D for when in UI and 3D when in game. Have a nice weekend! André

I can't exit fsuipc because it becomes unresponsive and i have to use the Taskmanager (see screenshots). I've attached another zip with a log of this happening with 7.53b. It would startup normal when in 3d, but had the memory issue in the main screen. Also attached are two screenshots with the console showing. One with 7.52 running in the 3d and the other with 7.53b in the Main screen. Btw, either fsuip starts normal, or the memory issue starts, right from the beginning. fsuipc.zip

Good morning, Here is a new log file with the extra options enabled, when a memory leak occured. This is now with SU1 installed and i had to restart fsuipc several times for it to happen again. The memory leak does not occur every time i start fsuipc. I first noticed it when i started up fsuipc during the walk around (when you start in 3d, outside of the plane). So i now always enter the cockpit first and then start fsuipc, but it still happens. Edit: Just tried starting fsuipc when on the main screen in msfs and also got a memory leak after starting several times. I've attached the log file. Cheers, Andre fsuipc.zip FSUIPC7_mainscreen_log.zip

Sorry, Family life caught up. I will test some more tomorrow morning, with the offsets you mentioned and will also disable the two lua files you mentioned. And then report here.

Hello John, I'm suddenly having issues with FSUIPC with started on version 7.5.1 and continued on 7.5.2. When starting FSUIPC after the MSFS2024 has loaded into the 3d world (and entered the cockpit), the sim freezes and looking at Task manager FSuipc is increasing its memory usage continuously. This does not happen every time i start fsuipc and it also does not happen when i load fsuipc before starting the sim. Attached are my ini and log file and a picture of the task manager showing the abnormal memory usage of fsuipc. Kind Regards, Andre fsuipc.zip

Hello Aurel42, You can add the Lvars to myevents.txt and set a Parameter to convert them: If you don't have a myevents.txt in your fsuipc folder, simply create one, then paste in: // Blacksquare Duke Mixture BS_Mixture_1#$Param 327.680 / 50 + (>L:BKSQ_MixtureLeverPosition_1) BS_Mixture_2#$Param 327.680 / 50 + (>L:BKSQ_MixtureLeverPosition_2) This will work for an Axis like the Honeycomb brave which has a range of -16384 to +16384. Then assign your Axis by selecting Send Preset to FS and select the Mixture. If your Axis is inverted, you can inverse them by adding ,*-1 to the Axis in your Duke Profile f.e. 3=LU,256,F,PBS_Mixture_1,0,0,0,*-1 -{ TO SIM: Preset Control }- Btw, the Lvar range is 0-100 for the Mixture. Hope this helps and have fun with the Duke. Andre

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).