[CKid]

Hey guys, It's me again with another problem involving 03-14-XT build. My primaries and hud crosshairs does not line up. Depending on the fighter that I select, the shots are off by a few degrees. I think my hud is not lined up correctly with my screen. My monitor is not a widescreen and running at 1024 x 768 ingame.

[colecampbell666]

I get this with newer builds as well, all recent kara builds, plus Wanderer's recent build. (080611)

[Swifty]

It may be a problem with the view slewing TrackIR stuff. Can you post a screenshot please?

[colecampbell666]

Voila:


Not using TrackIR.

[Snail]

Maybe it has something to do with faulty viewpoints (or are they called eyepoints?)

[colecampbell666]

I doubt it, it happens with every ship.

[haloboy100]

Is it with all campaigns?

[Goober5000]

It may be a problem with the view slewing TrackIR stuff.

Yep, looks like you introduced several bugs with that feature.  See the first attached screenshot, for example.

There are a number of issues here.  First of all, you neglected to include the HUD_nose_x and HUD_nose_y in all the appropriate places, so the FS1 HUD no longer aligns properly.  Second of all, it looks like your HUD_get_nose_coordinates function does not default to 0 -- which it should -- when the viewer is level and pointed directly ahead.

I've added the missing HUD_nose_x and HUD_nose_y offsets in hudreticle.cpp so that the FS1 HUD now displays properly; see the second attached screenshot.  However, the centering code is still broken.  I've disabled it for the time being, so why don't you take a look and see if you can fix it.  I bet once you fix that bug, this thread's bug will be fixed as well.

[attachment deleted by admin]

[Swifty]

Nice method of lighting a fire under my ass.

Two things are affecting the accuracy of the nose calculation for the HUD. First, I scaled the ship's forward vector too small of a value. The prior calculated magnitude was probably too small to give an accurate vertex projection. Second, I forgot to unscale the projected offsets from the unconventional resolutions to the Freespace defaults. I didn't know that a gr_unsize_screen_posf existed until today.

So yeah, bug fixed. It's in the SVN repo.

[Goober5000]

Much better.

However, it's still not 100% fixed. When the viewpoint is level and straight ahead, x is 0, but y is 1.

[Swifty]

Much better.

However, it's still not 100% fixed. When the viewpoint is level and straight ahead, x is 0, but y is 1.

Okay, I've gone and scaled the forward vector by 10000 instead of 1000. I seem to get (0,0) now for the HUD offsets when centered. Hopefully that'll end this bug once and for all.

[Goober5000]

Yup, that seems to have fixed it.