Message to the dev team
I only asked to set Reticle_target_sensitive to true by default so do not blame me for this mess
Set Reticle_target_sensitive to true by default
Moderators: winston, another_commander
- pagroove
- ---- E L I T E ----
- Posts: 3035
- Joined: Wed Feb 21, 2007 11:52 pm
- Location: On a famous planet
I like the sprites idea! Why not sprites and scrollbars
EDIT: just abandoned the idea of sprites. Because its quite difficult to make good sprites and you introduce another layer of complexity to the game. A user then constantly has to look on the wiki which symbol is for example for the docking computer.
EDIT: just abandoned the idea of sprites. Because its quite difficult to make good sprites and you introduce another layer of complexity to the game. A user then constantly has to look on the wiki which symbol is for example for the docking computer.
For P.A. Groove's music check
https://soundcloud.com/p-a-groove
Famous Planets v 2.7. (for Povray)
https://bb.oolite.space/viewtopic.php?f=4&t=13709
https://soundcloud.com/p-a-groove
Famous Planets v 2.7. (for Povray)
https://bb.oolite.space/viewtopic.php?f=4&t=13709
How about a little text box below the HUD icons, where some suitable text (via an existing or new equipment key?) could display exactly what the currently selected icon actually is...
My OXPs via Boxspace or from my Wiki pages .
Thargoid TV
Dropbox Referral Link
Thargoid TV
Dropbox Referral Link
Good idea.Commander McLane wrote:Or, if a scroll bar is too much of a re-write, what about 'More -->' and 'Back -->' as on the F3- and F3-F3-screen? This funcionality already exists in the code, so probably it wouldn't be too tricky to adopt it for the F5-screen-family as well.
And about the HUD. I thought about sprites, because it is a fast way - I think. Handling strings is always slow and needs time. But HUDs are timecritical. And the dev team has optimized Oolite so now we have a very fast processed game and I don't want to lose this result again. So I thought about a 3-state image with a fixed resolution (to avoid scaling too) - installed, active, damaged.
To make it more complete. I have no bad feeling about changing the Hyperradio. It wouldn't be a big problem. It already uses one missionVariable and this variable could be used to detect if the device - even if it has a limited life span .-) - is installed or not. But on the other side I also want to know what I have installed/paid for. And if it's no more handled as equipment (and therefore not displayed) then I would lose the overview after a week or two - or after loading an other (and maybe long time not used) savedgame.
So we may need some feedback from the dev-team if something is in mind or already planned to get some kind of direction and if not then we need an consensus here on the board. It wouldn't make sense for me to change the Hyperradio now, and a few days/weeks later I have to change it again. Eric's way is in my eyes a very good way to avoid this problem for some types of 'pseudo-equipment', but I think it doesn't fit to a lot of EQs.