Luis Hernández

Thanks, John. Inverting priorities (as you said) did the trick. Since I had to add the behavior for switching from half to full brake and back, this is what I got now: 32=CP(-0,1)0,0,CL5:S,1 -{LuaSet FS_ABS (Flag 1)}- 33=CU(-0,1)0,0,CL5:S,2 -{LuaSet FS_ABS (Flag 2)}- 34=CP(+0,0)0,1,CL5:S,2 -{LuaSet FS_ABS (Flag 2)}- 35=CR(+0,0)0,1,K190,8 -{Key press: .>key}- 36=CU(+0,0)0,1,CL5:S,1 -{LuaSet FS_ABS (Flag 1)}- This works beautifully for anything between FS9 and P3Dv5. For MSFS2020, the period key works a bit different, so I decided to use a different LUA. But regarding this thread, the same principles apply. So I say again: thank you very much!

Hello everyone. I'm trying to configure my dual-action trigger in my Gladiator NXT for two steps of braking: the first step would be half braking (done by a LUA I wrote) and the last step would be done by simply mapping the button to the period key (the key used in FS9-P3D for brakes). In my VKB (joystick 0), the first trigger step is Button 0, and the second step is Button 1. However, there's no way to press Button 1 without pressing Button 0. I'd only have three states: No button pressed, Button 0 pressed, and Button 0+Button 1 pressed. Trying each control separately, this is what I do: 32=P0,0,CL5:S,1 -{LuaSet FS_ABS (Flag 1)}- 33=U0,0,CL5:S,2 -{LuaSet FS_ABS (Flag 2)}- And as expected, it works with Button 0. Setting nothing to Button 0 and setting these two mappings to Button 1 also work as intended. If I try the full brake, this is what I need to do. 32=R0,0,K190,8 -{Key press: .>key}- And it works correctly. If I want to compound both buttons, this is what I enter into the ini file: 32=CP(-0,1)0,0,CL5:S,1 -{LuaSet FS_ABS (Flag 1)}- 33=CU(-0,1)0,0,CL5:S,2 -{LuaSet FS_ABS (Flag 2)}- 34=CR(+0,1)0,0,K190,8 -{Key press: .>key}- Button 0 works correctly (brakes are half applied, as intended). However, if I press the trigger fully (i.e., while Button 0 is pressed, I press Button 1), nothing happens, as if I never pressed Button 1. I mean, the condition set in assignment #32 is still applying (until I release Button 0). I'd have expected that the last line (assignment #34) would have applied, and I'd have full brakes. Is it there something I forgot to do?

After seeing some suggestions with Spad.next (setting trim rate in radians per click), I found FSUIPC7 (and previous versions too) has the same capability. After reading a bit about this, I find it's easier for me setting up the trim buttons using offset 0x2EA0, and setting the rate in miliradians, than using 0x0BC0 with their corresponding units (as suggested since FS9 times, at least), since I always want to use the full trim range. Is it there any difference by using 0x2EA0 instead of 0x0BC0? Or is just another way to skin a cat?

John, this post from the FSL forums may explain my issue better: https://forums.flightsimlabs.com/index.php?/topic/30340-did-fslabs-miss-the-msfs-train-with-the-upcoming-fenix-a320/&do=findComment&comment=243570 As I said before, it's not an FSUIPC7 issue but a MSFS one.

When setting the views, I need to pan and move my eyepoint at the default VC view. After this, if I switch to another view, all is OK. But I switch again, it will move me first to wherever I was looking in the default VC view. It's hard to explain. Anyway, I'm sure FSUIPC has nothing to do there: this also happened when using directly the key assignments, back when I didn't have FSUIPC7.

Thanks, John. I've been applying your workaround already. I don't know if there's something wrong with MSFS or it's just me, but sometimes I need to double press the button I set: first press takes me to wherever I was looking at, and the second one takes me to where I want. I'll take a look to the thread you mentioned.

I've never seen that option in the menus, at least not since FS9. I checked again in P3D v4.5, and effectively, there's no such control in the list of assignments. Neither in MSFS. However, in P3D works but not MSFS. Thanks, please let us know.

Good morning everyone. I've just purchased FSUIPC7 a week ago. I set up my controls, trying to keep the same settings I'm familar with in FS9, FSX and P3D4. However, I find that Pan_reset is not working in MSFS. This command is so useful, because it only resets sight direction but not position. This is how the assignment appears in FSUIPC7.ini: [JoyNames] 0= VKBSim NXT THQ 0.GUID={0D5BE840-496E-11EC-8001-444553540000} 1= VKB-Sim Gladiator NXT L 1.GUID={14F9D130-FAD0-11EB-8001-444553540000} A= VKBSim NXT THQ A.GUID={0D5BE840-496E-11EC-8001-444553540000} B= VKB-Sim Gladiator NXT L B.GUID={14F9D130-FAD0-11EB-8001-444553540000} [Buttons] PollInterval=25 ButtonRepeat=20,10 1=PB,3,C65875,0 -{PAN_RESET}- For reference, this is what I got in FSUIPC6.ini: [JoyNames] AutoAssignLetters=No 1= VKB-Sim Gladiator NXT L 1.GUID={14F9D130-FAD0-11EB-8001-444553540000} 0= VKBSim NXT THQ 0.GUID={0D5BE840-496E-11EC-8001-444553540000} [Buttons] PollInterval=25 ButtonRepeat=20,10 0=P1,3,C65875,0 -{PAN_RESET}- It should yield the same result. Am I doing something wrong?

That did the trick. I was using the old method (Key Presses). Now it works as in FS9 and FSX. Thanks a lot!

Hello everyone. I've started using P3D4.5, and immediately purchased FSUIPC6 and set it up as close as I had it for FSX-SE. In FSX-SE (and FS9 too) I use Advdisplay Toggle for seeing the messages issued by PF3. I assigned the same key to the same control in P3D4.5, but it does not react at all. However, all messages from PF3 ended up in Simconnect Window. I asked first in the PF3 forums, but they sent me here. From what I've read, there is no longer an Advdisplay in P3D4.5. So, what control should I use for toggling on/off the Simconnect window? I can't find anything either here, the PF3 forums or even the Radar Contact ones (that also use Advdisplay).

That was the issue!!! I corrected this line in the INI file, and now my latest code works as intended. I would have never seen this error. Thank you very much, Pete!

I've generated some logs. However, I can't see if the LUA was ever loaded, but I think it never did, actually. I tried logging with my current, non-working code version (see below) and the original one, as the one I described first in my first post. I'm attaching the 2 latest logs and my INI file. I can't see anything special, apart from the fact that somehow does not work. My full, non-working code: function AS_A320_lights(flag) -- Landing lights (retract/ext off/ext on) if ipc.testflag(1) then Landing=ipc.readLvar("L:Landlight_switch") if Landing==nil or Landing==0 then ipc.writeLvar("L:Landlight_switch", 2) else ipc.writeLvar("L:Landlight_switch", 0) end ipc.clearflag(1) end -- Strobe lights (off/auto/on) if ipc.testflag(2) then Strobe=ipc.readLvar("L:Strobe_light") if Strobe==nil or Strobe==0 then ipc.writeLvar("L:Strobe_light", 2) else ipc.writeLvar("L:Strobe_light", 0) end ipc.clearflag(2) end -- Taxi lights (off/taxi/takeoff) if ipc.testflag(3) then Taxi=ipc.readLvar("L:AB_TAXI_LT") if Taxi==nil or Taxi==0 then ipc.writeLvar("L:AB_TAXI_LT", 1) elseif Taxi==1 then ipc.writeLvar("L:AB_TAXI_LT", 2) else ipc.writeLvar("L:AB_TAXI_LT", 0) end ipc.clearflag(3) end -- Beacon lights (on/off) if ipc.testflag(4) then Beacon=ipc.readLvar("L:LIGHT_BEACON") if Beacon==nil or Beacon==0 then ipc.writeLvar("L:LIGHT_BEACON", 1) else ipc.writeLvar("L:LIGHT_BEACON", 0) end ipc.clearflag(4) end end event.flag("AS_A320_lights") FSUIPC4 - INI.txt Log with LUA only.txt Log with LUASet.txt

If you mean this, Adrem [Auto.AS_Airbus] 1=AS_A320 Yes, I had it auto-launched. I tried again with LuaToggle, but it didn't work. Also, using either Donovan and Roman's methods gave me the same result: nothing. There's something I must be doing wrong, but I can't find what may be.

I'm trying to add a way to control the lights in the Aerosoft A320 for FSX-SE. If I do a single LUA control per light, with this code, it works: Taxi=ipc.readLvar("L:AB_TAXI_LT") if Taxi==nil or Taxi==0 then ipc.writeLvar("L:AB_TAXI_LT", 1) elseif Taxi==1 then ipc.writeLvar("L:AB_TAXI_LT", 2) else ipc.writeLvar("L:AB_TAXI_LT", 0) end return This code allows me to cycle the Taxi lights between 3 different conditions. If I assign a button in FSUIPC as LUA AS_A320 (that's the filename I used for it), it works as intended, but it will require a LUA file per each light. However, for simplicity (and a bit of OCD), I'd like to have 4 functions (taxi, landing, strobe and beacon lights) in a single LUA, and call them using functions and flags, the code woild change to this: function Lights_TAXI_toggle() Taxi=ipc.readLvar("L:AB_TAXI_LT") if Taxi==nil or Taxi==0 then ipc.writeLvar("L:AB_TAXI_LT", 1) elseif Taxi==1 then ipc.writeLvar("L:AB_TAXI_LT", 2) else ipc.writeLvar("L:AB_TAXI_LT", 0) end end event.flag(3, "Lights_TAXI_toggle") After this, I assign a button in FSUIPC as Lua Set, and in the parameter box, i enter 3. However, I can't make this switch work. Changing to Lua Toggle or adding a Lua Clear does not change the situation at all. What may I be doing wrong? Best regards, Luis