[Kolgena]

I must say that looks kind of strange. For FSPort, I think it's imperative to keep the round central HUD stuff round. It's a little easier to fudge in FS2, and since most of us have played on stretched HUDs for years, we don't like the normal squarish looking central stuff and at least The_E has opted to keep the rectangular center stuff.

[rscaper1070]

That's pretty good. Just raise the threat indicator height to almost the same as the wingmen gauge and that would be pretty close.

[SC4RY_Z0MB13]

I decided to open a picture of the hud from Freespace 1 to try and guide my next iteration. I was very surprised to see how nice the original hud looked. The central gauges may not make a perfect circle, but they do not make some kind of weird potato. The new code is below.

Code: [Select]

+Afterburner Energy:
Position: (498, 439)
+Weapon Energy:
Position: (854, 439)
+Throttle:
Position: (570, 417)
+Weapon Linking:
Position: (791, 413)Of course a picture is worth a thousand words.

The obvious problem with this compared to FS1 is the threat indicator gauge is still too low. Now the oval FS1 created is bigger horizontal than vertical.
I don't want to move the threat indicator upwards since the hostile, missile, and target triangles are directly above that. Above those we have the objective complete gauge and above that is the players hull and subsystem status.
Most of the gauges seem off center, just look at this shot.

[Kolgena]

Does anyone have the original coordinates built for 640x480? I could modify my calculator and spit out something as close to the original as possible.

As a side note, it's bugging me that the ETS gauges will look screwed up without the shield gauge. Without new HUD builds, FSPort used to have the two gauges lined up nicely without the gap in the middle (similar to how things look when you're in subspace). I'm wondering if it's a code problem that's preventing us from doing the same with the new HUD code.

[Buckshee Rounds]

I'm getting this problem where any sound played, except music, gets doubled. I've tested this with and without the build and on different mods. It's definitely Antipodes that is doing it. Also, the speed and warning gauges are now coloured differently. I'd like it set back the way it was:


Before -

After -

[Kolgena]

What do you mean by doubled? Could you describe what you're getting a bit more? If EAX is turned on in your launcher, then you will get reverb sound effects. I'm not sure if that's what you're experiencing or something else.

I notice that you're not using a HUD_gauges.tbl with your setup. It probably won't make a difference to the coloring problems (which as far as I can tell are only affecting your left/right center brackets), but do you want to give that a try just in case?

[Buckshee Rounds]

How do I setup a HUD_gauges.tbl? Oh and turning off EFX solved the sound problem.

I really liked having the left and right parts of my HUD the same colour as the reticle so I'd really like to remedy this if at all possible.

EDIT: HUD_gauges is in there, I can tell it's working as the HUD has been bandied around on my current resolution. The colour problem still presists though. I'd really like it back the way it was.

[pecenipicek]

go to options, hud section and check the colors there.





[edit] actually, yeah, there seems to be a subtle thing there, possibly a bug, but still try and do what i said above

[Buckshee Rounds]

Yeah I checked again Peceni the colours for the warning indicator and throttle only apply to the whole sort of HUD element thing they're in, but they used to have the colour of the reticle. Ack, I'll just play as is. I can't play FS without Fury's lighting settings now!

[Kolgena]

You know that older builds should still work with Fury's lighting tags (if that's what you're talking about). Edit: Nm, realized you meant Fury's post-processing stuff.

They'll have stretched HUDs though.

[Zacam]

If there are no technical build issues involved with the HUD Code (aside from the aesthetics of getting a working config), then this is absolute Last Call for any problems related to the HUD Overhaul code before it goes Trunk.

Repeat: Last Call for any HUD Overhaul build problems

[chief1983]

What Zacam said

[pecenipicek]

Zacam, what about this?

[SypheDMar]

Yeah. That bug is easily reproducible. Although the new HUD build does what the HUD config shows it's supposed to do, it doesn't follow what the other builds do.

[Swifty]

I'm really not going to take the time to "fix" that. For the greater good of code sanity and modularity, those two arcs are not considered as an extension of the center reticle. The two arcs need to be considered separate from the reticle and from each other in order to make them easily modable.

I've thought about this for the one year I took working on this rewrite. But then I saw that this new behavior is consistent with the highlights for the Throttle and Threat Indicator in the HUD Config anyway. The HUD Config screen makes the impression that both elements in their entirety will be affected by the customizations when selected. This old inconsistency was actually a bug depending on how you look at this.

[Kolgena]

Well, the go-faster code is not at all related to the HUD code, but I think it causes heavy stuttering when head anis are played. Head anis are HUD elements so it might be relevant

[chief1983]

If it happens in trunk and Antipodes 7 though, it's not related to this code thus far.

[pecenipicek]

I'm really not going to take the time to "fix" that. For the greater good of code sanity and modularity, those two arcs are not considered as an extension of the center reticle. The two arcs need to be considered separate from the reticle and from each other in order to make them easily modable.

I've thought about this for the one year I took working on this rewrite. But then I saw that this new behavior is consistent with the highlights for the Throttle and Threat Indicator in the HUD Config anyway. The HUD Config screen makes the impression that both elements in their entirety will be affected by the customizations when selected. This old inconsistency was actually a bug depending on how you look at this.

could you maybe add it to the hud coloring screen then?

[Swifty]

could you maybe add it to the hud coloring screen then?

That's not a possible solution. Each gauge has a single reference which ties it to the HUD config. The Threat Indicator is it's own monolithic gauge. A gauge having multiple HUD config references just will not work.

[pecenipicek]

ah. very well then


i see that this was merged to trunk three hours ago, will compile and test it just in case