new Big E

[Mickey_Techy]

Thank you for the heads up Micro.

Is to good for multiplay. I mean, if one person 'drives' the boat, are others able to 'see' Tacan, ILS and also use cat's.

If, for a moment, we forget the 'advanced FLOLS', is the ball visible to all players in MP setup.

Thank you.

[Mickey_Techy]

The reason, I ask is, because we are looking for a decent MP compatible boat for the group I fly with.

[GOONIE]

-The "advanced" FLOLS simply does not appear for me despite numerous attempts (It looks like the lens has been turned off).

I am having the same issue, no luck on the new FLOLS after following the instructions.

I agree, the wake is pretty bad, if you want to change the wake to the to say the Javier Nimitz, go into the sim.cfg file in the CVN65_Enterprise folder, look for the line;

[Effects]
wake = fx_CVN65_wake

Change to the wake effect you like (maybe from Javier’s sim.cfg).

I am going to remove the helo, looks like you need to remove, VEH_SH-3H_Seaking folder/file from the Boats folder. 

Things I liked are the 80's/90's traffic on deck, high quality textures with no noticeable frame rate drop. Deck also looks detailed. I also like the night time lighting, especially the centerline white pulse (rabbit) and the CAT officer gets a lighted night wand for signaling the launch. Hopefully someone smarter than me will be able to figure out how to get the advanced FLOLS (3.5 glideslope) to work not only for the Enterprise, but for any FSX carrier. Maybe the CAT end speed too!

GOONIE

[Johan]

-I can't find documentation on how change the FLOLS glideslope

It appears to be in the carrier.xml file that was installed in your "gauge" folder, and currently set at 3.6, see below partial, and in other places in the .xml file.

Johan

"</Parameters>
<!-- Moving Carriers TACAN & Beacon data -->
<CarrierList>
    <!-- Carrier List / Type = 1 -->
   <Carrier Name="Foch PA1 circa 1975"
           Sim_Name="VEH_Foch_PA1"
      CarrierType="1"
           Frequency="109.00"
           Language="FR"
           RunwayAngle="8.5"
           GS_Angle="3.6"...."

[micro]

Mickey, I really don't know about MP. As of right now I don't know of a way to "drive" the Enterprise. Also, I didn't mention it before because I thought it was me being stupid, but I can't get the ILS to come up on the HUD. As of right now, I don't think the Hornet HUD we've come to love is compatible with this new carrier.

[Mickey_Techy]

Mickey, I really don't know about MP. As of right now I don't know of a way to "drive" the Enterprise. Also, I didn't mention it before because I thought it was me being stupid, but I can't get the ILS to come up on the HUD. As of right now, I don't think the Hornet HUD we've come to love is compatible with this new carrier.

Thanks Micro.

Since I haven't purchased this boat yet, so I am just guessing here. But, looking at Johan's post above, I noticed the line that says 'Frequency=109.00'.
Default hornet or T45 have their ILS/TCN set to 57X (112.00MHz). Did you try dialing in 109.00 (or 27X) and see if it works.

[Mickey_Techy]

On second thoughts, as far as I knew (and I'm not a software person), the new Hornet HUD (versions of which are in use in stock hornet, T45, Sludge hornet and even BA bird) had the boats ILS/TCN hard coded into the HUD code. Atleast that is what I was given to understand. The ILS frequency of 112.00 was hard coded as part of the new HUD code. Maybe that's why that HUD is not picking up the Enterprise.

Folks like Orion, Neutrino, Jimmy or Sludge would be able to provide more accurate answers, I'm certain.

[Sludge]

Mickey...

No worries, I got a few answers for ya. You are partially right. The "ICLS" is HUD hard-coded to work with Acceleration default/AICarriers (111.00) and Javier's carrier (112.00), it's JR's WORKAROUND for boats that couldn't have a moving ILS/TACAN installed. If this Enterprise has a working FSX ILS/TACAN "emitting" like a land station then all you have to do is FIND OUT what frequency its sending and dial it in and the jet will actually tune in and show you the ILS needles on the HUD and on the ADI panel. Just as in Johan's post, you can see in the XML coding that the "Foch" carrier has a freq of 109.00, so you'd just tune to 109.00 and the needles should come up.

Otherwise, JR would have to "revise" the HUD code to accept this carrier and apply his method to getting a ILS/TCN.

Later
Sludge

[Johan]

According to the carrier.xml, the 4 Enterprise have each a different frequency as seen below in the extract. That makes things a little complicated.

Johan


<Carrier Name="USS Enterprise (CVN65) 82-83 cruise"
      ...
      Frequency="115.00"
            ...
<Carrier Name="USS Enterprise (CVN65) 82-83 cruise Empty Deck"
      ...
      Frequency="115.50"
            ....   
<Carrier Name="Enterprise (CVN65) 89-90 cruise"
      ...
      Frequency="116.00"
            ...
<Carrier Name="USS Enterprise (CVN65) 89-90 cruise Empty Deck"
      ...
      Frequency="116.50"
            ...

[micro]

Well, I tried all day to bring up the needles with the Enterprise; no go. Since they have the manual available for free I figured it couldn't hurt to post it here so you guys could have a look:http://www.attach2.com/Team_SDB/CVN-65_Manual_FSX.zip

[GOONIE]

Got the new FLOLS to work finally. Looks good, it actually scales, looks bigger from far away, easier to see, then gets smaller. Not sure if it was the new  3.5 glideslope or the fact the big E is a big boat, but i was consistently high on every approach, when on the ball the sight picture looks low compared to the FSX FLOLS.

No joy on the HUD needles either.

Goonie

[SpazSinbad]

'GOONIE' I don't know about your experience so bear with me please. Thanks. It is common for new pilots to 'deck spot' - hopefully that ends well when they get back to flying only 'meatball, line up and airspeed (optimum angle of attack)'. Perhaps at beginning of their deck landing careers they will fly religiously but ONCE [or TWICE] like me they will look at the 'big picture' rather than the narrow deck landing picture as described.

I did that only once [twice to be sure] but in that brief instant (between 'in the middle' & 'in close' but not 'at the ramp') I could have sworn that I was going to miss the deck completely being too high (A4G approaching HMAS Melbourne). Then later in another approach [just to be sure :-) ] I looked ahead just an instant before touchdown to think again - I'm going to bolter. Those two instances convinced me NOT to deck spot and to only fly the approach as advertised. On the first one I had been intrigued by the circular rolling motion of the deck during base turn. It was not worth thinking about again. :-)

Remember the glideslope is calibrated for the hook point trailing below / behind the aircraft main wheels and this contact at the correct spot between 3 & 4 wire is the criteria - not the main wheels as one perhaps gets used to when landing on a conventional runway. Hopefully though a Navy pilot will have an IFLOLS on the runway to practice landing by in any event. The effect of the approach calibrated for the hook but viewed by the pilot eye way above that point/path (I forget the Hornet Hook/Eye vertical distance - I'll look it up) means that - to the pilot - the approach is higher than usual (by some amount). Fly the ball all the way to touchdown.

Aircraft H/E (Hook/Eye) Distance Value in feet

http://www.hrana.org/documents/PaddlesMonthlyApril2011.pdf

Legacy Hornet -- H/E 16.35 feet
Super Hornet --- H/E 17.15 feet
Goshawk T-45C -- H/E 12.00 feet

Some people complain about me promoting my FREE PDFs. Just today another up to date version of the 'How to Deck Land' 2GB PDF has been uploaded. It is more than just 'a how to' because I know only how to carrier land an A4G; but also a history of Naval Aviation from my perspective - A4G pilot as described - so it is not comprehensive. I doubt if so much information about Naval Aviation could be found in one document (with videos). Often the info is just part shown with a URL link to what may be found online. It is more like a notebook - so follow your interests - if interested.

http://www.a4ghistory.com/
&
http://www.a4ghistory.com/HowDeckLand31july2012.pdf
OR
SpazSinbad on SkyDrive has same info:
https://skydrive.live.com/?cid=cbcd63d6340707e6&sa=822839791

Please 'right mouse click on the download URL' to 'Save Target as...' or otherwise use a download manager because the downloads can be slow and may terminate abruptly if 'left mouse click' method used.

Nice screenshot from the FSX Carrier Manual (edited) mentioned by 'micro' above attached. Plus old H/E values .GIF from: http://63.192.133.13/VMF-312/LSO.pdf

And now an old 'Carrier Glideslope Geometry' .GIF showing the 'hook glideslope': http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA087012

[SpazSinbad]

Some more  'eye glazing' material re G/S angle. 

COMCARAIRWING SEVEN INSTRUCTION 1520.1N | Subj: LANDING SIGNAL OFFICER TRAINING/CARRIER LANDING SAFETY PROGRAM

http://www.cvw7.navy.mil/inc/cmodules/dms/download-rel.php?secid=99&id=0&filesystem_id=7199

(4) Glide slope. When using the FLOLS/IFLOLS, under normal conditions the following basic angles will be used.

BASIC ANGLE    Relative Head Wind
3.5  degrees    <33 kts
3.75 degrees    33-37 kts (Hornets 33Klbs)
4.0  degrees      >37 kts sustained (Hornets 33Klbs/half flaps)
-
(5) Wind. During normal operations wind calls will be made periodically. During “ZIP LIP,” wind calls will not be made if WOD is 25-30 knots. It should be emphasised that ARB 33-12 Series for MARK 7 MOD 3 arresting gear states that “recovery headwinds” (RHW) are based on 59 degrees Fahrenheit. For temperatures above 59°F, RHWs shall be increased using the density altitude tables in the 33/34 series. ARB 33-12 Series also recommends that 6 knots be added to RHWs to compensate for variations in WOD velocity and direction, pilot technique, approach speeds, turbulence, and to minimize loads on the aircraft and/or arresting system.
-
(9) Groove length. Proper groove length is 15-18 seconds, 19-21 seconds will be grades as “little long in the groove.” If it is required to waveoff a LIG aircraft it will be grades as 2.0 points (WOP).
-
(10) Hook skip bolters. Hook skip bolters may or may not count against boarding rate. If the hook skip was pilot induced i.e., fast nose down or dropped nose to land, then the hook skip shall be graded as a bolter and count against boarding rate. If the hook skip was not pilot induced, the pass will be graded as a "no-count" and shall not be counted against boarding rate.
-
m. TRENDS. Squadron LSOs shall keep current trend data on all squadron pilots. Trends may be recorded by hand using OPNAV form 3760/71 (Rev. 7-71) or by trend output from the APARTS computer program. At a minimum, Squadron LSOs shall debrief pilot trends prior to each at-sea period during work-ups. On extended deployments, trend debriefs shall be done at least monthly. Pilots shall initial and date the trend sheet each time they are reviewed. Trend files shall be maintained on each pilot. The file should include FRS trends (for nuggets) and contain all at-sea trends for the duration of the pilot's squadron tour.
-
k. FCLP. ...Test line-up and waveoff shall be initiated at least once per pilot per FCLP period.”

[Johan]

It would be great if Serge could look at Big E and at the possibility to make it work with vLSO (granted it's ok with the authors) ... Right now, the Enterprise would be a great add to Javier's Nimitz, but nothing is in sync...just a thought.

Johan

[Johan]

No joy on the HUD needles either.

Goonie

Yes, nothing in the HUD. I changed the ILS to 112.00 in the carrier.xml and called it in the Sludge, but it didn't improve anything...