Ever wonder what makes the AIM-120 only appear on the RWR 5nm from it's target when it has a lock? Yeap, me too! Well, as far as the JT file is concerned, I can't find a damned thing until now. I assume that is nothing to do with the JT file and more like a dll file or something that the game uses. But NOW YOU CAN DO THAT ON OTHER MISSILES. In order for this to occur, the missile had to be named as AIM120.JT, so basically if you saved you AIM-9X under AIM120.JT it would have the same characteristics. Well, not anymore. This method; however, has a flaw and I'll explain that later.
I'll be using the AA-12
as an example. Modify you AA-12 as you wish and save it in the Toolkit
as it's normal name, AA12.JT. Now you are down in the toolkit. Then
open up its JT file with notepad or whatever else you use and scroll down to
the very bottom.
;---------------- END OF PROJ_TYPE ----------------
:ot_names
string "R-77"
string "R-77 Adder"
string "AA12.JT"
:shape
string
"amski.SH"
:loopSound
string
"&missile.11k"
:si_names
string
"R-77"
string "R-77 Adder"
string "AA12.JT"
This is what you'd normally see if you named the missile R-77 Adder and so on and so fourth but all of that is useless except for one line, the one highlighted in blue. Change the AA12.JT to AIM120.JT and save the JT file. That is the filename. In the toolkit and when you install the LIB, it'll be separate from the real AIM120.JT file but the game will think that this is the AIM120 and cause it to have the 5nm thingy. Now here is the fault!
When you edit this missile
in the Toolkit, you open it up and see that the FILENAME is AIM120. That
has to be changed or else you'll overwrite the AIM120. You don't want
to do that, so simply re-save it as AA12.JT and go back to the JT file and redo
the process. Now you're ready to kick some major enemy ass!
By Centurian