Talk:Redesigning the Replay System: Difference between revisions
Jump to navigation
Jump to search
m (merged from proposals) |
m (Switch to the {{forum url}} and {{forum link}} templates for all forum links.) |
||
| Line 7: | Line 7: | ||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27849.html | * http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27849.html | ||
* http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28332.html | * http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28332.html | ||
* | * {{forum url|hilit=generic+protocol|p=26459}} | ||
= Replay Discussions from the forums = | = Replay Discussions from the forums = | ||
questions, feature requests and suggestions: | questions, feature requests and suggestions: | ||
* | * {{forum url|hilit=replay|p=61025}} | ||
* {{forum url|hilit=replay|p=53640}} | |||
* {{forum url|hilit=replay|p=52818}} | |||
* {{forum url|hilit=replay|p=51907}} | |||
* {{forum url|hilit=replay|p=49780}} | |||
* {{forum url|hilit=replay|p=46028}} | |||
* {{forum url|hilit=replay|p=45947}} | |||
* {{forum url|hilit=replay|p=45009}} | |||
* {{forum url|hilit=replay|p=40479}} | |||
* {{forum url|hilit=replay|p=36949}} | |||
* {{forum url|hilit=replay|p=36069}} | |||
* {{forum url|hilit=replay|p=28982}} | |||
* {{forum url|hilit=replay|p=27109}} | |||
* {{forum url|hilit=replay|p=15804}} | |||
* {{forum url|hilit=replay|p=65878}} | |||
= Suggested Approaches = | = Suggested Approaches = | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17035.html re-implementing replay on top of the generic protocol facility] | * [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17035.html re-implementing replay on top of the generic protocol facility] | ||
* | * {{forum link|p=12549|text=Using ARINC 429 for logging flight data}} | ||
* from a conceptual point of view, the replay system has the same requirements as the multiplayer system: it has to work with arbitrary aircraft/vehicles and arbitrary combinations of properties (differing among aircraft), thus a subscription based approach is most promising, as it has been frequently suggested and favored in multiplayer related discussions | * from a conceptual point of view, the replay system has the same requirements as the multiplayer system: it has to work with arbitrary aircraft/vehicles and arbitrary combinations of properties (differing among aircraft), thus a subscription based approach is most promising, as it has been frequently suggested and favored in multiplayer related discussions | ||
= Related Discussions = | = Related Discussions = | ||
* | * {{forum url|t=6328}} | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21356.html Saving Instant Replay to a File] | * [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21356.html Saving Instant Replay to a File] | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg19471.html Replay mode improvement suggestion...] | * [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg19471.html Replay mode improvement suggestion...] | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15655.html BUG when replay with generic protocol] | * [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15655.html BUG when replay with generic protocol] | ||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22799.html | * http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22799.html | ||
* | * {{forum link|p=40479|text=Output to file using ACMS.XML}} | ||
= Issues = | = Issues = | ||
* | * {{forum link|p=36949|text=Lag playback}} | ||
* | * {{forum url|p=28982}} | ||
* | * {{forum link|p=27109|text=Instant Replay of flight sequence issues}} | ||
* | * {{forum link|p=15789|text=Helicopter rotor in replays...}} | ||
* | * {{forum url|p=36069}} (unconfirmed) | ||
= Feature Requests = | = Feature Requests = | ||
* | * {{forum link|t=6284|text=Flight Path Trace}} | ||
* | * {{forum link|t=6290|text=flight path trace in autopilot mode}} | ||
* http://sourceforge.net/tracker/index.php?func=detail&aid=1848796&group_id=9456&atid=359456 | * http://sourceforge.net/tracker/index.php?func=detail&aid=1848796&group_id=9456&atid=359456 | ||
* http://fgfs.i-net.hu/modules/fgtracker | * http://fgfs.i-net.hu/modules/fgtracker | ||
| Line 62: | Line 62: | ||
* Relevant properties (or property branches) could be selected/ignored, similar to how loading/saving flights and simulator resets should provide fine-grained control over which state is going to be used or not | * Relevant properties (or property branches) could be selected/ignored, similar to how loading/saving flights and simulator resets should provide fine-grained control over which state is going to be used or not | ||
* If this approach is pursued, properties could be stored using unique property IDs, as is already done for multiplayer purposes | * If this approach is pursued, properties could be stored using unique property IDs, as is already done for multiplayer purposes | ||
* Similarly, the recording resolution should probably be runtime configurable | * Similarly, the recording resolution should probably be runtime configurable {{forum link|p=49780}} | ||
* it would probably be a good idea to extend the generic I/O protocol in order to re-implement the replay system on top of it | * it would probably be a good idea to extend the generic I/O protocol in order to re-implement the replay system on top of it | ||
* Having a way to optional delta-encode blobs of saved properties, would probably help reduce file size | * Having a way to optional delta-encode blobs of saved properties, would probably help reduce file size | ||
Latest revision as of 22:07, 7 June 2019
Related
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26123.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg12621.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17034.html (serialization)
- Replay mode improvement suggestion...
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15655.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27849.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28332.html
- https://forum.flightgear.org/viewtopic.php?p=26459&hilit=generic+protocol#p26459
Replay Discussions from the forums
questions, feature requests and suggestions:
- https://forum.flightgear.org/viewtopic.php?p=61025&hilit=replay#p61025
- https://forum.flightgear.org/viewtopic.php?p=53640&hilit=replay#p53640
- https://forum.flightgear.org/viewtopic.php?p=52818&hilit=replay#p52818
- https://forum.flightgear.org/viewtopic.php?p=51907&hilit=replay#p51907
- https://forum.flightgear.org/viewtopic.php?p=49780&hilit=replay#p49780
- https://forum.flightgear.org/viewtopic.php?p=46028&hilit=replay#p46028
- https://forum.flightgear.org/viewtopic.php?p=45947&hilit=replay#p45947
- https://forum.flightgear.org/viewtopic.php?p=45009&hilit=replay#p45009
- https://forum.flightgear.org/viewtopic.php?p=40479&hilit=replay#p40479
- https://forum.flightgear.org/viewtopic.php?p=36949&hilit=replay#p36949
- https://forum.flightgear.org/viewtopic.php?p=36069&hilit=replay#p36069
- https://forum.flightgear.org/viewtopic.php?p=28982&hilit=replay#p28982
- https://forum.flightgear.org/viewtopic.php?p=27109&hilit=replay#p27109
- https://forum.flightgear.org/viewtopic.php?p=15804&hilit=replay#p15804
- https://forum.flightgear.org/viewtopic.php?p=65878&hilit=replay#p65878
Suggested Approaches
- re-implementing replay on top of the generic protocol facility
- Using ARINC 429 for logging flight data
- from a conceptual point of view, the replay system has the same requirements as the multiplayer system: it has to work with arbitrary aircraft/vehicles and arbitrary combinations of properties (differing among aircraft), thus a subscription based approach is most promising, as it has been frequently suggested and favored in multiplayer related discussions
Related Discussions
- https://forum.flightgear.org/viewtopic.php?t=6328
- Saving Instant Replay to a File
- Replay mode improvement suggestion...
- BUG when replay with generic protocol
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22799.html
- Output to file using ACMS.XML
Issues
- Lag playback
- https://forum.flightgear.org/viewtopic.php?p=28982#p28982
- Instant Replay of flight sequence issues
- Helicopter rotor in replays...
- https://forum.flightgear.org/viewtopic.php?p=36069#p36069 (unconfirmed)
Feature Requests
- Flight Path Trace
- flight path trace in autopilot mode
- http://sourceforge.net/tracker/index.php?func=detail&aid=1848796&group_id=9456&atid=359456
- http://fgfs.i-net.hu/modules/fgtracker
- http://pigeond.net/photos/flightgear/fgmap/
- http://www.flightgear.org/Projects/SynthVision/
Misc
- The replay system would ideally be subscription based, so that individual aircraft could expose relevant properties/branches that would then be automatically tracked by the Replay System
- This would ensure that aircraft developers could explicitly configure certain properties to be tracked or not
- Relevant properties (or property branches) could be selected/ignored, similar to how loading/saving flights and simulator resets should provide fine-grained control over which state is going to be used or not
- If this approach is pursued, properties could be stored using unique property IDs, as is already done for multiplayer purposes
- Similarly, the recording resolution should probably be runtime configurable [1]
- it would probably be a good idea to extend the generic I/O protocol in order to re-implement the replay system on top of it
- Having a way to optional delta-encode blobs of saved properties, would probably help reduce file size