AvgWhiteGuy

@BIGNEWY....my mistake...all good now. A FOD inspection found a static object in the way. The 'suddenly TILT and WaveOff' was a Fouled Deck issue, my apologies.

@BIGNEWY...it's a little bit late when I get TILT...On the Glidepath, Call the Ball, On the Centerline....suddenly TILT and WaveOff!!!!!! Happening almost every time. This is SP.

@Dangerzone ....maybe you can provide a little more detail of your V/A-Vaicom solution, I'm using it a lot more and curious.

I understand what you're saying but my goal is all about providing a better visual perspective of the whole approach, lineup process without the added complexities of weather, the night time degradation of depth perception and other distracting variables in and outside the cockpit. A pilot (sim or real) may make 100 daytime traps but the 1st couple night or sloppy soup weather traps has a pucker factor of 9+, so by being able to see the whole process we might reduce a couple pucker factors and allow more confidence, especially since we can merge the instruments with our real vision...in our brain. Keep in mind this is only an initial training mission. Personally, I have <profanity>ty vision from a detached retina (and age), and others have similar limitations. We should all want members of the community to improve their flying skills and enjoy what they are doing. After reducing the associated frustrations and building that confidence we can move on to the next challenge.

That seems strange IRL....I would think that new aviators need to go thru Case III in daylight Case I conditions. I set up a mission at 13:00 and get Case III (with the COMS) by adding a little fog. The Long Range Laser Lineup is visible at 20+ miles and I'm trying to limit the fog so the flight deck is visible at 5 miles. Trial & Error... The goal is to get the carrier as visible as possible for Case III ACLS recoveries as a training aid for some of us mere mortals that would appreciate a bit more visual perspective in improving our carrier landings. Whether pilots use ACLS or not is up to them, I can see some using this as a tool to get more confidence in general carrier landings before stepping into the intimidating darkness of real Case III. I'm not advocating a feature option for regular flights & missions, just for training. Any other suggestions would be greatly appreciated. I'll post the MIZ after I tune it a little more.

Does anybody know if there is a setting or LUA entry or ??? that would allow-provide for the carrier to operate under Case III landing protocols even in a brilliant beautiful sunny noon environment? I would imagine IRL this is done with newer pilots and training, and it provides a much better visual perspective to view/experience the ALCS system as well as other aspects of carrier landings.

@dark_wood...you're right on target here. Lot's of information that is greatly appreciated. I'll read thru it and start to build some templates WITH documentation so others can use and augment to their particular needs. Thanks very much,

@dark_wood...appreciate the info there, did go and try that option but looking for more information. I want to understand what units are required to be 'paired' with other units in order for them to work effectively. What SAMs need 'eyes & ears', and which dishes interact with which SAMs. This may be more of a request for info than a request for a MIZ or template. And thanks again...

Does anyone have a template or diagram/document of SAM site configurations, something that shows the relevant units assembled in a small, medium and large air defense site. I want to build some templates for SAM sites but don't want them filled with senseless units that would not normally be integrated IRL. Ex: I wouldn't imagine wasting 5 MBTs protecting a SAM site that's 50km from the front line airspace. What types of units are networked together, where/why do I use one unit vs another. Which units might require a network to another to be functional? Excuse my ignorance but I'm not sure where to find this info.

Update after testing...it's even simpler now than Suntsag's YT posting. I added 2 Ka-50s to the convoy, set one as CAS, the other as Escort, and set both of them with different altitudes. In Advanced (Waypoint Actions) I set different Forward Distances. All went well EXCEPT regardless of the Altitude setting, they both descended to about 325-360 ft within a minute. One did attack-destroy my UH-1 sitting idly by watching...as expected. If anyone knows how to set them to maintain altitude it would be great...can't imagine 350ft as good escort altitude....would be a pretty easy man-pad shootdown.

Thanks Dark_wood, I'll play with that tonight. Should've known that if it can be done, has been done Suntsag did it. Cheers,

Anybody ever try having an AI helo escort an AI road convoy? Maybe a Hind escort a column of red tanks at XXX altitude in a circular or ??? flight pattern. Is it possible? In essence, can you 'attached' an AI air unit to an AI ground unit or group as it moves? I'm trying to set up mission with this in mind and would appreciate a clue or two.

Anybody ever try having an AI helo escort an AI road convoy? Maybe a Hind escort a column of red tanks at XXX altitude in a circular flight pattern. Is it possible? I'm trying to set up mission with this in mind and would appreciate a clue or two.

Sad, the CBU-105 would be such a lovely way to clear the beachhead......what were they thinkin?

Thanks to ALL of you, my problems have been resolved. Although my issue had nothing to do with VoIP (I fly solo in my cave) you left crumbs to follow with respect to beta updates and PPT assignment on the TM HOTAS. My assignments were correct but it seems the beta update might have scrambled some things in VAICOM. After updating VA & VAICOM thing are much better, and responses (audio & text) are back. Now I need to re-train speech and dial it in as the VA/VAICOM combo doesn't recognize about 90% of what I say. I guess I need to dive back in and go thru all these programs again. In any case I do appreciate your help, suggestions and 'crumbs'. Fly safe, wear a O2 mask, maintain safe wingtip distance....cheers my friends and a Happy New Year to all!

@Yurgon.....appreciate the response...I'm pretty sure I have it set up right since all work fine in F/A-18....responses from ATC-Carrier-Chief all give me verbal and text feedback. It's only the A-10CTK that give no responses. Maybe I'll just toss together a simple Startup-Taxi-T/O and lading to test both aircraft again and forward if still problems. Thanks again,

I have an issue with no audio or text response from ATC using comms on the A-10C Tank Killer. In contrast, there are no problems when flying the F/A-18 in the same mission...all works as normal with ATC, Carrier, etc. Whether I'm using the Functions keys or VoiceAttack, the results are the same...nothing. I know my messages are being received in most cases with F-keys because the options change accordingly. For example, if I request Engine Startup, that option is no longer display but the next appropriate option of 'Request Taxi' is, after this the next option of Request Takeoff/Abort Takeoff is then displayed. There is no text displayed in the upper left corner at any time indicating the ATC response. I have limited verbal response from 'Chief'; he'll give me external electrical power but won't Rearm-Refuel. There I need to use the F-keys So in the same mission with both A-10C & F/A-18 flights available, only the F/A-18 comms function as normal. I'm sure it's not a bug...I just have something setup wrong? BTW, Easy Comms is ON. Any idea of where I start this hunt for resolutions, Appreciate your help.

Is it possible to set an AI E2 Hawkeye launch from a specific CAT at mission start, or even delayed b xxx seconds as an Event? I noticed that if I set MY aircraft to Take Off from Runway, I get moved over to CAT 2. Can I set which CAT for either aircraft. I would really like to launch BEHIND the AI E2 Hawkeye on CAT 3 if possible....for the effects of the mission, storyline, immersion. If it matters...this Single player mission has no spawning later in the mission from the CVN.

Unless I missed it somewhere, it would be great if we could lock/unlock units after we place them (and their waypoints) and are satisfied. With all the waypoint displayed it get a pretty messy when you click and Delete 1 waypoint and find out you did the wrong unit(s). Or maybe be able to build and organize in layers...like an Adobe Photoshop or Illustrator project. It would only affect Mission Editor, not even be visible to the DCS.exe And finally, UNDO...I'm sure everybody has been asking for this editing feature!!!!

I'm not sure what you mean by 'atomic write' but a option for a 'versioning' system would be great whereas it saves in increments.

Have you tried the COMS menu....I think there is a 'Request Launch' or similar in there. I've had this happen until I discovered that.

@Grimes.....trying that now....it seems that the logic should be that the smaller groups and their waypoints are actually the templates that fit into the 'big picture' since most my zones and triggers are in the big one. Am I close????

AH............that's a lifesaver, I'll give it a try Thank you very much...

Can you merge 2 missions if they are on same Terrain? Simple Example: Mission #1 - has 1 F/A-18 on Carrier (Caucasus) with a flight plan of 3 points to land at Batumi. Mission #2 - has 1 A-10II at Vaziani with flight plan of 3 points to land at Sukhumi. Exactly same Start time, weather...all other variables. The reason I ask is that in the learning curve of missions I sometime test an idea or concept then want to incorporate in the 'big picture'. So I might have 3 different 'beta' missions I would like to merge. I'm sure it's not a function but is it something that a little NotePad++ could do?

@AG-51_Razor......yes, all good for me also now. I'm an amateur at this 'skinning' thing but learned some things here. I love the hummer Follow Me but another Follow Me in another MOD (Civil_Objects_JR_1.95) works much better at night with flashing lights. I got a whole line of 5 driving down the runway...looks cool as shit!!!