Jump to content

Recommended Posts

Posted

Hello Fellow Lomac flyers.

 

My question is about this 9M38M1, Medium Range, Radar-guided.

Was flying on our server. Got shot down twice by “Sam’s”. Checked the logs, the only thing apparent that launch at me was that missile. I never receive any warning tones. No missile launches detection whatsoever. My bird was flying like nothing was locking me up. I was hot at 5000 meters at the time in a Su27. Is this normal behavior for this missile? A glitch / Bug?

 

Thanks for your responses.

 

Cheers.

Posted

Hi Moose

A couple of 504 guys recently said that that happened to them on that server, no warning, ECM off. I suggested that it was in a very narrow valley/nook and thus had limited FOV; BUT this is the missile (aka s-11) fired by BUK sites, and if you were at 5km that would be an unlikely explanation. Perhaps you could ask the map maker if there are any sneaky placements that would cause such an effect?

Guest EVIL-SCOTSMAN
Posted

i had exact same thing happen on ur server on sunday/monday, i was in a 27 i had ecm on as i was engaged with E, next thing i know i was dead/crashed and i had no warning or anything, maybe if i didnt have ecm on it wudnt of launched at me or if it did i may have got a warning, but there was no missle launch warning whatsoever.

i was 20+feet and afterburner, but no warning sounds... no biggie tho

log said it was ground launched missle kill...

Posted

I think it is a problem with how the SAMs are set up in that mission.

 

The search radar can be placed anywhere on the map, as long as its in the same 'package' the launcher still gets the data link. That is why you dont get a lock or search warning either.

Posted

One bug that's been found and may be the problem.

 

If you join the server then leave when a sam launcher has expended its load. Then rejoin before its had time to rearm. When it does rearm that client will not see the missiles. They are invisible. Just like a an aircraft with an unsaved loadout. GG has been made aware of this bug.

 

Otherwise it could also be that because the Buk SR's (Search Radars) are not in the vicinity you will not get a lock warning before the sam fires. If the sam fires and its radar is not within the EWR envelope of your aircraft then you will get no warning either.

 

If anyone has any other possibilities, please record a track for me and ED to examine.

Guest EVIL-SCOTSMAN
Posted

That could be it cuz i did leave the server for a about 30 seconds as i got screen corruption, but i was out and in within 30 seconds, so that may verywell of been the cause for my downing...

Posted

Otherwise it could also be that because the Buk SR's (Search Radars) are not in the vicinity you will not get a lock warning before the sam fires. If the sam fires and its radar is not within the EWR envelope of your aircraft then you will get no warning either.

 

 

What Ice said, and the fact you're flying at ang.5... flying at an altitude of ang.5 to 8 will most certainly get you killed.

 

On "serious" missions the 355th handles a harddeck of ang.15 this to avoid possible "Gadfly" encounters.

:D

Posted
What Ice said, and the fact you're flying at ang.5... flying at an altitude of ang.5 to 8 will most certainly get you killed.

 

On "serious" missions the 355th handles a harddeck of ang.15 this to avoid possible "Gadfly" encounters.

5km I think he means :)

Posted
Hi Moose

A couple of 504 guys recently said that that happened to them on that server, no warning, ECM off. I suggested that it was in a very narrow valley/nook and thus had limited FOV; BUT this is the missile (aka s-11) fired by BUK sites, and if you were at 5km that would be an unlikely explanation. Perhaps you could ask the map maker if there are any sneaky placements that would cause such an effect?

 

I remember having occasionally friendly kills of these little bastards (aka s-11) on 1.02 servers.

Anyway, I can’t remember having friendly kills yet of these with FC 1.1 online.

DELL Intel® Core™ i7 Processor 940 2,93 GHz @3 GHz, 8 MB cache | 8.192 MB 1.067 MHz Tri Channel DDR3

| 512 MB ATI® Radeon™ 4850 | 500 GB 7200 rpm Serial ATA | Samsung SM 2693 HM 25.5 " | HOTAS Cougar Thrustmaster |

Posted
5km I think he means :)

 

Ah.. But still, at 16000 feet, give or take a few, you still are pretty vunerable, as a matter of fact, I flew along in the 169th server today, good old Mr. Ice puts the SA11's up on the mountain ridges, very very, VERY frustrating.......... :biggrin:

:D

Posted

Don’t know what happen initially. I tried to replicate today what happen yesterday. Recorded the track just in case. Flew the same route and altitude. Now, I received the warning tones and the launch warning…

 

But will try to make a habit on clicking on record track instead of clicking on fly. Just in case it re happens again.

I’m pretty sure I was not dreaming yesterday… :rolleyes:

 

Anyhow thanks for your input. Seems I was not alone experiencing this, so there might be something there to investigate.

 

 

Cheers.

Posted

There exists a genuine bug somewhere in there among the quite logical explanation also.

 

It's being worked on.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

  • Recently Browsing   0 members

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