Author Topic: NEW Realistic HUD for the Hornet (Read 120862 times)

SpazSinbad · « **Reply #15 on:** November 19, 2009, 09:41:04 am »

Just because... here is a new Free Video DVD zipped of mostly A4G Skyhawks doing visual landings (meatball, lineup and Opt AoA) onboard HMAS Melbourne. Most of the videos are amateur but you won't see the like of this again. Video possibly better quality than what is seen on Utube at: http://www.youtube.com/profile?user=bengello

4GB zipped A4G Ops on HMAS Melbourne DVD Video free file download was made available at top of page:

www.a4ghistory.com (http://www.a4ghistory.com/A4GvideoDVD.zip) 4GBs

neutrino · « **Reply #16 on:** November 19, 2009, 03:40:32 pm »

Spaz, the ILS needles in the HUD are referenced to the velocity vector symbol. If the velocity vector is below the horizontal (glideslope) needle, this means that the aircraft is below glideslope and needs to climb. If the velocity vector is left of the vertical (localizer) needle, this means that the jet is left of the runway centerline and a correction to the right is required. If the needles are centered on the velocity vector symbol, this means that you are exactly on glideslope, on centerline. If your position relative to the glidepath doesn't change, the needles will stay in the same position relative to the velocity vector no matter where the vector is currently on the HUD.

A full-scale deflection of the glideslope (horizontal) needle represents ±1.4° deviation from glideslope (center ball) and the localizer (vertical) needle full-scale deflection represents ±6° deviation from centerline. So the glideslope needle is more sensitive than the localizer needle. Also, because they represent the deviation in degrees, rather than distance, as you get closer they become much more sensitive, just like the ball.

Here is an example of the aircraft left of centerline and below glideslope:

Quote from: SpazSinbad on November 19, 2009, 04:58:16 am

Sludge, bear with my questions please - I'm not familiar with these systems. Do the crosshairs in the circle indicate on glideslope, lined up? I'm not complaining here, so in your screenshot as indicated by the ball 'slightly low' your glideslope indicates 'slightly low'? What is lineup info? Is that still visual? Both yours and neutrino's night screenshots are lined up so it is not clear to me about line up.

SpazSinbad · « **Reply #17 on:** November 19, 2009, 07:56:25 pm »

neutrino, thanks for clear explanation with graphic (pictures speak a thousand words). Certainly the new HUD looks to be a marvellous change. Congrats all.

wilycoyote4 · « **Reply #18 on:** November 19, 2009, 09:27:47 pm »

Glad to find another improvement for the Hornet.

Sludge · « **Reply #19 on:** November 20, 2009, 04:04:26 am »

This is to Neutrino...

As I was trying to describe, in the pics below, youll see the first pic, the GPS destination and range are displayed fully. The second, when the range increases, it starts to cut off the number. The third, at even farther range, and its almost halfway cutoff.

Will also include my "panel.cfg" so you can see the numbers I used for the full-screen (f10) HUD that stay correllated at .90 zoom. The three areas are: 1. [window titles], window00=main panel, window05=minipanel 2. [window00] 3. [window05] Cutting and pasting these to your panel.cfg file will enable a full screen usage of the new HUD.

Still enjoying the new HUD and probly flying right after writing this.
Later
Sludge

Sludge · « **Reply #20 on:** November 20, 2009, 04:37:06 am »

Spaz, this one's for you.

The new HUD works like a champ in FULLSCREEN. Check this picture out.

SpazSinbad · « **Reply #21 on:** November 20, 2009, 04:50:25 am »

Sludge, thanks for pic. Previous installation had HUD in that view always the same 'small' HUD no matter the zoom AFAIK. Can this be changed so that the HUD more or less fills the screen no matter the zoom view? It may be impossible - I did not get around to investigate in the old installation. It is still good though. Are you using a wide screen?

For example I would like the HUD to fill the screen (more or less) but be able to zoom the view as required. Does that make sense?

Nevertheless it all looks good - very much more usable for any kind of circuit to be able to use TACAN radial and needles to be close to glideslope no matter the distance from ship so that when ball is visible there is nothing much to do - except fly visually of course.

Sludge · « **Reply #22 on:** November 20, 2009, 05:00:53 am »

Yeah, Ill try to make it larger but probly wont be able to zoom cause the full screen and VC HUD have very different dynamics. Ill give it a whirl tho and tell you my results.

Later
Sludge

SpazSinbad · « **Reply #23 on:** November 20, 2009, 05:10:36 am »

Sludge, thanks - my eyes need all the help they can get these days. That is what makes the system so useful is getting close with HUD and then taking over for visual landing - rather than guesswork & being way out and when visual - too far away from ideal to recover in time....

Sludge · « **Reply #24 on:** November 20, 2009, 08:33:13 am »

Spaz...

Its not much, best I can do. Good news is that its at 1.00 zoom, so you dont have to fiddle around with it. However, bad news is you cant zoom in or out, as that causes all kinds of oddities on the correllation. Keep in mind with this new size, its "mostly" correllated. There is some minor creep up and down, but not too bad.

Just add: window_size= 0.3, 0.55 // 0.24, 0.45 and window_pos= 0.365, 0.305 // 0.39, 0.355 to your "Main_Panel" and "Minipanel" window settings to get the bigger HUD in fullscreen. Thats as far as I could take it with having to zoom to 1.5 or farther to get any correllation. The "//" rem's are just so you can get back to the first fullscreen HUD and for comparison. Enjoy.

Later
Sludge

SpazSinbad · « **Reply #25 on:** November 20, 2009, 08:46:37 am »

Sludge, Thanks. I'll have to check it out. Give me a few days etc. I'll try to make a 'scary' video again.

neutrino · « **Reply #26 on:** November 20, 2009, 11:57:03 am »

Sludge, I'll fix the GPS readout, no problem, thanks for pointing that out!

I will also include a full-screen option for the HUD, with a smaller and a larger zoom factor as Spaz requested. Just let me test it at different pitch angles, bank angles, screen resolutions etc. to make sure it is 100% conformal. I will check your numbers first

neutrino

JamesChams · « **Reply #27 on:** November 20, 2009, 08:41:03 pm »

Mr. J. R. "neutrino,"

Can the HUD read (the DATA) for an ILS on a moving carrier as well (i.e. AICarriers/Javier's Nimitz)?

neutrino · « **Reply #28 on:** November 20, 2009, 09:35:15 pm »

Yes, you can get ILS/TACAN data for moving carriers, in free flight (on schedule or placed with the AICarriers utility) or in missions, including Javier's Nimitz.

J.R.

Quote from: JamesChams on November 20, 2009, 08:41:03 pm

Mr. J. R. "neutrino,"

Can the HUD read (the DATA) for an ILS on a moving carrier as well (i.e. AICarriers/Javier's Nimitz)?

JamesChams · « **Reply #29 on:** November 20, 2009, 09:49:44 pm »

That's interesting, Mr. J.R. "neutrino!"

I was always led to believe, that with FS (all versions) for all navigation aids, that was a feature of the AFCAD or Scenery BGL files and ONLY worked with static runways. In FS2002, I use to be able to create the NAV Aids independantly of their Runways (AFCAD's). In FS9/2004 Lee Swordy's AFCAD ONLY allowed them to be implemented IF you had a FIXED Airport/Runway.

How is this achieved now? Is it married to the Scenery Object, as in the Nimitz Carrier itself, or are you adding this feature as part of a MISSION builder, etc.?

Quote from: neutrino on November 20, 2009, 09:35:15 pm

Yes, you can get ILS/TACAN data for moving carriers, in free flight (on schedule or placed with the AICarriers utility) or in missions, including Javier's Nimitz.

J.R.

Quote from: JamesChams on November 20, 2009, 08:41:03 pm
Mr. J. R. "neutrino,"

Can the HUD read (the DATA) for an ILS on a moving carrier as well (i.e. AICarriers/Javier's Nimitz)?

News: