Fragtality

Note that it does not need a registered/licensed Copy of FSUIPC per-se. But some pre-made Profiles do indeed need that because they use Lua-Scripts. (Even without a licensed Copy, some/most of the Functionality of such Profiles are still working - the ones not using Scripts) So it really depends on what you are using it for! 😉

Well don't know anything about that StreamDeck Feature. The Profile Switching Feature of PilotsDeck uses Sub-String Matching. So if you map "C414" to one of the StreamDeck Profiles (that is entering that Term in the Profile Switcher Action to any Textbox there), a match is considered found for any active FSUIPC Profile that contains "C414".

Don't forget to save the Profiles before that. The Profiles are just imported from the \Profiles Subfolder, but they are not updated if you change them afterwards in the StreamDeck Software.

What should that have helped? It effectively kills the whole Functionality of the Plugin. Don't know ... never used that. Does not make Sense for me for a Flightsim (with different Planes and therefore Profiles) - the Reason I build in the Profile Switching Feature ^^ What does "eventually" mean? The Profile Switching should happen when the Session is ready and the current FSUIPC Profile matches an associated StreamDeck profile (in the Profile Switcher Action)

Have you enabled Profile Switching? Check the Profile Switcher Action ... is "Enabled" checked? If so: is "Use Default" checked? If so: Does that Profile happen to be one of the Default Profiles that came with the Plugin?

Oh yeah, sorry - got I myself wrong ^^ It is pollInterval x longPressTicks = Duration for Long (Default 200ms x 3 = 600ms) Everytime the Plugin starts - so stopping the StreamDeck Software and starting it again should be enough

Theoretically you can change both, but I only recommend changing "longPressTicks". That is the exactly the amount of waitTicks used for the long press and is not used somewhere else. The waitTicks are also used at other locations (not related to Button Handling) and could change the Plugin Behavior in unknown Ways ^^

Sorry, forgot to add: - Untick the "Profiles Installed" Checkbox (after starting the StreamDeck SW again)

Hmm, maybe you done some extra Steps or still missed some Steps? Judging by the Screenshot the Names known/imported to PilotsDeck do not match the Profiles in the StreamDeck UI. Please follow the Procedure: - Disable Profile Switching (via the Button) - Export your Profiles (for which Switching should be enabled) and Copy them to the mentioned Folder. If you want to Rename them, do so before the Export. - Delete these exported Profiles (and to be sure their Clones) from the UI. The exported File saves the exact State of the Profile, so nothing is lost. - Stop the StreamDeck Software - Run the Importer - Start the StreamDeck Software - Enable Profile Switching and allow the Installation of the Profiles - In the End there should be exactly one Instance of each Profile (with matching Names StreamDeck UI == Profile Switcher) Also make sure you use the exact FSUIPC Profile Name in the Input Field. Even when the Profile Switching could work, it still won't do anything when the Name you entered can not be not matched to the current FSUIPC Profile. That the Plane/Livery is correctly associated with that FSUIPC Profile is assumed - the Plugin does not switch anything when FSUIPC is not switching anything 😉

No, only the ones configured/imported for Profile-Switching since these are the only one which the Plugin can switch to 😉 Sure they do - all with "Copy" appended. You missed the Step to remove them. So the Name and GUID are both wrong.

Make sure you follow the Instruction from Top to Bottom! No, it is global/unique. You can have as many of these Buttons as you want, but they all configure the same Thing / have the same Settings. The Area in the StreamDeck Software where you configure the Properties (Settings) of a Button. The Area you have in the Screenshots 😉 Then you missed a Step or have done it out of order, check the Instructions. Well, the Preparation/Import failed somewhere, so your Profiles are not listed there. When done correctly, your Profiles should appear there as additional Input-Fields (for the respective Deck-Type). In these you enter the FSUIPC Profile's Name it should be mapped to. When that FSUIPC Profile is active, that StreamDeck Profile will be loaded on that Device. The "Default" Profiles allow you to map any unmatched FSUIPC Profile to a Default StreamDeck Profile (when Use Default is enabled). This Default-Profile is already provided and included, but that can be changed also if needed. When Use Default is not enabled, the Plugin will not switch Profiles when no match is found.

Ehm, nope^^ That Feature switches Profiles automatically (after configured), so there is no Need for Elegato's Switch Profile Buttons 😉 No, it just works for me 99% of the Time.

What about the Profile Switching Feature? 😉

PilotsDeck does not start any Program/App. The StreamDeck Software informs the Plugin as soon as any supported Sim is running. Then it expects FSUIPC to be started while the Sim is loading (and also the MF WASM Module for MSFS) - which is the default Behavior. It should not make a Difference when you start it. The StreamDeck Software (and therefore the Plugin) can run all the Time, to allow normal StreamDeck Usage for the Users outside of Flight Simming (in contrary to Spad). I let it start with Windows, since I use my StreamDeck for other Things too. But if a User only wants to start it only when the Sim is running, that is also perfectly fine 🙂

Oh sorry, a bit of Context Missing ^^ That is the new Description for the Lvar Command 😉

What about: "*Name*: The Name of the L-Var with or without preceding `L:`. The L-Var Name can also contain Numbers (0-9), Dashes (-), Underscores (_) and Colons (:) as long as these are not the first Character in the Name. Please Note that **Space** is not allowed. Even though it seems technically possible, it is a very Bad Practice to have Variable Names with Spaces. Therefore Spaces will never be added. You can try if Calculator works for you as Work-Arround."

Try if the latest DevBuild fixes that: https://github.com/Fragtality/PilotsDeck/blob/master/Install-PilotsDeck-latest.exe

Hmm, have you tried without Prefix (L:)? 🤔

Not you, someone else did something "wrong". Even though Spaces seemed to be allowed for no comprehendible Reason, it is just very very Bad Practice to have Spaces in Variable Names. It's like a unwritten Baserule in programming. So I won't allow that in the Syntax-Checks. The last time I did that (FBW's fake L-Var Indices) it introduced Bugs in other Areas. So adding something no reasonable Developer would ever assume in a Variable Name could have that Potential too. I'm afraid you have to have the Workaround with Calculator Code. The Syntax is wrong, negative Numbers are prefixed with a minus in the normal World (=outside of RPN) 😅

Ah okay, I thought your Question / Issue would still be open or unanswered. But if everything is fine now, you're right - would not really serve a Purpose to rephrase the Question 😅

Uhm okay, so if you even know how to write RPN Code - I don't really what your initial Question is about to be honest 😕 Because with that Knowledge I'd assume the available Action-Types would directly mean something to you. Maybe try to rephrase that:

You don't and can't assign Keyboard-Keys and Joystick-Buttons in the first Place (in the Plugin). You tell the StreamDeck Button (respectively the PilotsDeck Action that is on that Button) what you want to send to the Simulator by the different Ways possible. Roughly spoken, the Plugin sends the Events directly to the Simulator, not by emulating Key-Inputs or Joystick-Inputs. I'd recommend to consult Chapter 2.1 of the Readme. For MSFS the Action-Types Control, Calculator or HVar might do the Trick.

You're welcome 🙂 Yeah I tried to move the Check-Symbols out of the Input-Fields ... but either I don't understand what "CSS-Magic" is required for that or it is just not possible with the StreamDeck-UI 😕

So you could sort it out? The Syntax-Checking in the UI is more an Assistance for the User - the "real" and thorough Syntax-Checking happens later on Execution. So it is still worth trying if it works even when the UI shows an Error there. But it could still be that some Corner-Cases for the A-Vars are not covered, though. For Example, I don't know if the current Check allows a Slash ("/") in the Unit-Type tbh!

*Version Bump* Version 0.7.10 Fixed: DataRefs containing only 1 Character long Names where not recognized (The first Name in the Path still needs to be at least 2 Character long!) Fixed: Offset-Addresses where sometimes registered as L-Var (and thus a L-Var with that Name was created) Fixed: Links in the Installer pointed to the wrong minimum .NET Version (listed for completeness, was already fixed in the 0.7.9 Binary after the 3rd April)