I’m hoping I can get help with what seems to be a crash/disconnect issue I’m running into. I’m going to upload my Elgato and Pilotsdeck logs, as well as the small profile I’m using.
I’m using version 0.8.10.0 of PilotsDeck
The disconnect seems to be related to Display Gauges. I have 2 that I’m testing now, and both of them will cause the disconnect. The DU BRIGHT (display brightness) one seems to cause it almost instantly.
So what happens is… with a new startup of MSFS2024, first flight. Buttons are all working correctly, and turning the Display Gauge works initially, then stops working. All the buttons that previously worked then stop working. This is in the default 737 Max aircraft.
Also in the Developer UI, under the monitor tab I get a constant stream talking about ‘No Hash found for InputEvent ‘FCC_APP_TOGGLE”’, which I’ve checked and is not contained anywhere in the profile, so not sure if it’s related or not.
You have more than that one ‘No Hash found’ Message in the Log. There are many many B-Var/InputEvents configured which apparently are not usable by SimConnect Clients. You are aware of that? => BVAR
You can try if the Dev-Version does anything for you: PilotsDeck-Installer-latest.exe
But using InputEvents not accessible via SimConnect is one way or the other an Issue - please use only those in the InputEvents File. I don’t know how the Sim and/or Plugin reacts when it is constantly tried to subscribe InputEvents which don’t exist.
And other Buttons work? I wouldn’t be aware that B-Vars/InputEvents are triggerable via Calculator Code … but I guess one’s never stop learning
But generally I’d recommend to stay away from Calculator Code as it has the longest Execution Time - which doesn’t make it a great Choice for Commands in quick succession (i.e. Dials) or rapidly changing Values.
BVAR Syntax with two InputEvents -or- Composite Action with 2 Commands
If I just use the command address LANDING_PARKING_BRAKE, then the Current Value shows correctly, and the button will turn the brake on, but not off. But if I use what’s shown in the screen shot above it flashes an error.
Maybe. No, don’t have the Aircraft. Yes. Don’t think so.
You have to differentiate between Calculator/RPN Code and Input-Events/B-Vars. Looking at a Calculator Code and just extracting the Variable Name for a Input-Event/B-Var Command doesn’t work out when that Input-Event isn’t accessible via SimConnect (as already mentioned and linked).
I stated I’m not using Calculator Events, even posted a screenshot. The Parking brake var is clearly in the Detected B-Vars file (I assume this is what you mean when you reference the ‘Input-Events’ file.
The 737 Max is a default aircraft, so if you don’t have it what sim are you actually using?
For anyone else struggling I did manage to make some progress by installing the Pilots-Deck-Installer-latests.exe version. At least now some of the functionality is generally behaving the way you would expect, and all the errors have gone away in the Monitor/Logs.
Fraggie84, can you recommend a active forum where I might be able to get help from a community of users of PilotsDeck? I have gotten some help from one of the profile creators on flightsim.to but I don’t want to keep bugging him. Thanks.
What your Screenshots showed: you had looked up a Calculator-Codes Expression on Hubhop and then just used the Variable Name in there in the Plugin.
You assuming what File I meant only shows you still hadn’t looked in the linked Part in the Readme.
The “long press” feature is possible in Dial_Up but not in Dial_Down. Obviously, the Command doesn’t trigger until the button is released, even if the time limit has been exceeded. You have to guess approximately when to release it. How can I get a feedback when the time limit has been exceeded ?
Unfortunately it isn’t possible to get such a Feedback - the Plugin also only knows if (and what) Limit was exceeded when the Up-Event was received by the StreamDeck. So basically it knows the roughly the same Time as you do.
The whole Idea to make the Timespan configurable with 0.8.x (Composite Actions only) was that Users can better finetune the timing to their “feel”. (It used to be fixed at 600ms - now 500 on Classic Actions)
So it is more a matter of fine-tuning to get the Value right for you
Most certainly not - as it doesn’t make conceptually Sense to me. The Timespan how long a Button/Dial was down (pressed) ends when it is released. Therefore it is configured at the Up Event.
I do get the Benefit behind the Idea of having some kind of Feedback if the configured Span is exceeded. Especially in Scenarios where there multiple Commands with different Spans. But I currently don’t know if this is possible within a reasonable Amount of Work. The whole Structure/Architecture is purely Event-Driven - when a Event from the StreamDeck comes in, it is taken from the Queue gets evaluated against the current State and the resulting Command that needs to be triggered is placed in another Queue.
So there isn’t really some kind of “monitoring” Instance that would know. And the configured Commands have no Reference to each other (they don’t know what came before or should come after).
Or long story short: It is challenging, since there would be a lot of Prerequisites to create first just to make this Check/Test and fire some kind of Feedback (something that would also have to be implemented first)
I recently bought the Piston Dukes and set up a small Streamdeck Profile to operate Prop and Mixture Levers (as I don’t have enough levers on my setup … :D)
Mixture Control works fine, but I’m struggeling with the Prop Controls!
I want to create a simple button (well, acutally 2 for left + right prop…) to bring my Prop to FEATHER position. I tried all possible comands, but nothing works. I try to use the K-VAR “PROP_PITCH_SET” for the respective engine, but I can’t enter negative values after the command…
For exampe, I also created a button to bring the props to zero position using
“PROP_PITCH1/2_SET:0” which works perfect.
To bring the props to feather I would asume to use “PROP_PITCH1_SET:-16383“ (also found this one on Mobiflight’s Hubhop). But this gives me a syntax error warning from the plugin and it also doesn’t work in MSFS2024…
Are you sure about that Value?
The SDK says the Range is positive: Aircraft Engine Events
(Generally I didn’t came across any K-Event/Var accepting negative Values - hence the Syntax-Check only Checks for positive Numbers)
Great that to hear that there is a Workaround - since there wouldn’t be any Fix to allow negative Values.
Although both SimConnect_TransmitClientEvent Functions are documented as taking DWORDs (so theoretically signed/negative Values) they are implemented in the SDK/DLL as UINT (so only allows positive Numbers)
