ark1320

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

John, thanks for the info. I had tried some presets (like View Left) but they send the same K event as in my Lua script above and didn't work. I will have to work with the Asobo default view bindings I think. Regards, Al

Using FSUIPC7 in the usual way I have tried assigning both keys and buttons to different cockpit views such as View_Up, View Down, View_Left and View_Right without success. It could be I'm suffering another "senior moment" (more like a senior day in this case 🤔 ). I have also tried using calculator code and presets, all to no avail. I frequently use a little Lua script to test things, and an example is below. I know the script runs because the test message at the end of the script is displayed as expected. When this script runs, just as when I try assigning a button or key to a view, nothing happens as far as the view from the aircraft is concerned. I have tried different aircraft with the same result. Other FSUIPC7 key and button assignments are working. The Asobo control bindings for the views also work. If you have an idea on what I might be doing wrong or overlooking, or you have successfully assigned a key or button to execute a "view command" using FSUIPC7 ver 7.4.16 without the same key or button also being assigned to a default Asobo view command, please let me know. Thanks, Al Here is my Lua test script: ipc.execCalcCode(" (>K:VIEW_LEFT) ") -- view left ipc.sleep(2000) ipc.control(65680) -- view left ipc.sleep(2000) --*************** Window to Display Test Message ***************** w = wnd.open("MSFS_Test", WND_FIXED, 20,90,600,20) -- Script uses FSUIPC Window (wnd) library for message display -- These set the colors and font to be used. -- The size "-1" means the largest font to fit 1 line(s) inside the window wnd.backcol(w, 0x000) -- black wnd.textcol(w, 0x6C0) --green wnd.font(w, WND_ARIAL,-1) wnd.clear(w) -- clear window wnd.text(w, " MSFS TEST SCRIPT " ) -- Getting this message shows code above ran ipc.sleep(2000) wnd.clear(w) -- clear window

It might also we worth checking that AUTO-RUDDER under Assistance Options > Piloting didn't get turned on. I have found that sometimes some of these sim assistance settings get automatically reset for some strange reason. Al

Just to be clear, this Lua script will not sync the heading bug to the aircraft current magnetic heading in all cases. For example, if the NAV/HSI is in GPS mode, the value in offset 0x2FA8 seems to be the bearing to the next GPS waypoint in the flight plan, which may not be the current aircraft magnetic heading. Al

Yes, you don't want to use the HSI BEARING variable to sync the heading bug. The SDK shows this: