Luis Hernández

No problem, John, thank you very much! I'd like to know. I don't want to think a lot about it, but whatever corrupted my FSUIPC7.ini also wiped me all my Quick Access shortcuts. I was able to regenerate them all, fortunately.

Ok, I generated a new log. Unfortunately, somehow my ini got wiped last night, and the latest backup I had was from February/2024. I'm recovering from a mix between that backup and last night's post. I'm attaching a new log and the ini file I could recover. Unfortunately, the trim issue still persists. UPDATE: looks like you had already found the culprit: I checked it and there was a calibration set there. I don't remember having done so, and less if the old ini I had was from more than a year ago (and way before v7.5.2). Anyway, I reset this calibration (so that nothing appeared), and looks like it's working. Just in case, I'm attaching a new ini and log, post-calibration reset. FSUIPC7 - log and ini.zip FSUIPC7 - log and ini after reset.zip

Thanks for your reply, John. Let me try this evening, as soon as I get back from work, I'll be generating the new logs. In the meantime: True. I keep 3 different sets of trim controls for my VKB Gladiator NXT: one is a thumb switch (buttons C5 and C7); another one is an encoder wheel at the base (that appears to FSUIPC as buttons C24 and C25, with no repeat set) and the other one is simply the Numpad 1/7 keys assigned directly in MSFS. For some planes (for which I didn't post the profile), I replace these assignments 13=RC,7,Cx32000BC0,x3FFF0040 -{offset sword increment, offset 0BC0 (Incr=64, Limit=16383)}- 16=RC,5,Cx42000BC0,xC0010040 -{offset sword decrement, offset 0BC0 (Decr=64, Limit=-16383)}- in FSUIPC into either Elevator Trim Up/Down controls, or Numpad 1/7 key presses. I remember in FSX days it was a good practice to set the keys in sim and then in FSUIPC assign the buttons to keypresses, but I don't know if that has changed for 2020/2024. As requested, I'll send you the full ini this evening. I saw the changelog, and that's how I found out downgrading to 7.5.1 worked for me, but I never had calibrated any trims. I'll check tonight after generating the logs.

I'm attaching FSUIPC7.log FSUIPC7 log.zip

Hello everyone. Since some weeks ago, I've been seeing this issue with the elevator trim, either using Numpad 1/7 or the buttons I set in MSFS or FSUIPC as elevator trim up/down: As you may see, I have AI autotrim off. This video was shot inside the A2A Comanche, but the issue also happens in several other GA aircraft (JF Turbo Arrow, Carenado Mooney and 182RG, default 172, DHC2 and Pipistrel). In all cases, my trim buttons end up useless. I have basically two big controller profiles: one for airliners (in which two of my 3 throttle quadrant levers are set for spoilers and flaps) and another one for GA (where I use these levers for prop pitch and mixture instead). This only happens when using the GA aircraft profile. With airliners (A300/A310/747/787/Maddog), somehow it doesn't happen. If I downgrade FSUIPC to 7.5.1, the trim behavior comes back to normal. But if I upgrade to 7.5.2 or 7.5.3, I start getting this problem again. If I use offsets, I also get a somehow normal behavior, unless the aircraft does not like offsets (as in the PMDG 777 or Asobo 787). Is it there a way to fix this problem? For reference, these are the assignments for each profile: [JoyNames] 0= VKBsim Gladiator NXT L 0.GUID={E63F1200-043B-11F0-8004-444553540000} A=VKBSim NXT THQ A.GUID={B046B480-AC8E-11EC-8001-444553540000} B=VKB-Sim Gladiator NXT L B.GUID={14F9D130-FAD0-11EB-8001-444553540000} C=VKBsim Gladiator NXT L C.GUID={E63F1200-043B-11F0-8004-444553540000} D=VKBSim NXT THQ D.GUID={E63F1200-043B-11F0-8008-444553540000} 1= VKBSim NXT THQ 1.GUID={E63F1200-043B-11F0-8008-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=CX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=CY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=CZ,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- 3=CR,256,D,3,0,0,0 -{ DIRECT: Rudder }- 4=DX,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 5=DZ,256,D,23,0,0,0 -{ DIRECT: Flaps }- [Buttons] PollInterval=25 ButtonRepeat=20,0 1=PD,2,C65751,0 -{LANDING_LIGHTS_TOGGLE}- 2=PD,3,C66240,0 -{TOGGLE_TAXI_LIGHTS}- 3=PD,6,C65560,0 -{STROBES_TOGGLE}- 4=PD,7,C66239,0 -{TOGGLE_BEACON_LIGHTS}- 5=RD,5,C66634,0 -{THROTTLE_DECR_SMALL}- 6=PD,0,K82,9 -{Key press: lshift+R}- 7=PD,1,K71,11 -{Key press: lctl+lshift+G}- 8=PC,2,K90,8 -{Key press: Z}- 11=PC,6,C65758,0 -{FLAPS_INCR}- 12=PC,8,C65759,0 -{FLAPS_DECR}- 13=RC,7,Cx32000BC0,x3FFF0040 -{offset sword increment, offset 0BC0 (Incr=64, Limit=16383)}- 14=PC,24,Cx42000BC0,xC0010060 -{offset sword decrement, offset 0BC0 (Decr=96, Limit=-16383)}- 15=PC,25,Cx32000BC0,x3FFF0060 -{offset sword increment, offset 0BC0 (Incr=96, Limit=16383)}- 16=RC,5,Cx42000BC0,xC0010040 -{offset sword decrement, offset 0BC0 (Decr=64, Limit=-16383)}- 17=RC,0,K190,8 -{Key press: .>key}- 18=RD,4,K190,8 -{Key press: .>key}- 19=RC,1,C65588,0 -{BRAKES}- 20=PC,20,C65752,0 -{PARKING_BRAKES}- [Axes.Propellers] RangeRepeatRate=10 0=CX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=CY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=CZ,256,D,29,30,0,0 -{ DIRECT: CowlFlaps1, CowlFlaps2 }- 3=CR,256,D,3,36,0,0 -{ DIRECT: Rudder, SteeringTiller }- 4=DX,256,D,5,0,0,0 -{ DIRECT: PropPitch }- 5=DY,256,D,4,0,0,0 -{ DIRECT: Throttle }- 6=DZ,256,D,6,0,0,0 -{ DIRECT: Mixture }- [Buttons.Propellers] 0=PC,22,C66279,0 -{RUDDER_TRIM_RIGHT}- 1=PC,23,C66278,0 -{RUDDER_TRIM_LEFT}- 2=PC,27,C67272,0 -{RUDDER_TRIM_RESET}-

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