Skip to content
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

HUD home position constraint #8838

Open
rts18 opened this issue Mar 1, 2023 · 4 comments
Open

HUD home position constraint #8838

rts18 opened this issue Mar 1, 2023 · 4 comments
Labels

Comments

@rts18
Copy link

rts18 commented Mar 1, 2023

I was testing @MrD-RC's new ESP32 radar updates. Really nice work !!
When I ventured out to test the rest of the HUD features as shown here.
radar

I stumbled across one that is not found in the GUI. Only the CLI. And doesn't require any of the above to be selected.
osd_hud_homepoint = ON
It allows the home point to be displayed on the HUD, with the distance from home being displayed below it.
hud home

Now for the problem. It isn't constrained by osd_hud_margin_h as the other radar HUD functions are. It will move all the way to the edges of the screen and merge with the characters position there.
It only appears to function if the crosshair is activated. Which is disappointing. Because it would be optimal if it could function independently of the ESP32 radar. So both can be used on alternate OSD screens and not clutter up the same screen.

@b14ckyy
Copy link
Collaborator

b14ckyy commented Mar 22, 2024

OK this covers basically 3 topics.

  • I agree that its time that we have HUD settings in the OSD setup tab. Will look into that (maybe you can open that as a short request in the configurator repo so we can keep track of that)
  • the HUD margin seems to be a bug. Will add the label.
  • The crosshair dependency is there because the crosshair is the reference point. I wonder if the HUD elements could be made part of the OSD layout settings in the future to change them dynamically. But for that we use the linked ticket.

@rts18
Copy link
Author

rts18 commented Mar 23, 2024

The crosshair dependency is there because the crosshair is the reference point. I wonder if the HUD elements could be made part of the OSD layout settings in the future to change them dynamically. But for that we use the linked ticket.

@b14ckyy
@mmosca Attempted to resolve this issue with the release of FormationFlight.
This would allow us to place FormationFlight on Alt1, HUD on Alt2 and Home radar on Alt3 OSD. Without them all clashing together on every OSD screen where a crosshair is placed.
However, it doesn't appear to have moved forward in a while. It would be very useful indeed.

iNavFlight/inav-configurator#1812
#9199

@mmosca
Copy link
Collaborator

mmosca commented Mar 24, 2024

I may revisit this in 8.0

Right now we are in the stage where we are talking about our grievances with the configurator and what we could do to improve it, if motivation doesn't tank when we touch the javascript code, there may be some room for changing this

@rts18
Copy link
Author

rts18 commented Mar 26, 2024

@mmosca Thank you

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

No branches or pull requests

3 participants