ldnz

Definitely the radar stuff here. Mirage team have done an awesome job showing the way. Yes it will upset people when they have to deal with more false contacts and RIOs actually have to work harder, but would be great to see the radar fully fleshed out.

Yeah sorry could have been clearer

turn up the brightness - knobs on far left.

Make sure you've turned up all the internal light brightness on far left, first time I didn't touch those knobs and I never saw the boresight targets.

The tid going blank is probably jester using the TCS to try for an id.

This is not a behaviour i've seen at all, and I've done a lot of 30 deg loft shots at many different ranges. The only time I've seen it go into space is if the track was immediately lost. Attached is a representative tacview of a ~30nm shot with a 30 deg loft, both track, one kill, one lost in the notch. Tacview-20220206-153720-DCS-f14 bvr range.zip.acmi

Ok, disregard then.

Hi, I've seen this mentioned but not sure if there is a ticket for it.. Assuming you have auto P-STT switching disabled, and have a valid PD-STT lock: 1. The first time you command jester to select P-STT (via wheel or direct button) he will attempt this, with limited success. 2. Any additional time you ask for this (after regaining PD-STT) jester will acknowledge, but not actually do anything (as shown by radar mode on ctrl-enter controls helper). So it becomes impossible to get a P-STT lock until it can be pilot acquired. This is costing me a lot of sparrows

Cheers will review. Appreciate the time in putting these tacviews together.

I am struggling now with just how good the AI is at notching. See attached tacview - what could I do better here? Doesn't look like there was any attempt to reacquire as they came out of the notch as well. But I can repeat this every time. Very hard to get a hit on these guys. Using Mk60s and a bigger loft + higher speed doesn't really change anything, doesn't seem to be a function of terminal speed. Tacview-20220206-090754-DCS-f14 bvr range.zip.acmi

Does TID range actually affect tracked targets? I don't think it does - I'm sure i've had the system decide that tracks at greater ranges were high priority.

One possible subtlety here is the track sweep time. Lets say you've got a track at the center of the sweep pattern, and the antenna has just moved over it moving left. If the computer swings the pattern left to follow a new track - the antenna has to go all the way to the new edge and back. Does this make it take longer than the strict 2 second refresh time?

Yep this one drives me nuts. I've taken as rio to binding 'do not attack' CAP button and mashing it on every new track I can see before the radar slews over to it. I especially hate it when it slews towards a track at ~100nm and trashes my missile that was on a high threat at ~30nm. Surely active guided tracks should have priority. Re de-sync and dropped tracks - me and my pilot have just given up on at least the first missile in any fight as its almost guaranteed to suffer immediate track loss. I assume there is a slight hesitation as the missile spawns, textures load or something, but again its enough for a single missed sweep and wasted launch.

FYI there are jester binds for switching between aircraft and ground stabilised - I use this to switch between Navgrid + ground and aircraft stabilised when committing.

Hi, check out Oceanic Combat Group. While we conduct much of our training in F-18 we heavily utilize Vipers for in our missions with a dedicated SEAD and a Multi-Role flight. We participate in SATAL and are looking to grow more people into competitive PvP. https://oceaniccombatgroup.com.au/ http://discord.gg/ZmXEBSU

Yeah gonna add to this - seems to be a very particular time of day that petrovich just takes a nap, often when the sun is well up. Wish it used local light levels instead of a simple clock.

So if I understand @GGTharos the missile is essentially doing intermittent SARH until such time as commanded active? It makes sense that the messages are getting reflected off the target - the missile isn't necessarily in the radar scan volume (given its large loft) so 1. the F14 doesn't track it, and 2. couldn't transmit direct path to it. Questions I have: 1. what could the datalink message usefully communicate to the missile? If missile knows angular position of the target (monopulse from reflection) then it could communicate information on velocity, heading, which would allow it to refine the intercept? 2. what happens in a track hold target? Is the radar just blasting this coded DL message out in the hope it sweeps over the target and the missile still gets it?

When creating a steerpoint from map, jester won't enter the ground altitude at that point - altitude on lantirn for QWP will be zero. This means cueing the lantirn to that waypoint is hopeless unless vertically overhead. Manually setting waypoint altitude via CAP works, but not available on multiplayer. Cueing lantirn directly to the markpoint does seem to point at ground level at that point, so is a valid workaround.

Hi mate, Oceanic Combat Group - http://discord.gg/ZmXEBSU

We've seen a couple in our group have problems trimming the Mi24 - no effect with the button (you could see it move in cockpit, but no effect), but the directional hat trim would work. Haven't found a consistent issue/fix - one guy fixed it after jumping into the Mi8 and then back and has had no trouble since.

I get this exactly as per original poster, both before and after 2.7 update. Worst offender is multiplayer on Syria map, where repeated F2, F6 to follow a missile, or F10 is almost guaranteed to cause it. Only remedy I've found is to turn down terrain textures and PD/steam SS. I get kicked to WMR failure (4 white balls on VR) and DCS still running at 5 fps on monitor, sometime still responding to position of the VR set. Restarting WMR is required. 2080 Super, G2, 32gb ram. I'm fairly sure its VRAM related.

Have you got options.graphics.stereo_mode_use_shared_parser = true set in autoexec.cfg? That will cause it.

This has happened to me twice - hook up to the shuttle and just as I run up engines the left engine shuts down. No obvious indications. I can restart the engine but as soon as it runs up to idle settings it immediately shuts down again. Respawn has been the only solution. This has happened once tonight and once on the previous patch, both times spawned on the super carrier.

Ok on re-reading the manual and thinking it through there is no issue here. To resync the AHRS there must be no acceleration - so level flight, at steady speed. Pressing the adjustment knob in for ~15 seconds brings everything back into alignment. I don't remember this ever being an issue before the supercarrier though?

I'm seeing this too. Immediately after a supercarrier takeoff the compass sync goes full deflection left andI'm about 40 degrees out. No other warnings or indications. Very frustrating! Happening everytime on OCG through the inferno server from cold start