ark1320

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

Did some more testing, and as long as I use a "profile term" from the long or short aircraft string, switching is working independent of whether the term is upper or lower case, as you expected. It would be a lot more user friendly if a term from something like the aircraft/livery "name" from the sim's aircraft selection matrix on the World Map page could be used instead of a term from the aircraft string. Don't know if that would be possible. Thanks for all the help. Al

You should see the info in the red box. I'm just reporting what I find in case it might be useful to you -- I am not in a position to determine what might be helpful, and what not. You are the Pilots Deck expert, not me. And NO, I have not been using MSFS2024 for any of these tests.

Yes, both sims where found, but see red box below.

I don't know what to do with the below. And what is a Switch-Back Profile. Where are details like this explained? Is there documentation somewhere for new Pilots Deck users that explains how to use the different features of the Profile Manager?

Using the lower case "learjet" for the mapping seems to work. Here's how the install went: And here's the log file:PilotsDeck-Installer.log Still didn't see that MSFS2024 was detected.

I got the latest PIlots Deck build, but how do I start Install-PilotsDeck-latest.exe with the --debug option? Usually I just click on the installer to run it.

This is the long path I assume. Learjet does show up, but all lower case. And this is the short path. I see now Learjet is all caps.

Reported where? Sorry -- don't know where to look for this info. Al

The value is: "C:\Users\arkla\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages" That's what I thought, but, for example, for the Learjet I could only get profile switching to work in MSFS2020 using the FSUIPC7 profile name LJ35A as shown below. If in place of LJ35A I used just LEARJET it did not work. In the aircraft.cfg file for the Learjet, the plane is identified as Title="LEARJET 35A N145AJ PMSGTN750+RADAR" Perhaps I am doing something wrong with the Profile Manager. Just had a thought -- does the entry in the Profile Manager have to uniquely identify the particular plane AND LIVERY, or just uniquely identify the plane. The addon Learjet has a number of liveries.

Yes, in the General section both FSUIPC7.ini files show UpdatedByVersion=7500b I should have mentioned that above. I also was using the latest Stream Deck version. Al

BTW, using the Profile Manager I did get automatic profile switching working with ver 0.8.3 in MSFS2020, but like in previous versions of Pilots Deck, I had to use the aircraft profile names for each aircraft as used in the FSUIPC7 profiles. I first though with ver 0.8.3 I could just use a unique subset of the name shown in the sim's aircraft.cfg file Title entry, e.g., LEARJET for the LEARJET 35A, but that didn't work. Al

Ver 0.8.3 did not find MSFS 2024, only MSFS2020. Both sims are MS store versions and are installed in their default locations, each with their own copy of FSUIPC7, own Community folder, etc. I don't know if that fact that each sim has it's own FSUIPC7.ini file is a problem. How does Pilots Deck locate the FSUIPC7.ini file for the currently active sim? Any suggestions? Thx, Al

I am still using ver 0.7.12. Should that work with MSFS 2024? If not, does 0.8.0 work with MSFS 2024? Thanks, Al

My mistake, I meant ver 7.12, not 7.9 above. Ver 7.12 in conjunction with FSUIPC7 is working well for me so I'm reluctant to make any changes until I actually need some of the new features in ver 0.8.0. Thanks for the info. Al

I don't see any install instructions except the suggestion to back up existing profiles. Maybe I'm not looking in the right place. I do see a detailed change log. Should the existing PilotsDeck be removed or uninstalled before running the new installer? Will the existing auto selection of profiles based on the loaded aircraft be preserved by the new installer? Should the new installer be downloaded to the StreamDeck directory before being run? Is there a suggested install procedure to maximize the likelihood that whatever PilotsDeck functionality one has with version 0.7.9 will be preserved by the new update to version 0.8.0? Or are you saying to just download the new installer and run it and whatever you had working with PilotsDeck version 0.7.9 and will continue to work after version 0.8.0 is installed? Thanks, Al

Thank you for the continued development of PilotsDeck -- seems like the new version took a lot of work! As a start, If I simply want to run my existing profiles with no changes is the update procedure to Ver 0.8.0 detailed somewhere so I can review it before actually doing the update? Thx, Al