Integrating Blacksquare HVAR Remote Failure Triggers On The Pilot Edge Network
-
Hey Nick, I was hoping you might be able to comment on an interesting development over at the Pilot Edge Network. ( https://www.pilotedge.net/ ) The Devs over there have implemented a live flight tracker ( https://tracker.pilotedge.net/flights ) that also allows failures to be triggered by an authorized remote user on a current flight/aircraft. Currently the failure trigger system has only been implemented for X-Plane users, but the developer is considering the idea of expanding that feature to MSFS users as well. Your Blacksquare addons are the most popular MSFS GA addons on the PE network, so naturally, I was thinking of how amazing it would be to implement your custom failure model in to future development over at PE. Do you think this would work? And.. Is there a way via sim connect, HVARS, or other variables can be read remotely to identify if the aircraft on the network is a Blacksquare addon and which model addon it is?
-
What fun! I have great respect for the PilotEdge folks. Please pass along my best wishes, if you are in touch. In reverse order, my aircraft should be easily detectible by the same means used for 3rd party career applications, which just look at the aircraft demographic information in aircraft.cfg. Both ui_manufacturer, and ui_createdby should be "Black Square" for all my aircraft, and he model can be read from ui_type. I already support the triggering of failures remotely via HTML Events, which is documented in my manuals. The trouble right now is reading the state of those failures, since that would require updating hundreds of L:Vars. If no feedback is required, then it should be immediately possible. Let me know if you have any more questions! I would be happy to help.
-
What fun! I have great respect for the PilotEdge folks. Please pass along my best wishes, if you are in touch. In reverse order, my aircraft should be easily detectible by the same means used for 3rd party career applications, which just look at the aircraft demographic information in aircraft.cfg. Both ui_manufacturer, and ui_createdby should be "Black Square" for all my aircraft, and he model can be read from ui_type. I already support the triggering of failures remotely via HTML Events, which is documented in my manuals. The trouble right now is reading the state of those failures, since that would require updating hundreds of L:Vars. If no feedback is required, then it should be immediately possible. Let me know if you have any more questions! I would be happy to help.
@Black-Square Thanks Nick!
