JB's Dynamic HUD

Showing Contraster Underlay

Showing Critical Condition/low energy

Overview

• Deliberately designed for 1680px x 1050px
• Combined compass/pitch/roll/precision flying indicator (inner circle turns green when on) - sized to correlate with planet/sun disks
• Dynamic: changes for docking, critical condition, red, yellow and green conditions, use of a certain device...
• Contrasting underlay to improve visibility with sun glare

Detail

This HUD switches modes based on Alert Condition, Ship Energy, and Cloaking Status.

Modes

• Docked: Targeting Disk and Panel Contraster Underlay are turned off. Oolite turns off the crosshairs by default.

• Condition Green, Yellow, Red: Crosshairs change color to green, yellow, or red.

• Critical Condition: Crosshairs are forced to red, the screen takes on a red glow at the edges; when energy is at a severely low level. Crosshairs will change to current alert condition after energy recovers some. After more energy recovery, red glow disappears.

• Certain Device: Crosshairs turn blue, the screen takes on a blue glow at the edges. When the device is turned off

OR it shuts itself off from energy depletion, crosshairs reflect current alert condition.

TAF Reset

TAF_Reset oxp isn't needed with this, it's functions are built-in. TAF reset function kicks in when docked, Witching to a new system, and when Condition Red. Unless you use time acceleration, you won't notice.

Dark Arts details

HUD plists:

• JBHUDDCK.plist, *hud.plist; Docked HUD
• JBHUDGRN.plist; Condition Green
• JBHUDYEL.plist; Condition Yellow
• JBHUDRED.plist; Condition Red
• JBHUDCRT.plist; Critical Condition
• JBHUDCLK.plist; Certain device is active

Images:

• disk.png; Targeting Disk / target contraster (128x128).
• panel.png; Instrument Panel underlay / contraster (1463x229).
• CRITICAL.png; "red glow" for Critical Condition (768x480).
• CLOAKED.png; "blue glow" (768x480).

• An exact copy of the Docked Hud is present; but renamed to hud.oxp

On my system this forces Oolite to START-UP with the Docked Hud (otherwise you would have to launch from the station to see the new HUDs).

It might malfunction (along with possibly other HUD functions) if other HUDs are installed.

Adjustments for Monitor Size

This HUD is optimized for a 1680 x 1050 widescreen monitor. You will probably have to tweak the coordinates, heights, and widths (including images) for your individual resolution (unless yours is 1680x1050, or possibly any WS with an aspect of 1.6).

This might help: Even though my native resolution is 1680 x 1050, and I am running Oolite full screen at the 1680 x 1050 setting, the COORDINATES in the HUD PLISTS are in a 768 x 480 frame of reference. The aspects are both the same; 1680/1050 = 1.6, 768/480 = 1.6

To illustrate: Even at 1680 x 1050, if I wanted to put a 1-pixel object at the upper left corner, the x coord would be -384 (768 wide = -384 to +384), NOT -840 (1680 wide = -840 to +840).

The y coord ALWAYS seems to be in a -240 to +240 frame of reference. It seems that the Oolite core programming "works as if" it is a 640x480 screen, and then if the resolution is set to some widescreen format, makes adjustments via the * x coordinate axis* to match the specified screen aspect.

You can experiment and come up with conversion factors (that is what I did for other HUDs, and used a programmable calculator to make it easy).

You will probably need to tweak the x coords, heights, and widths. POSSIBLY the y coords.

You can alter the alpha setting for the Critical/Deviced "fog at the edge of the screen" (glows), to change the transparency and make it "thinner" or "thicker".

For the critical condition/red glow; edit JBHUDCRT and change the alpha for the image CRITICAL.png from the default 0.20; increase this to make the glow "thicker".

For the deviced/blue glow; edit JBHUDCLK and change the alpha for the image CLOAKED.png from the default 0.20; increase this to make the glow "thicker".

Credits

• Thargoid, Killer Wolf, for the generic Dynamic HUD script.
• Killer Wolf, Wyvern, for releasing their Dynamic HUDS; I studied these and learned from them.
• Kaks for providing advice in the Oolite Forum on how to work the device-sensing.
• I've arbitrarily assigned the version number 1.02 to the script.

License

• Author: JeffBTX
• License: This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Download

• Box.com

Links

• Release BB Thread (2010)
• Development BB Thread] (2010)
• JeffBTX also helped with Coluber Pitviper & SWHUDDAI
• Jeff BTX's sounds project (2010)