A more accurate description would be a WVR IRST with MAWS & MLD functionality.
LKF: All but 7 of the 1800+ F-35 flights to date (including the nighttime refueling ones) were done with VSI’s helmet.
The problem with 360 AESA would be that in order to detect, you have to emit. That is like suicide for a VLO environment. You would basically be broadcasting a shoot-me beacon wherever you go. It also does not solve the navigational-aid function of NVGs.
The cameras themselves work just fine and provide near 20/20 visual acuity. The part that was having the problem (I did say “was” because many of the issues VSI “was” having are already fixed) was displaying that video image in the helmet and did not affect the mission computer’s ability to use EODAS info.
btw, My cellphone has an 8mp camera, so if EODAS does half that I will be happy. 😉
To followup on Phaid’s great picture, the F-35 mission computer takes the feeds from all 6 cameras and merges them into a single stream of data. Wherever one FOV overlaps another, the computer will merge the two so that the seam is not noticeable.
When the pilot moves his head (regardless of where his head is in the cockpit) the feed being sent to the helmet changes to match his forward FOV.
To get an idea of how this works, check out this 360 pic http://voyager360.com/
This Northrup Grumman vid shows the planed EODAS capabilities with actual usage at the 4:17 mark.
http://www.youtube.com/watch?v=CwvnhFgzIKI&feature=player_embedded
One thing that the NG did was to move the main landing gear to outer blisters. They then put two fuel tanks into where the gear used to retract.

There are 6 IIR cameras located around the F-35 called EODAS.
The helmet tracks where his head is pointing and displays the appropriate view in the HMD.
That is the definition of an SDD program.
Yes, but the F-35 also has passive range determination capabilities.
Sure, you can throw a God’s Eye View of what the DAS is seeing on the panel. But how do you display range when you don’t always know what it is (or with different degrees of confidence)? How do you show elevation?
The 360 video display of EODAS imagery in the HMD is more of a navigational aid than anything else. The real core of it’s capabilities (auto tracking of WVR stuff, MLD.MAWS, etc) is all handled automatically and does not depend on what helmet is being worn. BAE’s temp helmet will still provide HUD info, cuing, and NVG capability.
I never said the problem solved, just that there is already a fix in the works.
Hey, where are the sources for the body-lift stuff you were selling us a few pages back? You went all quiet on that (probably because the source is a gamer on a fan page).
I don’t have time at work and my home laptop is on the fritz until I can get a new one next month to do detailed research.
The 360 IR data can still be displayed in the HDD (Heads-Down Display), the backup helmet will provide legacy NVG usage, and VSI is already working on the fixes to bring the original helmet back.
It takes longer to develop planes because they are more complex and we don’t accept loss of life if it can be prevented. This is why you will not see planes going supersonic, no fancy maneuvers, etc on their first few flights.
The short term costs associated with development concurrency and lowered LRIP build rates do not directly affect what the next LRIP or FRP is going to cost.
For example, you could redesign a part a dozen times, but when it comes down to what that parts costs to make, only its direct mfg cost is applied (not dev costs).
Lack of ca$h?
Aim-9X is Increment 3.2B which is to be ordered in 2016 for install in 2017.