Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility!
Overview
I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports.
What’s New
- Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules.
- Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically.
- Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs.
- Added safeguards to flight event detection to make analysis more reliable.
- Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :)
Challenges
Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible.
Next Steps
- Continue refining the FlightScope UI and overall user experience.
- Add support for more telemetry formats.
- Expand flight analysis and visualization tools.
- Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.)
FlightScope is now fully documented on GitHub:
https://github.com/zombieking1555/FlightScope
devlog 4 in the bag, now that’s some type stuff. And check this demo:
Comments 1
Nice job man!
Keep up the good work
Sign in to join the conversation.