[Avernus]

Hi there!
 
It's been long enough since my last visit my old account was nuked

Anyway, I've been messing around with the Hud_gauges.tbl file to center the hud.
Being terrible at any kind of maths i found a table to modify. tweaked it a bit and everythings in its place nicely.

The issue i've had which made me give up on it years ago was, when locking a target with an aspect seeker,
any roll or lateral movement really throws the seeker off track.

Either i'm doing it wrong, or have i run into a limitation of the game?
Using 3 screens at 1920 1080 each (6040/1080) 

Any ideas?  i cant go back to single screen i just cant!! 

[coffeesoft]

You mean something like this ?

These pics are 3840 x 1024, my setup, but the hud is on the center and not streched, just an example.







I found this hud_gauges code on internet, is for 3 screens 1920 x 1080 each ( Total 5760 x 1080 ), try...

http://joshmccarty.com/2011/08/play-an-enhanced-version-of-descent-freespace-2-with-fs2open/

Code: [Select]

#Gauge Config
$Base: (5760, 1080)
$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, 7)
+Training Messages:
Position: (2651, 175)
+Multiplayer Messages:
Position: (1935, 337)
+Support:
Position: (2805, 750)
+Damage:
Position: (2769, 85)
+Wingman Status:
Position: (3718, 202)
+Auto Speed:
Position: (3771, 946)
+Auto Target:
Position: (3771, 911)
+Countermeasures:
Position: (3618, 846)
+Talking Head:
Position: (1930, 79)
+Directives:
Position: (1930, 391)
+Weapons:
Position: (3618, 738)
+Objective Notify:
Position: (2761, 259)
+Squad Message:
Position: (3515, 7)
+Escort View:
Position: (3618, 391)
+ETS Weapons:
Position: (3618, 911)
+ETS Shields:
Position: (3652, 911)
+ETS Engines:
Position: (3686, 911)
+Target Monitor:
Position: (1930, 829)
+Extra Target Data:
Position: (1930, 777)
+Target Shields:
Position: (2610, 942)
+Radar:
Position: (2776, 828)
+Player Shields:
Position: (3054, 942)
; If you want different types of radar running, be my guest
;+Radar Orb:
; Position: (2763, 828)
+Afterburner Energy:
Position: (2507, 526)
+Weapon Energy:
Position: (3187, 526)
+Text Warnings:
Position: (2907, 386)
+Center Reticle:
Position: (2860, 525)
+Mini Target Shields:
Position: (2887, 662)
+Throttle:
Position: (2592, 380)
+Threat Indicator:
Position: (3070, 380)
+Voice Status:
position: (1930, 231)
+Ping:
Position: (3648, 7)
+Lag:
Position: (3128, 744)
+Supernova:
Position: (2248, 238)

+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, 540)
+Target Triangle:
Position: (2907, 540)
+Missile Triangles:
Position: (2907, 540)
+Orientation Tee:
Position: (2907, 540)
+Mission Time:
Position: (3771, 1007)
+Kills:
Position: (3618, 877)
; FS1 specific gauge
;+Weapon Linking:
; Position: (3073, 543)
; Komet's lead sight. Looks for "leadsight.ani"
;+Lead Sight: default
$End Gauges
#End

[niffiwan]

One suggestion, replace this:

Code: [Select]

+ETS Weapons:
Position: (3618, 911)
+ETS Shields:
Position: (3652, 911)
+ETS Engines:
Position: (3686, 911)

with this:

Code: [Select]

+ETS Retail:
Position: (3618, 911)

That'll remove Mr Ugly & Stretched on the right hand screen.

[coffeesoft]

Thanks niffiwan for the correction, much better   

 I want to ask to Avernus wich system specs he is using for triplehead x3 (1920x1080) total (5760 x 1080).

I mean ...

- CPU type and speed,
- Graphic Card, if you are using ( 1 card with 3 outputs ) or ( 2 cards making the 3 outputs )...
- Memory, type  and GB

Also if the FPS are running good with this resolution and ths hardware, without freezes or jumps.

I want to update my computer or buy a new one because here the FPS goes down sometimes with 3048x1024 and 2 screens.

Thanks.

[Avernus]

Thanks for the replies guys

The table file is indeed the one linked by coffeesoft

The issue i have is..  for example: using standard hud stretch(no table file used)
When using an aspect seeker, the  reticle will attempt to track and lock the target with respect to my 'single screen'

The Target Designator Cue will track outside the central monitor to the real huds boundaries , all very normal.

With 3 screens and using the table file, the TDC will still track beyond the central screen (to a degree)
It seems to behave as though the hud is still stretched..

The behavior results in  the TDC moving very very fast laterally if i turn or roll..
that is to say  vertical camera movement seems fine, horizontal movement is the problem.

So to be more clear, the table has fixed the hud visually.
But game behaves exactly the same way when the table file is not used.  The TDC for aspect seekers plays as if its still 1 screen..  being very wide.. the horizontal movement (the lock cue) is VERY sensitive.

I wonder if it can be fixed, or if this is a hardcoded wall of a problem.

As requested Specs are:
Intel I7 950
8g ddr3@1600
Gainward 670 Phantom
Creative x-fi extreme music
3x Samsung 2494hs
trackir 4
Thustmaster Warthog
Saitek Combat pedals
Saitek X52pro

Framerate is not an issue in the slightest
Disabled Vsync via the launcher
Limited Fps to 60 via Nvidia inspector, more than 60 results in frames getting too bunched up.


I'd like to be able to use the warthog and pedals here, but i think i'm asking too much :}

[coffeesoft]

Uf, really i don´t know...

If you want to try with this hud_gauges.tbl, i´m using it and runs good with 3840x1024, change the resolution on the launcher and use the "run in a window" option on the Dev tool.
If you have the same problem, may be it comes from other place, i hope it helps...

Code: [Select]

#Gauge Config
$Base: (3840, 1024)
$Required Aspect: Wide Screen
;$Min: (3840, 1024)
$Gauges:

;Messages
+Messages:
Position: (1286, 5)
+Training Messages:
Position: (1754, 166)
+Multiplayer Messages:
Position: (1290, 319)
+Talking Head:
Position: (1286, 74)

;Comm Menu
+Squad Message:
Position: (2314, 5)

;Objectives
+Escort View:
Position: (2361, 439)
+Directives:
Position: (1286, 370)
+Objective Notify:
Position: (1825, 245)

;Reticle
+Afterburner Energy:
Position: (1622, 564)
+Throttle:
Position: (1712, 358)
+Center Reticle:
Position: (1900, 500)
+Threat Indicator:
Position: (1997, 358)
+Weapon Energy:
Position: (2112, 564)
+Target Brackets: ; Target Brackets, Lock Indicator, Lead Indicator, and Offscreen Indicator don't need a "Position:" field.
+Lock Indicator:
+Lead Indicator:
+Offscreen Indicator:
+Hostile Triangle:
Position: (1920, 515)
+Target Triangle:
Position: (1920, 515)
+Missile Triangles:
Position: (1920, 515)
+Orientation Tee:
Position: (1920, 515)

;Target
+Target Monitor:
Position: (1286, 785)
+Extra Target Data:
Position: (1286, 734)
+Target Shields:
Position: (1645, 891)
+Mini Target Shields:
Position: (1901, 625)

;Player Status
+Damage:
Position: (1830, 81)
+Player Shields:
Position: (2072, 891)
+Kills:
Position: (2380, 830)

+ETS Retail:
Position: (2380, 911)

;Wingmen & Support
+Wingman Status:
Position: (2445, 192)
+Support:
Position: (1854, 710)

;Radar & Targeting
+Radar:
Position: (1794, 785)
;+Radar Orb:
; Position: (1794, 785)
+Auto Target:
Position: (2480, 862)
+Auto Speed:
Position: (2480, 894)

;Weapons
+Countermeasures:
Position: (2380, 801)
+Weapons:
Position: (2380, 698)

;Warnings
+Text Warnings:
Position: (1920, 366)
+Supernova:
Position: (1492, 226)

;Mission Info
+Mission Time:
Position: (2491, 952)

;Multiplayer
+Voice Status:
Position: (1290, 339)
+Ping:
Position: (2400, 5)
+Lag:
Position: (2064, 704)

$End Gauges
#End

[Avernus]

I gave that table a go.

As expected, the width of total resolution is the problem.

Single screen resolutions are mostly fine.
I am unable to use bi-finity since i no longer have an ati card.
Lowering screen resolution width  closer to 1920, 2560 or 3840, and the problem is much less pronounced.

Moving back up to 3 screen resolutions such as 5040,900 or 5760,1080 and the moving lockon cue moves extremely fast with any yaw/roll actions

I suspect i've hit a hardcoded limitation here, something that perhaps the antipodes test builds either missed,
Or simply can not fix/test

Either way, it looks like i have to say a very difficult goodbye to this game. but it does not want to die all the same.

[coffeesoft]

I´m remember a similar problem with the Freelancer Mod Tides of War, when i switch to 3 screens resolutions,
the movements of the mouse are too bigger and was impossible to control the craft.

Finally was solved with a file cameras.ini, applying some values on the FOV.

May be is a zoom problem ?

[Avernus]

That sounds very similar to this problem.
However, moving the ship around is fine,  problem is only the lock on cursor.

Yaw in any direction and the lock cue moves away very quickly.

If the hud ends about a hands widh from center screen, thats where the lock ends too (naturally)
With the table file in place, hud is centered, but cursor acts like it is not.

[Goober5000]

Avernus, what was your old account?

[Avernus]

The system told me my username was suspended, likely due to tedious inactivity

maybe try  eidolon>eid    if you find the clone, nuke it for me please.

I'd still like to know if I've hit an Scp limitation here with multi-screen width accelerating the Lock cue horizontally.

Can it be fixed, tweaked out or patched one day?
Or am i doomed to stick with single screen until freespace 3  

[Goober5000]

Is this it?
http://www.hard-light.net/forums/index.php?action=profile;u=1326

I can reset your password if you want.

[Avernus]

Might as well go ahead and delete it  thanks.

This multiscreen issue however,  is it well known? 

Do i hold my breath for a few more years or  admit defeat
I never expected a 3dfx game to use more than 1 screen to be honest 

Now if only i could get it to use my Tm Warthog