![]() To actually replay even just a single aircraft specific animation in FlightGear, you would have to write a python script that 1) loads the aircraft, 2) looks up the 3D objects, 3) maps the properties to animations - and completely ignore anything related to scenery, because it's typically just aircraft specific stuff that is recorded. So there's really just numbers stored there, nothing visual that would make sense to visually re-interpret outside a flight simulator environment like FlightGear. FlightGear's I/O means are generally pretty simple and flexible, so it would probably be much more work to reverse engineer the serialization scheme used by the fgtape format - simply because you can configure your own 'protocol' and do with the data whatever you want, without having to use any workarounds at all. Data is transmitted via UDP network packets to a running instance of FlightGear. things like altitude, longitude, latitude - but also engine settings, flap settings, gear status etc. The FlightGear flight simulator interface included with the blockset is a unidirectional transmission link from the Simulink interface to FlightGear using the FlightGear published netfdm binary data exchange protocol. Imagine those files to be containers for binary FlightGear properties, i.e. What FlightGear is writing to those files is not actual "visual" stuff at all, it's just "gibberish" in the sense of properties that are only meaningful to FlightGear itself, and its features, most properties are in fact aircraft specific. Unless that is something that you are interested, willing and capable to do, I'd just leave it at that. There's no reasonable way to visually "replay" those files outside FlightGear, short of rewriting FlightGear itself, or extending another flight simulator to partially re-interpret certain values. There's really no need to continue this discussion at all - all the responses given so far were rather exact, detailed and 100% correct. Your favorite flight simulator is not yet supported Use our comprehensive technical documentation to create your own data exporter. Here is some sample output: Time,Rudder,Ailerons 6522,0.000000,0.000000 7668,-0.000000,0.000000 8702,-0.000000,0.000000 9705,-0.000000,0.000000 10784,-0.000000,0. Thanks, all!Īgain, the format is basically seralized FlightGear properties, please see $FG_ROOT/Docs/flightrecorder.README - these are all just "numbers", the format is determined by FlightGear, and these numbers do not mean ANYTHING outside FlightGear, and even inside FlightGear it's really just the flight recorder subsystem that is able to open/process those files, read in the numbers and map them to the corresponding FlightGear properties - which in turn allows things to be animated/replayed over time JUST VIA FlightGear. For this reason a real-time pacer block 22 has been included in the model, as visible in the bottom part of the Simulink scheme. I don't mean that it is a video format, but rather could I import it into, say, Blender, and then export it as something else? It's way too optimistic, I know. I opened it in Notepad ++, but it was just rubbish. HelldiverSquadron wrote in Mon 7:54 pm:Seemed like a binary trait. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |