FreeSpace 2

[The_cranky_hermit]

Widescreen Grade: C
Ultra-Widescreen Grade: C
Multi-monitor Grade: C
4k Grade: Incomplete

Read Full Detailed Report - FreeSpace 2

FreeSpace 2 is a space shooter from Volition, the sequel to Descent: FreeSpace. FSO is an open-source port of the game that adds tons of new features to the engine like pixel shaders, and more importantly, widescreen support.

4:3

16:10

16:9

21:9

3x1

Read More

[ambivert]

These instructions assume you've properly installed Freespace Open. When using the launcher, be sure you browse and select the fs2_open_ant_7r beta version and not the latest 3_6_12 version as the code hasn't been tweaked in that version to accomodate the hud fix table. These instructinos will tentatively fix the stretched hud when running Freespace Open on three-monitor setup for a 3 X 1920 X 1200. This will not fix large fonts or stretched menus, so don't expect it to be the final solution. This is just temporary to get by until widescreen multimontors are fully implemented in a final FSO version.

You have to use Freespace Open, not the mere retail and you have to download the beta for fs2_open_ant_7r_INF for this to work. This will eventually make it into a final release in Open, but it's just experimental for now.

1.Take the following code, which was created by Hurlybird, and paste it into a .txt file

2. Rename the txt file to hud_gauges.tbl and drop the hud_gauges.tbl into your Freespace 2/data/tables folder.

3. launch the game using the FreeSpace open mod launcher and enjoy!

#Gauge Config
$Base: (5760, 1200)
$Required Aspect: Wide Screen ; Can be "Wide Screen" or "Full Screen" ATM
$Min: (4320, 900);
$Max: (7680, 1600) ; These Min and Max fields are Inclusive
$Gauges:
+Messages:
Position: (1930, 8)
+Training Messages:
Position: (2651, 195)
+Multiplayer Messages:
Position: (1935, 375)
+Support:
Position: (2805, 833)
+Damage:
Position: (2769, 95)
+Wingman Status:
Position: (3718, 225)
+Auto Speed:
Position: (3771, 1051)
+Auto Target:
Position: (3771, 1012)
+Countermeasures:
Position: (3618, 940)
+Talking Head:
Position: (1930, 88)
+Directives:
Position: (1930, 435)
+Weapons:
Position: (3618, 820)
+Objective Notify:
Position: (2761, 288)
+Squad Message:
Position: (3515, 8)
+Escort View:
Position: (3618, 435)
+ETS Weapons:
Position: (3618, 1012)
+ETS Shields:
Position: (3652, 1012)
+ETS Engines:
Position: (3686, 1012)
+Target Monitor:
Position: (1930, 921)
+Extra Target Data:
Position: (1930, 863)
+Target Shields:
Position: (2610, 1047)
+Radar:
Position: (2766, 921)
+Player Shields:
Position: (3054, 1047)
; If you want different types of radar running, be my guest
;+Radar Orb:
; Position: (2763, 921)
+Afterburner Energy:
Position: (2507, 585)
+Weapon Energy:
Position: (3187, 585)
+Text Warnings:
Position: (2907, 429)
+Center Reticle:
Position: (2860, 584)
+Mini Target Shields:
Position: (2887, 736)
+Throttle:
Position: (2592, 423)
+Threat Indicator:
Position: (3082, 423)
+Voice Status:
position: (1930, 257)
+Ping:
Position: (3648, 8)
+Lag:
Position: (3128, 827)
+Supernova:
Position: (2248, 265)

+Target Brackets: ; Target Brackets, Lock Indicator, Lead Indicator, and Offscreen Indicator don't need a "Position:" field.
+Lead Indicator:
+Lock Indicator:
+Offscreen Indicator:
+Hostile Triangle:
Position: (2907, 600)
+Target Triangle:
Position: (2907, 600)
+Missile Triangles:
Position: (2907, 600)
+Orientation Tee:
Position: (2907, 600)
+Mission Time:
Position: (2907, 1119)
+Kills:
Position: (3618, 975)
; FS1 specific gauge
;+Weapon Linking:
; Position: (3073, 604)
; Komet's lead sight. Looks for "leadsight.ani"
;+Lead Sight: default
$End Gauges
#End

If you need to tweak the data to suit another resolution setup, then you'll find the following thread useful and you'll want to get your hands on the ResolutionCalculator_1440810_base.rar file, that will figure out the positions for whatever setup you want.

Here's the thread where all of the geniuses are for further exploration:

http://www.hard-light.net/forums/index.php?topic=69858.120

[Paradigm Shifter]

FreeSpace 2... in Surround?

:rockout

[ambivert]

Here's a much better HUD code that only requires you to enter your base resolution. I found this from a guru on one of the forums. Not my code. It autocalculates your eyefinity or nvsurround settings. Just enter your resolution in the $Base field and your off and trucking:

$Scale Gauges: no
#Gauge Config
$Base: (6000, 1200)
$Min: (1280, 640)
$Gauges:
+Messages:
Origin: (0.34, 0.0)
Offset: (8, 5)
+Wingman Status:
Origin: (0.66, 0.0)
Offset: (-92, 144)
+Auto Speed:
Origin: (0.66, 1.0)
Offset: (-64, -96)
+Auto Target:
Origin: (0.66, 1.0)
Offset: (-64, -120)
+Countermeasures:
Origin: (0.66, 1.0)
Offset: (-144, -166)
+Talking Head:
Origin: (0.34, 0.0)
Offset: (5, 56)
+Directives:
Origin: (0.34, 0.5)
Offset: (5, -106)
+Weapons:
Origin: (0.66, 1.0)
Offset: (-144, -257)
+Squad Message:
Origin: (0.66, 0.0)
Offset: (-197, 5)
+Escort View:
Origin: (0.66, 0.5)
Offset: (-159, -54)
+Mission Time:
Origin: (0.66, 1.0)
Offset: (-55, -52)
+Target Monitor:
Origin: (0.34, 1.0)
Offset: (5, -178)
+Extra Target Data:
Origin: (0.34, 1.0)
Offset: (5, -216)
+Multiplayer Messages:
Origin: (0.34, 0.5)
Offset: (8, -144)
+Voice Status:
Origin: (0.34, 0.5)
Offset: (8, -129)
+Ping:
Origin: (0.66, 0.0)
Offset: (-128, 5)
+Kills:
Origin: (0.66, 1.0)
Offset: (-144, -144)
+Fixed Messages:
+ETS Retail:
Origin: (0.66, 1.0)
Offset: (-144, -120)
$End Gauges
#End

[Garrett]

I have updated the report with the latest FSOpen details and the simpler multi-monitor HUD fix above. The HUD is a bit smaller than the default with this script so there is probably something that needs to be tweaked a bit more to get that result.