Radar orientation on slope of hill effects Beriosa

[Ironhand]

I may have stumbled on something you--the Devs--aren't aware of concerning the issues people are having with the Beriosa and Su-25T anti-radar mission issues in general. I'm uploading two track files as well as the mission files for your perusal.

 

I'm testing with a single Patriot SR set on a slope.

 

In Track 1A, the unit is oriented to 270 degrees which has it facing more rather than less along the line of the slope (facing downhill, so to speak). When I flew the mission, I climbed to acquire the signal above the hill's horizon and then lost altitude. I lost the audio signal tone again when about 1200 meters ASL (TIME: 08:02:40). That is when the signal was lost below the horizon. But the Beriosa remained lit and stayed lit throught the rest of the rest of the flight. I was even able to lock and launch on the target, since the Phantasmagoria also continued to display the target.

 

 

In Track 2A the unit is oriented to 200 degrees which is perpendicular to the slope of the hill. In tis track, the Beriosa and Phantasmagoria behave as they should.

 

 

So, the orientation of the radar on the slope seems to come into play with at least some of the reported problems. Just wanted to pass this on.

 

EDIT: Forgot to add that this effects the vertical orientation. You only see the difference in the vertical. The horizontal effect remains normal. Moving side to side to put the radar behind a hill crest, the Beriosa etc function normally in both scenarios.

 

 

Rich

Edited August 17, 2012 by Ironhand

[159th_Viper]

Ta Rich

 

Even with a 200 degree orientation the behaviour persists. Does depend on your ingress/engagement parameters, but as seen the Patriot has X-Ray vision :D

 

 

 

Investigating with latest build and will confirm when reported.

[Ironhand]

Ta Rich

 

Even with a 200 degree orientation the behaviour persists. Does depend on your ingress/engagement parameters, but as seen the Patriot has X-Ray vision :D

 

....

 

Investigating with latest build and will confirm when reported.

Damn. And here I thought I had stumbled on something significant that might be helpful. Oh well. Just have time to test thoroughly anymore.

 

 

 

Rich

[159th_Viper]

Damn. And here I thought I had stumbled on something significant that might be helpful.

 

You did - You provided a track and mission files. Had you not done so, I would not have bothered investigating this issue as I attempted to replicate yesterday and was unable to do so.

 

As an aside, even with the Radar on level ground the issue persists in the public version so there is definitely something seriously amiss:

 

 

 

Moving on to the testers build now.

[Weta43]

It's not just Su-25T, it's also true of Su-25.

A week or so ago I logged a bug saying that a Beriosa will register the presence of a S-300PS 64H6E radar if terrain masked, as long as it has previously been legitimately detected while unmasked.

I'll link this to it...

Edited August 18, 2012 by Weta43

[159th_Viper]

It's not just Su-25T, it's also true of Su-25.

A week or so ago I logged a bug saying that a Beriosa will register the presence of a S-300PS 64H6E radar if terrain masked, as long as it has previously been legitimately detected while unmasked.

I'll link this to it...

 

Ta Weta :)

 

Found it - attached further 25T track: Replicated with Patriot, SA-15 and SA-19. Interestingly enough the SAM radars also continue to track even though masked.

[Ironhand]

Ta Weta :)

 

... Interestingly enough the SAM radars also continue to track even though masked.

Shades of the old Flanker series, when SAMs would track you and launch the instant you cleared the masking terrain. :)

 

 

Rich