ark1320

For completeness, here is how I expanded the information in my post above for the HJet throttles to use two physical throttle levers on my Saitek Throttle Quadrant. With the throttle1 main script the Saitek controller throttle axis value is stored in offset 0xA000. If the value changes by at least a magnitude of 128 the function HJet_Throttle1() is called to convert the raw axis value to a number between 0 and 1, and this number is written to the HJet Lvar that controls HJet throttle1. Same idea for throttle2 which uses offset 0xA002. These scripts are loaded automatically when FSUIPC7 starts through the FSUIPC7.ini Profile Specific file entry as shown below: [Auto.HJet] 1=Lua HJet_Throttle1 2=Lua HJet_Throttle2 Here are the two main throttle Lua scripts that get loaded automatically: -- HJet_Throttle1.lua function HJet_throttle1() throttle = (ipc.axis("T","X") + 16384)/32587 -- need throttle range of 0 to 1 for TQ throttle axis range of -16384 to +16203, which is idle to full power. ipc.writeLvar("L:THROTTLE1_SET", throttle) -- ipc.axis("T","X") is the FSUIPC "X" axis value of TQ "T" (approximately between -16384 and + 16384 ) end --*********************************************************************** --*** Main Part of Throttle1 Program That Calls the Above Function *** --************************************************************************ ipc.writeLvar("L:THROTTLE1_SET", 0) -- initialize throttle1 to idle position. ipc.writeLvar("L:HA420_ThrottlePos_L", 50) event.offsetmask(0xA000, 0xFF80, "SW", "HJet_throttle1") -- mask requires a change of at least 128 in offset 0xA000 to trigger the function call. -- Under FSUJIPC7 Axis Assignments, this HJet throttle1 axis value has been assigned to Offset 0xA000 as Offset Word Set as shown below Main script throttle1 FSUIPC7 axis assignment. -- HJet_Throttle2.lua function HJet_throttle2() throttle = (ipc.axis("T","Y") + 16384)/32587 -- need throttle range of 0 to 1 for TQ throttle axis range of -16384 to +16203, which is idle to full power. ipc.writeLvar("L:THROTTLE2_SET", throttle) -- ipc.axis("T","Y") is the FSUIPC "Y" axis value of TQ "T" (approximately between -16384 and + 16384 ) end --*********************************************************************** --*** Main Part of Throttle 2 Program That Calls the Above Function *** --************************************************************************ ipc.writeLvar("L:THROTTLE2_SET", 0) -- initialize throttle2 to idle position. ipc.writeLvar("L:HA420_ThrottlePos_R", 50) event.offsetmask(0xA000, 0xFF80, "SW", "HJet_throttle2") -- mask requires a change of at least 128 in offset 0xA000 to trigger the function call. -- Under FSUJIPC7 Axis Assignments, this HJet throttle2 axis value has been assigned to Offset 0xA002 as Offset Word Set as shown below. Main script throttle2 FSUIPC7 axis assignment. The four tiny scripts below move the HJet throttles between cutoff and idle. There is a switch at the bottom of my Saitek throttle axes. When the switch is closed by moving a throttle lever down into the switch, the associated HjetThrotCuttoff script is called, and when the lever is moved up out of the switch position the associated HjetThrotIdle.lua is called. Here are the two scripts for throttle1 --HjetThrotCutoff1.lua ipc.writeLvar("L:THROTTLE1_SET", -1) -- cutoff value is -1, idle to full power is 0 to 100 ipc.writeLvar("L:HA420_ThrottlePos_L", 0) -- cuttoff position, 50 is idle, 100 is full power position --HjetThrotIdle1.lua ipc.writeLvar("L:THROTTLE1_SET", 0) -- idle value, -1 is cuttoff, 1 is full power ipc.writeLvar("L:HA420_ThrottlePos_L", 50) -- idle position of throttle lever, 0 is cuttoff, 50 is idle, 100 is full power position Here are the two scripts for throttle 2 --HjetThrotCutoff2.lua ipc.writeLvar("L:THROTTLE2_SET", -1) -- cutoff value is -1, idle to full power is 0 to 100 ipc.writeLvar("L:HA420_ThrottlePos_R", 0) -- cuttoff position, 50 is idle, 100 is full power position --HjetThrotIdle2.lua ipc.writeLvar("L:THROTTLE2_SET", 0) -- idle value, -1 is cuttoff, 1 is full power ipc.writeLvar("L:HA420_ThrottlePos_R", 50) -- idle position of throttle lever, 0 is cuttoff, 50 is idle, 100 is full power position HjetThrotIdle1.lua HJet_Throttle1.lua HJet_Throttle2.lua HjetThrotCutoff1.lua HjetThrotCutoff2.lua HjetThrotIdle2.lua

The PilotsDeck displays look OK as shown below, didn't see much change from the originals. Profiles: Test CTL.streamDeckProfile Test+.streamDeckProfile

Just to make sure I understand the big picture, I am to basically repeat the first test I did above but using a new version of PilotDeck and with new actions put into the new "empty" profiles. Correct?

Yes, seemed close to what it was as best as I can recall. I can go in an adjust the font sizes if necessary, just don't want it to change significantly between displays.

1. I started the computer with the small main display. 2. Created the two profiles below 3. Downloaded and installed the PilotsDeck test version from MediaFire. 3. You didn't mention starting the sim in your list above -- so I did not do that. Here are the two profiles and the associated displays on the StreamDecks. Looks good to me. Hope this is what you wanted. Test CTL.streamDeckProfileTest+.streamDeckProf

When the computer boots with the smaller main display and I move the sim window to the 4K display, the PilotsDeck displays are still correct and Powershell reports a DPI of 96. When the computer boots with the larger 4K main display and the sim is running and the PilotsDeck fonts are too large and the ALT VALUE is truncated, Powershell reports a DPI of 168. I noticed the 168 value is 175% of 96. In the first case above I am accessing Power Shell using the smaller display since that is where the Start Menu is, and in the second case above I am accessing Power Shell using the 4K display since again that is where the Start Menu is. Hope I did that right, and that is the info you wanted.

I don't know what you are asking, I know nothing about Powershell, sorry. In the picture below, the displayed altitude value is supposed to be 12000, but the right most digit was dropped because the font is larger than "normal". However, the altitude values of 1000 to 11000 were displayed correctly in PilotsDeck, so I assume the display of 12000 required a bit more space and so didn't fit. And as I mentioned above, the altitude values actually set in the aircraft in the sim are always correct. The labeling above the 1200, the ALT ALERTER, is also larger than "normal".

I was wrong above regarding Commands not working -- they work regardless of the display being wrong. I was fooled because with the large, incorrect font size certain numerical values will no longer "fit" and the displayed values get truncated. But the value actually set in the sim is correct. I should have realized that -- sorry. If I start the the computer with the smaller display as the main display, then the PilotsDeck displays are correct even when I move the sim window to the larger 4k display. But if I start the computer with the 4K display as the main display, I get the oversized font on the PilotsDeck. The 4K display setup values are shown below. The 175% scale setting I use is quite a bit less than the Win11 recommendation of 300%.

Interesting problem. I have two displays connected to my computer. If I start the sim on the smaller display that has a resolution of 1920x1080, I get the first PilotsDeck display below on the StreamDeck. If I start the sim on the larger display that has a resolution of 3840x2160, I get the second PilotsDeck display below on the StreamDeck where the font size has changed and no longer "fits" within some of the buttons. In addition, when this happens, some PilotsDeck controls, like an encoder on a StreamDeck+ unit that uses a FSUIPC7 Lua script, no longer works correctly. Thanks for any suggestions. Al

No, these FSUIPC Control commands where never a toggle switch -- pushing the associated button on the Stream Deck simply always sent the same control code. Sorry, I don't have the not-updated profiles. Al

Had a strange problem. Almost none of the Command type FSUIPC Control as shown below for HDG, were working . This problem existed across multiple aircraft. The profiles were not new, they all worked with previous versions of Pilots Deck. Other FSUIPC related Commands, such as FSUIPC SCRIPT, did still work for these aircraft as expected, as did other commands like Calculator/RPN code. Pushing a Stream Deck button using FSUIPC Control resulted in the yellow triangle error icon with the black exclamation point inside. When I looked at the log, there was no Command Address value shown for these control commands: Turns out the problem was the option Toggle Switch with two different Commands based on value had been turned on somehow ,but was not being used, there was no second command. Maybe this happened when these profiles were "brought over" from the older version of PilotsDeck to this new version, or else the option being on didn't make any difference in the older version of PilotsDeck. Just reporting this in case anyone else runs into a similar problem. Al Thanks, Al

Just tried to see if I could force a profile switching failure by trying neither all caps or all lower case, so tried the term "LeArJeT". Still worked. 😀

I don't know if it makes any difference somehow (timing issue maybe?), but just in case wanted to let you know that usually the sim starts FSUIPC7 via the exe.xml file, and there is a section in the FSUIPC7.ini file that will start Stream Deck IF Stream Deck is not already running.

I agree, I also don't understand why that happened, especially since "learjet" is in the long path, and "LEARJET" is in the short path.

Sorry, but I don't understand what you are saying here. What I said above is I now find using a term from the aircraft path works, and it makes no difference if I use it in caps or not. I used a term from the path, tried it as caps, tried it as lower case, and both worked. I do not see any cases now that do not work. My understanding is that is exactly how it should work according to you, that is, upper or lower case should not make a difference since your code checks for that. So since it all seems to be working I don't know what logs you are asking for. I am not currently seeing any profile switching failures. 🙂