Threat Guide
-
For the SA-5 I read this at ausairpower.net,
“The K-2 series Fire Control Centre van would qualify in part, under Western nomenclature, as a fire control van, and in part, as a radar control and management van for the 5N62 Square Pair. The 5N62 Square Pair is used to acquire the target, perform fine tracking, and provide FMCW illumination for the semi-active homing missile seekers. The K-2 van houses all of the radar consoles, but also houses the Plamya fire control computer which performs pre-launch and post launch missile trajectory calculations. Missile telemetry and command link functions are all controlled from the K-2 van.”
I’m still not sure about the command part not being present. It sounds like information on telemetry can be passed to the missile post launch.
Thanks for the SA-4 article reference. This was at the beginning,
“4. the difficult beginnings birth PZR “Krug”.
On a rocket 3M8 initially envisaged the use of a combined direct-radiokierowania on the primary flight segment and homing on the final flight segment. Semi-active radar homing head should work receiving the reflected signal to pulse radiation tracking channel to rocket guidance station.”It may be that they only planned to have SARH but didn’t implement it. But I couldn’t find that in the article. The article tends to use the word radiokrierowania in many spots which I am guessing is the command link. The translation to English was ok but not good and it was hard to read. It is also using names that are different from what I found in other sources so I am not sure if it is the same thing.
-
The KS-19 shoots up to at least 30K in BMS in my experience.
Nice doc TeeSquare
i often receive flak at ~32k (possible that the gun is on a hill somewhere, though)
-
Radiokierowanie means radio command guidance.
And HAPASP mentioned this about SA-5:
http://simhq.com/forum/ubbthreads.php/topics/3207415You’d think the Russians would’ve also given the missile the ability to remember it’s targets location/flight path and search for it with it’s seeker in the event the RPC lost track of the target. Any deviation by the target would probably result in a miss, but it’s better than nothing… And yes, a backup command guidance mode would’ve been extremely useful.
It is included. After loosing track, the missile will fly ahead, and will try to look for the signal received from the target, as long, as its battery runs out. (You can try it against a practice target, by switching the RPC off-on for few sec. The KRO signal will dissapear, and the missile should try to get the target at least.)
Command guidance would be inaccurate on these ranges, and would make this system more complex and expensive, and the missile even bigger.
(Just remember the S50 Dal, they were thinking about similar system)Mid course update would make the missile more susceptible against jamming.
So when missile looses target it simply flies ahead and waits for the target to be reacquired.
It sounds like information on telemetry can be passed to the missile post launch.
But where is antenna for command link?
-
Outstanding work - I remember the old version of this guide, which was also very useful.
-
Thanks for the SA-4 article reference. This was at the beginning,
“4. the difficult beginnings birth PZR “Krug”.
On a rocket 3M8 initially envisaged the use of a combined direct-radiokierowania on the primary flight segment and homing on the final flight segment. Semi-active radar homing head should work receiving the reflected signal to pulse radiation tracking channel to rocket guidance station.”It may be that they only planned to have SARH but didn’t implement it. But I couldn’t find that in the article. The article tends to use the word radiokrierowania in many spots which I am guessing is the command link. The translation to English was ok but not good and it was hard to read. It is also using names that are different from what I found in other sources so I am not sure if it is the same thing.
I think there are both versions. Original SA-4 (Krug) being command only, and later Krug-M being SARH for terminal. In any case it doesn’t really affect us in the sim whether it is one or the other.
-
SWEET ! You the man.
F-Bear
-
thank you!!
-
Big thanks from me as well!
Uwe
-
Cheers brother.
-
Wow, this is superb great work!! Just what I was looking for.
-
A new link to an updated version is on the first post. I changed the S-60 information and fixed a few errors.
-
Great threat guide just placed it in my bms docs folder.
-
Quality workmanship, a great resource and a fascinating read. Thank you.
-
Thank you for the information on everything that wants to kill me!
-
Sticky Please!!
-
Good Work …! thanks for sharing:D
-
Hijacking the thread as I think that the Thread guide is a great document and is an extension to the internal TacRef.
TacRef is indeed quite nice in game, under UI, to check, remind, or learn what are the specificity of a given vehicle, weapon … etc … Unfortunately, it is quite out to date and not synced with curent database.
As BMS team member can not do EVERYTHING, we would need the community’s good will to update the BMS TacRef to feature all (or almost all) what is present in the Falcon4BMS world?
In the past, I remember there was such a team for this … it is time to continue the legacy, no need to be part of BMS team for that!
Tool for this is SkyfireTacRefEditor_v2.
Open the TacRefDB.bin located into J:\Falcon BMS 4.33\Data\Terrdata and play with it … you will see, it is rather easy to use!
If and/or once you are familiar with the tool, maybe some of you will have the wish to start something.
I am sure it could be possible to create a room for a team of ppl who wants to organize such a project … or … a dedicated thread could be also enoughFor ppl looking for other information, maybe starting there could be a first step:
https://www.benchmarksims.org/forum/showthread.php?27571-TacRef-Editor-where-to-place-VB6FR-dll&highlight=tacref
https://www.benchmarksims.org/forum/showthread.php?15469-Which-TacRef-aircraft-can-be-added-to-BMS&highlight=tacref… or on some other places in the forum, just search for “TacRef” or maybe “SkyfireTacRefEditor”.
Ideally, one person in this team with minimum knowledge of database would be helpful but not absolutely necessary because I am sure that you will find some precious help on the ppl forum anytime you need it or have a question.
-
I started some work on this last year and made it thru the SAMs and AA missiles. It is truly a huge amount of work. I will post what I have so far when I am on my pc if anyone wants to continue work on it.
Below is a link to the progress files and the editor.
https://dl.dropboxusercontent.com/u/56935687/TacRef%20Progress%20Files.zip
The TacRefDB.bin file can be used in BMS and it will show the updated data for SAM and AA weapons. I still have some text that runs behind the window in the sim in a few spots that was not fixed yet.
My first step was to review what was already in the database. Then see if maybe it could be organized differently. Then I decided on a standard format to go with. This proved to be challenging since many of the systems can be very different.
I looked up current data. In some cases this means testing the item in the sim. Lucky for me, I tested all of the stuff that is in The Vault threat guide but there are hundreds of other items that I did not test so they will need to be tested if accurate data is going to be used.
Then I put the data into a word document. It is easier to save in word and word can also do a spell check for typos. As I finished each one, I would use TacRefDB Editor.exe and put the data into the TacRefDB.bin file. Be careful on how long each line of text is. The text can go off the window in the sim and not be visible if it is too long. Read the help.txt file for info on how to use the editor.
Keep back ups of the bin files in case a mistake is made.
This project could very well be broken up into smaller pieces. But to keep the actual entries consistent, a format for the data should be decided on before it is put into a word doc or the tacrefdb.bin. The pieces could be collected and entered into a word doc then put into the tacrefdb.bin file.
-
Thank you
-
Nobody for Tacref.
Ok … so I take it internal … at least to update CT.
See ya 3 - 4 weeks … maybe some ppl will be more inclined to help for text update.