Author Topic: Strange HUD problem - sizing and target lockbox  (Read 884 times)

0 Members and 2 Guests are viewing this topic.

Offline Tyr74

  • 21
Strange HUD problem - sizing and target lockbox
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. 

 
Re: Strange HUD problem - sizing and target lockbox
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.

 
Re: Strange HUD problem - sizing and target lockbox
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.

 

Offline Tyr74

  • 21
Re: Strange HUD problem - sizing and target lockbox
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...

 
Re: Strange HUD problem - sizing and target lockbox
$Scale Gauges: no should be the default value for MediaVPs_2014. It's enabled in 3612 though.
[19:31] <MatthTheGeek> you all high up on your mointain looking down at everyone who doesn't beam everything on insane blindfolded

 
Re: Strange HUD problem - sizing and target lockbox
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:

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Strange HUD problem - sizing and target lockbox
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?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline Jehoel

  • 20
Re: Strange HUD problem - sizing and target lockbox
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.