Jump to content

Much harder locking Mavericks' targets in 2.5


Recommended Posts

Posted

Following Chuck's Guide procedure I find impossible to lock moving targets after 2.5 update. I made a test with a still target and it locks only when I'm closer than 2 miles, instead of around 7 miles before the update. Has anybody the same issue?

Posted

I was noticing this the other day. Wasn't sure what the deal was but I'm glad to see someone else replicating this issue. Prior to 2.5 around 7-7.5nm for a lock using the tpod/Mac combo.

 

Now less than 5nm. Not sure if it's a shading or contrast issue effecting the lock or how it's coded. Team Raz please look into this.

 

 

.

Posted
I was noticing this the other day. Wasn't sure what the deal was but I'm glad to see someone else replicating this issue. Prior to 2.5 around 7-7.5nm for a lock using the tpod/Mac combo.

 

Now less than 5nm. Not sure if it's a shading or contrast issue effecting the lock or how it's coded. Team Raz please look into this.

 

 

.

Me too. I'm finding that locking Mavs is very difficult unless you are right on top of them. More times than not, I can't even lock in anymore as I just get the larger crosshairs and rarely the locked in ones.

 

Sent from my Vivo XL2 using Tapatalk

Posted

not happening for me in 2.5 caucasus. to confirm u need 2 nm only for moving ones or doesn t it matter?

could you please tell more details, which mav ir/tv?, and the map.

just because nevada temperatures are relevant too

Posted
not happening for me in 2.5 caucasus. to confirm u need 2 nm only for moving ones or doesn t it matter?

could you please tell more details, which mav ir/tv?, and the map.

just because nevada temperatures are relevant too

 

I made some new test and it seems that the AGM65D works well, while the problem regards H and K type, which absolutely cannot lock moving targets and lock below 2 nm still targets. It's a Caucasus winter map, maybe the snow has something to do with that? I also noticed that H and K don't have the "stand by" phase but they are immediately ready as they are selected...

Posted
I made some new test and it seems that the AGM65D works well, while the problem regards H and K type, which absolutely cannot lock moving targets and lock below 2 nm still targets. It's a Caucasus winter map, maybe the snow has something to do with that?

 

Same debate has been going on for A-10c and the mavericks for a while, I and others queried ED about it and they came back with no fault, working as it should, I am no expert so I can't dispute it.

 

https://forums.eagle.ru/showthread.php?t=204350

 

Regards, Ian.

Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV).

 

DCS Tech Support.

Posted

k and h are equipped with tv-seekers not ir! thats why they need no cool down, lock should be contrast related, the more contrast the better/earlier, they are not night usable

Posted

A way around this is to use the force correlate mode in the A-10C...can extend range of mavs to 14-17nm (depending on altitude).

 

But I don't think the Harrier has this capability...need to ask a dev.

Posted

Mavericks locks fine here.... at least the D's in Nevada

Mainboard: ASUS Maximus X Hero Intel Z 370
CPU: Intel 12-Core i7-8086K @ 4.0 GHz    Memory: 32GB Corsair DDR4-3000 MHz
Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB
Monitor ASUS - Oled PG42UQ 41.5" @ 4K    1 SSD Samsung 860 PRO 256 GB    1 SSD Samsung 990 PRO NVMe M.2 4 TB
Windows 11 Home - 64    CH Products Combatstick, Throttle and Pedals

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...