Jump to content

Not Able to Lock MSI Tracks in MP


Recommended Posts

I see MSI tracks on my radar but can’t seem to lock on them in multiplayer. In SP if I see those MSI HAFUs but not the radar track file it’s because my radar elevation needs adjustment and that will always work to get a radar return on the target. In MP this never works. Why is that?

Velocity Micro PC | Asus Z97-A | i7-4790K 4.7GHz | Corsair Liquid CPU Cooler | 32GB DDR3-1600MHz Memory | EVGA RTX 2080 Ti XC | 240gb Intel 520 Series MLC SSD | 850 W Corsair PSU | Windows 10 Home | LG 32UD99-W UHD Monitor | Bose Companion 5 Speakers | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

[sIGPIC][/sIGPIC]

Link to post
Share on other sites

Check your radar elevation to ensure the contact is inside your scan volume. If you hover the TDC cursor over a contact on the SA page you'll get it's reported airspeed (in Mach) and altitude.

REAPER 51 | Tholozor

VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/

Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/

Link to post
Share on other sites
2 hours ago, Tholozor said:

Check your radar elevation to ensure the contact is inside your scan volume. If you hover the TDC cursor over a contact on the SA page you'll get it's reported airspeed (in Mach) and altitude.

Right, that’s what I usually do. Get the altitude from the SA page and use that on the radar. Maybe the contacts I’m looking at are just too far away in MP

1 hour ago, NineLine said:

Please make sure to include a short track of your issue. Thanks!

Yes if I thought it was a bug I’d try to make a track. In MP these tracks are huge files though. I’m sure this probably isn’t a big, just something I haven’t figured out. More a question than a bug report. 

Velocity Micro PC | Asus Z97-A | i7-4790K 4.7GHz | Corsair Liquid CPU Cooler | 32GB DDR3-1600MHz Memory | EVGA RTX 2080 Ti XC | 240gb Intel 520 Series MLC SSD | 850 W Corsair PSU | Windows 10 Home | LG 32UD99-W UHD Monitor | Bose Companion 5 Speakers | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

[sIGPIC][/sIGPIC]

Link to post
Share on other sites

It could be too far away to be picked up, there could be terrain in the way, the target could be notching or not generating enough of a doppler shift to be detected. There's a ton of factors that can contribute to it.

REAPER 51 | Tholozor

VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/

Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...