[Zacam]

Recommended running with builds 7176 or later. (So that +Orb Radar: and +Radar can co-exist and play nicely based on users options)

Posting this in code tags as the attachments from Ant7 have disappeared.

**Edit: Using the latest 3.2 FSPort-MediaVPs means that this file will have to be called Hud_Gauges.tbl. 
Otherwise you will end up with duplicated HUD entries (assuming your HUD even displays in the first place).

The Following presents properly place WideScreen elements, for the most part and should be used instead of the included Hud_Gauges.tbl

Code: (Hud_Gauges.tbl) [Select]

$Load Retail Configuration: No
$Reticle Style: FS1

#Gauge Config
$Base: (1440, 900)
$Required Aspect: Wide Screen
$Min: (1280, 720)
$Max: (1920, 1200)
$Gauges:
+Messages:
Position: (7, 6)
+Fixed Messages:
+Training Messages:
Position: (533, 146)
+Multiplayer Messages:
Position: (11, 281)
+Support:
Position: (645, 625)
+Damage:
Position: (619, 71)
+Wingman Status:
Position: (1311, 169)
+Auto Speed:
Position: (1350, 788)
+Auto Target:
Position: (1350, 759)
+Countermeasures:
Position: (1238, 705)
+Talking Head:
Position: (7, 66)
+Directives:
Position: (7, 326)
+Weapons:
Position: (1238, 615)
+Objective Notify:
Position: (613, 216)
+Squad Message:
Position: (1163, 6)
+Escort View:
Position: (1238, 326)
+ETS Weapons:
Position: (1238, 759)
+ETS Shields:
Position: (1263, 759)
+ETS Engines:
Position: (1288, 759)
+Target Monitor:
Position: (7, 691)
+Extra Target Data:
Position: (7, 647)
+Target Shields:
Position: (503, 785)
+Radar:
Position: (617, 691)
+Player Shields:
Position: (827, 785)
+Afterburner Energy:
Position: (498, 439)
+Weapon Energy:
Position: (854, 439)
+Text Warnings:
Position: (720, 322)
+Center Reticle:
Position: (700, 438)
+Mini Target Shields:
Position: (705, 552)
+Throttle:
Position: (570, 417)
+Threat Indicator:
Position: (594, 287)
+Voice Status:
position: (7, 193)
+Ping:
Position: (1260, 6)
+Lag:
Position: (881, 620)
+Supernova:
Position: (239, 199)
+Target Brackets:
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
+Hostile Triangle:
Position: (720, 450)
+Target Triangle:
Position: (720, 450)
+Missile Triangles:
Position: (720, 450)
+Orientation Tee:
Position: (720, 450)
+Mission Time:
Position: (1363, 839)
+Kills:
Position: (1238, 731)
; FS1 specific gauge
+Weapon Linking:
Position: (791, 413)
$End Gauges
#End

#Gauge Config
$Base: (1024, 768)
$Required Aspect: Full Screen
$Gauges:
+Messages:
Position: (5, 5)
+Fixed Messages:
+Training Messages:
Position: (379, 125)
+Multiplayer Messages:
Position: (8, 240)
+Support:
Position: (459, 534)
+Damage:
Position: (440, 61)
+Wingman Status:
Position: (932, 144)
+Auto Speed:
Position: (960, 672)
+Auto Target:
Position: (960, 648)
+Countermeasures:
Position: (880, 602)
+Talking Head:
Position: (5, 56)
+Directives:
Position: (5, 278)
+Weapons:
Position: (880, 525)
+Objective Notify:
Position: (436, 184)
+Squad Message:
Position: (827, 5)
+Player Shields:
Position: (634, 670)
+Target Shields:
Position: (292, 670)
+Escort View:
Position: (865, 330)
+ETS Weapons:
Position: (880, 648)
+ETS Shields:
Position: (898, 648)
+ETS Engines:
Position: (916, 648)
+Target Monitor:
Position: (5, 590)
+Extra Target Data:
Position: (5, 552)
+Radar:
Position: (411, 590)
+Afterburner Energy:
Position: (274, 424)
+Text Warnings:
Position: (512, 275)
+Center Reticle:
Position: (493, 376)
+Mini Target Shields:
Position: (497, 470)
+Throttle:
Position: (347, 390)
+Threat Indicator:
Position: (386, 219)
+Voice Status:
position: (5, 165)
+Ping:
Position: (896, 5)
+Lag:
Position: (627, 529)
+Supernova:
Position: (170, 170)
+Target Brackets:
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
+Hostile Triangle:
Position: (512, 387)
+Target Triangle:
Position: (512, 387)
+Missile Triangles:
Position: (512, 387)
+Orientation Tee:
Position: (512, 387)
+Weapon Energy:
Position: (666, 424)
+Mission Time:
Position: (969, 716)
+Kills:
Position: (880, 624)
; FS1 specific gauge
+Weapon Linking:
Position: (598, 387)
$End Gauges
#End


[Goober5000]

Is this an example, or a recommendation to replace what we have with this?

And is this dependent or independent of having MVPs running?

[mjn.mixael]

FSPort must run a HUD table if it's run with 3.6.13 or higher.

If the mediaVPs are present, then the HUD table must have the same name as the mediavps version or you'll see extra HUD elements.

The one posted is (was) the same as what I was using. I don't know what Zacam changed yet.

[Goober5000]

FSPort must run a HUD table if it's run with 3.6.13 or higher.

Why exactly?

[Dragon]

Because it's Mediavps inclued a bogus HUD_gauges.tbl , which needs to be overrun by the new table.

[Zacam]

It's not that it's bogus, it's that elements don't line up correctly on the defined widescreen.

In reality, each resolution achievable should have it's own definition, but I still have not even finished that for FS2, much less FS1.

The file also should (like in SVN) have been a TBM to start with, not a TBL, but that's neither here nor there at this point.

[Goober5000]

So if you run without a hud_gauges.tbl and without mediavps, what will happen?

[Zacam]

FSO will run and display HUD's without a hud_gauges.tbl/tbm just fine. It will just continue (at widescreens) to be the same 1024x768 stretched out ugly mess it's always been.

But FSPort MediaVPs has a hud_gauges.tbl (which should have been a TBM, and it is in SVN) that, for whatever reason, is off on it's display alignment. Plus as it turns out, the Max display resolution was off too (people were running a higher than specified resolution, and hence, no HUD elements being displayed). To correct that, the above code is to be used as an over-ride TBL to correct that for the 3.2 version.

[Zacam]

Edit Update: Added "+Fixed Messages:" to the list so that "Viewing From" etc messages will display.

HAT Directional view messages still do not display though (yet). And player_death_messages is still being obscured by the cutscene bars.

[KyadCK]

upon trying this, it mostly worked and looked aweosme but i was missing one thing: a reticle

it may well be that i messed up somewhere, so this is all i did (after reseting hud in options):

copy everything in zacam's code box
make new txt file in mediavps_3612\data\tables
paste code
rename to Hud_Guages.tbl

and a screenshot i intentionaly did not lvlshot:

[attachment deleted by ninja]

[Commander Zane]

With this .tbl I noticed the collision notification no longer appears when flying into objects.

Edit: There's also other quirks like the missile warning and evasion notifications (Same location as collision), and when aspect lock is aquired, the triangles that surround the diamond are offset.

[Satellight]

With this .tbl I noticed the collision notification no longer appears when flying into objects.

Edit: There's also other quirks like the missile warning and evasion notifications (Same location as collision), and when aspect lock is aquired, the triangles that surround the diamond are offset.

Maybe you should check THIS

And especially this part :

Make sure you guys turn on all the HUD gauges in the HUD Options Menu. I know that FSO by default sets Squad Messages and Text Warnings off; originally FSO would just display them regardless of they were off or not but my code, for better or worse, does not make any such discrimination.

[Commander Zane]

Why the **** does it do something that retarded?

[Kolgena]

Here's some alternate tables for FS1 in 16:9, 16:10, and 4:3 in a layout that (at least IMO) is faithful to the original HUD.

16:10

Code: [Select]

$Load Retail Configuration: NO
$Max directives: 8
$Max escort ships: 8
$Reticle Style: FS1
#Gauge Config
$Base: (1440,900)
$Min: (1024,768)
$Max: (1920,1200)
$Gauges:
+Messages:
Position: (5,5)
+Training Messages:
Position: (587,191)
+Multiplayer Messages:
Position: (216,306)
+Support:
Position: (667,600)
+Damage:
Position: (648,127)
+Wingman Status:
Position: (1348,210)
+Auto Speed:
Position: (1376,804)
+Auto Target:
Position: (1376,780)
+Countermeasures:
Position: (1296,734)
+Talking Head:
Position: (5,59)
+Directives:
Position: (5,344)
+Weapons:
Position: (1296,657)
+Objective Notify:
Position: (644,316)
+Squad Message:
Position: (1243,5)
+Escort View:
Position: (1281,462)
+ETS Weapons:
Position: (1296,780)
+ETS Shields:
Position: (1314,780)
+ETS Engines:
Position: (1332,780)
+Target Monitor:
Position: (5,722)
+Extra Target Data:
Position: (5,684)
+Target Shields:
Position: (458,802)
+Radar:
Position: (619,722)
+Player Shields:
Position: (884,802)
+Afterburner Energy:
Position: (482,490)
+Weapon Energy:
Position: (874,490)
+Text Warnings:
Position: (720,341)
+Center Reticle:
Position: (701,442)
+Mini Target Shields:
Position: (705,536)
+Throttle:
Position: (555,456)
+Threat Indicator:
Position: (594,285)
+Voice Status:
Position: (5,231)
+Ping:
Position: (1104,5)
+Lag:
Position: (835,595)
+Supernova:
Position: (170,179)
+Hostile Triangle:
Position: (720,450)
+Target Triangle:
Position: (720,450)
+Missile Triangles:
Position: (720,450)
+Orientation Tee:
Position: (720,450)
+Target Brackets:
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
Position: (720,450)
+Mission Time:
Position: (1385,848)
+Kills:
Position: (1296,756)
+Weapon Linking:
Position: (806,453)
$End Gauges
#End

16:9

Code: [Select]

$Load Retail Configuration: NO
$Max directives: 8
$Max escort ships: 8
$Reticle Style: FS1
#Gauge Config
$Base: (1440,810)
$Min: (1024,768)
$Max: (1920,1200)
$Gauges:
+Messages:
Position: (5,5)
+Training Messages:
Position: (587,146)
+Multiplayer Messages:
Position: (216,261)
+Support:
Position: (667,555)
+Damage:
Position: (648,82)
+Wingman Status:
Position: (1348,165)
+Auto Speed:
Position: (1376,714)
+Auto Target:
Position: (1376,690)
+Countermeasures:
Position: (1296,644)
+Talking Head:
Position: (5,59)
+Directives:
Position: (5,299)
+Weapons:
Position: (1296,567)
+Objective Notify:
Position: (644,226)
+Squad Message:
Position: (1243,5)
+Escort View:
Position: (1281,372)
+ETS Weapons:
Position: (1296,690)
+ETS Shields:
Position: (1314,690)
+ETS Engines:
Position: (1332,690)
+Target Monitor:
Position: (5,632)
+Extra Target Data:
Position: (5,594)
+Target Shields:
Position: (458,712)
+Radar:
Position: (619,632)
+Player Shields:
Position: (884,712)
+Afterburner Energy:
Position: (482,445)
+Weapon Energy:
Position: (874,445)
+Text Warnings:
Position: (720,296)
+Center Reticle:
Position: (701,397)
+Mini Target Shields:
Position: (705,491)
+Throttle:
Position: (555,411)
+Threat Indicator:
Position: (594,240)
+Voice Status:
Position: (5,186)
+Ping:
Position: (1104,5)
+Lag:
Position: (835,550)
+Supernova:
Position: (170,179)
+Hostile Triangle:
Position: (720,405)
+Target Triangle:
Position: (720,405)
+Missile Triangles:
Position: (720,405)
+Orientation Tee:
Position: (720,405)
+Target Brackets:
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
Position: (720,405)
+Mission Time:
Position: (1385,758)
+Kills:
Position: (1296,666)
+Weapon Linking:
Position: (806,408)
$End Gauges
#End

4:3 (higher resolution/smaller HUD elements)

Code: [Select]

$Load Retail Configuration: NO
$Max directives: 8
$Max escort ships: 8
$Reticle Style: FS1
#Gauge Config
$Base: (1080,810)
$Min: (1024,768)
$Max: (1920,1200)
$Gauges:
+Messages:
Position: (5,5)
+Training Messages:
Position: (407,146)
+Multiplayer Messages:
Position: (36,261)
+Support:
Position: (487,555)
+Damage:
Position: (468,82)
+Wingman Status:
Position: (988,165)
+Auto Speed:
Position: (1016,714)
+Auto Target:
Position: (1016,690)
+Countermeasures:
Position: (936,644)
+Talking Head:
Position: (5,59)
+Directives:
Position: (5,299)
+Weapons:
Position: (936,567)
+Objective Notify:
Position: (464,226)
+Squad Message:
Position: (883,5)
+Escort View:
Position: (921,372)
+ETS Weapons:
Position: (936,690)
+ETS Shields:
Position: (954,690)
+ETS Engines:
Position: (972,690)
+Target Monitor:
Position: (5,632)
+Extra Target Data:
Position: (5,594)
+Target Shields:
Position: (314,712)
+Radar:
Position: (439,632)
+Player Shields:
Position: (668,712)
+Afterburner Energy:
Position: (302,445)
+Weapon Energy:
Position: (694,445)
+Text Warnings:
Position: (540,296)
+Center Reticle:
Position: (521,397)
+Mini Target Shields:
Position: (525,491)
+Throttle:
Position: (375,411)
+Threat Indicator:
Position: (414,240)
+Voice Status:
Position: (5,186)
+Ping:
Position: (924,5)
+Lag:
Position: (655,550)
+Supernova:
Position: (170,179)
+Hostile Triangle:
Position: (540,405)
+Target Triangle:
Position: (540,405)
+Missile Triangles:
Position: (540,405)
+Orientation Tee:
Position: (540,405)
+Target Brackets:
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
Position: (540,405)
+Mission Time:
Position: (1025,758)
+Kills:
Position: (936,666)
+Weapon Linking:
Position: (626,408)
$End Gauges
#End


upon trying this, it mostly worked and looked aweosme but i was missing one thing: a reticle

it may well be that i messed up somewhere, so this is all i did (after reseting hud in options):

copy everything in zacam's code box
make new txt file in mediavps_3612\data\tables
paste code
rename to Hud_Guages.tbl

and a screenshot i intentionaly did not lvlshot:

The tables posted here go into FSPort_mediavps, and NOT into mediavps 3.6.12.

If you want widescreen tables for FS2, PM me.

[Ramzee]

Hi, to get the FSport HUD to display correctly at 640x480, 800x600 and 1024x600 (it had offset/missing elements) I've changed the first line of the example 3:4 Hud_Guages.tbl to:-

Code: [Select]

$Load Retail Configuration: YES
as changing

Code: [Select]

$Min: (640,480)had no effect.

Although resoultions below 1024x768 aren't officially supported I wondered if there was a better way and/or what I was missing out on as there has obviously been a lot of effert put into these custom fsport .tbl files.

[WhiteFox]

FSO will run and display HUD's without a hud_gauges.tbl/tbm just fine. It will just continue (at widescreens) to be the same 1024x768 stretched out ugly mess it's always been.

But FSPort MediaVPs has a hud_gauges.tbl (which should have been a TBM, and it is in SVN) that, for whatever reason, is off on it's display alignment. Plus as it turns out, the Max display resolution was off too (people were running a higher than specified resolution, and hence, no HUD elements being displayed). To correct that, the above code is to be used as an over-ride TBL to correct that for the 3.2 version.

@Goober5000: Can confirm this! On 1600x1200 Pixels the HUD isnt in the middle of Screen, without that File.
Edit: Argh, seen too late, that this Post is from last year.