Fragtality

That is what all the other Command/Variable Types are for ^^ https://github.com/Fragtality/PilotsDeck?tab=readme-ov-file#12---supported-sim-commands---variables The same as with the other Requirements: the Installer will download and run the necessary Stuff. With the only Difference for the vJoy Driver that the Installer will inform/offer to install or update it (it is only an optional Requirement). So you have to manually click the Link in the Installer to initiate the vJoy Driver Installation (or Update). In the Developer UI / QRH View (Click on the Systray/Notification Area Icon of the Plugin). Not only does that View have Links to essential Plugin-Directories (e.g. like the log Directory), it also has Links to some general References to lookup Command or Variable Names (e.g. the MSFS SDK for SimVars / SimEvents).

Nope. I asked for specific Information which you didn't provide. Support/Troubleshooting is a Two-Way-Process 😉 It is now even more unclear what you are trying to build there. I can't see a sound Reason for a Chain of PilotsDeck -> vJoy -> FSUIPC -> MSFS. StreamDeck can talk to both FSUIPC or MSFS directly. A vJoy Driver Command is mostly only used when the Sim doesn't provide any (good) Way to send a Command directly (i.e. Load Custom Cameras in MSFS, Push-and-Hold Buttons in X-Plane which don't really work/make Sense when triggered with command_once). So I'd understand PilotsDeck -> vJoy -> MSFS, but still can't follow what FSUIPC has to do with that. Further more, using FSUIPC is only really needed when there are 3rd Party Addons using Offsets to share Data or if you have some existing Stuff (e.g. Scripts) in FSUIPC which you want to continue to use with PilotsDeck. Else mostly everything else FSUIPC can Read or Send is in the End a SimVar or SimEvent that the Plugin could directly send to MSFS. And even if there is a very specific FSUIPC Use-Case where "something" can only be bound to a Joystick - FSUIPC has its own vJoy Facility. Maybe the Problem is the Feeder App acquiring the Device and thus blocking it maybe? I don't even know where you got that App from, since the vJoy Fork you should have installed doesn't have that. So please provide the Logs. Else you have to figure it out yourself, got no Time Seek-and-Hide 😉

I honestly don't know ... something, maybe!? I see that you try to give Information, but unfortunately it confuses more than it helps. - Why would an Assignment in FSUIPC matter at all? - Two what Type of vJoys previously? Why does that matter? - Latest Plugin Version means what exactly in Numbers? - The Brunner Fork of the vJoy Driver was installed during Plugin update/installation? - Why would it matter what Character FSUIPC has assigned to the vJoy Device? - Where are the Logs? - A copy of that non-working Action?

*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)

*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)

*Version-Bump* Plugin updated to Version 0.8.0 Major Plugin Overhaul - it is basically a new Plugin under the Hood! Please make an Export/Backup of your Profiles your created with PilotsDeck! The Intention is that existing Profiles just continue to run (with a bit smaller Fonts), but it is better to be safe than sorry Installer Improved UI Check & Installs all Requirements (either automatically or by starting the Setup for you) Check for the vJoy Driver now tests for the Brunner Version/Fork - which should work on both Win 10 & 11 Ability to remove the Plugin (including all Customizations!) New Profile Manager Application Enables easier Profile Installation in a few Clicks - extracts & copies the Files for you, assists with adding the Profiles to the StreamDeck, automatically removes old Profiles on Updates Own Package Format to distribute Profile Files, Images and (Plugin) Scripts as one File Allows much easier Profile Mapping to switch Profiles automatically depending on the Aircraft (or Sim) Profile Switching now only can switch back to specific Profiles when the Simulator exits These Profile Mappings will automatically be transferred to new Profiles on (Profile) Updates Plugin Property Inspector is now tabbed to allow easier Navigation Option to add a Guard (Image & Command) to an Action (Guard Images can also use Image Mappings) Added Image Mapping to more Actions Top and Bottom Image for the Korry Action can independently enabled/disabled Most Actions can now be used on an SD+ Encoder (except Simple Button and Gauge Dual) B-Var Support added - per default handled as Command-only but can also be used as a Variable Added dedicated Command Type for K-Var (allows to define a Sequence) HVAR Command supports passing a Value to the H-Var New Calculator ("C:") Variable to read the Result of Calculator/RPN Code (read only) Added Internal (X:) Variable to share Data within the Plugin Added Copy and Paste Buttons to all Actions to share single Actions between Users (or to copy between a Keypad and Encoder) Added a new "Composite Action" that gives you much Freedom to design your own Action (Display and Command wise) - most Feature Requests should be now possible with that Action (and can even replace Actions that would only be possible with Lua Scripts) This new Action is configured through its own dedicated "Action Designer" UI (opened via the Property Inspector) The Script now has its own Engine to run Lua Scripts (does not need external Engines like FSUIPC or FlyWithLua anymore) The Functions of these Lua Scripts can be directly addressed as a Variable or Command - like all other Variable/Command Types Multiple Script Types available to be run on-demand (Variable, Command) or constantly when the Session runs The Scripts can read all Variables and send all Commands the Plugin supports FSUIPC7 is now only the secondary Connector for MSFS - it is possible to use it without FSUIPC7 installed if needed! Remote X-Plane Setups are now supported Images can now be stored in Sub-Directories to better Organisation of different Packs and easier Navigation Image Drawing overhauled - Images are now drawed on top of each other (i.e. on the Dynamic Button) Added an Icon in the System Tray / Notification Area to restart the Plugin or show the Developer UI The Developer UI offers Links to some Reference Source to look up Variables or Commands and to access the Plugin's Folders easier The Developer UI has also a Monitor View to look up the current Aircraft-String/-Path or the Plugin's State, Ressources & Statistics Changed vJoy Driver Library to the Brunner Fork Plugin Configuration is now persistent between Updates and allows much more Tweaking Removed Error Image (and Error State) Sim Connection, State Handling Variable Handling completely overhauled Moved to .NET 8 (LTS) and upped minimum OS to Window 10

*Version-Bump* Plugin updated to Version 0.8.0 Major Plugin Overhaul - it is basically a new Plugin under the Hood! Please make an Export/Backup of your Profiles your created with PilotsDeck! The Intention is that existing Profiles just continue to run (with a bit smaller Fonts), but it is better to be safe than sorry Installer Improved UI Check & Installs all Requirements (either automatically or by starting the Setup for you) Check for the vJoy Driver now tests for the Brunner Version/Fork - which should work on both Win 10 & 11 Ability to remove the Plugin (including all Customizations!) New Profile Manager Application Enables easier Profile Installation in a few Clicks - extracts & copies the Files for you, assists with adding the Profiles to the StreamDeck, automatically removes old Profiles on Updates Own Package Format to distribute Profile Files, Images and (Plugin) Scripts as one File Allows much easier Profile Mapping to switch Profiles automatically depending on the Aircraft (or Sim) Profile Switching now only can switch back to specific Profiles when the Simulator exits These Profile Mappings will automatically be transferred to new Profiles on (Profile) Updates Plugin Property Inspector is now tabbed to allow easier Navigation Option to add a Guard (Image & Command) to an Action (Guard Images can also use Image Mappings) Added Image Mapping to more Actions Top and Bottom Image for the Korry Action can independently enabled/disabled Most Actions can now be used on an SD+ Encoder (except Simple Button and Gauge Dual) B-Var Support added - per default handled as Command-only but can also be used as a Variable Added dedicated Command Type for K-Var (allows to define a Sequence) HVAR Command supports passing a Value to the H-Var New Calculator ("C:") Variable to read the Result of Calculator/RPN Code (read only) Added Internal (X:) Variable to share Data within the Plugin Added Copy and Paste Buttons to all Actions to share single Actions between Users (or to copy between a Keypad and Encoder) Added a new "Composite Action" that gives you much Freedom to design your own Action (Display and Command wise) - most Feature Requests should be now possible with that Action (and can even replace Actions that would only be possible with Lua Scripts) This new Action is configured through its own dedicated "Action Designer" UI (opened via the Property Inspector) The Script now has its own Engine to run Lua Scripts (does not need external Engines like FSUIPC or FlyWithLua anymore) The Functions of these Lua Scripts can be directly addressed as a Variable or Command - like all other Variable/Command Types Multiple Script Types available to be run on-demand (Variable, Command) or constantly when the Session runs The Scripts can read all Variables and send all Commands the Plugin supports FSUIPC7 is now only the secondary Connector for MSFS - it is possible to use it without FSUIPC7 installed if needed! Remote X-Plane Setups are now supported Images can now be stored in Sub-Directories to better Organisation of different Packs and easier Navigation Image Drawing overhauled - Images are now drawed on top of each other (i.e. on the Dynamic Button) Added an Icon in the System Tray / Notification Area to restart the Plugin or show the Developer UI The Developer UI offers Links to some Reference Source to look up Variables or Commands and to access the Plugin's Folders easier The Developer UI has also a Monitor View to look up the current Aircraft-String/-Path or the Plugin's State, Ressources & Statistics Changed vJoy Driver Library to the Brunner Fork Plugin Configuration is now persistent between Updates and allows much more Tweaking Removed Error Image (and Error State) Sim Connection, State Handling Variable Handling completely overhauled Moved to .NET 8 (LTS) and upped minimum OS to Window 10

Awesome, didn't know that! Thanks to you both for making our Sims run so much smoother 😃

Not quite correct. The first one was MSFS_AdapativeLOD by muumimorko (https://github.com/muumimorko/MSFS_AdaptiveLOD) - which is defunct now because not updated to the SU's released after it. BUT: without it we would not have anything of the Tools thereafter. That Developer found the original Mechanic to change the xLOD Values dynamically in Memory by either Altitude/AGL or FPS. Even the original Icon comes from that Project. So if anything, we need to thank muumimorko.

I mean I would somehow agree if this is the "right" Direction. BUT: That does not mean it is wrong in any Sense. It is just not what I had in Mind for my Tool, but there is no right or wrong here. If it works better for some with this FPS Focus, that is absolutely fine. That is why I've favored the Route of multiple Forks - so there is Choice (my Variant is not dead in any Sense, it still works fine and will be updated for SU15 (Release) if necessary). Users have the Choice and can choose the Approach they believe / they evaluated better for them 🙂 I personally continue to use my Variant, because I was never concerned about my FPS. I just wanted a Tool that allows me to keep a xLOD Value my System can handle fine but just not on bigger Airports without Stutters. So in that Sense, Congratulations to @Reset XPDR on what he has achieved. And to everyone else: Just use the Variant you're more comfortable with 😉

Ok, that is as much Time as I will invest in a Topic I don't have any Benefit from and which I especially can't do any Research/Development/Tests on. There was only *one* Response which actually tried to help. The other basically saying "you just don't know how to use it" which even gets an upvote. (To be honest, that is a true Statement - I can't figure out to find one single Bit in GB's of Memory.) So what I'm gonna do: Adding a Mechanic to switch automatically between PC/VR Mode based on two Offsets (from the FlightSimulator Base Address). With these Offsets being editable in the config File. Thereafter everyone for themselves. If one does not know what to enter there: don't ask me, I don't & can't know and don't care. If the Mechanic does not fit your Needs: Hope that somebody else offers a preferred flavor. 😉

That would at least match with what Umberto has said, that these Offsets where meant for the MS Store Version. Maybe @virtuali can shed some Light how he managed to find two booleans/bits in the Gigabytes of MSFS Memory? 😉

To the VR Folks driving me Nuts: Latest Binary-only Package available here. Does it detect PC/normal and VR Mode (For Example TLOD/VR: <100> / 100 should switch to TLOD/VR: 100 / <100>)? Which Store-Version? (If it is not clear how to download, how to extract, where to put => not eligible for testing)

👍 Well, I forgot to write that FindPairs() should reset ForceEvaluation at the End. (But it's kinda obvious, don't you think^^) As I already explained, the VR Flag can still be useful. If there should be an Auto-Switch maybe someday, it would be quite handy. (Or how would you decide to which Profile you would switch to for VR?) And considering some of the Comments here and the instant-closed Issues on GitHub, you can be very certain that you will find at least one User who forgets which Profile he/she uses for VR (and need that Flag as Reminder) 🤪

Well I honestly don't know ^^ I tried to minimize Intrusion - we're still talking about injecting "bogus" Values in the Memory and Engine. But it very well could be that it makes no Difference for MSFS if you change both the PC & VR Values at the same Time. At the same Time it makes no Difference in regards to switching Profiles - you fancy VR People still want to switch between different Profiles without getting your Hands dirty I guess 🤪 (So removing the VR Flag by that does not get you further with that. It would also create the Problem: which Profile to switch to when going to VR?)