LastRifleRound

Deployment isn't much better. I get it the KA50 is old, but this isn't games as a service nonsense. It should be stable and good to play, not progressively ruined over time. I'm really disappointed I have to say. I've owned this module since 2009 and have bought it essentially twice. Soon I will be asked to buy it a third time. Official campaigns should not be allowed to deteriorate like this.

Thanks for the reply @Flappie I love the BS but the missions throw way more under your responsibility than it's reasonable for the little bird to deal with. Deployment is ok, but mission 2 was really annoying. Without labels, I don't know how you're supposed to be successful on the first try. After getting through that I was turned off from the campaign.

Can someone show me them actually executing mission 1 of this campaign? (Not the one divided in chapters). I tried everything. I don't know who I'm supposed to be shooting, the fog means I can't see a damned thing, my wingman is useless and dies or doesn't shoot anything, and won't do recon. No one talks to you so I don't know where I'm supposed to focus, then fighting the auto-hover that refuses to do anything about the wind blowing you down the valley makes it all worse. This mission feels cheap, like it's just designed to throw all of the weakest parts of DCS at you in place of actual difficulty (invulnerable trees, poor visual acuity, terrible friendly AI. In fact, most of the Black Shark campaigns feel this way.

I have this same issue. Even ACM modes struggle picking up targets lower than me

Did you guys see the A10 CCIP fix in today's patch? Looks like the same thing.

I'm glad that worked for you guys. It didn't work for me. This is what I had to do. If someone is out there, and restarting isn't working for them, maybe this can help them.

Restarting did not help me. Also, some who say they restarted said the issue returned.

Fixed this. As usual @Frederf came through in a separate thread. Apparently a well-known DCS issue I've been lucky enough to avoid until now. Here's what I did: C:\Users\<myusername>\saved games\DCS.openbeta\Config\Input\M-2000C\keyboard\Keyboard.diff.lua I opened this file, then did ctrl-f for "knee" and found the following 2 blocks of code: ["d3001pnilunilcd100vd1vpnilvunil"] = { ["name"] = "Kneeboard Next Page", ["removed"] = { [1] = { ["key"] = "]", }, }, }, ["d3002pnilunilcd100vd1vpnilvunil"] = { ["name"] = "Kneeboard Previous Page", ["removed"] = { [1] = { ["key"] = "[", }, }, }, I DELETED these lines of code (saved them along with the line number they were on, 106 for me, in case they are needed again). Saved the file then exited and re-opened DCS. It was fixed then. For a description of why this works and the history of this bug, see the below thread:

The controls for "Next Kneeboard Page" and "Previous Kneeboard Page" do nothing when assigned. Additionally, the fields are each labeled twice and in yellow. No amount of mapping or re-mapping does anything. Anyone encounter something like this? How do you fix it? No mods.

What are sinkers? Usually that refers to the mooring or launcher of a sea mine. I can't get anywhere close enough to the target area to see anything before I get launched on by SA6. They tell you the limit is 14nm, but I'm getting shot at 25nm. I couldn't see anything at that range.

Yeah but that's what you're given so that's what you use

Yeah usually the enemy has to do something though, since we're not simulating actual missile technical failures yet. Like maybe dispense some chaff, jam, or, I don't know, not just lazily dive at 10 degrees at 10nm. Unless they want to make R27's randomly miss, too, as I'm sure they did/do in real life as well. Anyway, RCS used to control when the AIM120 turned on its seeker head in DCS. It might still do this, I haven't tested it in a while. Since the AIM120 used to be hilariously easy to notch, I got in the habit of delaying when the seeker turns on as long as possible or I'd never hit anything with it against more experience players. The less time for them to set it up, the better. Some forum users posted TACVIEWs showing the RCS value for the AIM120 affecting when the missile went pitbull. The lower the RCS value, the later the missile would wait. Makes sense I suppose. I don't know if it did anything to the AIM7, but since we were told it didn't do anything in the AIM120 and it did, I thought maybe it had a hidden effect for the AIM7 as well. Turns out it may be the Hornet radar itself. I'm keeping a sharper eye on the HUD and noticing the radar breaking lock constantly for seemingly no reason (targets at 10nm cold with v-sub-c of like only 80-100 or so). I'm also noticing HMD/BORE ACM mode is having MAJOR trouble locking anything below you, and a decent amount of trouble locking anything else that isn't dead-on nose hot. Didn't report it as a bug because I don't know if it is one, just trying to see if anyone else has any experience with this. I fly many older scenarios, so I use AIM7's probably more than the average user. TL:DR; Any of you noticing less performance of STT on lightly maneuvering targets or look-down targets close to the terrain?

CCIP is wrong in all modes all the time. I reported this bug here: Take a TPOD and make sure no target designated so you can see where the TPOD thinks the bombs will hit vs where the CCIP cross is located. The TPOD shows you the correct aimpoint. Conclusion: CCIP cross is mis-placed in all modes. EDIT: Looking back on this thread, it looks like we have two bugs, one on top of the other (possibly 3) 1. The CCIP cross is naturally displaced from the actual aimpoint, usually to the left. This occurs in all modes and is a confirmed bug. @IvanK this bug could explain the miss in your first test. Run it again with a TPOD like shown in the track in the bug report above and you can confirm. 2. The INS system is picking up some sort of lateral displacement it shouldn't in the absence of GPS. 3. (possible this is the same as 1 manifested differently) AUTO bomb fall line will "jump" around the TD box depending on airspeed and altitude, with certain combinations being just wrong and leading to misses. This happens in all modes. It is possible 1 and 3 are exacerbated by 2 and vice versa. I've said it once and I'll say it again the iron bombing needs to be the first thing ironed out in these jets when they roll out and they need to stay tight, as they expose many of the other issues around the programming of how the jet works in sim. Things AA modes and the like may not exhibit because of the way they must be coded. Also, there is a bug with Mk83's I reported that is over a year old that was never fixed. If you are not at 7000k and 370kts, you will miss long and short unless you adjust your altitude and airspeed accordingly. Lower = faster, higher = slower. Too low/fast you will miss long too high/slow you will miss short. So don't use Mk83's in your testing if in-line impact measuring is important to the test, they'll confound your results.

After the latest update, I have not been able to get a single kill with an AIM7, shots within 15nm at Mach .9 25k on an F-pole, second shot taken at under 10nm. Impossible to score a hit. They're not even dumping chaff half the time. They dive for the deck and the missile goes stupid almost immediately. Run the 4v4 mission. Good luck and may God have mercy. EDIT: Just got 2. One of my SOPs before was to switch the RCS setting to the smallest setting. I tried not touching it and now the pk seems back to normal. Don't know if it's placebo or not but there you go.

It's doing that thing again where it tracks objects on the way to slewing to the target

Thank you for your input. I have reported the re-scan issue already as well. Bug report is in status "investigating". I hope they address this bug as well.

ED, what are you doing? I make a post to discuss with fellow community members MSI symbols and you move it off to bugs and lock it and say it was reported earlier. I wasn't making a bug report. Now I don't know what the bug is, I can't find the earlier post that was "reported earlier", and it's locked so I have to make a new topic just to talk about it. Is the fact that the symbols are showing up the bug? Is the fact that they sometimes DON'T show up the bug? Is it the fact that it's using ground track symbols? No one knows, no explanation given and no one can discuss it further. Referenced post below:

No, I am not confused. Sometimes, MSI contacts are on the AZ/EL page. Don't know how they are on there sometimes, but they are, hence the shock. Will try to grab a screen next time.

I'm seeing many small cosmetic items on the release schedule, but there are many long-standing bugs in the Viggen weapons delivery methods. 1.) DYK pull-up cue is wrong in ANF 2.) Wind not factored in for RB04 release cue on CI 3.) Wind not factored in for RR/ANF release cue on CI 4.) Placeable objects and most native map objects invisible to radar Since dive bombing and wind-corrected release of RB04's are common things to do in a Viggen (DYK bombing probably by far the most frequently used), I would think these would need to be a priority. Being able to place a large structure as a landmark for a nav update would be a useful tool for a mission maker, particularly scenarios with a long over-water or over-desert component to their navigation. Indeed, one of the main campaign mission tasks you with shooting RB04's on a very windy day in a pretty nasty cross-wind from the launch point. I'm sure that's not a coincidence. Seeing as there is no mention of these things, I don't have an expectation that they'll ever be fixed. Is this a correct assertion?

Whoa, how long have they been in and I haven't noticed? To anyone else out there dense like me, MIDS symbols now appear on the AZ/EL format. SA in the Hornet with that, the SA page, and the HMCS is top-notch.

EXP2/3 designation inaccuracy is due to the same bug that is confirmed and causes FRZ to be inaccurate. It is not due to some ED modeling of real-world inaccuracy of radar designations. This discussion here, marked "correct as is", likely due to the title, contains evidence of the above, including tracks and references to prior bug reports with tracks showing the same behavior. The confirmed FRZ bug, reported by @Frederf, is here, as of August of 2020

I've had the M2000 and Harrier for over 3 years now. I've got to say, I'm very impressed with the dedication and level of fidelity coming out lately. I know there's always more to do, but I really appreciate what you guys have been doing over there. Your recent efforts have convinced me to day 1 the F15E and Mig23. Keep it up!

Yes I've reported this numerous times, though I didn't know the cue was operating correctly in "quick" mode.

M2000C requires ground power

For the TWS one, are you guys setting your aging to 8 or 16? If you don't TWS drop contacts like crazy. You shouldn't have to do this in the real jet but this will get you by in DCS for now.