[Kiloku]

I'm aware that it is a known problem, and that technically the "solution" is to change your resolution.

I don't think that is a solution at all, it's like putting the dirt under the carpet.
People like to play on the highest available resolution and it's no fun to be forced to play below the top your computer can reach. Is it very hard to make the HUD work on more resolutions? How would I go about adding my own resolution to the supported ones? I'm willing to fiddle with .tbms if that's what I have to do.

Also, why has a bug that has been known for so long not been adressed?

[niffiwan]

I'm not sure of the exact cause of the problem, but if you're interested in trying to solve it yourself, here's the reference to the hud gauges table.  To modify the table, you'll need to extract it from one of the "core" VPs, using something like this, and put it into blueplanet/data/tables or blueplanet2/data/tables, depending on which "core" VP it is in.  You'll probably need to create those directories as they don't exist by default.

[Kiloku]

What I notice with this problem is that one is the HUD as it would look like normally in FSO (with the old font and all), and the other seems to be more dynamic, and uses the prettier font that shows up in WiH's menus and briefings. I suppose the "old" HUD has to be deactivated and isn't.

[niffiwan]

yeah, each hud configuration in the file has a supported resolution.  This is useful to configure 4:3 differently to 16:9 / 16:10.  In addition to the configurations in the table there is a default configuration.  One of the options, something like "use retail" should be the config item that configures whether or not the "retail config" is used in addition to the rest of the "custom" gauges.

What is your max/native resolution?  Perhaps you just need to alter the "$Max:" value for one of the configurations in the table?  (I can't really test this myself, since my max res is 1680x1050 and that works OK)

[Kiloku]

I have 1920x1080. When I checked the reference, "Use Retail" meant that the retail HUD configs would be used if a certain element was not added to the table, so it's not in addition.
The hud_gauges.tbl has my resolution as "$Base", and 1920x1200 as "$Max". Changing the $Max does nothing, and changing the $Base to another resolution makes me see only the retail hud. I'd prefer to use the new HUD though, if there is a way to actually remove the old one. The new hud is aligned properly, but appears overlapping the old one.

[General Battuta]

We would absolutely love to have a HUD table that supports all resolutions.

[niffiwan]

I have 1920x1080. When I checked the reference, "Use Retail" meant that the retail HUD configs would be used if a certain element was not added to the table, so it's not in addition.
The hud_gauges.tbl has my resolution as "$Base", and 1920x1200 as "$Max". Changing the $Max does nothing, and changing the $Base to another resolution makes me see only the retail hud. I'd prefer to use the new HUD though, if there is a way to actually remove the old one. The new hud is aligned properly, but appears overlapping the old one.

Hmmm.. what's the base/max of the rest of the resolution configurations in the table?  Maybe one of the others is matching your res as well?  i.e. two configs match for 1920x1080?

[Yarn]

I figured out what the problem is. The widescreen HUD included with BP2 does not have the "$Required Aspect: Wide Screen" line, so the game is using both the widescreen and fullscreen HUDs in non-widescreen resolutions 1280x768 and greater. Adding "$Required Aspect: Wide Screen" just below the "$Base:" line should fix the problem.

[General Battuta]

A ha, awesome.

[BlasterNT]

And here's a table that should work:

Put it into blueplanet2/data/tables

I had thought that was the issue, but I didn't know if leaving out the Wide Screen was intentional, and it was just because of my nonstandard res that things were getting messed up

[attachment deleted by ninja]

[Klaustrophobia]

give that man a cookie.