AvgWhiteGuy

The excitement is killing me after reading all this thread...and I can't seem to get it work. Mission Planner has the Blackhawk Cold at Batumi but the mission starts at Ext views of another airfield. I cannot get an F1 position in the aircraft; only F2 and other views. The mission starts with the APU cranking up although I have NO settings or bindings. In other words, I have no default position as Pilot.

CONFIRMED as FIXED in v2.8.0.32937 for AI [F/A-18] launching AGM-141 TALDs, used same settings as image above EXCEPT switched 'Weapon' from 'Guided' to 'Decoys'. I'll test same mission with multiple salvos tomorrow. Thank You ED

Thanks [ED]Obi, I just receive a note from Redkite on latest update and d/l'ng now. I did see 'Decoys' in the weapon selection for Waypoint action but it didn't work on my v2.8. I'll give it a test in the next 24hrs. Do you know if the settings in above image are correct other than selecting 'Decoys'? Cheers

In v2.7..... I used TALDs deployed by an AI F/A-18 flight, then I followed up with HARMs & AGM-154 once the airspace was active & saturated. Since upgrading I can't seem to get the AI flight to release the TALDs. Bugged or some settings were change? Image is from Redkite YT video that worked for me before

My opinion on this VAICOM issue as a SINGLE pilot/player on a retired fixed income; Many thanks to Hollywood for adding such immersion over the years, and additional thanks for the decision to hand it on to others to further expand and support. We all owe a debt of gratitude to him for that. He didn't get rich doing this, do the math on 'Revenue x Licenses'; it was a passion. A possible future of VAICOM product development & support without a license fee, balderdash...continue charging for the product! It takes effort, talent, time and some passion to build/maintain this, TIME is MONEY. For those of you that may complain because you've already bought a license...it was well worth it. Divide that license fee by the number of hours you spent flying with such immersion....do the math; damn well worth it! How many beers, cups of Starbucks, packs of cigs, bags of Tostidos was that. Sorry, but you should be embarrassed by even whining about that small, token license fee. Continuing a license based product ensures a future for it, especially with a larger team and a growing community. Be happy Finally, upgrading to the 2.8 version??? I was considering rolling DCS back to 2.7xxxxxx latest version out of frustration. Then MAXsenna gave me simple instructions to d/l and install new Vaicom DLL. It took a whopping 3 minutes to complete and I was back on the tarmac 'requesting engine start' in my A-10C, F/A-18 and F-16. Thanks again MAXsenna! So please, stop the whining, do the upgrade (doesn't even hurt), praise Hollywood's contribution to our community, and go drop a BOOM or FOX an adversary...be happy.

Damn MAXsenna, that was really complex, tough exercise...about 3 minutes after d/l...brilliant. No rolling back. All my A/C are back flying again, thank you very much.

Thanks guys, I got to figure out the path to least insanity... IF "new community fixed version" fixes problem, even if it just resolves the '\' and or HOTAS Mic issues so I have COMMS menu that seems reasonable; at least I can get clearance to crank the engines. IF rolling back to v2.7.16.27869 is faster, easier and I can find an updated Skazillas Updater GUI (mine was ancient), that would give me pleasure as well. @Horns, see images regarding 'hooking'

Lost COMMS & COMMS Menu - All Aircraft Updated to latest version last week, all seemed good. Yesterday lost all COMMS menu but had made NO changes. Keyboard ' \ ' (Open COMS Menu) does nothing Warthog HOTAS MiC switches, I hear Clicks and I see there is a proper response on VoiceAttack/Viacom but it does nothing. VoiceAttack/Viacom recognizes commands...but something about 'nobody available' OrbWeaver Keyboard mapping does nothing. Batumi BLUE, No Ground Crew, No ATC MY A/C affected include ALL A-10-c models, F/A-18, F-16, P-51 I'm patient and I would be happy to role back to previous stable DCS Beta 2.7xxxxx if someone could direct me to the proper DCS_Updater CMD. I know you folks will solve it soon but need DCS during COVID lockdown in Shanghai. Anybody got an idea...please

@MAXsenna.....In the meanwhile, can I retreat to the last 2.7xxxx Beta version?

Lost COMMS & COMMS Menu - All Aircraft Updated to latest version last week, all seemed good. Yesterday lost all COMMS menu but had made NO changes. Keyboard ' \ ' (Open COMS Menu) does nothing Warthog HOTAS does nothing OrbWeaver Keyboard mapping does nothing. Batumi BLUE, No Ground Crew, No ATC Voice Attk-Viacom recognizes commands...but something about 'nobody available' @Primetime Casual...sound similar...everybody on strike or in the <profanity>ter? Anybody got an idea...please @Moderator...sorry about <profanity> but it is a US Military term, along with FUBAR

I guess as an idiot or maybe as an exclusive SP flyer/mission builder I don't understand 'spawning', and can't figure how to do something I thought would be logical and easy. MY F/A-18 is on Late Activation (5secs) sitting on Elevator 1. All other elevator slots on starboard side are occupied with statics. The mission starts with an E2-D taking off from Cat 1. I have a row of static F/A-18 sitting on Cat2 as in Minksky's image above. Then, I simply want to have a 2 ship AI F/A-18 flight taxi and launch from Cats 3-4. Right now AI F/A-18#1 waits to launch from Cat1 and AI F/A-18#2 crashed thru the statics on Cat2!!! I tried blocking Cat2 with a static, now AI F/A-18#2 just sits there waiting for ????? (not very 'green friendly') Is it that complicated? Please help.....

@toutenglisse...sorry for long delay...Shanghai lockdowns are ridiculous. I'll try this out tonight or tomorrow. Really appreciate your help on this.

Well this thread is a goldmine for anyone contemplating a Throttle disassembly/repair...thank you so much. I just lost my LASTE panel button and 3-way with nowhere in Shanghai to go for fix, at least that I know of. This will make it quite simple for someone unfamiliar with it but with general electronic skills to replace. @DeadMeat...any other suggestions ??? Cheers,

Anybody know of an authorized or respectable repair facility for Thrustmaster in China...maybe in Shanghai. Have 2 switches that suffered water damage on my throttle. 任何人都知道Thrustmaster在中国有一个授权或受人尊敬的维修设施......也许在上海。有2个开关在我的油门上遭受了水损坏。 Appreciate any suggestions,

Any update on your throttle....this sounds like a conflict between throttle and Reverb G2

Can you start a mission with YOURSELF (Player-Client) in an F/A-18 cold on the deck of a SuperCarrier while multiple AI aircraft (2) are in approach/landing. Then, after the AI are recovered/parked, you startup, taxi & launch from either waist or bow cats? I can set up the AIs and they do their thing, but as soon as I add a Client (myself) the deck is set to Launch exclusively (deck crew manning all cats), and the AIs just keep circling at 3,000ft. This all seems to occur automatically WITHOUT me initiating startup. Would it not be logical to have Recovery and Bow Cat(s) Launching at the same time? Is this a trigger thing possible in ME?

I'm just trying to figure out what I need to do to get an airborne F/A-18 AI to land on the carrier WHILE I'm sitting on the deck cold. It appears the deck is set up for Launch and not allowing Recovery. Capt. AI just keeps flying around at 3,000ft. Is this a 'trigger' thing?

@Dangerzone....sorry about delay responding but you've nailed down my problem...the COMS setup with VAICOM. This is where I need some help. I have a Thrustmaster Warthog Throttle but I really didn't set the COMS switches up correctly many wars ago. I also have VAICOM Pro with the relevant addon/mods for Chatter, Realistic ATC & Kneeboard. I want to separate COMS into 4 areas if this is possible-reasonable-logical; Forward - Radio#1, Back - Radio#2, Up-Ground Crew, Down - Internal Cockpit commands (Gear Up/Down, Launch Bar Up/Down, TakeOff Trim, & other lazy commands). Some of these Internal Cockpit Commands are needed since my Throttle has some rain damage!!! I honestly don't know how to set this up correctly....for at least the 2 Radios so if someone can walk an old man thru it I would greatly appreciate it. If the 2 images above are relevant to solving,fixing my problem please advise. Thanks,

Interesting....and quite logical...glad to hear the view of the experienced. Most those USAF planes have such skinny legs, always worried about them on landings. Love those USN F/As, look like a squatting sumo wrestler I gotta go play with this now that my tracking under full brakes is so much better.....thanks to all!

I am in awe of all of your observations, insights and suggestions along, with the speedy responses. Mimicking @rforce axis settings has effectively resolved the problems for both A-10C and CII. I did about dozen landings late last night (Shanghai Time) and she just settled down and tracked straight without incident.....much cleaner than my previous 'serpentine waggling' that was frustrated me. @ASAP...I'm still curious about the reasoning/logic behind NOT aerobraking as it does slow things down faster than the normal procedure. The only thing I can think of is it may impose greater stresses on the front steering assembly as it does come down a little harder when it finally falls. Thanks much to all of you, you're a credit to the community...!

@rforce & @horstweihrauch.......I'll give that a try first, not sure where/why I have such a big deadzone...shows my ignorance of these settings in general. Calibration (TPR external shows normal) @ASAP....reasonable speed for NWS is below 50 as long as rudder can keep me relatively straight, which seem fine in regular flight. As for aerobraking, been doing that for a while as it does seem to slow me down effectively, especially on shorter runways. I figure those long wings along with speedbrakes (100%) do a good job of that while I raise the flaps to decrease any further positive lift after solid ground contact.... I hold the nose up until it just falls down. Then start applying brakes....holding off NWS until below 50. I'm never in danger of over running, just keeping left/right on the blacktop Do I need to go back to school here.... In any case, thanks to all of you and I DO appreciate further input...

There's a thought but I really like the feel for the other 2 planes. I just don't quite understand the curvatures...might need to take a night class on that topic. Am I in the right range (in image) compared to your settings?

I've had this problem with the A-10 C & C II for a while, the nosewheel steering and braking is insanely sensitive. Obviously it's manageable during normal taxi but almost veers off the runway on landings after slowing to reasonable speeds after aerobraking to under 100mph, especially braking. My other tricycle gear A/C (F/A-18 & F-16) have no problems; I can stomp on the brakes and they track perfectly straight coming to a slow roll & stop. If I assume it's my axis settings (where I'm a moron) could someone with normal steering/braking results post an image of their axis settings. I can't imagine this is typical of these pedals or system.

@Dangerzone.....moving forward slowly...I did not have the ATC Extended but purchased and registered last night. See below. But I'm still at a loss for having no additional commands after Inbound. Is there a response in image below that gives a clue, especially 'Selected recipient is not a SuperCarrier unit' ? It's CVN71....

@OLD CROW....no, I think believe the predicate is a 'weather' related value, just ATC. I started my MIZ with more serious Case III parameters then just whittled my way down by removing them piece by piece (darkness [time], rain, cloud formations, etc...) until it end as Case I. Then I noticed the Fog and started to play with that until I got it down to the present settings in my MIZ where it retained Case III. As another test I just created a new mission on Channel map with CVN72 and a single F/A-18, default weather at 10:00hrs. On the 'Inbound' call it was automatically set for Case I. When I then just added Fog (Visibility=10,000ft and Thickness=150ft) it immediately changed to Case III. As you can see from the image below, CVN72 is clearly visible from 21mi @ 5,700ft, so the parms for Case III seem to be pretty liberal. @Dangerzone...I'm still curious how you are able to get the additional ATC commands, I'm not able to do that on VAICOM..what am I doing wrong, or did you add some commands. null