fudabidu

Are you using a HOTAS? If so, put SRS on there. When you're in a dogfight and need help you don't want to look at and reach for the keyboard to request assistance. When talking to AI you need to use the function keys anyways. I've bound UHF and VHF to R-Shift + / and R-Ctrl + /, because it's easy to remember and quick to find.

- Small targets, like MiG-21s, are harder to detect because of their size. You might have been too far away to pick them up. - Ground clutter can further inhibit your ability to detect targets in a look-down situation. - The aircraft might have been outside (above or below) your FCR scan volume. I'm probably forgetting something, but I'm still working on my first coffee today.

You're probably looking at AWACS datalink targets, not targets picked up by your own radar. Really hard to tell because you provided NO useful information and all we can do is guess. A simple screenshot would have helped already.

That snap btw is called "detent". Everybody will know what you're talking about. The TM Warthog does have a detent, but it can easily be removed as described in the manual (loosen 2 screws, flip one piece around, done). Same with the TM Cougar, although it works slightly different. Older Saitek throttles had no detent at all, but it's still Saitek. Not my favorites. Don't know about others, because I never did the research, but it's a feature I'd expect from every mid to high end throttle.

You know what's really frustrating? This kind of response. There is plenty of information in this thread and the only response is "we're not going to fix it". So, you know this is an issue? It can't be realistic or the thread would be marked as 'correct as is', right??? And please stop with that "thanks" BS after each message. Thanks for what? Wasting so much time on the forums just to be basically ignored? Yeah, thanks for that!

"Easy comms" still doesn't work with F-16 AI wingmen. You'll need to disable it and use the correct radio buttons. Your wingmen should stay on the same frequencies as you are at the start of the mission.

Did you remember to repeat the process for the second pylon?

With "easy comms" enabled it doesn't matter which button you use or what frequency you're tuned into. Just press the regular comms button and you'll be able to talk to anybody. With "easy comms" disabled you have to tune your radio(s) to the correct frequency and use the corresponding VHF / UHF transmit button. The regular comms button will be mostly useless. AI F-16 wingmen currently only work without "easy comms", because fixing the radio is obviously a low priority for ED. In multiplayer this option is set by the server, which is another reason to get used to the 'more complex' procedure. SRS does allow using DCS' transmit buttons as push to talk, but please don't do that. Getting interrupted by clicks every time somebody opens the comms menu on the same frequency gets annoying really really fast. The comms menu doesn't ever change and greyed out options don't seem to matter at all. Just because a tanker or AWACS or ATC is greyed out doesn't mean you can't contact them. Seen it dozens of times and stopped trying to spot a logical pattern. Hope that explains some things.

Consider opening the throttle and sanding down the bump in the center to get rid of that "snap zone". Having a throttle that moves smoothly is better than fiddling with curve settings that will only work for one speed anyways.

Your R-27 clearly makes a slight right turn after launch. You probably didn't see it from the cockpit, but it's easy to see with free camera in TAC. At 14:55:32 you can see its trajectory change (very slight pull up), indicating the missile lost track. At the same time the A-10 is beaming and dispensing CM like crazy, which is what defeated your missile. Good job by the A-10 pilot. Similarly your R-73 stops tracking as soon as the A-10C starts dispensing again ( 14:55:38 ), although I have no clue where it's going. It wasn't a good launch angle anyways since the A-10's engines are rather cold in comparison and they were masked by the stabilizers at the back.

How is Deployment not for beginners? The missions are very simple and there are no serious high-threat targets throughout the entire campaign you have to face yourself. The briefings are so detailed, they almost qualify as walkthroughs. If you can read briefings and have watched Wags' (old) Ka-50 tutorials, you can beat Deployment with relative ease. GOW on the other hand scatters dozens of dangerous units all across the battlefield and leaves most decisions up to the player. I don't understand how the increased workload and threat level is supposed to help beginners. Here's a 'fixed' version of Deployment, if you wanna give it another shot. I think it's an excellent 'extended tutorial'. https://www.digitalcombatsimulator.com/en/files/3308753/

Yeah, it's a 'known issue' (lol). The pod isn't on the centerline, so it shifts the center of mass to the side and causes asymmetrical drag. Same happens if you drop/launch a weapon from just one side. This is perfectly normal. The solution is simple: manually trim the airplane. No, there is no way around it. It's aviation 101.

Try locking the target with the TGP via TMS up (handoff will fail), then switch to the WPN page and slew. So far this has fixed a 'stuck' MAV every time for me.

LGBs and JTAC codes need to match. LSS only changes the code for the TGP. The bomb codes have to be set up in the ME or while shut down on the ground, using the kneeboard. If the JTAC is lasing for you (and the codes match) the TGP doesn't need to keep looking at the target. Otherwise you'll have to manually lase using the first trigger detent

LGBs and dumb bombs work. MAVs still don't handoff properly (even when boresighted), but DMS down + TMS up helps with that. CBUs have a fixed burst altitude, but they work if used correctly. Haven't spent much time with HARMs. The Viper isn't useless in A2G just because you can't deal with it.

You have to manually "boresight" the MAVs first to align them with the TGP - Point the TGP at a target that's easy to see. - Switch to the WPN page and lock onto the exact same target. - BSGT will appear on the left side of the WPN page, press it. - BSGT will be highlighted briefly, after that the MAVs on this pylon are good to go. You will have to repeat the process for the other pylon. Ideally you'd do this on your way to the target. Just power up the MAVs, do the boresighting and power them off again.

If it's not exactly on the centerline it will create drag and you'll need to trim it out. If we're talking about the old TM Cougar I highly recommend checking the sensors, because they are garbage. They will wear off and you will get some jitter in the axis response.

Night lighting on the Shkval (and other TV sensors) has been broken since 2.5 and here we are again. Are we supposed to wait another 2 years for a fix? Good to know how much ED cares about maintaining their content. This is just ridiculous.

Thank you very much for spreading wrong information. Yes, CZ (or TMS down) will lock your SPI to the selected waypoint. That's what it's meant to do. If you want to slew your TGP you need to go into AREA track first, either by TMS up or TMS right. It's not a bug, it's RTFM

And this is exactly why one of my axes is always reserved for zooming.

I bought the Ka-50 12 years ago. The module (including the campaigns) still has issues and we even see new bugs occasionally. Do we see that fixing the module is a priority? No, we don't. Instead we get new content. And this extends to DCS as a whole. ATC, AI, performance, several long known MP issues, small things like the MPRS, almost no improvements for helicopters, CA unchanged and not even VR compatible ... there are tons of individual issues. After 17 years (LOMAC) the negatives start to outweigh the positives. I'm so sick of running into the same issues year after year. Once I see some major improvements I'll be happy to praise ED, but I don't even see anything on the horizon.

Your track doesn't contain any replay information, so there is nothing to look at. In case you don't know: the number on the HUD is NOT indicated airspeed. IAS is shown on the HUD as a scale and it comes with a small 'max speed' indicator. Easiest tool to avoid overspeed. The max speed does NOT account for maneuvering. It only warns you about a rotor clash in forward flight. Don't try to maneuver while the alarm is going off. Increase in collective and/or kicking the rudder the wrong way will most likely result in a crash (unless you know exactly how to handle the aircraft).

An external Blk.50 looking cockpit hooked up to an AM++. Since I didn't get a chance to look inside the actual plane I'm assuming they were the same. Even if the CMDS panel was indeed different, the geometry of the pit remains largely the same. Judging by the geometry I don't see a possibility to bump that switch in the Blk.50 cockpit. Would you agree with that statement? And while we got an expert at hand here: Isn't the ECM switch on the CMDS panel just a power switch and 'music' is commanded via the CMS?

Known issue. Numerous threads about it. No reliable fix. Wait for ED to finally fix the SPI mechanics.

I got a chance to lay hands on a real RNLAF F-16AM++ cockpit (remote maintenance setup) and thinking about it I don't see how you'd do that. All the switches in the cockpit require some force to flip, so a light bump isn't enough. The throttle sits higher than the switch, so when you reach towards the CMDS panel you'll always approach it from the top. Even if you turn the CMDS program select knob all the way clockwise you're not going to bump that switch upwards by accident.