Fragtality

Calculator-Code can be used as Variable/Value since 0.8.0: https://github.com/Fragtality/PilotsDeck?tab=readme-ov-file#calculator TL;DR: Put 😄 in front of the RPN-Code And remember that the integrated Lua Engine is also there for Use-Cases of calculated Values. Sure it doesn't really have a Benefit for 1-3 of such simple Calculations in a Profile. With an increasing Number of such Calculations and/or more complex ones, a Lua Script might be an easier Solution to create and maintain. But well, I absolutely can't get around with the Reversed-Notation, so I might be a bit Lua-biased 😅

*Version-Bump* Plugin updated to Version 0.8.6 NOTE / IMPORTANT A Backup of your Profiles is recommended! This Update fixes the Font-Scaling Issues experienced by some Users after the 0.8.0 Release (especially when using a shared Profile from someone else). Due to the Nature of the Bug and to provide a clean Solution going forward, the Plugin will adjust the Font-Sizes to keep the same visual Size on the StreamDeck (once, when an Action appears for the first Time). Or put differently: the Plugin tries it best so that your Actions look the same as before. Due to rounding there is Margin of Error of 0.5 - so that is the worst the Text will be "off" in (visual) Size 😉 The Recommendation to make a Backup is mainly to keep the Ability to go back to the previous Version, but the Update is intended as a simple "drop-in" as usual. But there is a Caveat: The Conversion of an Action has to be done under the Windows Font-Scaling / DPI Setting it was created to lead to the correct / intended visual Result: If you're a Profile Author, you need to update/convert your Profiles on your PC and then distribute the Profiles as an Update to your Users (just navigate through all Pages/Folder of a Profile, export, distribute). If you're a Profile User, you need to ask the Author to provide an updated Profile. The Profiles I share will be updated shortly. Installer Fixed using wrong .NET Runtime on new Installs / Updates Set FSUIPC 7.5.1 as Target Version Set StreamDeck SW 6.8.1 as Recommended Version Plugin Fixed Font-Scaling affected by Windows' Text Scaling/DPI Setting Render DPI is now fixed at 96 DPI (the pre-0.8.0 Default) Font-Sizes will be automatically converted to keep the same visual Size The Conversion uses the current Windows DPI, so it is only correct on the PC where an Action was designed The Conversion is only applied once when an Action becomes visible for the first Time on the new Plugin Version Improved Session-Ready-Detection for 2024 Slightly, as the SDK allows - Asobo has no Interest in improving a Situation that exists since 2020 🤷‍♂️ Added MSFS 2024 SDK Links to the Developer UI / QRH View Added Button in the Developer UI to open the Profile Manager from there Manifest Version corrected Updated SDK / Libraries Profile Manager Fixed Links not working for Profiles with Spaces in the Filename (Package Installation)

Pushed the changes now as normal Dev-Build on GitHub: https://github.com/Fragtality/PilotsDeck/blob/master/Install-PilotsDeck-latest.exe So free for everyone to test (note the Comments on the Commit) 😉

And for me the exported Profiles/Actions look the same as in your Setup - Nice! I think that is the Way going forward - even old (pre 0.8.0) Profiles imported stay pretty much the same now 😀 Thanks for your Help 👍

Yes, the same Procedure as before with a different/new Build. Yes, new Actions in the Sense of a new Copy of an existing Action. Put differently: don't use the Actions modified in the previous Test. Copy them over as before.

@ark1320 Testing Time again 😉 Again, follow closely: If you changed them, ensure your Windows Display Settings are as they were before (when you created your Profile / Actions) Create an empty Profile on all your StreamDeck(s). You can use the Profiles from the previous Test, but then delete the Actions there (they are already modified, they won't give a Result) Copy at least one Classic Action (anything not a Composite Action) containing Text and at least one Composite Action containing Text to this empty Profile(s). Actions you have created in your Setup. Do not modify them - copy them as they are. And with Text I mean Text rendered by the Plugin - so no Buttons with just a StreamDeck Title displayed on it. Ensure such an empty Profile is set as the current Profile on all your StreamDeck(s) Do not run a Sim during the Test. If you do, ensure that you have Profile-Switching disabled. Install this Version: https://www.mediafire.com/file/17avi48rdxuvwq9/Install-PilotsDeck-latest.exe/file Do not switch Profiles on any Deck! Please answer: How do the (copied) Actions look (in Terms of Font-Size)? Maybe they slightly changed in Size* but are they about the same - not overly small or large? (* = visually, the actual Font-Size in the Settings will be different!) Put differently: how do they looked to you, if and what difference did you notice? Export that empty Profile, with the copied Actions (regardless of the Answer to the previous Questions) and attach it here (change the Extension as needed, doesn't hurt). Optional: if you still have a pre-0.8.0 Profile lying around, import that to the StreamDeck Software (it is okay to switch to that Profile then). Same Questions apply, but do not export. Install the Release Version (0.8.5) again! Done, all good again. Yes, the copied Actions from the Test will look different then. That is expected and the Reason for all the Steps: We want to make sure that special Build only modifies Actions intended to be tested. The intended / expected Results: Good Result => Only slight Changes to the Text-Size - it is more or less as it was before (with the Release Version) and doesn't require any Intervention (not too small to read nor too big to fit). Perfect Result => No noticeable Difference.

Cool 🙂 Nah don't change any Font-Sizes yet, it was just the first proof of concept for a possible Fix. But that already included that the Actions would not have changed between different Display-Setups 😉

Exactly - as Profile Switching might have got you in Trouble 😉 Don't forget to install the Release Version 0.8.5 again! (Yes, the Actions you have copied for the Test will look different) Yep exactly 🙂 So you didn't see a Difference to what it looked before after you installed that special Version (from mediafire)? Or at least not so much that it would be a big Issue?

Attention, you need to follow these Instructions very closely now: (Instructions only for ark1320) If you changed them, ensure your Windows Display Settings are as they were before (when you created the Profile) Create an empty Profile on all your StreamDeck(s) Copy at least one Classic Action (any will do) containing Text and at least one Composite Action containing Text to this empty Profile(s) (Actions you have created) Ensure such an empty Profile is set as the current Profile on all your StreamDeck(s) Install this Version: https://www.mediafire.com/file/7yd9ziol5iphqai/Install-PilotsDeck-latest.exe/file Do not switch Profiles on any Deck How do the (copied) Actions look (in Terms of Font-Size)? Maybe they slightly changed in Size* but are they about the same - not overly small or large? (* = visually, the actual Font-Size in the Settings will be different!) Export that empty Profile, with the copied Actions (regardless of the Answer to the previous Questions) and attach it here (change the Extension as needed, doesn't hurt). Install the Release Version (0.8.5) again Done, all good again

Type "Windows Powershell" in the Start Menu and copy & paste the Command there. Else let it be and just stand by (no further troubleshooting and descriptions).

Please run that Command in Windows Powershell and tell me the Number (with your usual Display-Setup/-Settings - e.g. when the Actions in Question where created) (Get-ItemProperty 'HKCU:\Control Panel\Desktop\WindowMetrics').AppliedDPI

Yeah, just got another Report on x-plane.com that there is something going on with Font Scaling, gotta look into this 🤔 But: I don't really know if that has really any Connection to Commands not working - It's different Parts/Threads doing different Things. So I'd need the PilotsDeck-Logs and one Action covering that Issue (attach the whole File, paste the Action here). The Information/Description you gave on the Scaling Issue was really helpful and vital for Troubleshooting - for the Commands not working unfortunately not.

Small Bump: 0.8.5 Just checking for and installing FSUIPC 7.5.0 😉 https://github.com/Fragtality/PilotsDeck/releases/tag/v0.8.5

Would have been helpful, can't replicate that: - Created a Simple Button Action (Control, 65798, no Toggle) on 0.7.12 - Installed 0.8.4 - Checked Action: Toggle still disabled So for the Moment I can just assume you had actually set a Toggle Switch unintentionally. And that a Setup of Toggle Switch enabled +no Alternate Command+ no Monitor Address + no Monitor Value/Comparison just behaved differently with a on pre-0.8.0 Versions 🤔

So it wasn't a Toggle Switch before or what and after the Update it was enabled? Wouldn't know how that would be possible, when pre-0.8.0 Actions are loaded, the ToggelSwitch Option isn't touched. Do you still have that Profile in its not-updated Form? If so, please share so I can take look.

That Link wasn't meant as an User-Facing Link - they would still use the actual File-Name with the Version embedded - was more an Idea for Apps 😉 But sounds good, I'll just update the Forum Link then until Release! 🙂

Btw, would it be possible to offer a permanent Link to the Beta? Maybe something like "Install_FSUIPC7.5.0-beta.zip" Link to the respective current File?

Ohh! 😮 Then I shall add that to check Paths I guess ^^ Thanks for the Feedback!

Well, maybe, that is why I request Logs usually 😂 But it shouldn't - the Intention is that the Plugin can be (re)started at any Time. The only known Difference is that MSFS Issue of reporting different Paths depending on the Situation - that it is why that is documented. Further thinking about it, maybe it would be good Idea to shorten the Path on Purpose. So the User just always see the "reliant" Part of the Path 🤔

Hmm well, the Reason could be that most of my Response to that was completely pointless, because I did not properly read your Post - sorry 😔 I was still in the State of "mysterious lower/upper case issue where I really need logs to go further" and you responding with Experiments did not match the expected Input. 😅 But then I don't understand now, how the Issue has suddenly gone away?! I mean it made a Difference in your Setup if "learjet" or "LEARJET" was used. 🤔

I assume it was somehow necessary to change the RegistryPath to FSUIPC7Both? (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\FSUIPC7Both)

I wondered what you wanted to point out / ask with that. I mean I have written the Code and Text 😉 And the message is also explained why it is and what to do. So really couldn't figure out what was meant. But if it was just some form of Confirmation / Status-Update: Yeah looks good now 😅 You are following the wrong Approach, unless you really want to possibly waste *your* Time ?! It could be a possible Bug, maybe some kind of unexpected Situation / Input / Data from the Sim which results in a Situation that doesn't match. PilotsDeck has Logs for Reasons. For example to better troubleshoot Issues. But instead of bringing me in the Situation to help you (=>Logs) you attempt it for some Reason all by yourself. It is totally fine if you want it that Way, but then please don't update me about it - I can not help you like that. If you actually want it to be troubleshoot, please give me the Information I requested. For the Request Part: sorry, but (mostly and for the Moment) - Nope. The Title is rather "dynamic" - you can have the exact same Aircraft with totally different Names. You could title the Fenix as PMDG even. The new Component Model of 2024 makes it even weirder. And partly also because you are rating the new System while still having an Issue - so it not really works as intended in your Setup. The current Source - the actual Path of the Aircraft - is just more reliable. You could have a totally "fancy" Livery for the Fenix titled (!) "PMDG House Colors" and the Fenix would be matched as Fenix (or to be more specific "FNX_3" - which btw never was an Issue for me). And compared with the old Approach it is so much easier now. I mean you got two Sources for the current Aircraft's Path, one of which you can copy & paste the Text out of it (makes me think - would be good Idea to make it copyable from the Dev UI). When having multiple Decks (so multiple Profiles to be switched) you can just copy & paste the Settings between them. You can multiple totally different Strings per Profile to match multiple Aircrafts to the same Profile (e.g. mapping Asobos, Horizons and Kuros 787 to one Profile) But I could look into the work needed to have different Sources. There is already something like that for XP, since Versions below 12 don't have a Aircraft-Path-Ref so the Plugin uses a different Source for anything below 12. But there would be some Constraints for MSFS: - It has to be a SimVar / SystemState / something that I get through SimConnect. So anything read from FSUIPC is already out. - The Aircraft Path is part of the State-Checking (e.g. is the Session Ready) so whatever other Source must draw the same Conclusions. But if it is possible, then I could add it as an "advanced" Option to the Config File (but the Path will stay the default!)

Uhm ... please do not tell me that all your Profile Switching Tests where done in 2024?!?

And what exactly should I see there ...?

O M G - I'm so dumb ! Download the Dev-Build (-latest File) again, I had a Typo in the Path 🙄 The Installer Issue should now be fixed. But I am still waiting for the Logs of the Plugin not switching. I don't understand any of that, because it doesn't make any Difference either Code-Wise or in my Tests which Case-Style the Search-Strings have. Even Camel-Case works.