SmirkingGerbil

Takes practice. I know it can be frustrating as a close to the ground operator. Different approach than fasties that just boom and zoom from afar. When we fly as a flight of A-10's and get coords for a target, we always pull up short and wagon wheel to spot and identify all targets before attacking. Couple of problems though. Wagon Wheel works great, if you know what type of threats you face. If you have manpads or short range SHORADs like a Strela, 18,000 feet will keep you safe. The greater the threat range though, the higher you need to go, which creates all kinds of logistical issues. So the other approach is with a general idea of where the enemy is, to pull up short and zig zag outside of a medium threat range at about 5 to 15K feet, but if I was in a chopper, much lower would work. That way we bait the enemy to reveal what they have, but are far enough out we can evade. Dunno if the AH has a RWR like the A-10, but two A-10s working together can triangulate RWR threats pretty well. We will fly low enough we can terrain mask if a larger threat like a SA-11 lets loose on us, I imagine in a Chopper terrain masking and zig zag pattern approaches would allow you to get a fix on targets before committing?? Just some random thoughts. Or work with a flight of A-10's, as a chopper. We will do that in our group. A-10's will wagon wheel and use their TADs to identify targets and call out locations and types to the rotor guys. If things get spicy, then we engage also. Full on group working has fasties doing CAP/SEAD, A-10's working CAS and target identification and spotting, with the chopper fellas working ground targets. That way everyone is covering everyone else's weakness and allows each airframe to flex their strengths.

Every AH-D pilot in their new shiny Apache, that has armor and neat tech - learning the stark realities of CAS, and danger close missions against infantry fighting vehicles and whatnot sporting 20mm and 30mm auto cannons - just like A-10 pilots learned. Brrrt, and titanium tub don't help when a few 30 mm shells rip through your engines or wing surfaces. 2 miles is the min safe distance for mounted heavy machine guns and cannons.

Opppph, the best I can do is, do the research. Everyone's system is different, settings can vary. For instance, I now run the Reshade app, and it doesn't improve FPS, but it improves visual quality as a post processor, there are so many things you can do. Even certain maps can change all that. 32 GB of RAM should be fine, remember DCS trends in the direction of better performance via optimization over time, but overall, you do need to upgrade hardware at some point to keep pace. Try these links, there is no one size fits all. I spent a lot of time with trial and error, also google for updated articles on this topic:

Same, noticed it the other day, confirmed since then a couple of times. DSP brightness doesn't raise or lower MFCD brightness as it did in the past.

Thanks. Been here since it was just the KA-50. That is why I love this product "devs spilling over into the isle's . . . " is the antithesis of something built with passion, and a labor of love. Which is why I am here flying ED/TFC products. I might still whine every now and again, but I certainly don't want to see it stop. Keep doing what you do. When we get the radio, will just be all that much more agog over it.

Yup.

FWIW I read somewhere from a SME or other contributor that if you are going to be maneuvering hard, as you egress/ingress to a target, you should set to "INR Area" vs. "Point". I have a habit now of switching to "INR Area" in the TGP after a target run, and setting up an ingress/egress run when I know I will be nosing over hard, or banking hard to do a short turnaround to come back in on a target. Once the maneuver is done, TMS up short to switch from "Area" to "Point" - works really well. I only still have issues on a hard nose over to get pipper on a target, and my angle of attack is very steep, like 35 deg or higher steep.

Sorry on the Ninja! Was driving me nuts first day on Beta drop, I was everywhere asking for help! My handle is literally decades old, and has a long storied history.

@QuiGon Go to the bottom of this thread. Found the fix on the Discord Channel - SRS has their own Discord Channel. Started having issues from first day of OB update. MIC switch still doesn't move in DCS Beta, but this will allow SRS to function. "Allow SRS Hotkeys Always" or something like that, in pic at bottom of thread.

IAD's continuing development. Continuing development of RCS, radar modes, missile behavior, and functionality of ECM/EWR and Electronic warfare. A-10 radios please! ARC 210. A-10 HMCS Air to Air modes.

Yes, sorry forgot to mention Mission 1. Will try it with just the Mode 3/A setting. Still not clear on order of operations for Stdby to Norm. I think you flip Norm before take off on Transponder, but still not clear on when you select Stdby in which sequence of that cold start.

Which is purely my issue, bad hearing. I cannot tell, or having a hell of a time determining if I am setting the modes to M-3/A first, then to M-C? No problem with MODE 3/A code, that is clear. Plus not clear if I am setting the master mode dial to STBY before all that or during/after. Many thanks in advance.

Hey no worries, I am glad you found it! I should have updated here also. The fix is to "Allow SRS Hotkeys" so that SRS can interact with the cockpit even if the control bindings are jacked due to the Beta Update.

See above - "Allow SRS Hotkeys", you should be good.

Found the fix on SRS Discord server. Ciribob had solution. HOTAS MIC button still doesn't work, but I can comms again!!