LastRifleRound

FINALLY! THANK YOU! BTW, this seems localized to non-axis slewing. I don't have a TDC axis control, and the hornet doesn't allow one to use the mouse, so I added a modifier key and used my x52 to slew to see what it was like and it was MUCH better. Very, very touchy, but much better. It still wasn't as precise as it should be, but there you go.

Yes, it should see static objects and vehicles.

There is a slight difference in DCS. Use a small building, like a boiler house. Fly straight at it, one time holding INR over the top corner, the other with SCENE. As you pass the object underneath you, you can see what the pod was really tracking. You'll find INR is more likely to be looking further past the target than scene is. You can observe this same thing in all versions of litening as well (hornet, A10, viper).

There is a bug currently where all placeable objects do not appear on AG radars for both the Hornet and the JF17 introduced in the last patch, suggesting it's not likely a DEKA issue. It was confirmed in the Hornet forum. Report is here:

This is still an issue in this latest patch. Open instant action caucuses, select fighter intercept. AWACS will call out the targets, seems like they come from 115 or around 85 degrees at 60. When they get on the screen, you'll find the contacts completely unmanageable in TWS. TMS Right does nothing, TMS Up does nothing.

Here's an additional track, from Persian Gulf. I thought maybe it was just a map thing. It is not. I'm also able to get FTT tracks on the two buildings I placed here, so the FTT algo can "see" the buildings, they just don't show on the map. Objects_missing_2.trk

Track attached. This complex and it's many buildings were a practice range for me with radar bombing since the patch that allowed all objects to appear was released some time ago. The objects have all disappeared. The JF17 recently "fixed" it's AG radar as well so it may now be viewed in EXP, DBS1 and DBS2, and the objects are all missing from that display, as well, which suggests an issue outside of the aircraft itself. Right now, in terms of radar use on static targets placed in the ME (as well as roughly 50% of the native map objects), the AG Radar is entirely broken Objects_missing.trk

One issue you're having is trying to make a DT2 in RAID. RAID is basically an overscanned STT. Bugging a new target in RAID will make the new target L&S and the new scan center. Another is you say you TDC depress an already bugged target to make a DT2. This would actually command STT on that track. It sounds like you want to make two bugs on a tight group. To do this, you must use EXP mode, as RAID will only allow one bug at a time. Bug a target in your group contact in TWS, enter EXP mode. Use NWS to step to the target you want to be primary. Use TDC to manually select the target you want to be DT2. Further presses of NWS should step between them. I don't know if DCS models this, but if the targets are close enough that they won't show up as more than one contact outside of RAID, then it is impossible to do what you want.

Track attached. What happens: 1. Initiate TWS 2. TMS right to make system tracks (bug makes this invisible) 3. TMS right again to bug priority target 4. Repeated presses of TMS cycle targets 5. Move cursor to bugged target, TMS up to enter STT 6. TMS down to undesignate and return to TWS 7. FCR format will no longer respond to TMS right or TMS up. It is not possible to cycle bugged targets, manually bug new ones, or enter STT using the cursor. Expected behavior: After #6 above, TMS right and TMS up should function as they did before. EDIT: Bug appears to sometimes appear without STT. From Instant action "Fighter Intercept" in the Caucuses. TMS right and TMS up will not do anything in TWS here. Can't upload this mission as base file size is 5MB F16FCR_unresponsive.trk

Can anyone point me to some good demonstrations of these in use? I had a grasp on the old way of doing it, but I can't this new way to work at all. Also, does TOT now work from a route perspective, or is it still bugged?

Also just fixed EXP/DBS modes according to the dev notes, so next patch hopefully will have that in it!

AUTO isn't working right for QTY and/or bombs with terminal parameters. In fact with QTY it not only doesn't plot a centroid, release is entirely inhibited. Here's a post with more information: https://forums.eagle.ru/topic/225699-later-in-early-access-jdam-auto-loft-mode/ EDIT: here's another great post on the topic https://forums.eagle.ru/topic/262806-is-jdam-autoloft-already-implemented/

It's not stable as in the difficulty spikes along with the maintenance. The main issue is when these campaigns were made there were less trees and most of the scenery had no collision model. Therefore, you have point air defense units placed in essentially invulnerable positions, and units put in places that, without labels, are literally impossible to see. With the cloud placement, these units are behind structures that you cannot gain enough altitude to shoot over, meaning you will have to frontally assault AAA and SA9 units. This is fine, except the mission expects you to not only see them, but to see and engage every single last one of them. That's crazy, and it's unreasonable and not in the nature of this sim to handle that sort of thing. I just played mission 2 of the republic, same thing. You're asked to dogfight two MI24's over an armed convoy with no warning. There is no way someone lives through that without A.) Labels and B.) Foreknowledge I don't ask mission designers to be nice, I ask them to be logically consistent and not to ask for super-heroics. Asking me to take on an SA9 hiding in the woods where 1-in-10 missiles can actually hit is suicidal. It's cheap. It's not good design. I can't see it without cheating and then I can't hit it because trees are invulnerable. Ground units don't even bother taking it out for me, so if I want to advance with the column, I'm playing chicken with that Strela and the ZU23 southeast of it every time. It's not difficult because it's good, it's difficult because the mission designers have taken advantage of 3 shortcomings of the DCS engine in the placement of those units. Also, asking me to shoot the front armor of that T80U will drain at least 4 missiles. Your wingman will not engage it and even if he does he will die. It's not "nice" to not put that unit there, it's in keeping with the limitations of the AI. In a threat rich SAM/AAA environment, the AI rarely survives. I am clearly meant to be using double the missiles I'm carrying, which means I am intended to use my wingman. That's not good design, knowing what we know about AI wingmen in DCS. It's my opinion that either A.) these missions were never that great or B.) the DCS engine has made too many changes to AI and ground scenery that weren't kept up, and made previously reasonable missions frustrating and cheap, and sometimes even impossible.

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?