[VicRattlehead]

Current Target view is bugged.
It doesn't show messages like with the bug with the external camera view and in addition to that, most of the HUD elements remain on screen, when normally, only some of them, like the target monitor, extra target data, messages, talking head, center reticle and the "viewing from xxx" message are the ones that remain.

[General Battuta]

When using a ballistic primary, both the weapon energy gauge and the ballistic ammo gauge are moved to the far right side of the screen, and in fact most of said gauges are just dangling off the edge of the screen.

I'm at 1680x1050. Will try for screen.

[swashmebuckle]

Have the alternate header name lines been added to the other gauges, and would it be possible to get an up-to-date table that shows all of the available configuration options (any resolution would be fine)?

The only other things I had left over from the other thread were a vertical spacing adjuster for the wing names in the wingmen gauge and I think a horizontal (and maybe vertical?) clip distance for the normal messages readout.  Hooray for the HUD!

[Sushi]

The Lead Sight seems inaccurate when flying backwards vs a stationary target, at least in Diaspora. I'm not sure how the sight is calculated, but we might want to double-check the math on it.

[Admiral LSD]

Out of curiosity, what distro are the Linux builds compiled under? While installing under Fedora (13) yesterday it kept telling me it couldn't find "liblua5.1.so.0" even though I was positive I had it installed (even after symlinking a .so.0 to the .so). After a few minutes of head scratching, I discovered Fedora was calling it "liblua-5.1.so" (note the dash). Creating a symlink for that solved the problem (and a second one I wasn't even thinking about at that point).

[chief1983]

Ubuntu 10.04 LTS 32bit.  I'm not surprised there's some differences between a Redhat distro and a Debian distro.  There was some talk about possible ways to fix the problem, but I don't know nearly enough to tackle it myself.

[Admiral LSD]

It's the kind of **** anyone who uses Linux is more than used to (that doesn't mean it's acceptable, but that's another topic entirely...), I was just curious as to where the issue was creeping in from.

[Admiral LSD]

I upgraded the FSPort files on my MacBook to 3.2 last night and I noticed a couple of the HUD elements, namely the speed gauge and the threat indicators are being drawn in the wrong spot. Switching back to the retail campaign and they get put in the right spot, which indicates it's a problem specific to the Port, but I don't recall seeing it on Windows, so I have no idea. I'd post a screenshot, but I lack a PrtScr key to take one with :/ Any ideas what might be up?

[chief1983]

Cmd-Shift-3 can take that screenshot for you.

[Admiral LSD]

That works in 3D? Neat. Will post back in a bit

[Admiral LSD]

There we are. I just realised, going in and taking that, that I was referring to the wrong gauge when trying to describe it on IRC That said, both the two I was confusing seem to be in the wrong spot, so it's not all bad 

[Kolgena]

I don't think there's a HUD_gauges.tbl for FSPort yet. If I'm wrong, then I'd really like a copy.

[chief1983]

Shouldn't matter.  The default layout probably shouldn't be breaking.

[Dragon]

There's a HUD table included with FSPort.
And it screws things up.

[Admiral LSD]

I just checked with the Port on the Windows computer, same issue. Which is odd, since I could have sworn it looked fine when I first started using these builds...

edit: I should add here that I did see the post above this one, just mentioning that my initial belief that it was specific to the Mac was wrong, which jives with the above explanation.

[Maverick]

Problems with the target information monitor, the system/turret targeting is off, screens to follow

[FUBAR-BDHR]

I've noticed that as well but even before the new HUD code.  Can you check with trunk and see if it's the same.  I haven't tested it myself with retail. 

[origin]

Just wanted to say thanks this is really a good thing something that I personally was hoping for.

[Sushi]

Might be a widescreen thing? I've noticed the same problem, half the time the bracket in the target window won't even be on the ship (it looks like you're targeting empty space near it). I think it's been happening since before Ant7, but I'm not entirely sure about that.

[Galemp]

There's a HUD table included with FSPort.
And it screws things up.

The FSPort hudgauges.tbl does nothing but specify Hud Style: FS1. I've been asking ever since this HUD code was made public for someone with knowledge of it to make a FS1-style compatible HUD. This way we can put the code to immediate use by assigning FS1-style HUDs to the Hercules, Ulysses, Loki, Zeus, Medusa, and Ursa in the FS2 Media VPs.

I've taken a few cracks at it but there's a conflict with the TopArc and the Laser/Missile Warning Indicators that's stumped me. I would really like someone with access to the code itself to try it.