MarkyMark

no, they cannot be self destructed, they do that fine when they hit the ground

Radar slew speed go weeeeeeee It’s a bit of a curveball to get used to, but I’m used to it after a couple hours flight time.

Curious what you mean here, we can narrow up the azimuth to 20 degrees if desired, to increase scan update frequency.

Yes, and it will keep the settings when you switch to TWS mode as well, except for settings outside the TWS abilities (such as, an 80 degree azimuth with a 4 bar vertical scan). I believe it will default to the closest available setting in that case.

Fixed: Upon entering TWS, the priority 1 target was not automatically set as the L&S. from the patch notes, it should be working as intended now. You can SET for aim9s as well. I usually set aim120 to high PRF, 80nm, 80 degree and 4 bar scan, then switch to aim 9, set to 20 miles, medium PRF. Then, whenever you switch weapons it will default to that.

He’s right, you don’t need a pod, but it helps. If targets are close enough to a wptdsg location, auto drop will let the bomb find the laser (with code set appropriately). Usually, the higher the drop, the better and more likely it is that the bomb will track properly. Jtac is ideal, buddy lasing requires some very good communication and coordination to get right.

Im sure I do that every time, but I wonder if it’s a timing issue if I do it too quickly or if the targets are too close together. Designating is second nature for me, I am 100% sure I do it every time.

I’m not sure if this was discussed previously, so I apologize, I couldn’t find it. Has anyone had instances where targeting ground unit with T-pod, dropping a Jdam, slewing and targeting a new target close by, and dropping a second bomb, both will hit the 1st target only and completely miss the 2nd? Is there a subtle thing I’m doing wrong? It doesn’t seem consistent, perhaps 25%-50% of the time. thank you

Thank you, I suspected the same. I played the through the inferno servers yesterday, 1 team kill and 2 missiles in the face with no warning from Sam sites. 4th time was a flanker with R27-ET so that’s my bad lol. Yep, RWR is busted and boy, does it suck.

Can anyone confirm if this is MT or a general bug? I am getting mixed results, seems like still no launch warnings but some rwr contacts in the standard version. Just asking if it's worth switching back to standard threading for the time being

Makes SEAD almost impossible, need launch warnings to time the egress, but now, you’re lucky to get a visual and by that time it’s probably too late. Not sure how the harms in PB mode are affected but I’m having no luck with that either, only thing working is harm too mode for me but still need to get a visual on a launch to be able to avoid. People getting smoked left and right heh

Agree 100%. This is a very big problem. Very few spikes before a missile in the face right now. SEAD not really possible effectively

Yeah, this isn't right.

Same issue, I was able to see sams with HARM seeker head, but were not showing on RWR display or HUD.

This is good. Very good. Well done ED.

Performance was much better but had some stutters when switching views, until finally a crash. Will try again dcs.log-20230310-180508.zip

No wonder the F16s I fly with are always carrying lots of luggage, didn’t know the internal fuel was 3000lbs less than the hornet.

You sure about that? Not in an F18 you can’t.

Ability to move chat box, change colors, mute players, start separate channels for groups?

Thanks, I figured as much, thought maybe there was some submenu page hidden deep that I was missing. It’s tricky to punch in the new code while doing an a/c pullback launch sometimes (pucker factor often high)

Is there a way to set each station (with 4 HARMS, for example) with a unique threat code in PB Pre-brief mode ? Example, station 8 set to 130, station 2 set to 129, etc)

I thought this was my joystick dead zone settings but you’re right, I’ve had the violent swings for no reason as well.

You're welcome, a disk check may have solved it, that happened during the upgrade. So perhaps it will save someone frustration in the future.

Update. A full upgrade to windows 11 from windows 10 appears to have fixed it. Perhaps a disk error.

The 3rd image shows trying to launch a simple free flight, uninstalled srs, uninstalled DCS completely, reinstalled, still getting this. Frustrating. dcs.log-20221209-043907.zipdcs.log-20221209-043907.zip