Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Tyr74 on December 31, 2017, 05:45:33 am

Title: Strange HUD problem - sizing and target lockbox
Post by: Tyr74 on December 31, 2017, 05:45:33 am
Hi all, I've encoutered strange hud problem to which I cannot find solution yet.

I'm using nVidia GTX 970 and 1920 x 1080 widescreen on 32" TV that poses as monitor.

When i start game with "$Scale gauges: yes" on in \MediaVPs_2014\data\tables\ mv_root-hdg.tbm mission directives and other text and gauges are readable but somewhat smudged due to scaling. I can live with that, but during a mission sooner or later my aiming recticle and target box get stuck in upper left corner on the screen, no matter where target actually is or what is targeted. When I set scaling to no, that problem is gone but text is too small to be readed at all, and gauges are really small.

I have tried alternate HUD (Axem Large HUD) and that helps a bit, with scaling off, text can now be read, if you are really close to screen, and gauges are somewhat bigger but still rather small.
Still with scaling set to yes aiming recticle and target box eventualy slip to upper left position and get stuck there. 
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: vkapadia on December 31, 2017, 07:43:58 pm
Same issue with the targeting box here. I haven't been able to fix this. You said you could fix it by turning scaling off. How do I do that? I can see an option to turn off scaling for videos, but not any other scaling options.
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: vkapadia on December 31, 2017, 07:51:00 pm
For full information, I'm playing this on a 60" 4K TV, Radeon R9 360, tried at multiple resolutions all give me the same issue.
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: Tyr74 on January 01, 2018, 06:54:02 am
Create file called mv_root-hdg.tbm in your mediavp folder i.e. d:\Program Files (x86)\GOG.com\Freespace 2\MediaVPs_2014\data\tables for me. If folder "tables" is missing create it.

copy and paste following in that file:

Code: [Select]
$Max directives: 8   
$Max escort ships: 13 
$Scale Gauges: no

And solution isn't mine i just snitched it from somewhwe, i belive steam forums...
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: FrikgFeek on January 01, 2018, 11:53:28 am
$Scale Gauges: no should be the default value for MediaVPs_2014. It's enabled in 3612 though.
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: vkapadia on January 02, 2018, 09:20:43 am
Still no good. Added the file to both MediaVPs_2014\data\tables and fsport-mediavps_2014\data\tables with no luck, target boxes still end up going to the top left corner after a while.  :banghead:
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: AdmiralRalwood on January 03, 2018, 07:49:03 pm
Still no good. Added the file to both MediaVPs_2014\data\tables and fsport-mediavps_2014\data\tables with no luck, target boxes still end up going to the top left corner after a while.  :banghead:
That file is the default file from the 2014 MediaVPs. What if you try with scaling enabled, instead?
Title: Re: Strange HUD problem - sizing and target lockbox
Post by: Jehoel on January 06, 2018, 09:47:29 pm
I'm experiencing the same problem.

Computer:
* Dell XPS 15 with 4K display (3840x2160).
* NVIDIA GeForce 1050 with Intel HD Graphics 630
* Windows 10 x64 build 1709
* Windows desktop running at 200% scaling (192dpi) - I don't know how this affects the game at all.
* Running "fs2_open_3_8_0_x64_AVX.exe", modified date: 2017-08-22. I didn't use any launcher.

I had no issues with scaling/blurring for any of the game's menu/briefing UI, and the simulator HUD seemed fine - except for the current-target box and the targeting reticle which were all constrained to the top-left corner of the screen.

I also experienced another problem: some voice dialog lines in the second main campaign mission (where Bosch's asteroid/Iceni escape) weren't played and I think some of Command's voice lines were being played prematurely.