[Release] AlmostAlmostDefault HUD 1.1.4

[spara]

What's that in the bottom left corner of your 2nd picture?
Some sort of alternate main station?

It's the fabled Griff Industries Icosahedron Station - available from the ZGrOovy spaceyard.

Tetrahedron...

[Tricky]

What's that in the bottom left corner of your 2nd picture?
Some sort of alternate main station?

It's the fabled Griff Industries Icosahedron Station - available from the ZGrOovy spaceyard.

Tetrahedron...

Icosahedron has a lot more sides, plus it still is a fabled station that Griff has been promising.

[Cody]

Icosahedron has a lot more sides, plus it still is a fabled station that Griff has been promising.

The Griff Ico is on its way, though.

[spara]

New version is up. The link in the first post is updated.

* bug fix pointed by Wildeblood
* small adjustment of the message_log
* compatibility fix for sniper sight and other hud borrowing OXPs

If you are using this hud, you should update it for the bug fix.

[Rese249er]

A note for those who prefer the witchpoint-planet unit and the change to the unit for each system; a separate script.js file in another OXP folder with the following code -

Code: Select all

this.shipExitedWitchspace = function()
{
     	missionVariables.aadHudUnit = Vector3D(0,0,0).distanceTo(system.mainPlanet);
}

- will do this. I discovered this after thinking on how to get the desired tweak with as little modification of the original script.js file. No modification at all works well.

[spara]

There will at least be one more update after I have carefully gone through the script trying to make it a bit more lightweight. I will also include some user options to choose the basis of the distance calculation (planet-sun or planet-wp), the unit (OU, AU, km, clicks or what ever) and an option to choose the permanency of the unit.

[Wildeblood]

A note for those who prefer the witchpoint-planet unit and the change to the unit for each system; a separate script.js file in another OXP folder with the following code -

Code: Select all

this.shipExitedWitchspace = function()
{
     	missionVariables.aadHudUnit = Vector3D(0,0,0).distanceTo(system.mainPlanet);
}

- will do this. I discovered this after thinking on how to get the desired tweak with as little modification of the original script.js file. No modification at all works well.

That's very clever, but it won't work properly with the latest version. Spara's script isn't using missionVariables.aadHudUnit directly, and is only checking it once at start-up. So it will update the unit periodically - each time you load a saved game - but not in every system. You need to add two things: an update to the variable actually used, and a check that mainPlanet actually exists.

Code: Select all

this.name               = "AadHUD Tweak";
this.version            = "2";

this.shipExitedWitchspace = function()
{
   if (system.mainPlanet)
   {
     	missionVariables.aadHudUnit = Vector3D(0,0,0).distanceTo(system.mainPlanet);
     	worldScripts["AadHUD"].ostronomicalUnit = missionVariables.aadHudUnit;
   }
}

[Commander McLane]

And again,

Code: Select all

this.name               = "AadHUD Tweak";
this.version            = "2";

this.shipExitedWitchspace = function()
{
   if (system.mainPlanet)
   {
     	missionVariables.aadHudUnit = system.mainPlanet.position.z;
     	worldScripts["AadHUD"].ostronomicalUnit = missionVariables.aadHudUnit;
   }
}

or

Code: Select all

this.name               = "AadHUD Tweak";
this.version            = "2";

this.shipExitedWitchspace = function()
{
   if (system.mainPlanet)
   {
     	missionVariables.aadHudUnit = system.mainPlanet.position.magnitude();
     	worldScripts["AadHUD"].ostronomicalUnit = missionVariables.aadHudUnit;
   }
}

would do the same thing. Whichever you prefer. But no need to set up a new vector.

[Eric Walch]

Or, when comparing the distance with the zero vector:

Code: Select all

missionVariables.aadHudUnit = system.mainPlanet.position.magnitude()

But, as for the main planet the x and y position are zero, above code by McLane it even more lean.

Edit: Ninjaed By McLane who added a second example

[spara]

A new version is up.

* Some code tidying and small tweaks. Thanks to all who have suggested changes.
* Rese249er and others who want to change the distance unit shown, distance unit basis and permanency can now do it easily by modifying the variables in the script.js file.

[Rese249er]

Well, the tweak is now obsolete. Thanks for v0.7, Spara!

[spara]

I adapted a few tweaks from Wildebloods ETA OXP to the Aad-HUD and uploaded a new version. Most notably I'm now using Wildebloods method of flushing the message area rather than switching huds. I also added some missing interrupts that Wildeblood is using to the display function.

The main difference (apart from being a hud) to the ETA OXP is the configurable distance functionality.

@Tichy. The hud switching is now gone, so the script is no longer straight forward compatible with the clean hud. To make it compatible, you'll need another script that will do the hud switching. Not very hard thing to do actually.

[Tichy]

@Tichy. The hud switching is now gone, so the script is no longer straight forward compatible with the clean hud. To make it compatible, you'll need another script that will do the hud switching. Not very hard thing to do actually.

Ok! Tomorrow I'll try to adapt my hud to the new script. For the switching, I found a very clear example in modHud2 by Capt. Solo.

[Tichy]

Since now the script don't dependens on switching the hud, have you thought of releasing it separately? In this way, any hud could benefit.
In that case, in my Clear-hud, I would leave only the code that changes the hud depending on the status and it would become indiependet from your version of the talkative space compass.
For me it, would be cleaner and easier to maintain.

[spara]

Since now the script don't dependens on switching the hud, have you thought of releasing it separately? In this way, any hud could benefit.
In that case, in my Clear-hud, I would leave only the code that changes the hud depending on the status and it would become indiependet from your version of the talkative space compass.
For me it, would be cleaner and easier to maintain.

I'll see about that. Only trouble I see is with hud borrowing oxps such as the sniper scope. Presently display updating is halted, when something borrows the hud. Is that necessary? If not, then there's no problem.