SmirkingGerbil

This is the fix, found it on SRS Discord server from @Ciribob My HOTAS Mic button still doesn't work, but I can comm again!!

Since you found my thread, posting here of all the things I have tried to get my A-10CII to function on any level with comms since Beta drop. Also posted in DCS Voice Chat sub forum.

Might be wrong place, but trying here to see if there is a solution. If extraneous or not applicable, have mod remove. Thread below, but the nutshell is as follows: Stable works, SRS works with Stable, HOTAS MIC switch works with Stable in A-10CII. Mods and all. Latest OB, HOTAS (Thrustmaster) MIC switch ceases to function will not manipulate in game at all. Buttons and SRS will function in Multiplayer lobby, but as soon as I hit "Fly" and in game, button mapping ceases to to work in game/cockpit. F-16 works, F/A-18 works. I have done a full repair, removed obsolete files to "backup". Disabled all mods. Scrubbed export.lua of all entries (it is blank). Tried only MIC (menu call) mappings, MIC switch no longer functions. Tried VoIP PTT Radio.1, .2, .3 etc. MIC switch no longer functions. Tried Voice Chat enabled, or disabled with above settings. MIC Switch on HOTAS no longer functions or reacts to input. All other buttons and switches do.

I may not be following your meaning correctly. Do you mean uncheck the VoIP chat option under settings? I have also under keyboard and control settings binding removed all references to PTT VoIP R1., R2. etc. This morning I did a full repair, moved obsolete files to backup folder, disabled all mods, and even removed all references in my Export.lua to anything (it is empty now). Still can't get A-10CII HOTAS Thrustmaster MIC switch to work at all. Single player or Multiplayer. What is really strange, is the F-16C and my F/A-18C comms menus and HOTAS mappings work fine. Only the A-10C has been affected by this OB update. At my wits end with this problem. See above. I have done a full repair at this point, removed obsolete files, scrubbed export.lua, disabled all mods. Still broken. What is really strange is F-16 and F/A-18 work.

Yeah, I am getting similar results, but in my bug post, even weirder stuff. No matter how I bind my HOTAS Mic switch now, it never moves in game. All other key and Thrustmaster bindings work stick and throttle. But my MIC switch never moves now. I did a repair, no luck.

Ever since the new Beta drop, I too have had issues with comms, but in a different matter. Has to do with the complete change and designation of MIC button function vs. VoIP MIC function. MIC forward/aft/down is now flagged as (menu call), where before it was for actually toggling comms. That is now moved or relegated to (or I am assuming as no documentation supports what I found in key bindings) VoIP Radio PTT.1, .2, .3 . . . and so on. I detailed it here:

One more errata. Latest Stable on Multiplayer works fine for key bindings and SRS. Only having issues on latest OB, with the new bindings and multiplayer with MIC switch on HOTAS of Thrustmaster in A-10CII. Haven't tried A-10C old.

Another element that is odd. With key bindings mapped under VoIP and A10CII Real, + SRS, when I bring up the SRS overlay, you can see that the radios show no binding (amber light), but SRS is registering the default radio channels above the overlay. What is really eye catching is if I enable the IFF Transponder, set to Normal, it does register in SRS! An Export. lua problem?

Here is a track file, from a multi-player server. SRS is running, buttons are mapped, and can be remapped correctly. I do an autostart, when radios get power, SRS shows in top left corner with frequencies. I manipulate ALL the switches and hats on the Throttle HOTAS, all switches buttons work except! For MIC switch! With the (call menus) MIC mappings, they do come up when I move the MIC switch, but the MIC switch does NOT move in game. CA_Intervorto_v1-20211224-055326.trk

This may not be the place, need to start somewhere. With the new Voice Chat, VoIP addition, A-10CII mappings for MIC switch are very different. Also, my MIC switch no longer shows activated in any direction, in cockpit/game no matter how I map my MIC switch on the HOTAS. Of course, before this drop of DCS 2.7.9.17830 Open Beta, SRS, all my button mappings worked, and my MIC switch showed changes in cockpit/game. Now nothing works, no matter my settings. There is an entirely different menu under setup now for VoIP and radios, and the standard HOTAS MIC mapping for A-10CII real, is now qualified as "(call radio menu)" - not just MIC forward/aft/back/down. None of this is covered in the PDF for VoIP. I have done a Repair. Very frustrating, cannot comm with teammates in SRS, MIC will not key, etc. Examples of completely new menus, and no explanation I can find anywhere of how they are supposed to interact or be independent of each other: Any insight would be greatly appreciated: New Menu call MIC and VoIP binds . . . they appear to be completely independent of each other

Seriously? I got a hangnail the other day.

Ohhh nice! Figured the X-Ray damage and damage decals weren't one to one. Sweet!

Nope, lots of people feel the same way, including myself. Silver's thread is the go to, to get some kind of idea where things are at in the DCS queue. CA is a hoot, love it, and it is getting some love (now), but they are doing a major revamp and that is exciting.

@Silver_Dragon And his Unofficial Road Map thread is your friend. Best unofficial resource we have for all things DCS development: Land Modules: Combined Arms (2.0 on progress) (2021+) Add IFV / APC infantry transport capability (Planned) Detailed damage model system for ground units (on progress) Infantry Improvements (on progress) Improved ground unit AI decision making (on progress) New and improved ground unit effects (on progress) Player-controlled naval units (Planned) A much more detailed ground environment

I observed the behavior that OP listed . . . thought it was just me doing something wrong (quite possible), will test and confirm.

Echoing @QuiGon - I do have 32GB of RAM, and Syria runs well for me, even on high settings. I do not have a monster system. I can maintain 60 FPS in single player, and 30 to 40 in Multi with a lot of stuff going on in the background, with Ultra skies, and SSAO etc. The real question is, have you researched the numerous articles regarding "Alt Tabbing", Enabling/Disabling device scanning, FXO/Meta Shaders folders, Clean installs, or installs on SSD's with non X86 locations for core binaries, and "Saved Games"??? Have you played around with "pre-load" and "radius" or viewable ranges? When was the last time you did a clean and repair? DCS isn't easy to play or run. It takes some research, and some tuning - but the rewards are worth it.

Lead and second (myself) working targets at night over Cyprus. Clean up operations after a successful campaign. Teamwork and coordination. View full screen, to remove any white space or bright borders, can see detail better. When milsim, and teamwork create a great session.

GM mode, in F-16. Expand, doppler offset, DB1, DB2, enhance, freeze. BWAAAA HA HA HA HA HA . . . clouds what clouds??????????? I can target anything in A2G . . . TGP (TPOD) what is that?

Thank you - all it takes is patience. I am not saying ED hasn't dropped the ball here and there, but they always come through on some level, and the complexity of their creation when you really delve into the meshing of Combined Arms, Carriers, Flight, weapons systems, radar, weapons dynamics, radio, radio interoperability between airframes (think completion of SADL with A-10 and F-16) - it is mind boggling what they are reaching for, and what it will look like 5 years from now. DCS was mind boggling in 2012, and now it just blows my mind compared to then - it will only get better.

People get sick. Their families get sick. Their co-workers get sick. The impact ripples throughout. You are talking to a network engineer that built the resources so "desk drivers" and "coders" could work from home - and production still faltered, not just with code, but many things. Peoples lives have been thrown into chaos, due to families and co-workers impacted by COVID - and their jobs too. Even "small" Indie studios, though I wouldn't characterize DCS in that manner. I deal with the impact to WFH day in and day out. For instance, lots of folks are not (drum roll) network savvy, they work from home, and their spouse or kids are on the home net. People have slow connections, or realize they have way too low bandwidth for what they are trying to do now - then you get "I build computers in school" jacking with everything while home from college and wreck the home net. We get calls day in and day out about inability to connect, and trying to troubleshoot home junk networks is a nightmare. WFH isn't some glorious cure that is going to "shatter" the centralized work place, it isn't going to go away either, but it isn't like Johnny code slinger goes home, and all his other code slinging WFH work buddies are suddenly more productive and nailing project deadline in the middle of a pandemic. First hand experience with this, from South America, North America, into Western Europe, Russia and China - code slingers and desk drivers are just as prone to impacts from COVID as a shop floor machine operator is, who cannot get enough sheet steel to manufacture product.

Man, this is the BOMB!!! Thanks so much @scoobie The light bulb went on, when I modified the file, and now (as you mention) I can see multiple options to bind "standard speed" or "super slow" in my controls panel. Really slick - opens up a new way to map controls, and identify them accordingly.

Flying DCS since 2011 as Steam version before switching over. Original Kickstarter participant of 4 aircraft. Years waiting. ED/DCS saved the project. They lost money on it. Yet they salvaged it. I just flew other excellent aircraft in the meantime. Now I am getting beautiful warbirds, and over time they keep getting better. Paid like everyone else (and then some). ED/DCS is working an entire world, ground/sea/air - extremely ambitious and far reaching. If they say they will get to the Yak, they will - fly another module in the meantime and enjoy one of the premier simulators for desk top nerds out there, in the combat arena. EA is EA. Focus changes, even on released modules. Also - COVID for 2 years now. There are always other titles if you are that aggrieved. This isn't Borderlands 3, or CoD. (I do enjoy some mindless Borderlands 3 Moze mech grind/build).

I too get the jittering switch for Boost, bound to TM Throttle button/switch.

Thank you sir! That was it! Not sure how that happened - I did not explicitly map those yet prior to latest OB. OR, I had, and prior to OB the logic wasn't working or was reversed. Prior to start, I set the switches to neutral, and viola! Fly my bird! Much appreciated. Silver lining, at least now I have functionally mapped feathering on my HOTAS! Not a bug - a problem then. Moderator can delete or move post, sorry for bother. Thank you, same reasons as mentioned for @Nealius

Load up any free flight, or Mossie mission. Engines die no matter what I try to do to avoid it, almost immediately. All was fine prior to this update. Throttles, pitch etc. mapped to TM HOTAS and stick. Thinking a "problem", and not a bug. Possibly a new mapping interfering? Any help would be appreciated, can't fly my bird. Tried re-mapping, checked Axis controls etc. Trk file attached, happens immediately after mission start. Did I miss something in the change log? Tried instant missions with my P-47 which has similar HOTAS mappings, and all is well with engine management. Any Mossie mission, you get that chugging and stuttering on near full throttle, and one or the other engine will die quickly. Video coming soon - apologies for all the background noise. Had mic on, you get to hear my chair squeaking! Comment will take you to engine failure at 1:09 - engines always drop in RPM on mission start, even with throttles full forward, can see this at beginning of vid. Happens on any mission. MossieEngineshutdown.trk