kaha

Is there a possibility to bind a hardware axis to throttle, prop and mixture of engine numbers greater than 4? I only succeeded to bind the throttle axis using Avars (A:GENERAL ENG THROTTLE LEVER POSITION:nr) Maybe this is a sim restriction? Karl

Thank you John. Karl

How can I get a notification that an aircraft is unloaded in an automatically loaded lua script [AUTO]? I use a bidirectional com communication between the Arduinos and my lua scripts. My Arduinos know which aircraft is currently loaded and can react accordingly. I do that using the offset event at 0x3D00. Now, as an example, if I go back to main menu in the sim no aircraft is loaded anymore but the Arduino doesn't know. At the moment the Arduino has to poll the lua script to check if it is still running. It would be nice to have sort of a callback in the lua script that tells me the script is about to end because the aircraft is unloaded. Any chance to get that?

Ok. As you explain it it might as well disappear in the future, maybe it will get substituted by something else. But for now it's my only possibility to store and recall my own camera views. Thank you, Karl

Thank you! Actually I use offsets 0x86A0 to 0x86B4 to set (and store) my own camera views and to restore them at the press of a button. Please don't make them inactive. Karl

Is there a possibility to read the 6DOF values of the current camera? Offsets 0x86A0 to 0x86B4 are write only. By the way: Offset 0x8320 is readable (still red in "FSUIPC Offsets Status.pdf". Karl

John, this works. For the WBsim 172 I had all 4 lights working already. It was the Asobo classic 172 I was struggeling with. I use a switch to switch the light on (to 75%) and off: local light = math.floor(ipcPARAM / 1000) local percent = ipcPARAM - light * 1000 local n if light < 1 or light > 30 then return end local function rtrim(s) n = #s while n > 0 and string.byte(s:sub(n, n)) < 32 or string.byte(s:sub(n, n)) > 127 do n = n - 1 end return s:sub(1, n) end local aircraft_name = ipc.readSTR(0x3D00, 256) aircraft_name = rtrim(aircraft_name) --ipc.log("Aircraft = " .. aircraft_name) if aircraft_name:find("Cessna Skyhawk Asobo", 1, true) and not aircraft_name:find("WB", 1, true) then if light == 5 then -- pedestral lights calc_code = percent .. " s0 (>L:LIGHTING_PEDESTRAL_1) l0 1 (>K:2:PEDESTRAL_LIGHTS_POWER_SETTING_SET) l2 ! 1 l0 (>K:2:PEDESTRAL_LIGHTS_SET)" ipc.execCalcCode(calc_code) end end

Great! Thank you, Karl

Can't get it to work. I'll do it using the other software, but I would prefer to be able to do it with FSUIPC as I love the possibilities lua scripting gives me. Maybe you consider to implement this in the future, that would be great. Karl

Thank you John, I will give this a try. Karl

I want to set the pedestral lights for the Asobo classic C172. I got word from someone (not using FSUIPC but something else) that the event PEDESTRAL_LIGHTS_POWER_SETTING_SET works, but needs two parameters. One parameter is the number 1 and the other is the percentage of the light intensity. Now, with FSUIPC I can only give one parameter: ipc.control(67211, x) where x is the percentage. Regardless what value I use for x, the pedestral lights get always switched off. Same goes for GLARESHIELD_LIGHTS_POWER_SETTING_SET (67212). Is there something I miss? Karl

I also had the stuttering with SU12, but 7.3.19 cured it. Karl

Ok, understood. Thank you, John! Karl

Yes, the script is running. I just extracted the relevant lines to a .txt file. Karl ini_log.zip

John, I now removed the profile specific axis assignments and made none profile specific ones, see attached screenshot. But now the offset event does not fire anymore. There must be something I still don't get. Karl

Thank you! Karl

Of course you are right, John, it's the axis assignment window. Here is my use case: I connected hardware potis to change the cockpit light in the Cessna 310. For this I made some profile specific axis assignments (see attached screenshot) and then set the appropriate cockpit lighting in a lua script. This works. Now I want to utilize those potis for other aircraft as well. Therefor I need to get rid of the profile specific nature of the axis assignment. The corresponding lua code is in the attached file lua.txt. Karl lua.txt

Thank you. Karl

Is it not possible yet? Karl

With an aircraft loaded that has profile specific controls defined I want to define an additional control that is not profile specific, in contrary it should be available for all aircraft. Now, bringing up the Button Assignment window the checkbox "Profile specific?" is checked and greyed out. How can I uncheck? Karl

Thank you. I use the store version. I found two FlightSimulator.exe files on my ssd. I changed both to be started as admin, and now it works! I searched for FlightSimulator*.exe on my C drive and then changed to "Start as Administrator" in settings->compatibility. I use the software "Agent Ransack" for searching my drives. Karl

Since some time (already happened with v7.3.8) FSUIPC does not start when I use the desktop shortcut. The sim starts, but not FSUIPC. The shortcut and FSUIPC.exe are set to "Start as Administrator". There is not even a .log file, so FSUIPC does not start at all. Once the sim runs and I start FSUIPC.exe it runs. What can I do, what additional info do you need? Thanks, Karl

Thank you John. I got it to work. Not sure what caused the irregularity, I guess it was my frequent switching between different aircraft for testing and not restarting the sim. Everything is perfect now. Thank you, Karl

Sorry, if FSUIPC is not the reason for my problem, but I don't know where to look for a solution. I try to assign this event "Starter 1 Held" to a switch, but nothing happens. The event "Set Starter 1 (Hold)" in plain MSFS works. "Starter 1 Held" works with other aircraft, though. Where is the issue? MSFS, FSUIPC, that specific aircraft? I'm at a loss. Best, Karl

Thank you!