[Release] HUD Selector v1.17

[Norby]

had to revert to a backup a few hours older?

I think the same: around yesterday noon the forum reverted to about half day back. My pm to Zireael what I sent within that time is vanished also so I sent it again.

[Anonymissimus]

Since my switch to the 1.84 branch, my HUD frequently "disappears" while docked. I have to press key_hud_toggle after undocking. It may just as well be an engine bug. It seems it appears primarily (or only) at main stations, and the longer I keep pressing keys to switch through the station menus, the more likely it is that it happens at some point. From then on the HUD is gone until key_hud_toggle. So when undocking, none of the MFDs or controls are visible (as if key_hud_toggle had been pressed). Saveloading while still docked also restores the HUD. The station menus and so on are visible, just not the elements that belong to the in-flight HUD.

[another_commander]

Since my switch to the 1.84 branch, my HUD frequently "disappears" while docked. I have to press key_hud_toggle after undocking. It may just as well be an engine bug.

Does it happen in strict mode? If not, then it is an OXP causing it.

[Anonymissimus]

It happens as soon as I enter the email system, so probably that's it.

[Norby]

I have to press key_hud_toggle after undocking.

Please try HudSelector 1.17: https://app.box.com/s/jwga1dwkbjlvd38i7fungrmg899pcg6g
In this version I force to show HUD at launch and when you press F2 in dock, probably help just I can not upload it at the moment due to a problem in the wiki.

[Anonymissimus]

This sounds like you added a workaround. The problem should be fixed instead.

[Norby]

Now v1.17 is uploaded with these changes:
- Always turn on the HUD at launch and at Options(F2) to fix problems in any addons.
- Removed "(adjusting)" text from timer in Large and other included HUDs.
- A comma added into "Press Space, Commander".

[dybal]

 HUDSelector v1.18 is available on the Expansion Manager and here.

Changes

• Display HUD Selector Removal in red at Ship Outfitting screen.
• Sets Station Interface (F4) when loading savefile (previously done only when docking).
• Deals with more than one HUD from the same worldscript.
• Adds Primeable Equipment MFD to the default MFDs list.

[PAA-61]

Hi!
forgive me if i hadn't read the solution yet , but if i use large or extra large hud the precise indicator is covered by the energy banks.
Any solution to move to an other place ??
Thank You

[Cholmondely]

Hi!
forgive me if i hadn't read the solution yet , but if i use large or extra large hud the precision indicator is covered by the energy banks.
Any solution to move to an other place ??
Thank You

Did you ever sort this out?

Cholmondeley

[Cholmondely]

MFDs and HUD Selector compliance:

Note for the Record:

As far as I know, the following MFDs are not compliant:

•Advanced System Data MFD (from Strangers World: Sun Gear: 2 MFDs?)
•Bounty System's Warrant Scanner MFD
•MFD - BroadcastComms (Digebitian Variant)
•MFD - Damage Report
•Fighters MFD (and presumably the Tie-Fighters MFD in Star Destroyer)
•Manifest Scanner
•Primeable Equipment MFD
•Range Finder MFD
•Ship's Library MFD
•Star System Lane Indicator MFD
•Station Dock Control
•Technical Reference Library MFD
*Target System Plugins (SRS, TMI & TBM) MFDs
•Waypoint Here MFD

The seemingly relevant bit of javascript currently reads:

Code: Select all

//default MFD 1-10 worldScript names
this.$HUDSelectorMFDs = [["combat_MFD"],
			["telescope"],
			["escortdeck"],
			["CommsLogMFD"],
			["BroadcastCommsMFD"],
			["trophy_col", "trophy_mfd"], //mfd name is different
			["navi_mfd"],
			["market_inquirer", "inquirer_mfd"], //mfd name is not equal with worldScript name
			["manifest_mfd"],
			["useful_MFDs", "useful_MFD_general_info"] //mfd name is different
			];

Edited to add MFD - BroadcastComms (Digebitian Variant); MFD - Damage Report; & Station Dock Control to the list of non-compliant MFDs

[Nite Owl]

There has to be a clever bit of code in there that reads other such files and gathers data about the M.F.D.s they generate aside from the listing you posted. The listing you posted is possibly the default M.F.D. setup for when you first open the M.F.D. selection screen via the F4 interface.

The Proof is in the Pudding. Just went in game and one of the M.F.D. selection options off of the F4 interface screen was for the Launch Queue M.F.D. This is the M.F.D. from the Station Dock Control OXZ which is on your list as being unsupported and is not in the list you posted as code. No idea as to what other M.F.D.'s might be readable (and thereby selectable) in such a manner but if one of them is then my best guess is that all of them are. Have my suspicions as to which bit of code is doing this work but they remain just that, suspicions and not facts. If any of the coding gurus that are out and about has the time and desire to confirm this and, perhaps, post the significant bit of code that is doing said reading of other files then that would be ideal.

Great Wiki Work by the way, Much Appreciated.

[Milo]

http://wiki.alioth.net/index.php/HUDSel ... _Dark_Side

Other HUDs can add themselves to HUD Selector’s list as part of their startup scripting.

[phkb]

Other HUDs can add themselves to HUD Selector’s list as part of their startup scripting.

Damage Report MFD is doing this, as is Station Dock Control, Range Finder MFD and Waypoint Here. Looks like I forgot about the Warrant Scanner. I'll add that fix for the next release.

"Broadcast Comms - Digebiti Variations" doesn't need to be added separately, as it's using the standard "BroadcastCommsMFD" item.

[Nite Owl]

So an M.F.D. or H.U.D. can add itself into H.U.D. Selector's list of selectable items by adding code to its own JavaScript. Got it. Should have thought of that in my previous post as that sort of thing has been witnessed by me in previous studies.

Thank You Very Much.