Fragtality

Nope. Still don't ^^ Is is that? - PFC Display and Plane are OFF - Press Button on PFC to turn Plane ON - When Plane turns on, PFC Displays become alive?

Now I'm confused too, although you've showed it too me during our call 😅 So is it: 1) The Plane should turn on when you press a Button on the PFC? 2) The PFC should turn on when the Plane is turned on?

Oh man, very frustrating indeed 😞 But to be completely honest with you: You're really taking a hard way - I would not get started with such a raw and complex Hardware Box, if I don't want or can't do the tinkering to get it work. I'm too frustrated with Fenix that they can't provide the "Quartz Display Data", but they have very extensive API (you can even pull Circuit Breakers. And much "cleaner" compared to FBW and like "500% more" then FSLabs). FSUIPC is just the "middleware" here, it can only exchange the Data and Information both Parties allow. In my opinion, PFC are the ones which really let you down! For a 4-digit-priced Hardware Product - being it used or new, someone payed that Money. I would expect a better Support (both in User-Support and pre-done Integrations with Planes) and more technical functionality to just some nice GUI-dropdown in FSUIPC and listening for the Standard "Master Avionics Switch" SimVar (my Guess). That approach reaches exactly then the Limit when you have an complex external simulated Aircraft (like in this Case with the Fenix). Could you get the other Buttons to work? Is it just the turn-on Feature that is missing now? If so: ask PFC again what SimVar / Offset it is they are monitoring for that. I'll do the Script for you! 🙂 And who is following this Forum? Fenix? PFC? If so: @Fenix: give me more Data, that's a joke! @PFC: you can do much better for that Price.

*Version-bump* 🙂 The Plugin was ported to .NET 6 and x64 only. Be sure to read the Requirements and the Upgrade Procedure in the Readme! (It is NOT just dropping it in) The Plugin now uses the WASM/WAPI Module from FSUIPC7 on MSFS2020. With that: - The Lvar Access is now faster and more reliable (not reporting the last Lvar's Value for unknown/inaccessible Lvars) - Hvars are also available as an additional Action-/Command-Type - CalculatorCode can be now directly be run from the StreamDeck as Action-/Command-Type (can't really imagine a Use-Case for that, but it was possible so why not^^) This only affects / is only available with MSFS2020 / FSUIPC7.

What if you use a Lua-Script which polls the Battery Lvars every 250-500ms (see event.timer) if they are turned on and then send a Command to your Shack? (However that is done with PFC - that has to be answered by their Support). But yeah, I just hit a similiar Wall to have my FCU back on the StreamDeck ... "licensing issues blabla". 😐 Which is probably true (but which they probably did not understand in my Case): They did indeed license the ProSim-AR 320 Software on which they build up on (the Reason they can offer such a System-Complexity on a new Product). And this Software has indeed built-in Support to communicate with a range of Hardware-Manufacturers directly. So that is what they probably don't have licensed respectively have license issues with. But I never asked them to Support the StreamDeck (or my Plugin directly), I just wanted to read the "raw" Data from the FCU (Values, Dashed, Dot ... doesn't even need to be via FSUIPC). So things they already present visually in the Cockpit and in case of the Dot more or less already as Lvar. It's very frustrating ... I got a working FCU (or MCP) on every on my other Planes, there was always a way. As in this Case too ... I've "hacked" my way through and have my FCU at least basically working 😈 (Not as accurate, but working)

Uhoh okay ^^ But I can't teach you FSUIPC Basics and you have to know your Radio Shack is interfaced 😉 Discord - you got a PM 😉

🤦‍♂️ 🤦‍♂️ 🤦‍♂️ Thanks 😅

Uhm ... can it be that the Textfile/List with all the Standard Controls is missing is this release? Just reinstalled 7.3.6 again and it doesn't appear (all the PDFs are there though).

Hey Paul, so your Radio Shack uses FSUIPC to communicate with the Sim (in both directions)? I've found it rather easy with the Fenix, compared to the messy FBW to make a StreamDeck/PilotsDeck Profile for that. Which is more or less your Use-Case: an external Hardware which interfaces with FSUIPC to read from/write to the Sim (and therefor the Plane). The only thing I'm missing now is to read out the Quartz-Displays - But for COM and XPDR you can use the default FSUIPC Offsets (SimConnect Vars). Are you aware of these two KB-Articles? - https://kb.fenixsim.com/example-of-how-to-use-lvars - https://kb.fenixsim.com/useful-default-keybinds Some Functions are available directly via Standard-Controls (directly selectable in FSUIPC GUI) and for nearly everything else there are Lvars which can be read from or written to. For manipulating there are either FSUIPC Marcos (never used myself) or Lua-Scripts (called via LuaToggle / event.flag - the way I prefer). Here the Lua-Script I use for the Fenix: FNX320_AUTO.lua (the Functions could also be mapped via FSUIPC GUI as LuaToggle <scriptname> and as Parameter the event/flag number from the Script-File). It doesn't have all Controls in it since my "Hardware" can directly manipulate Lua-Values (via FSUIPC) and so the Script-File only is needed for some which require more Logic/Automation. But that's basically how you manipulate Buttons in the Cockpit and can read their State/Position. If you want we can look through an Example together? Regards, Daniel

Said and done - thanks! 🙂 So Events/Callbacks, Init, Config, Start - right? Like so: WASM.OnLogEntryReceived += OnVariableServiceLogEvent; WASM.OnVariableListChanged += OnVariableServiceListChanged; WASM.Init(System.Diagnostics.Process.GetCurrentProcess().MainWindowHandle); WASM.LVARUpdateFrequency = 0; WASM.LogLevel = LOGLEVEL.LOG_LEVEL_INFO; WASM.Start();

YEP! That works 😃 I can restart either FSUIPC or my Plugin and neither Crashes anymore! Although I only replaced the FSUIPC7 Executable - don't know where I would need the static Libraries. Since my Plugin is C#, I use Paul's C# Client which in Turn uses the dynamic WAPI Library (FSUIPC_WAPID.dll from the Utils-Directory). In addition my Plugin now sets the UpdateFrequency to 0 (but I've tested that before the Special-Build, that was not the Issue). Many thanks!!! 🙂

I can give it a try, sure! But I'm very unused to C/C++ and especially how I debug a library which is not part of the project 😕 Nope, I'm to spoiled from C#/.Net -.- After getting it finally somehow compiled, the Plugin is crashing now because "Unable to find an entry point named 'fsuipcw_isRunning' in DLL 'FSUIPC_WAPID.dll'. " 😕 Which is true - none of the source-File would contain such a function. I'm missing some kind of Info/Step here which I can't figure out myself. I wanted to give it a try with a quick & dirty try/catch Block and (and write the Exception to the log) around that specific area if that would yield any info.

Hey Paul! I wanted to bring your attention to this thread: There is also the question if and where the UpdateFrequency should be set. Any advice?

As simple and dumb as I said - I added another [WAPI] Section at the Bottom of the Ini to enable Logging completely unaware there was already one^^ So only the first was used and the second one was ignored. Typical Problem where the Root-Cause was in front of the Monitor 😄 Strange thing, for sure! 🤔 I can only do wild and uneducated guesses: Either dwdata, lvar_cdas or lvar_cdas at cdaId causes a Null-Pointer-Exception or the Critical/Mutex Section should also include those lines (because multiple Clients alter the Counter/Index which in turn generates a Null-Pointer/Out-of-Range Exception). *g* I can give it a try, sure! But I'm very unused to C/C++ and especially how I debug a library which is not part of the project 😕 Sure, I'll ask Paul! I do not set the Frequency to leave it at the default, since per his description in the Thread it defaults to 6Hz (the same in the WASM-Config). So I thought the Default is fine for me! Did not want to mess around with the settings 😅 But I can set it explicitively to zero 😉 Great! If you need anything more or any testing with special Builds, just drop me a line 🙂 Thanks & Cheers Daniel

Some Updates: - It seems to be dependent on which plane is loaded. I accidentally choose the FBW32N and FSUIPC7 did not crash (twice). - With the Default 747 I tested all the time it crashed again. - Found the Reason for the missing Messages in the FSUIPC7.log: I've added a second [WAPI] Section -.- Sorry! - Although I now forgot to re-enable Event-Logging. Will redo later ^^ - But: FSUIPC7 crashes at the same Point like my Plugin: after the "EVENT_LVARS_RECEIVED" Log-Message is received. - Compressed with 7-Zip, else it would be to big logexport-crashed.7z logexport-working.7z

Of course it does not show anything ... FSUIPC crashed, that is the Test-Case you requested ^^ It is a very hard crash - even the catch-Block in my Plugin is not able to catch any exception that would help 😕 Got the information about the "Access Violation" from the Debug Output from VS (debugging my Plugin). The Debugger itself also just stops and is not able to show the location. Please provide me with the exact Settings you want me to set in the FSUIPC7.ini - I did like I described in my Post earlier and that was described as per Advanced User Guide. But either that is not want you wanted or I configured it wrong. Uhm ... I don't know what you mean, I'm not aware that I enabled something like that in the first place 😮 I'm just starting it (IPCManager.cs#L73) and checking the IsRunning State (IPCManager.cs#L29). Only after WASM is ready (that is after VariableListChanged Event received) the Lvars are read (IPCManager.cs#L267 --> IPCValueWASM.cs#L18 - for every unique Lvar the User has configured and currently visible on the Deck) Here the Logs 🙂 Whenever you have time - it's no showstopper for normal usage and for developing the loading of new flight thankfully does not take that long in msfs (compared to p3d^^) logexport.zip

Yeah it was only the Test-Case that FSUIPC7 keeps running and the Plugin is restarted - you didn't mention wich one you prefer^^ I surely added something to the FSUIPC7.ini to enable it (see my previous Post), but I'm not sure if that enabled it xD Here the Logs when FSUIPC7 crashes! Steps: - Loaded MSFS via the FSUIPC Shortcut (Plugin is running) - Loaded a Flight - Stopped FSUIPC7 - Started FSUIPC7 => Crashed FSUIPC_WASM.log FSUIPC7.log PilotsDeck.log

Same Behavior with 7.3.5/0.5.9 😕 I've started MSFS/FSUIPC without the Plugin running and started it after the Flight was loaded. I hope the FSUIPC and WASM Logs are as expected? I've changed LogLevel to Debug in the FSUIPC_WASM.ini and added that to the FSUIPC7.ini: [WAPI] EnableWAPI=Yes LogLevel=Debug FSUIPC7.log PilotsDeck.log FSUIPC_WASM.log

Hi! I'm currently integrating the WASM Module in my StreamDeck Plugin/PilotsDeck via Paul's C# Client and it works great so far. But only if FSUIPC7 or my Plugin are not restarted when a Plane/Flight is loaded (no Problem in the Main Menu). When I restart my Plugin it will crash with a "Access Violation". When I exit FSUIPC the Plugin will load but FSUIPC7 will crash when I try to start it again. From what I can tell it happens when the WASM Module tries to load/setup the Lvars, because the last line I receive in my Plugin is "EVENT_LVARS_RECEIVED" (FSUIPC running, StreamDeck/Plugin restarted). The other way around (StreamDeck/Plugin running and FSUIPC restarted) the last line in the FSUIPC7.log is "Connected to MFSFS".

You're welcome, thank YOU for your Feedback 🙂

*bump* Some Moons and Versions have passed, we are now at 0.6.5: https://github.com/Fragtality/PilotsDeck/releases/tag/v0.6.5

Sorry but this Answer is confusing. So the Virtual Buttons are only really usable (e.g. assignable in the FSUIPC UI) with a registered Version. But basically with a free Version it is still possible to write to this Offset(s). How they are intended to be used is really simple: My StreamDeck Plugin writes to this Offset(s) to trigger the Buttons, so a User can have their Mappings/Bindings within FSUIPC (instead of directly assigning a Control/Lua/Macro via StreamDeck), if he/she prefers that.

Thanks

I would need to know if the "Virtual Buttons" (Offsets 29F0/3340) are usable with a free Version? Does that count as "access to Offsets" (=free) or "Joystick control facilities" (=registered)? So Offsets & Controls are "free", Lua is only available when registered. Correct? Therefor I'd assume Macros and Lvars are also only available with a registered Version (since using the same Offset), right?

Sorry for the late Answer, didn't get a Notification. I've send you the inis via PM. As reported, the problem somehow went away with a fresh OS/P3D Install and new/fresh Install of the newest FSUIPC Version (.13). Regarding your Answer on the three Configuration Parameters (LuaTrapKeyEvent, SetForegroundOnKeySend, KeyboardFocus): These are not existent within the new ini File (currently in use in the new/fresh Installation). But the strange thing is, I only added/altered these Parameters in the attempt to troubleshoot the old Installation (and therefore old ini-File)