Skip to content

Merge OSD file format V2 updates #422

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

Merged
merged 6 commits into from
May 21, 2024
Merged

Merge OSD file format V2 updates #422

merged 6 commits into from
May 21, 2024

Conversation

benlumley
Copy link
Collaborator

The comprises the changes to the OSD overlay tool from last week; we'd like to get MSP-OSD v0.12.2 released; which breaks compatibility with the OSD overlay tool that is live currently. So we'd like to get this released.

This also includes a change/fix from j005u; have checked in with him on discord...

"it may or may not help with step 5 stability, but in any case it's harmless. so yeah, include it."

The one issue; I added a new translation string; which we won't have translations for. But we figure this working with a missing translation trumps this not working and not missing translations.

stylesuxx and others added 5 commits November 27, 2023 22:53
Fixed missing sync in exploit step 5
Switch to using new png fonts + .osd file format v2 support:

- Use PNG font files instead of the old bin format
- Only 2 fonts now; one for sd + one for hd, rather than separate pages
- But the PNG can have equivalent of 4 pages; so BF 4.5 colour is supported
- OSD v2 support; which uses a 4 char string (BTFL/INAV etc) as the FC identifier. Can still handle v1 files too
- Font files now optional; it will use the FC variant to load defaults from the msp-osd repo
@benlumley benlumley requested a review from stylesuxx May 20, 2024 09:23
@benlumley
Copy link
Collaborator Author

Just saw #421 after opening this - I'll run through that process later on!

@stylesuxx
Copy link
Collaborator

stylesuxx commented May 20, 2024

That step 5 fix is already in develop. I'd change the base branch for this PR to go against develop and things should be fine. #421 is just a checklist for the new release.

Edit: Ah, this PR is just to merge into master. I'll double check the state of the translations and prepare a new release later today.

Spanish & Italian update
@benlumley
Copy link
Collaborator Author

Anything I can do to push this along / make your life easier ?

Do shout!

@stylesuxx stylesuxx merged commit 168af56 into master May 21, 2024
3 checks passed
@stylesuxx
Copy link
Collaborator

@benlumley Thank you - I just deployed it, could you do me a favor and check on prod that everything is working as it is supposed to?

@benlumley
Copy link
Collaborator Author

Looks good!

@stylesuxx
Copy link
Collaborator

Whoop, whoop - thanks for checking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants