dtmdragon

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.)

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 can dream.......

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.

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....

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

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.

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.

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.

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.

My Nato fighters install seems to have become quite unstable since applying this update. My game freezes up occasionally when I try to use the single mission mission editor and when I try to continue after completing a mission in one of the nato fighters campaigns

I'm sure I got it from one of the cat files, can't remember which one sorry

Haha I agree! I still need an acurate cockpit for my Kiwi Skyhawks instead of the modified Kfir one I'm using. Since you mentioned seats for the gunners, I have unpacked the Third Wire A-4 seat and repainted it green to use as their seats (I also use it for crew seats in the SH-3. It looks good unless you zoom right in lol but like you say sometimes it’s about compromises...actually, come to think of it that might have been my wife... haha

Fair enough, let me know if you want me to get rid of that post then. Cheers, Dan.

Nice work! I’ve made a few edits in the data.ini file in the interest of realism if your your interested. ***This will change the position and firing angles of thecountermeasure launchers: // Countermeasure System--------------------------------------------------------- [FlareStation1] SystemType=DECOY_DISPENSER EjectPosition= -0.5,-3.9,1.0 EjectVelocity=-15.0,8.0,-4.0 NumFlare=120 [FlareStation2] SystemType=DECOY_DISPENSER EjectPosition=1.365,2.0,0.2 EjectVelocity=15.0,8.0,0.0 NumFlare=60 [ChaffStation1] SystemType=DECOY_DISPENSER EjectPosition=-1.365,2.0,0.2 EjectVelocity=-15.0,8.0,0.0 NumChaff=60 [ChaffStation2] SystemType=DECOY_DISPENSER EjectPosition=0.5,-3.9,1.0 EjectVelocity=15.0,8.0,-4.0 NumChaff=120 ***And the following edit will remove the pilot & co pilot’sdoors and have the main cabin doors open. Which is what you quite often see inpictures of the MH-60L on operations. ***Replace this: [RemoveBit4] ModelNodename=Empty DestroyedNodeName=CargoGlass_R DetachWhenDestroyed=TRUE HasAeroCoefficients=FALSE [RemoveBit5] ModelNodename=Empty DestroyedNodeName=CargoGlass_L DetachWhenDestroyed=TRUE HasAeroCoefficients=FALSE [Canopy] SystemType=HIGHLIFT_DEVICE DeploymentMethod=AUTOMATIC_SPEED Setting[1].Angle=30.0 Setting[1].DeployValue=333.0 Setting[1].RetractValue=5.0 MaxDeflection=30.0 MinDeflection=0.0 ControlRate=0.5 AnimationID=6 ***With this: [RemoveBit4] ModelNodename=Empty DestroyedNodeName=door_R DetachWhenDestroyed=TRUE HasAeroCoefficients=FALSE [RemoveBit5] ModelNodename=Empty DestroyedNodeName=Door_L DetachWhenDestroyed=TRUE HasAeroCoefficients=FALSE [Canopy] SystemType=HIGHLIFT_DEVICE DeploymentMethod=AUTOMATIC_Speed Setting[1].Angle=5.0 Setting[1].DeployValue=0.01 Setting[1].RetractValue=0.01 MaxDeflection=5 MinDeflection=0.0 ControlRate=0.5 AnimationID=6

Been working on upgrading the A-12 Avenger for SF2