You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fly your ship to the nearest star or planet with a bright enough surface and orient the ship so that the text on the HUD is over the star/bright surface.
My pioneer version (and OS):
Visible on all OSes and in latest release of Pioneer 2020-02-03
Assignees
I've pre-assigned it to people who might be most interested/involved in fixing it... 'cos I can 😝
Feel free to re-assign if not appropriate.
Previous issues and fixes
Also see very old PR #325 which was to fix issue #39
So we've actually regressed slightly in this area.
The text was updated successfully, but these errors were encountered:
Observed behaviour
The white text is almost unreadable
![1](https://user-images.githubusercontent.com/825083/76142178-0deebd00-6063-11ea-8f7d-abeea2227cd5.png)
Expected behaviour
The the text has a drop shadow or outline rendered to distinguish it from the background
![HCjVKx4](https://user-images.githubusercontent.com/825083/76142201-41314c00-6063-11ea-8b88-244436481b2e.png)
There are a number of open issues and alternative options of Dear IMGUI that might help. Using a drop shadow or signed distance field font rendering to provide contrasting backgrounds for text.
ocornut/imgui#745
ocornut/imgui#2965
signed distance field builder https://gist.github.com/Flix01/254005101903fe1bc22fe0b9f3ed3931
SDF vs Freetype discussion etc https://community.khronos.org/t/font-rendering-freetype-vs-signed-distance-field/103929
Steps to reproduce
Fly your ship to the nearest star or planet with a bright enough surface and orient the ship so that the text on the HUD is over the star/bright surface.
My pioneer version (and OS):
Visible on all OSes and in latest release of Pioneer 2020-02-03
Assignees
I've pre-assigned it to people who might be most interested/involved in fixing it... 'cos I can 😝
Feel free to re-assign if not appropriate.
Previous issues and fixes
Also see very old PR #325 which was to fix issue #39
So we've actually regressed slightly in this area.
The text was updated successfully, but these errors were encountered: