Bonz

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.

As someone who has done both ... RL and Sim traps ... what's missing is the physical sensation of deceleration and being thrown forward into your straps... Not something even Navy RL simulators can duplicate. I would focus Future Super-Carrier improvements on the AirBoss station, better CATCC operations, ACLS, the Burble effect and pitching and rolling decks.

The perfect place to add a Naval Air Station in DCS is on the Nevada Map. NAS Fallon is already within the maps scope. It's visible in ME... I have a mission that uses the Fallon Bombing Ranges. The airfield itself would have to be upgraded to a functioning airfield within DCS... But I can't imagine that would be all that difficult. Probably more of a priority issue. However, you would probably want to upgrade the city of Fallon as well... with just a bit more work ED could add the RENO area with Stead Airfield... for all those folks interested in doing Air Races and Airshows. All Naval Air Stations, that I've ever flown into have IFLOLS (Improved Fresnel Optical Landing System) including several Overseas Airfields. The IFLOLS is mobile and could be added to any airfield that US Naval Forces use routinely.

I see that... I thought I had, but didn't see it. Thanks.

FLAPS Light on lower left panel This light should come on with the Battery on and no hydraulics is available... It's a critical step on the aircraft shutdown procedure... The light should come on when hydraulics reads zero on both systems and the Battery is still on. Only then can you turn the Battery OFF. Ref: III-7-35 of the NATOPS Flight Manual. There is a WARNING... WARNING: Turning battery switch 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. I suspect that the FLAPS light should also be on during startup with the Battery on and no engines running (No Hydraulics).

The OFF position should turn the radio and the channel indicator OFF... but doesn't...

FLAPS Caution on the Lower Left Instrument panel incorrect The FLAPS (amber) indicator caution light on the front instrument Panel should illuminate after engine shutdown prior to securing the Battery due to Lack of Hydraulic Pressure. It likely won't come on right away but the pilot should verify that the FLAPS light illuminates prior to turning the Battery OFF. Reference NATOPS Manual paragraph... 2.8.4.3 Flap Position Lights.

I have the "Use custom DCS Path: checked even though it is the default path... C:Progrm Files\Eagle Dynamics\DCS World OpenBeta. This did not correct my issue... the menu continues to cycle and although what I say is recognized... nothing happens in game.

One additional statement on development of complex projects. I had the chance to fly the Hornet before leaving the Navy back in 89... I had been an A-7E pilot in the fleet in my first assignment and an A-4/F-5 adversary pilot in my last assignment... Fortunately I left for a job where I could continue to fly small jets. In this new job I helped install three completely new cockpits in two different jets (T-38 and WB-57). Rarely did I ever fly a feature complete aircraft. Everything I flew, was continually looked at by its community for ways to improve and update it and make it better for its current mission... that includes some very old aircraft (The WB-57 was originally built in the early 50s). Having a feature complete F-18C hornet in DCS is the utopian vision of how things work. For me, I just love having the opportunity to fly this aircraft (even though just a simulator) after deciding to put family first by leaving the Navy for a job with more home time. I was able to fly real world aircraft for 40 years... I left happy. Thanks ED for doing what you do... Keep it up.

Glad you did the survey... Nice to know ED's future focus... Great job on the SC... seems to have added signficant stability to boat ops... Press-on

Why do we still have to reset the export.lua file to correct this issue... Is it something that Voice Attack and Viacom creators can discuss with ED and DCS World to develop a solution? Is it something they can place in the Saved Games folder so that it isn’t changed with every update? Just asking... obviously, not a programmer.

I’ve got this same issue... I’ve had this issue... It’s been around for quite some time... Is the “fix” truly deleting the export.lua file each time? It seems that we are not fixing the problem but just temporarily hiding the symptom! Is there a real solution for this issue?

In a related issue, to my previous submission about Voice Attack recognizing what I say but taking no action... The DCS comms menu cycles in view and out again about every 7 or 8 seconds. It does this despite my having selected in the Viacom Pro plugin to HIDE MENUS. Another possible clue to what’s happening is that Viacom Pro doesn’t always recognize the MODULE I’m in... This program is very useful when it works, but it has high overhead to keep working. I’m hoping that it’s just me not having something set correctly... just need to find out what that is. Hollywood 315... I reviewed your FAQ#4 earlier... I learned a few things and would like to see your FAQ 1-3... but so far haven’t been able to locate them.

Recognizes Command but takes no Action Recognition of command (evidence in Notification window) but no Action... I've been using Voice Attack with Viacom Pro for a long time. This particular problem keeps coming back... I search for a fix and think I apply it correctly … the problem disappears for a few days, but returns... So I guess I just don't understand what's causing it and/or I'm applying the fix incorrectly or applying the wrong fix. Can someone help me understand this issue and hopefully help me solve it permanently.

I'm not running in debug mode any longer … reinstalled VoiceAttack and Viacom Pro and still get the "UNABLE TO ACCESS COMMAND, COMMAND NOT AVAILABLE (Chatter)" notification in the notification window... Chatter is in the VIACOMPRO/Extensions folder in the Voice-Attack Apps folder... However, I don't see it in the Extensions Packs folder in the application in the "Edit a Profile" window within Voice-Attack.