-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add version number to OSD #6328
Add version number to OSD #6328
Comments
Could just be added to the Arming screen, avoid taking up room on the flight display. |
That’s an option. But also, it would only take up room on the display if you allow it to. Just having it on the arming screen would mean you can’t show it along with your PIDs. Also, when I envisioned it, I actually wanted it there for the whole flight, so that it is visible in wherever you edit the video. I agree that it would be a good addition to the arming stats. Nobody really ever sees the boot screen. But I would still like to see it as an optional OSD element also. |
Its already on the arming screen. |
Just Position (Lat, Lon and Plus Code) date and time on mine. No version info. |
You are correct - its engrained on my brain from the startup sequence |
Current Behavior
Currently, this does not exist..
Desired Behavior
Select Version from a list in the OSD tab. Position it where you want it. The firmware will show it's version number in the OSD, where you position it.
Suggested Solution
Add an OSD item to the firmware, and implement it in the configurator
Who does this impact? Who is this for?
My initial thoughts were that this would be a useful tool for content creators. Having the version number visible would make it easier to keep track of the version used when making the specific video.
However, then I went on to believe it could also benefit tuners. If you have a specific tuning OSD layout, adding the version number here would also make it easier to keep track.
Finally, I thought it may be beneficial to new iNav pilots, as most use the configurator version number when talking about problems. This would make the firmware version number more prominent. However, I also have an idea for the configurator that may help this last point too.
The text was updated successfully, but these errors were encountered: