Jump to content

dtmdragon

MODDER
  • Posts

    2,102
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by dtmdragon

  1. Here is a photo I have found but have no idea what the missiles are? http://www.airliners.net/photo/Romania---A...632a35b0438f570
  2. Does anyone have any info on Romanian Mig-21 LanceR operational weapon loadouts? I have photos of Litening pods with LGBs but nothing of air-to-air loads. I am aware they can carry the Python 3, AIM-9 and R-60 etc but what would a common air-to-air weapons load consist of? Cheers, Dan.
  3. Will the mission editor be combatable with addon/modded aircraft/ground vehicles and terrain? Or will it only work with stock aircraft etc? Cheers, Dan
  4. I thought that might be the case but was unsure as its a bit of a coincidence I named mine exactly the same (eg A-4N_78_Ahit) allowing it to work. Cheers.
  5. I have been recently modding a copy of the stock A-4H Ahit into an A-4N and to my surprise the game seems to have integrated my A-4N into the stock Israeli campaigns!!??? In the Yom Kippur war my ‘A-4N_Ahit’ is avalible instead of the A-4H_Ahit in some but not all A-4H squadrons. So is my ‘A-4_Ahit_78’ in the 1982 Lebanon War. How has this happened??????? Here is a copy of the UNMODIFIED campaign data I have unpacked to have a look: From 'CAMPAIGNI2_DATA.INI' [AirUnit009] AircraftType=A-4N_Ahit <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< AlternateType=A-4H_Ahit Squadron=115IDF ForceID=1 Nation=ISRAEL DefaultTexture=IDFCamo1 BaseArea=Tel Nof Airbase BaseMoveChance=0 RandomChance=100 MaxAircraft=16 StartAircraft=16 MaxPilots=16 StartPilots=16 Experience=100 Morale=100 Supply=50 MissionChance[sWEEP]=0 MissionChance[CAP]=0 MissionChance[iNTERCEPT]=0 MissionChance[ESCORT]=0 MissionChance=50 MissionChance[CAS]=90 MissionChance[sEAD]=50 MissionChance[ARMED_RECON]=40 MissionChance[ANTI_SHIP]=10 MissionChance[RECON]=10 UpgradeType=FIXED Upgrade[01].Date=10/20/1973 Upgrade[01].Type=A-4H_Ahit_73 Upgrade[01].Texture=IDFCamo1 From 'CAMPAIGNI2.INI' [israelUnit008] Squadron=115IDF ForceID=1 UnitID=9 StartDate=10/06/1973 AircraftType=A-4N_Ahit <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< AlternateType=A-4H_Ahit DescFile=woi2Start.txt StartText=woi2Start.txt
  6. Great work guys. I have noticed one small issue; the skin for the Mirage 2000 pilot’s face must be missing or something as it un-painted/completely black. Cheers, Dan.
  7. Thanks that does help. Cheers guys I will continue my A-4M/N fact finding quest :P
  8. Does anyone have any good information sources on the A-4M and A-4N? I am trying to put together one but am struggling to find any hard information on either aircraft other that how they differ from previous models. I need dates of when certain upgrades were preformed such as the addition of the HUD and the AN/ASB-19 Angle Rate Bombing System etc on the USMC version. As well as any info on what changes were made to the M model to create the Israeli N model. Cheers, Dan
  9. Haha nice :) Il'd still rather fly fast.........
  10. I don't think we will ever see a kiwi air combat wing again, all the experience and infrastructure is gone from the current RNZAF and to rebuild that would take many years, as not only would pilots have to be trained from scratch, but so would maintenance and support staff/networks etc Even if the current government did decide to re establish it (as it is a National party government and was pro keeping and upgrading the combat air wing) I doubt it would be up and running before a switch back to a Labour government some time in the future would see it scraped again. Oddly enough the New Zealand public was well and truly behind keeping/upgrading our air combat capability when the previous Labour government went ahead and axed it anyway. No doubt so they could increase unemployment benefit payments for some 'poor underprivileged' group that they needed votes from.
  11. Don’t think we’d be seeing the old Euro 1 paint job if we were ever to see the kiwi air combat wing re established somehow lol- it’s grey all the way these days
  12. View File Royal Australian Air Force F-35A Skin and fictional Royal New Zealand Air Force F-35 “what if” skin Set of skins for the F-35A in the proposed markings of RAAF No. 3 Squadron and Fictional markings for a RNZAF version. INSTILATION INSTRUCTION Simply drop the files in the correct location specified by the name of the folder they are in. Submitter dtmdragon Submitted 09/06/2010 Category What If Skins  
  13. View File Royal Australian Air Force Hornet/Super Hornet Skin pack for SF2 Here is a rehash/ edit of some old RAAF Hornet skins to create a set of skins for the SF2 FA-18C, FA-18A or CF-18 (from NF4) which are all available here at combatACE. There are two sets of skins for No. 3 Squadron in low and high vis for the SF2 F/A-18A or C or CF-18 Also included is a skin for the new RAAF F/A-18F Super Hornet. Credit goes to all those that have done an F/A-18 or RAAF skin in the past. INSTILATION INSTRUCTION Simply drop the files in the correct location specified by the name of the folder they are in. Submitter dtmdragon Submitted 09/06/2010 Category F-18
  14. 83 downloads

    Set of skins for the F-35A in the proposed markings of RAAF No. 3 Squadron and Fictional markings for a RNZAF version. INSTILATION INSTRUCTION Simply drop the files in the correct location specified by the name of the folder they are in.
  15. 262 downloads

    Here is a rehash/ edit of some old RAAF Hornet skins to create a set of skins for the SF2 FA-18C, FA-18A or CF-18 (from NF4) which are all available here at combatACE. There are two sets of skins for No. 3 Squadron in low and high vis for the SF2 F/A-18A or C or CF-18 Also included is a skin for the new RAAF F/A-18F Super Hornet. Credit goes to all those that have done an F/A-18 or RAAF skin in the past. INSTILATION INSTRUCTION Simply drop the files in the correct location specified by the name of the folder they are in.
  16. Ok thanks
  17. What do I have to edit to get the formation lights to switch off? They are always on and the lights on/ off key has no effect on them. The lights section of the data.ini seems to only refer to the normal navigation/ landing lights. Cheers, Dan.
  18. Thanks, that solved the problem with the trees but now I have noticed the city buildings are shimmering as well! Dan.
  19. I have tried the 1024x1024 High resolution GermanyCE for Strike Fighters 2: Europe but for some reason the trees appear to shimmer? Any idea how to stop the shimmering or what files make up the windmill, so I can swap in the files from 1024x1024 High resolution GermanyCE for Strike Fighters 2: Europe to NF4 Europe terrain.
  20. Will that conflict with NF4 in any way?
  21. Hi guys, I am having an issue with what I think are ment to be windmills showing up in my NF4 install. I can’t attach an image in this topic so have posted my problem and a picture in the 'Uploading NF4+ Now ' topic in the ‘Thirdwire SF2/SF2:V/SF2:E/SF2:I - Mission & Campaign Building' section. http://combatace.com/topic/48928-uploading-nf4-now/page__st__100 Thanks, Dan.
  22. Hi guys, Any idea what is wrong with the windmills (I assume it’s meant to be a windmill) in my ‘NATO Fighters 4+ Patch Post Dec 2009 Patch Level’ game? If you’re wondering about the photo I have added my A-4K to my NF4 install. I am using windows vista 32 bit and an ATI 5750 1GB video card. Dan.
  23. An annoying issue I have noticed is having to update every individual RWR.lst file in each of your aircraft folders every time you add another aircraft, SAM or AAA that can be displayed on your TEWS RWR. This is a pain as the file can have different names and be in different locations within an aircrafts folders. For example the RWR.lst file for the JAS39C Gripen is called “JAS39C_RWR.lst” and is located in the ‘RWR’ folder inside the ‘cockpit’ folder which is inside the main ‘JA39C’ folder. An add-on aircraft that has a radar that can show up on the RWR has a ‘RWR_xxx.TGA’ file that goes in the ‘Flight’ folder in your mods section. As everything is now if you added another aircraft to your game, let’s say a Su-99, which has a TGA file (RWR_Su-99.TGA) so it can show up on a RWR. You need to add the following line to EVERY RWR.lst file of every aircraft with a RWR.lst file for it to show up in the game on you RWR – “Su-99=RWR_SU-99.tga” This can take some time to find and update every RWR.lst file! To streamline this process I have compiled a ‘master list’ RWR.lst file that is called ‘RWR.lst’ and has every aircraft, SAM or AAA radar in my game (including stock aircraft). I then copy and paste this file into the main file of every aircraft. The last step is to edit the [RWR] section of the avionics.ini file of EVERY aircraft with a TEWS RWR (including stock game aircraft) so it uses this file. The example below is for the JAS39C Gripen [RWR] Type=TEWS AirSearchTexture=RWR_Unknown.tga AirTrackTexture=RWR_Unknown.tga AirLockTexture=RWR_Unknown.tga GroundSearchTexture=RWR_Unknown.tga GroundTrackTexture=RWR_Unknown.tga GroundLockTexture=RWR_Unknown.tga MissileActivityTexture=RWR_Missile.tga PriorityTexture=RWR_Priority.tga SearchSize=0.20 TrackSize=0.20 LockSize=0.20 SearchFlash=FALSE TrackFlash=FALSE LockFlash=TRUE LockFlashRate=0.1 TrackSound=RWRTrackSound.wav LockSound=RWRLockSound.wav FlashActivityOnLaunch=TRUE ThreatLibraryFile=cockpit\RWR\JAS39C_RWR.lst <<<<<<<<<<< Change this line to: ThreatLibraryFile=RWR.lst Now whenever I add another aircraft to the game I only have to edit any one of my rwr.lst files then copy and paste it into the main aircraft folders of the rest of the aircraft that have a TEWS RWR and let it override. I think this is the easiest way? Dan. This is the contents of my “RWR.lst” master file: F-14=RWR_F-14.tga NASARR=RWR_F-104.tga ScanOdd=RWR_MIG-17.tga RS-2US=RWR_MIG-21.TGA SpinScan=RWR_MIG-21.tga JayBird=RWR_MIG-21.tga Kopyo=RWR_MIG-21.tga HighLark=RWR_MIG-23.tga Smerch-A=RWR_MIG-25.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-10=RWR_SA-10.tga SA-11=RWR_SA-11.TGA ZSU-23=RWR_ZSU-23.tga EF2K=RWR_EF2K.tga AV-8=RWR_AV8.tga SlotBack=RWR_MIG-29.TGA Mirage2K=RWR_Mirage2k.tga Mirage2KI=RWR_Mirage2ki.tga Mirage2K=RWR_Mirage2k.tga MirageF1=RWR_MirageF1.tga MIRAGE3=RWR_MIRAGE_III_CJ.TGA MISSILE=RWR_MISSILE.TGA PATRIOT=RWR_PATRIOT.TGA Orion=RWR_SU-24.tga FlashDance=RWR-MIG-31.tga Irbis=RWR_N-035.tga Bars=RWR_SU-30.tga Zhuk=RWR_SU-30.tga SlotBack27=RWR_SU-27.TGA J-10=RWR_J-10.tga A-4=RWR_A-4.tga A-10=RWR_A-10.tga AMX=RWR_AMX.tga B-52=RWR_B-52.tga C-5=RWR_C-5.tga EF-18G=RWR_E-18.TGA F-15=RWR_F-15.TGA F-16=RWR_F-16.TGA F-35=RWR_F-35.tga F-18=RWR_F-18.TGA F-4=RWR_F-4.tga F-8=RWR_F-8.tga HarrierGR=RWR_Harrier.tga IL-28=RWR_IL28.tga Jaguar=RWR_Jaguar.tga MiG-21=RWR_MIG-21.TGA MiG-23=RWR_MIG-23.TGA MiG-25=RWR_MIG-25.TGA MiG-27=RWR_MIG-27.TGA MiG-29=RWR_MIG-29.TGA MiG-31=RWR_MIG-31.TGA Tu-22=RWR_TU-22.tga Su-24=RWR_SU-24.tga Su-27=RWR_SU-27.tga Su-30=RWR_SU-30.tga Su-35=RWR_SU-35.tga Su-39=RWR_SU-39.tga JAS39=RWR_JAS-39.tga F3=RWR_F3.TGA F-22=RWR_F-22.tga SA-13=RWR_SA13.tga SA-15=RWR_SA15.tga SA-17=RWR_SA-17.tga SA-19=RWR_SA19.tga Roland=RWR_Roland Firecan=RWR_Search.tga M167=RWR_M163.tga AESA79=RWR_AESA79.tga AESA73=RWR_AESA73.tga
  24. Funny you mention that as I have already raised that question: http://combatace.com/topic/43260-jas-39c-gripen-for-sf2-series/ Personally I have changed it to reflect what you pointed out, however you need to edit your avionics.ini information as well as data.ini information. By that I mean not just the ranges but the range settings of SST mode etc. I had nothing to do with the original Gripen so I don’t know what information they based their avionics on. I use: Avionics.ini - [TextureData] RadarTexture=cockpit\jas_mfdrdr.bmp RWRTexture=cockpit\rwr.bmp EOTexture=cockpit\L-MFD.BMP RadarTextureSize=256 [RadarData] AvailableModes=SEARCH,TWS,STT,ACM,TV,GM RangeUnit=NM RangeSetting[1]=10 RangeSetting[2]=20 RangeSetting[3]=40 RangeSetting[4]=80 RangeSetting[5]=120 RadarPosition= MaxElevationAngle=60 MinElevationAngle=-60 MaxAzimuthAngle=60 MinAltitude=40.0 BoresightElevation=0.0 BoresightAzimuth=0.0 ACMMaxPitchAngle=55.0 MinReturn=0.04 MinimumSpeed=32.41 SearchRange=55 SearchStrength=90 TrackRange=80 TrackStrength=90 TWSUpdateTime=0.5 AcquisitionSymbolSpeed=1.0 AcquisitionResetPosX=0.5 AcquisitionResetPosY=0.20 AcquisitionResetTime=5.0 DisplayLimitLeft=29 DisplayLimitRight=226 DisplayLimitTop=29 DisplayLimitBottom=226 [RadarDisplaySearch] RangeSetting=1,2,3,4,5 BarElevation[1]=1.50 BarElevation[2]=0.50 BarElevation[3]=-0.50 BarElevation[4]=-1.50 ScanRate=140 ScanBeamAngle=2.5 ScanArc=60 PPI=FALSE Symbol[01]=HorizonLine Symbol[02]=RangeScaleText Symbol[03]=ElevationCaret Symbol[04]=AzimuthCaret Symbol[05]=AcquisitionSymbol Symbol[06]=TargetSearch [RadarDisplayTWS] RangeSetting=1,2,3,4 BarElevation[1]=0.75 BarElevation[2]=-0.75 ScanRate=100 ScanBeamAngle=2.5 ScanArc=60 PPI=FALSE Symbol[01]=HorizonLine Symbol[02]=RangeScaleText Symbol[03]=ElevationCaret Symbol[04]=AzimuthCaret Symbol[05]=TargetTWS Symbol[06]=TargetTAS Symbol[07]=TargetAspect Symbol[08]=TargetHeading Symbol[09]=TargetRangeCaret Symbol[10]=TargetAltitude Symbol[11]=TargetClosure Symbol[12]=AimDot Symbol[13]=ASECircle Symbol[14]=ShootCueTWS Symbol[15]=BreakX Symbol[16]=RMinCaret Symbol[17]=RMaxCaret Symbol[18]=AcquisitionSymbol Symbol[19]=TargetPDT [RadarDisplaySTT] RangeSetting=1,2,3,4 ScanBeamAngle=2.5 PPI=FALSE Symbol[01]=HorizonLine Symbol[02]=RangeScaleText Symbol[03]=ElevationCaret Symbol[04]=AzimuthCaret Symbol[05]=TargetPDT Symbol[06]=TargetTAS Symbol[07]=TargetAspect Symbol[08]=TargetHeading Symbol[09]=TargetRangeCaret Symbol[10]=TargetAltitude Symbol[11]=TargetClosure Symbol[12]=AimDot Symbol[13]=ASECircle Symbol[14]=ShootCueSTT Symbol[15]=BreakX Symbol[16]=RMinCaret Symbol[17]=RMaxCaret [RadarDisplayACM] RangeSetting=1 ScanBeamAngle=3.5 Symbol[01]=HorizonLine Symbol[02]=RangeScaleText Symbol[03]=ElevationCaret Symbol[04]=AzimuthCaret //Symbol[05]=LockLine [RadarDisplayGM] RangeSetting=1,2,3 ScanRate=120 MapPPIArc=60 MapBackgroundLevel=0.2 MapHighlightLevel=0.8 MapNoiseLevel=0.1 Symbol[01]=HorizonLine Symbol[02]=RangeScaleText Symbol[03]=ElevationCaret Symbol[04]=AzimuthCaret Symbol[05]=TargetPDT Symbol[06]=TargetTAS Symbol[07]=TargetAspect Symbol[08]=TargetHeading Symbol[09]=TargetRangeCaret Symbol[10]=TargetAltitude Symbol[11]=TargetClosure Data.ini – [DetectSystem] RadarName=Ferranti-Ericsson PS-05/A RadarType=AIR_INTERCEPT RangeUnit=NM RadarFamilyName=JAS39 RadarAzimuthLimit=60 RadarElevationLimit=60 RadarSearchTime=1.0 RadarSearchRange=120 RadarSearchStrength=90 RadarTrackTime=5.0 RadarTrackRange=80 RadarTrackStrength=90 MaxVisibleDistance=8400.0 DopplerLookdown=TRUE RadarSearchFreq=9.5 RadarTrackFreq=9.5 RadarMissileGuidanceFreq=6.0 RadarSearchCW=FALSE RadarTrackCW=FALSE RadarMissileGuidanceCW=TRUE HasRWR=TRUE RWRMinFreq=0.5 RWRMaxFreq=20.0 RWRCanDetectCW=TRUE VisualBlindArc=6L VisualRestrictedArc=5L,7L Dan.
  25. Just wanted to say great work guys. I haven’t been able to run the NF4 terrain due to my computer just not being able to handle it without a few stutters. But after replacing my 512 ATI 4850 for a 1GB ATI 5750 and doubling my RAM I’ve had no problems :) I spent this morning getting blown out of the sky in a GR3 the 1986 campaign by a flight of SU-27’s haha. I have even added my Kiwi Skyhawks to some of the campaigns since it’s always a bit more fun flying your own country’s birds into harms way haha. Dan,
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..