+PureBlue Posted June 18, 2009 Posted June 18, 2009 I've got Hercules, Hawk and S-10 sites in my map. Defined in the types.ini of the terrain and used from groundobjects. They show up correctly and work perfect, beating me to the ground! The problem is NONE of the search/tracking radars register on my RWR. I don't see them searching nor get a warning when locked on. All I hear is my wingman calling SAM Launch.. This is on SF2:E, and I tried different aircraft, stock A-10, F-4s, converted over Netz,F-18.. It's the same with all. No problem with the ZSU-23s, M113 ZPUs , they all can be seen w/ RWR. I checked the data.ini's and they are similar, of course not including the new frequency range and radar family parameters. (I tried adding but no change..) So anybody got a clue? or experiencing this? Thanks for the help. Quote
malibu43 Posted June 18, 2009 Posted June 18, 2009 Check out number 4... http://forum.combatace.com/index.php?showt...st&p=303057 Quote
+PureBlue Posted June 18, 2009 Author Posted June 18, 2009 I thought if these new parameters weren't defined it would show up as an "unknown". Now, I just copied the frequencies and other new parameters from ZSU-23, put it inside Flaplid and defined it RadarFamilyName=ZSU-23. Basically making it a Shilka. This is just messed up.., zero, nada on my stock A-10 RWR. My wingie calls spike so he is aware, but me that SA-10 is on me in a few seconds. I must be having a brain freeze, I double triple checked everything, but still can't figure it out.. Surely you guys got Nike,Hawk or SA-10s working?? Quote
MigBuster Posted June 18, 2009 Posted June 18, 2009 (edited) Did you put new text files into each jets folder with the new RWR defining what it can pick up? as #11 here http://forum.combatace.com/index.php?s=&am...st&p=301650 edit: sorry - see what your saying there - time for bed i reakon will test it again tommorow Edited June 18, 2009 by MigBuster Quote
+PureBlue Posted June 18, 2009 Author Posted June 18, 2009 (edited) Yes, followed your kb article, put in a default aircraftname_rwr.lst with everything listed. But that cant be the problem, because for troubleshooting purposes I'm trying the mission with the stock A-10. It sure doesnt need any modifications, right? The Shilkas are visible, the Flaplid which is exactly configured as a Shilka, is a ghost radar.. I copied the whole ZSU-23 DetectSystem to Flaplid_data, the range is messed up but it still fires at me. Here's a shot: There's ZSU at about 20 miles behind me, and this Flaplid with 2 SA-10L right in front, chugging missiles, surely got me locked. edit: yeah thanks for the help, remember these are hand placed sites using types ini definitions. I'll try using them as Mobile_AAA and other generic types see whats up.. Edited June 18, 2009 by pureblue Quote
MigBuster Posted June 18, 2009 Posted June 18, 2009 Okay - just for you I put the service dates of my other radar SAMs to 1975 and went on a recce mission My Flaplid Radar is RadarFamilyName=SA-11 and is defined as SAM_RADAR The SA-10 Launcher is defined as STATIC_SAM I dont need to edit anything else to get the game to pick them up - it will just stick them where SA-2/6s normally live - well in a single mission anyway I went up in an F-4E_78 heres its F-4E_RWR.lst file (TK has included an SA-11 tga file btw) F-4=RWR_F-4.tga F-8=RWR_F-8.tga F-14=RWR_F-14.tga F-15=RWR_F-15.tga F-16=RWR_F-16.tga F-18=RWR_F-18.tga NASARR=RWR_F-104.tga ScanOdd=RWR_MIG-17.tga SpinScan=RWR_MIG-21.tga JayBird=RWR_MIG-21.tga HighLark=RWR_MIG-23.tga FoxFire=RWR_MIG-25.tga SlotBack=RWR_MIG-29.tga Cyrano=RWR_Mirage3.tga BarLock=RWR_Search.tga LongTrack=RWR_Search.tga DogEar=RWR_Search.tga AAA=RWR_AAA.tga Hawk=RWR_Hawk.tga M163=RWR_M163.tga SA-2=RWR_SA-2.tga SA-3=RWR_SA-3.tga SA-6=RWR_SA-6.tga SA-8=RWR_SA-8.tga SA-11=RWR_SA-11.tga ZSU-23=RWR_ZSU-23.tga Here is the result - i did target it to make sure it was an S300 site - and recce it before a zuni got me :) here is the flaplid detect system [DetectSystem] TargetType=AIR RadarFamilyName=SA-11 RadarSearchTime=5.0 RadarSearchRange=150000.0 RadarSearchStrength=140 RadarTrackTime=2.5 RadarTrackRange=150000.0 RadarTrackStrength=280.0 RadarMinimumRange=300.0 RadarMaximumAlt=33000.0 RadarMinimumAlt=23.0 RadarPosition=0.0,0.0,8.0 RadarSearchFreq=5.0 RadarTrackFreq=7.0 RadarMissileGuidanceFreq=9.0 RadarSearchCW=FALSE RadarTrackCW=FALSE RadarMissileGuidanceCW=TRUE DataLink=TRUE NetworkType=SA-10 OpticalSight=TRUE NightSight=TRUE VisualRange=2000.0 MaxVisibleDistance=5500.0 RadarCrossSection=100 Quote
+PureBlue Posted June 19, 2009 Author Posted June 19, 2009 Thank you for your time MB I think I've found the culprit. If I let the game place them as SAM_RADAR and STATIC_SAM, they work as they should. SA-11 lights up on my RWR. BUT if I place them myself, using an entry in the _TYPES.INI, they will not register as radars for the game engine. I had Hercules, Hawk and S-300 sites acting the same. Now this I will investigate more. It wasnt broken in the classic series and if it's really broken here, we got a problem. Don't you all think so? Wrench or any other terrain guru, can you please try something similar to this and see whats up? I know column5 is not using this technique for NF4+. He would've come by it already. Well, I'll report back again tonight. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.