WytchCrypt

Got it working, which is great! Though it doesn't make much sense :huh: Decided it would be wise to open one of the DCS provided missions and see if I had the same problem there compared with the missions I created myself. Opened the "FA-18C/Missions/QuickStart/Caucasus FA-18C Case I Carrier" mission in the mission editor. Gave it a try and I was finally able to communicate with the Stennis! Changed the start time to 11pm and gave it another go and after accepting my inbound request the lights came on! To learn why the Stennis comms/lights in my missions weren't working and this one was, I went through all the details between my mission and this quickstart mission and found 1 big difference. In the mission editor, the properly working mission had the Stennis comm set to 127.5Mhz AM not FM. Tested this by changing the Stennis setting in the mission editor to FM and it wouldn't answer. Changed it back to AM and it consistently worked. Went to my mission that wasn't working and changed the Stennis to AM in the mission editor and it now also worked. Went back and reviewed the latest version of Chuck's Hornet Guide and saw that his Case III Recovery tutorial also was setting the Stennis to AM in the mission editor (as shown on pg 316) - a small but apparently huge thing I originally had wrong :doh: I'm very happy to have it working, but this doesn't make sense because everything I read researching this on the forum said the Stennis was 127.5Mhz FM not AM. Strange that setting the Stennis to AM in the mission editor, but setting my comm1 to 127500 FM in the Hornet is what works. I'm just happy I have it working, but it would be very informative if anyone could explain why this works :smilewink:

^ Not that I've noticed.

I've done that...set it to the default 127.5Mhz FM in mission editor...no joy. I'm also able to contact airfields successfully by manually setting comm1 and comm2 during the flight. Everything works but the Stennis...there's definitely something wrong here.

Easy comms off. Have tried setting and sending 127.5 FM from comm 1 in manual mode (as in Chuck's guide). Also tried manually setting in comm 2 just for fun. Have tried pre-setting them to comm1 channel 1 and comm2 channel 1 in the mission editor. Have tried calling with both RAlt-\ and RCtl-\. Even tried with the Stennis both activating TACN and ILCS in the mission editor as it's first actions and not. Tried while on final approach with both gear and hook down. Tried from over 10nm's out. Seriously I've tried everything I can think of and the Stennis doesn't respond to any of my calls so obviously doesn't light up. As I mentioned the only time I can communicate and get an answer from the Stennis is when I'm sitting on the deck :helpsmilie:

So I set up a night landing mission on the Stennis and even though I'm following the Case III landing guide on Chuck's Hornet manual (beginning with calling the ship and requesting inbound triggering the Stennis to light up the deck), the Stennis won't light up. I've tried all sorts of variations on this theme (inbound close to the boat, gear & hook down...flying directly over the boat, etc) and haven't been able to get the Stennis to light up once. Also can't get the Stennis to reply to any of my contact requests...except, when I'm sitting on the deck awaiting takeoff :smilewink: Is anyone else having the same problem with the Stennis?

Food for thought. I do find it interesting though that waypoint elevation is considered critical enough info on the Su25/27/33 that it is both displayed on the HUD and integrated into the ADI (description from the DCS Su33 manual): Attitude Direction Indicator The Attitude Direction Indicator (ADI) shows the current angles of pitch and aircraft roll. In the lower part of the indicator is a yaw slip indicator. Changing the rudder position eliminates slipping, so try to have the indicator in the central position. On the front portion of the indicator are the required bank and pitch indicators to reach the next waypoint. When both yellow bars are in the central position,the aircraft is following the correct route.

Thanks for the tip. I read through the nav section and couldn't find anywhere that showed the WYPT elevation being integrated into any nav systems displaying real time info on where the plane is compared to the next WYPT elevation. I guess it must be a difference in design approach and pilot situational awareness expectations between the Su27/33 and the Hornet pilots? I'd love to hear from a real Hornet pilot if my assessment is correct :smilewink:

Interesting. So it sounds like the Hornet pilot is expected to manage altitude without any automated assistance from onboard NAV systems...like they don't have enough to remember already :smilewink:

When you say, "as it is now in DCS" do you mean that the actual Hornet does display waypoint altitude on the HUD and it's something that hasn't been implemented yet?

Yes, I have seen it there. My question is more toward the way NAV mode doesn't seem to include the elevation in active guidance systems. For example, looking at the HSI screen on a DDI. It tells me the bearing, distance and time to the next waypoint but doesn't tell me whether my altitude needs correction. Similarly, the HUD tells me distance to the next waypoint and the compass tape tells me how to turn to correct my bearing, but there's no information on what my expected altitude should be. Is this just a difference in approach between Russian & American NAV systems? I just find it odd that there's no info on the HUD that guides me to the correct waypoint altitude :smilewink:

Hi all, I've searched the forum & watched youtube vids on NAV mode but haven't found an answer to this. I've been flying the Su33/27 since the early DOS days and am used to a waypoint navigation mode which takes into account not just the waypoint direction but also the waypoint elevation as part of the HUD display. Also, the crosshairs on the HSI ILS bars direct me to not just the waypoint direction but also the elevation. I've only been flying the Hornet a few weeks so still have a lot to learn but from what I've seen, waypoint elevation is not displayed on the HUD or any other informational NAV system. I know there's a way to display the info on the waypoints including speed, elevation and coordinates, but elevation doesn't seem to be integrated to any NAV system that shows me whether I'm too high, too low or just right. Could some experienced F18 pilots out there let me know if I'm missing something obvious here? Thanks! Dennis

I'd like to request that in addition to the SMK position (which brilliantly recreates the Blue Angel implementation of the smoke pod out of the left engine) that we also have the option to attach smoke pods to at least the outer pylons. I don't believe it's tasking the plane with something mechanically impossible and it would be nice to have the option. It's something I've done on the Su33 for years - where smoke pods are available on every pylon but upper center #7. Besides a fun viewing experience on replays, I've found outer pylon smoke pods to be a great tool for practicing/reviewing carrier landings to easily see from the LSO station the stability of your approach. Thanks :smilewink:

Thanks for the recommendation but no interest in VR :smilewink:

Hi all, I'm running an Alienware A51 and am considering driving a separate monitor (crazy I know, but if I do I'll build a stand so the big monitor sits directly above the A51). I'll be driving the monitor with an NVidia GeForce RTX 2070 8GB GDDR6 (full specs in my sig). Just for fun I hooked it up to a 28" Magnavox LED monitor I've had lying around for a few years and it was OK, but the text wasn't very sharp. Checked the specs and found the monitor was only 720p. Anyway, not looking for something huge (30" or less) but my main requirement is it has to be able to render the text dead on sharp just like the monitor on the A51. Recently began flying the Hornet and all those knobs and dials are tough to read on a laptop monitor no matter how great it is, especially with my 59 year old eyes :smilewink: I'm guessing since I'm flying at the highest resolution possible on my A51 (1920x1200) I'd need a monitor that could handle at least that? Also How does the whole 4K issue play into this? Price wise, I'm looking to try and stay under $500 if possible. Specific recommendations appreciated! Thanks, Dennis

Thanks Chuck :thumbup:

Great Chuck! Could you please tell us what chapters were updated by the first 4 changes (I don't need to reprint the chapters with typo corrections). Thanks :smilewink:

You're absolutely correct :smilewink: It's only available on the SMK column and the smoke comes directly from the left engine exhaust just like the Blue Angels. I guess I was just surprised after being able to put a smoke pod on every position under the Su33 except the upper center pylon that I didn't have the same option on the Hornet. Is there an actual mechanical reason a smoke pod couldn't be put on the other Hornet pylons?

I realize the Blue Angels have a single smoke source, but it's not a pod on the far left pylon, it comes from shooting oil into the exhaust. Anyway, my point about it being a limitation is other planes like the Su33 allow a smoke pod on both outside pylons, so why does the Hornet only allow one on the far left?

I wanted to add smoke pods on the 2 outside pylons of the Hornet - as I do when I fly the Su33. It appears I can only add a smoke pod on the left outside pylon. Is that correct and is due to a real-life restriction? If so, could someone please explain the limitation? Thanks :smilewink:

Guess I could but I like a printed manual so I can make notes and highlight stuff...time to admit I'm just old school :book:

Fantastic! Thanks Chuck, you're the man :thumbup:

Wow! Can you tell me which chapter's changed so I only need to print those out to update my printed version? Thanks :smilewink:

When I grew up in the 60's/70's our house was in the landing flight path of USN Moffet Field. 364 days a year that meant the drone of the P3 Orion sub hunters flying overhead...but...once a year it meant the Blue Angels! I'd climb up on our roof to watch the show. My favorite part was always the last delta pass...gear/flaps/hook...low and slow so close I thought I could touch them. By the 80's I was living in San Jose but always went back home so I could climb on the roof and watch the show. The 1st time I saw a Blue Angels F-18 Hornet I thought it was the baddest bird I ever saw. Fast forward a couple decades... Began flight sims with the YF-23 Black Widow of JetFighter II...then the Su27 of Flanker 1.0 to the Su33 of Flaming Cliffs. Loved all 3 of those birds...but...I really always wanted to fly the F-18...and now I am! Thanks ED for making my dream of flying the Hornet a reality, keep up the great work :thumbup:

Thanks Chuck...I printed it out so I could study anywhere. My plan is when you release updates when the new ground attack systems come online I'll just reprint those chapters :smilewink:

SP for me. Started with Jetfighter II/DOS Flanker back in the 90's and have never played MP. I have my fun creating missions and recording tracks :smilewink: