Bonz

We should switch... I have three screens but only one MFD shows up in DCS Controls.

There are a few reasons why you get the amber FLAPS light (Ref. Page 1.2.57 of the NATOPS manual). 1. Flap switch HALF or FULL and airspeed over 250 Knots. 2. Abnormal Flap Condition (Any Flap is off or Lacks Hydraulic Pressure). 3. Aircraft is in Spin Recovery Mode. 4. Gain Switch in ORIDE position. On aircraft shutdown there is a WARNING (Ref. Page III-7-35 of the NATOPS Manual), "Turning the battery off before the amber FLAPS light illuminates could result in severe uncommanded flight control movement. The only cockpit indication that Hydraulics have been removed from the flight controls and that they are no longer powered is the amber FLAPS light. The FLAPS light in DCS works for three of the four conditions... 1. Both the flaps HALF and FULL Overspeed conditions, the ORIDE position of the Gain switch, and when the aircraft is in the SPIN mode. (Spin switch in the SPIN position). It doesn't work in the Hydraulics zero position following engine shutdown.

What is the latest version of this MOD?

I can see that as well. It would have to be turn on or turn off ...

The first iteration is spelled out above... Mostly to enhance the Multiplayer environment so that controllers have the information they need to "Control and Direct". Great Game so Far, keep it up.

Lots of examples above... I have the same problem... Thanks

I could also be that whoever set up the carrier may have used a frequency other than the default... that will also give you the "UTM Fail" indication following the initial TEST.

I have a mission that requires a MOD titled HESCOPACK. I added those items on an old computer and saved the mission to an Online location. When I opened my new computer and tried to open that mission, it tells me I need HESCOPACK. The thing is in both cases (Both Computers) I used the same MODS, loaded via OvGME from JTF-1. So I'm confused as to why the difference. However, is there a mod titled HESCOPACK? I haven't been able to locate it.

I have a mission that requires a MOD titled HESCOPACK. I added those items on an old computer and saved the mission to an Online location. When I opened my new computer and tried to open that mission, it tells me I need HESCOPACK. The thing is in both cases (Both Computers) I used the same MODS, loaded via OvGME from JTF-1. So I'm confused as to why the difference. However, is there a mod titled HESCOPACK? I haven't been able to locate it.

I have the solution... I attempted to calibrate using Windows. Once I realized that this throttle require calibration via SimAppPro the solution was possible. I had to go back into the Window Calibration tool and select my throttle and reset to default.

The Button functions for both throttles work fine... When shutoff both 1 and 2 boxes light up green. When pushed to Idle both circles light up green and both boxes grey out. However, My left throttle axis is off ... a lot. The pictures show both axis at OFF, IDLE, MIL and MAX. My question is... My throttle worked fine until recently ... could this be the result of an incorrect calibration or a mechanical issue in the throttle? Does anyone have a solution?

I'm hoping you can help me as well. I have a different issue, but it sounds like the remedy is the same. A good calibration. I have discord, Do you have time to help... Bonz

Is this still available? If so, I'm willing to spend $300 plus shipping to Texas. Assuming it in working order. I send particulars of necessary.

I flew the same mission again (Marianas) only this time in Multiplayer Mode with one other pilot on with me. The Mission configuration was unchanged from the one where I had success… that is with removal of the ship born AI aircraft. My wingman (same group) launched first and proceeded to Marshal at 6K and 21nm. I launched next and proceeded to Marshal at 7K and 22nm. He pushed first and completed all necessary radio calls on the way inbound. I followed a minute later also completing all necessary radio calls. My wingman did receive the Mode I and TADPOLE and coupled-up with ATC for a Mode I. He was not getting proper steering so felt he had to decouple and waved off. I never got the Mode I and TADPOLE indication so flew a Mode II approach to a bolter. We both entered the wave-off/Bolter pattern, remaining at 1200’ and turned back in for a second attempt outside 10nm. My wingman was able to couple again receiving both the Mode I and TADPOLE indications and flew to a successful trap. I had the same indications as before and flew manually to a Mode II trap.

On one of my existing missions (Marianas Map) I made the ME changes Matt outlined in his video (Activated Link-4 and ACLS and a similar naming convention), then followed Matt's video through a CASE III marshal and approach. I made all the calls highlighted by Matt and available in the Comms Menu. I got all the correct indications until six miles. At that point the ACL RDY and T/C indications remained. I did not get the TADPOLE nor did I get the MODE 1 indication in place of T/C. I tried to Couple anyway and got the above mentioned HDG indication and not the correct P/R indication on the HUD. Later I tried a new/clean mission with just the Supercarrier and two F-18c both in Client mode (two groups). I took off and flew from the deck entering the Marshal pattern as directed at 6K and 21 miles. This time it worked as advertised. So something in my old mission is interfering with proper ACLS operation at the point where MODE 1 and the TADPOLE should be active. Having read comments above, it sounds like other folks are having the same issue. Just flew another couple of flights on my old mission (Marianas Map). The first time I first removed the four F-14s I had staged on the flight deck. All four were set to spawn with engines running in the Client mode. I was playing, as I was before, in SP. For this flight, I still had two helos, an E-2D, and an S-3B Tanker (All three AI's) set to launch via triggers. The Helos and Tanker from a Cold Start and the E-2D from the CAT running. All at different times during the mission. Additionally, I still had several F-18C (set as Clients) ready to spawn. On the Beach, I had dozens of targets and several aircraft both AI and Client some on the ground but many flying in the area (Tankers and AWACS). So the only difference for this first run is that I removed the Spawn to Engines running F-14s. I got no difference... the MODE 1 and TADPOLE did not show. The second flight I removed the two Helos, the S-3B and the E-2D (All AIs) from the flight deck, everything else remained the same. This time I did get the MODE 1 and TADPOLE on the HUD and was able to couple and fly a good ACLS to a 3 wire. I did not get the "CMD CNT" indication nor did I get the "10 Seconds" Indication.

On one of my existing missions (Marianas Map) I made the ME changes Matt outlined in his video (Activated Link-4 and ACLS and a similar naming convention), then followed Matt's video through a CASE III marshal and approach. I made all the calls highlighted by Matt and available in the Comms Menu. I got all the correct indications until six miles. At that point the ACL RDY and T/C indications remained. I did not get the TADPOLE nor did I get the MODE 1 indication in place of T/C. I tried to Couple anyway and got the above mentioned HDG indication and not the correct P/R indication on the HUD. Later I tried a new/clean mission with just the Supercarrier and two F-18c both in Client mode (two groups). I took off and flew from the deck entering the Marshal pattern as directed at 6K and 21 miles. This time it worked as advertised. So something in my old mission is interfering with proper ACLS operation at the point where MODE 1 and the TADPOLE should be active. Having read comments above, it sounds like other folks are having the same issue. Just flew another couple of flights on my old mission (Marianas Map). The first time I first removed the four F-14s I had staged on the flight deck. All four were set to spawn with engines running in the Client mode. I was playing, as I was before, in SP. For this flight, I still had two helos, an E-2D, and an S-3B Tanker (All three AI's) set to launch via triggers. The Helos and Tanker from a Cold Start and the E-2D from the CAT running. All at different times during the mission. Additionally, I still had several F-18C (set as Clients) ready to spawn. On the Beach, I had dozens of targets and several aircraft both AI and Client some on the ground but many flying in the area (Tankers and AWACS). So the only difference for this first run is that I removed the Spawn to Engines running F-14s. I got no difference... the MODE 1 and TADPOLE did not show. The second flight I removed the two Helos, the S-3B and the E-2D (All AIs) from the flight deck, everything else remained the same. This time I did get the MODE 1 and TADPOLE on the HUD and was able to couple and fly a good ACLS to a 3 wire. I did not get the "CMD CNT" indication nor did I get the "10 Seconds" Indication.

First, I'd like to acknowledge the work done so far. As a RL ex-Navy pilot (A-7E) what you have done with the F-18C is really quite amazing. I left the Navy after four tours and was likely heading for the F-18C. The A-7E was at the end of its run. Having missed the opportunity to fly this amazing aircraft in RL, it's been a real joy to fly it here in DCS. The Supercarrier has been great so far as well. I'm looking forward to seeing all the new capability being planned. The recent addition of Night wands and ACLS with Link-4 is good but a few, well placed, changes could make a big difference. I agree with others who have suggested that providing a multiplayer option where AI comms are not needed would go a long way to making it more like RL. I know that the AirBoss station (Prifly) is in the planning stages and that a Ready Room of sorts was or is planned? The Airboss is primarily in charge of CASE I and II operations and so Prifly should have access to at Least one radio... two or three might be better. He also talks to the flight deck via the 5MC. The 5MC is a Mega-Phone (very loud) that can be heard all over the flight deck ... even while Jet engines are running. He should also have a radar feed so that he can see where aircraft are in overhead holding, the pattern, and approaching the pattern, including the Spin Pattern. He should also have a screen that lists aircraft by side number, Remarks, fuel state and minutes since the last fuel update. To accommodate CASE III, it would be nice to have CATCC which is where the Marshal Controller and the Approach and Departure controllers reside. It's located on the O-3 level just below the flight deck. CATCC would also need the list of aircraft by side number, Remarks, fuel state, and minutes since last fuel update. the Marshal controller would need a wide area radar picture that encompasses the Marshal Stack, out to beyond 50nm. The approach controller would need this same radar and also a short-range radar out to say 15 miles to cover final approach and the wave-off/bolter pattern. The departure controller would need the same two radars. CATCC would need at least 4 radios... to Monitor Marshal/departure/and conduct operations on two Approach frequencies. During CASE III operations, the LSO shares the two approach frequencies with approach controllers ... so that the pilot does not need to switch frequencies once below 5,000 feet. Input of fuel updates and other information could be entered/changed by human controllers, so, a means to enter/edit information by all controllers would be nice.

First, I'd like to acknowledge the work done so far. As a RL ex-Navy pilot (A-7E) what you have done with the F-18C is really quite amazing. I left the Navy after four tours and was likely heading for the F-18C. The A-7E was at the end of its run. Having missed the opportunity to fly this amazing aircraft in RL, it's been a real joy to fly it here in DCS. The Supercarrier has been great so far as well. I'm looking forward to seeing all the new capability being planned. The recent addition of Night wands and ACLS with Link-4 is good but a few, well placed, changes could make a big difference. I agree with others who have suggested that providing a multiplayer option where AI comms are not needed would go a long way to making it more like RL. I know that the AirBoss station (Prifly) is in the planning stages and that a Ready Room of sorts was or is planned? The Airboss is primarily in charge of CASE I and II operations and so Prifly should have access to at Least one radio... two or three might be better. He also talks to the flight deck via the 5MC. The 5MC is a Mega-Phone (very loud) that can be heard all over the flight deck ... even while Jet engines are running. He should also have a radar feed so that he can see where aircraft are in overhead holding, the pattern, and approaching the pattern, including the Spin Pattern. He should also have a screen that lists aircraft by side number, Remarks, fuel state and minutes since the last fuel update. To accommodate CASE III, it would be nice to have CATCC which is where the Marshal Controller and the Approach and Departure controllers reside. It's located on the O-3 level just below the flight deck. CATCC would also need the list of aircraft by side number, Remarks, fuel state, and minutes since last fuel update. the Marshal controller would need a wide area radar picture that encompasses the Marshal Stack, out to beyond 50nm. The approach controller would need this same radar and also a short-range radar out to say 15 miles to cover final approach and the wave-off/bolter pattern. The departure controller would need the same two radars. CATCC would need at least 4 radios... to Monitor Marshal/departure/and conduct operations on two Approach frequencies. During CASE III operations, the LSO shares the two approach frequencies with approach controllers ... so that the pilot does not need to switch frequencies once below 5,000 feet. Input of fuel updates and other information could be entered/changed by human controllers, so, a means to enter/edit information by all controllers would be nice.

Kitty Hawk class is slightly smaller than Nimitz Class ships. They are not Nuclear powered. However, the deck layout is similar to the Nimitz boats in that elevators are laid out the same… two forward of the island

DCS and ED try to make products that sell... presumably. They have spent boat loads of money making the F-18C and the Supercarrier... It makes sense that Fallon and China lake be fitted out on the NTTR map. People who say that we should use the NTTR map for what it was intended to be... Two things about that. 1. It was built to make money! It would make more money if it was more relevant to the Navy community by adding Fallon and China Lake. I was stationed at Fallon in the late 80's as an adversary in VFA-127... we flew the F-5E/F and the A-4E and other variants. Now the adversary unit there flies the F-18. 2. I do use the NTTR and like it very much... It's a good map. I'd like to see them make it better.

Don't feel to bad... You don't get your choice in RL either. Your aircraft is where it is and the Handler does not care what you think or want.

The launch weight board is a good idea... The value shown at the catapult could be pulled from the load you requested when configuring your aircraft in either ME or adjusted with the F-10 menu. You could then vary the aircraft end speed (end of CAT stroke) by errors in actual weight and weight approved by the Pilot during CAT hookup. There should also be a penalty for landing over Max-Trap weight... A little over - damage... or a Lot over - cable break and/or hook-point separation and damage.