Radar v. terrain
-
it’s not because we don’t care, but actually because we DO care about terrain
oh you tease
-
I just wanted to bump this thread. We are are easily able to reproduce this behavior in 80s ITO, which is very dependent on NOE flying, lofting and DTOS attacks.
I think whats happening in campaign are a combination of two things:
1. omniscient AI which instantly share all information. So SAMs will know you are coming even if you crest a ridge by 1 cm you will instantly be fired upon. In reality the operator needs to identify, track, lock, IFF and fire which even for the fastest, most prepared operator will take 10 seconds or more.
2. LOS bugs - AI can in some cases see through terrain the combination of both of these things = extremely dangerous for NOE and 80s engagement methods
then again #2 seems like it doesn’t apply to some areas/terrainI think Lukas and I-hawk here have the #2 issue well identified.
For #1 have we thought about influencing the AI behavior in the following ways?
morale, skill, disposition (if prepared for an attack basically), position, ability of the system and chance
Right now it seems like god himself is fighting you and the IADS is perfectly optimized. -
1. omniscient AI which instantly share all information. So SAMs will know you are coming even if you crest a ridge by 1 cm you will instantly be fired upon. In reality the operator needs to identify, track, lock, IFF and fire which even for the fastest, most prepared operator will take 10 seconds or more.
This is incorrect. The SAM AI takes time to detect, identify, track and fire ….this is defined in the radar files like:
fan song example
Timetosearch1 30000
Timetosearch2 15000
Timetosearch3 10000
Timetoacuire 5000
Timetoguide 7000There might be a bug when the sam looses completely the radar contact, maybe the timers are not reinited again when new contact.
need checking
-
This is incorrect. The SAM AI takes time to detect, identify, track and fire ….this is defined in the radar files like:
fan song example
Timetosearch1 30000
Timetosearch2 15000
Timetosearch3 10000
Timetoacuire 5000
Timetoguide 7000There might be a bug when the sam looses completely the radar contact, maybe the timers are not reinited again when new contact.
need checking
Some SAMs have very small time. For S-75/125 and other older Cold War systems the time from first detecton to launch should at lest 30 sec but in reality 60 sec “lag” was not uncommon in case they were not in IADS. 2K12 Kub (SA-6) was a bit faster but SA-2/3/4 were very manual and time consuming to use as well as SA-5.
Because of the very lowres terrain = radar meash this is needed to mke more worthwhile fly at low. Reaction time of MANPAD/SHORAD or any AD units should be set a bit better if it is possible.
-
i confirm that there is a problem in the search and acquire timers once you have been detected one time and the sam looses track afterward
3-4 weeks to wait
-
-
i confirm that there is a problem in the search and acquire timers once you have been detected one time and the sam looses track afterward
3-4 weeks to wait
Some SAMs in RL can perofrom this for ex. SA-5. Basically the FCR in basic mode just measure the heading, speed and alt and just calculate the flight path, therefor in case target is lost because of any reason it extrapolates its trajectory and rotates as way the anennta and will find the target if follows this. If targets are low and for short time terrain blocks the LOS this is very useful. You can read about different modes of FCR in SAMsim manual, (MHI, FKM, etc.).
-
Some SAMs in RL can perofrom this for ex. SA-5. Basically the FCR in basic mode just measure the heading, speed and alt and just calculate the flight path, therefor in case target is lost because of any reason it extrapolates its trajectory and rotates as way the anennta and will find the target if follows this. If targets are low and for short time terrain blocks the LOS this is very useful. You can read about different modes of FCR in SAMsim manual, (MHI, FKM, etc.).
Sure sure this is what we have as well and this is defined with the timetocoast time
However the bug is that the targeting is nearly immediate even after a long time ….
This is clearly a bug
-
So cool Jp you can look at it …
-
@Cloud:
:bdance::bdance::bdance:
What he said !
That’s great news !