So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights.
This video demonstrates the results: https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://youtu.be/50J-gjkgJxE (pick your poison)
To be perfectly clear: I am aware that Ace Combat is not a "flight sim", not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see if I can make it. This may be hard to believe but chipping rocks together until the computer does what I want is "quality time" for me ๐ค
You may have noticed that I'm a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.
This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for space and not for flight sim. This is also why I sometimes talk about "ships" or "docked". This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.
