can not reproduce STT - freezing target on FCR

skywalker22 · February 6, 2023

When locking a radar contact into STT, no matter of the mode (RWS or TWS), from 40nm to cca 20nm, the target is not moving on FCR. It stays on approximately 35nm range.

This applies for following aircraft: F-14, F-15, F/A-18, M-2000, Mig-29S

and regardless of the map. Example is in attached track.

f16_FCR_STT.trk

BIGNEWY · February 6, 2023

Hello

please include your dcs log

please remove all unofficial mods and run a repair

When we test we can not reproduce

skywalker22 · February 6, 2023

Hi there @BIGNEWY

I did as you instruced, but the issue is still there.

f16_FCR_STT.trk dcs.log

NineLine · February 6, 2023

Can you supply the mission you are using, also I have not heard of anyone else having this issue, you are sure there are no mods being used, no edits to DCS, have you run a slow repair?

I can see it in your track but when I try it myself it works fine, even taking control of your track.

BIGNEWY · February 6, 2023

I can see it in your track, the problem is as soon as I take control of the track replay, unlock the target and lock again in STT the behaviour is correct.

Please also remove all mods from Saved Games\DCS.openbeta\Mods and run a full slow repair again

thank you

skywalker22 · February 6, 2023

I don't have any mods in there.

So when you lock the target in STT (twice TMS UP), it moves towards you? For me it doesn't at least not to approx. 22-30nm (depends of the aircraft).

If its not in STT, its all fine, but in STT, it nots (its as explained).

12 minutes ago, NineLine said:

Can you supply the mission you are using, also I have not heard of anyone else having this issue, you are sure there are no mods being used, no edits to DCS, have you run a slow repair?

I can see it in your track but when I try it myself it works fine, even taking control of your track.

Its a simple one, me in F16 and AI in what ever plane facing hot to each other (no matter of altitude). Always the same on all maps.

I repeat, No mods, and slow repair done! I almost never use STT, but I used it today, and found this out.

BIGNEWY · February 6, 2023

Yes when in STT the contact is moving as it should for me

Please also check your scripts folder as you have some errors relating to mods from the script folder

skywalker22 · February 6, 2023

One thing I noticed, when in STT, I got those 2 yellow symbols over the target like I am being jammed. Only in STT, when going a step back, those jamming disappears. Do you also get that?

Edited February 6, 2023 by skywalker22

Furiz · February 7, 2023

8 hours ago, skywalker22 said:

One thing I noticed, when in STT, I got those 2 yellow symbols over the target like I am being jammed. Only in STT, when going a step back, those jamming disappears. Do you also get that?

When you get jammed that means the radar can not determine range of the target, it can only determine the azimuth, so it shows the target at max range, in your case 40 miles.

That's why the target is not moving, cause radar display is showing it at max range all the time.

skywalker22 · February 7, 2023

13 minutes ago, Furiz said:

When you get jammed that means the radar can not determine range of the target, it can only determine the azimuth, so it shows the target at max range, in your case 40 miles.

That's why the target is not moving, cause radar display is showing it at max range all the time.

So there is nothing wrong? It's only strange that no one (BN and NL) could reproduce this issue. What about you?

Furiz · February 7, 2023

10 minutes ago, skywalker22 said:

So there is nothing wrong? It's only strange that no one (BN and NL) could reproduce this issue. What about you?

I didn't watch the tracks, just commented on the picture, but I fly every day and I didn't have this issue he is describing.

Moonshine · February 7, 2023

Furiz is right. i did not see anything wrong in my test.

set the target jamming to always be on, co-alt to avoid any of the borked lookdown effects, found him on scope as a brick at around 40nm, entered STT, then the radar scope changed to 160nm with the locked target "stuck" at the very top end due to jamming and range showing 99.9 in the HUD (as in, cant get any range due to jamming)

continued hot, burned through at around 28nm, then the radar scope changed to the 40nm range and the locked target started moving down on the radar scope as the range closed in.

nothing wrong there.

if anything i question why the chevrons indicating a jamming contact do not show up on radar scope prior to even finding a radar contact (brick). isnt it supposed to always be there in the direction of where that jamming signal comes from?

F16_STT.trk

Edited February 7, 2023 by Moonshine

BIGNEWY · February 7, 2023

the mystery here is, how are you creating this condition so it shows in the track replay.

Taking over the track and unlocking and then locking the target makes everything ok for me.

Fresh missions work as intended

My immediate thought is mod or edit to the game files, but you have said you have removed all mods and run a slow repair, so I am unsure currently.

Edit:

have you used any F-16 mods in the past?

Try removing / deleting the F-16 in the module manager, then downloading it again.

skywalker22 · February 7, 2023

@BIGNEWYso you are saying that when you lock into STT any of these aircrafts (bricks) F-14, F-15, F/A-18, M-2000, Mig-29S, you do not get any jamming chevrons over the bricks (contacts) on the radar scope between 40nm and 30nm, and not even any freezing of them (so they are standing still not moving)? They all work as usual, coming closer and closer and with no jamming chevrons?

I will try to do as you said, delete the F-16 in the module manager, and istall it all over again.

I have no mods installed what so ever, and never had any F-16 (double seater or any other) module installed eitgher - not interested into any, I am too much in love into yours

skywalker22 · February 7, 2023

I deleted F-16 module, and installed it all over. And its same thing.

Why would jamming appear only in STT, but not in any other target type (system and bugged)? This makes no sense. If I would really get jammed, I would see that much earlier then 40nm on FCR with those chevrons on top of the screen like @Moonshineexplained (questioned). And surely not only in STT mode. There has to be something wrong here, because I doubt that's only me having this issue (if we all have same modules of course!).

It's not that it's some kind of a big deal, but it can be frustrated.

Moonshine · February 7, 2023

some options only have the AI using the jammer upon getting locked by radar (i think its the default ECM option for AI). thats why i specifically set it to always jamming in the ME during my test.

however, top of HSD and Top of FCR did not show chevrons at all. to note, there was no AWACS in the mission but that should not have any effect on it

Edited February 7, 2023 by Moonshine

skywalker22 · February 7, 2023

Thx for that @Moonshine but what's also puzzling me, that @BIGNEWY didn't have those chevrons (as far as I understood him - based on his words).

And another thing, this ECM Using option is not even used or turned on by default in editor - so how come it works in game?

Sign In

can not reproduce STT - freezing target on FCR

Recommended Posts

skywalker22

BIGNEWY

skywalker22

NineLine

BIGNEWY

skywalker22

BIGNEWY

skywalker22

Furiz

skywalker22

Furiz

Moonshine

BIGNEWY

skywalker22

skywalker22

Moonshine

skywalker22

Recently Browsing 0 members