dtmdragon

Is there any way to make your wing man and flight fly as low as you can e.g. nap of the earth? It seems they are programmed somewhere not to go below 1000ft which also happens to be the lowest height you can set a waypoint at. When you try and have them follow you lower or even at 1000 ft they ‘bob’ up and down as the AI tries to follow you then realises it shouldn’t and shoots back up only to repeat the cycle. It makes them very good SAM targets lol. I’m assuming there must be a minimum height setting somewhere in an .ini file that tells the AI to try and stay above a certain height....

Cheers mate. Yours are the same as the stock figures which the 'low' and 'very low' seem way off. I think TK has left them in feet not meters so I converted them to meters which after goggling low level flying and nape of the earth etc seems more realistic. Unfortunately it seems to have no effect lol so maybe it’s something to do with the fight engine???

Cheers, at the moment I'm going through the new DLC A-4K and A-4G ini’s to integrate them into my Kiwi Skyhawks mod, as I have mentioned before the DLC A-4K is quite lacking in some areas. I also have the Mirage Factory F-16A Block 15 OCU updated for SF2 to do a 'what could have been' RNZAF F-16 had we gone through with the purchase of the embargoed Pakistani order in 2002, hence why I asked about a Pakistani skin as I'm just using the USAF one with kiwi markings at the moment.

That worked, thanks :) Any chance of a Pakistani F-16 Skin or total Aircraft?

Great mod but the skin for the fake pilot parts don't seem to be showing up? The 3d model is there but it is just black without any skin....

Hi guys, Does anyone have a good repaint of a Pakistani Air ForceF-16 that will go on the Mirage Factory F-16A BLK15 model that they wouldn’tmind uploading or sending me? Cheers Dan.

I actually already have an all over green skin for the mirage factory model however the RNZAF switched to an all over tactical grey for all its aircraft in the mid 2000s so I doubt green would have ever been used, but I’ll still include it as an option. What I want is it to have the PAF scheme to start off with and then switch to an all over grey latter on, which brings me to my next point- needing an all over grey for the mirage factorymodel! lol

You and me both! I’m trying to create a more accurate ‘what could have been’ New Zealand F-16 from the deal that fall through in the early 2000’s. So far I’vetaken the Mirage Factory F-16A Block 15 OCU and updated it for SF2 with some updates to the cockpit, hud and radar displays from the F-16C that’s just been released. I’ve also added a kiwi pilot and a more likely RNZAF loadout. At the moment I’m using a USAF skin with RNZAF markings but the actual aircraft New Zealand would have received were from a canned Pakistani order and were already painted in the PAF scheme. Given that the RNZAF Skyhawks switched from a multi-colour euro camo pattern to an all over green for purely financial reasons I doubt we would have repainted the F-16s for some time had we received them! lol. http://f-16.net/f-16_users_article28.html (Scroll down to the New Zealand section.)

I can dream.......

Hay guys, all of a sudden every time I start SF2 it re-sets all my aircraft.ini files to the default, just like it does the first time you run it after installing a new patch. Has anyone run across this problem and know how to stop it? The result is I can’t make any stock aircraft flyable as each time I start the game my ini edits are undone! Grrrrrrr lol very frustrating....

Thanks that seems to have sorted the problem out. I have changed the main aircraft.ini files of the stock aircraft I've made flyable to read only as well just to see if it stops them being re-set to default next time I patch the game.

Thanks :)

Have you released this one somewhere or the No. 1417 flight badge? Cheers, Dan.

The JAS39C Gripen pit could use a going over

Open the extractor program, browse to the ‘Third Wire >Strike Fighters 2 > DLC’ folder, then change the drop down menu next to the ‘Filename’ box from ‘Third Wire Catalog Files (*.cat)’ to ‘All files (*.*)’ The DCLData002.DLCfile will now show up and you just select it and click open.

Same here, the new A-4G models means I can finally replace the A-4E model in my RNZAF A-4K mod to give it sidewinder rails on the outer wing pylons and working spoilers :) Here is a project Kahu upgraded 75 Squadron A-4K above New Zealand's Southern Alps in the late 1980's

Hay guys, Does anyone know where the texture skins for the A-4 IRMrails are? I know they are not in the individual texture folders like the droptanks are but I believe they are a node of the aircrafts model like the droptanks. Does anyone know the game handles the rails, where the texture is and what they are called? Cheers, Dan.

Thats what I am after! Thanks

Hay guys, Does anyone know the node name of the pitot tube just in front of the canopy on the A-4E model and half way down the nose on the new A-4G model? Cheers, Dan.

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

That’s what I thought to so I repainted every singlet exture (eg A-4F_body, A-4F_RightWing...) in one of the texture files a different colour but the rail still appearedcorrectly coloured in the game.

I’m having a problem with add on aircraft that have been designed with multiple copies of their drop tank so one aircraft can have different coloured drop tanks of the same type eg NF-5A. Each drop tank in the weapons folder has a different name eg DT1, DT2, DT3 etc but in the droptanks data.ini file they all have the same ‘TypeName’ statment which is the same as ‘FuelTankName’ statment in the aircrafts data.ini file eg ‘DT’. This means you can load any of the drop tanks that have the ‘DT’ statement as their ‘TypeName’ onto the fuel tank station of that aircraft. However the latest weapons editor seems to automatically make the ‘TypeName’ statement match the name of the main folder containing that weapon/droptank eg the drop tank that had the folder name DT1 but its data.inifile said ‘typename=DT’ has been changed to ‘folder name DT1’ and in thedata.ini file: ‘typename=DT1’. The effect of this is that none of the drop tanks can no longer be loaded onto the aircraft as the ‘typename’ statement of the weapon/fueltank does notmatch the ‘FuelTankName’ statement of the aircraft’s weapon station. Anyone know a way around this? It’s affected the NF-5A, RNZAF Canberra and probably some others I haven’t noticed yet. Cheers, Dan.

After applying the new third wire patch I'm getting a CTD every time I request fighter support in any of the Nato fighters campaigns and sometimes when I hit the accept/continue button after a mission in the debrief screen

I'm getting a CTD every time I request fighter support in any of the Nato fighters campaigns and sometimes when I hit the accept/continue button after a mission in the debrief screen.

By giving it a catapult and flight deck does that make it indestructible or is there a way around that? Cheers, Dan.