kct

At least, AmericaNW (4 seasons) and DBS (current version) are compatible with the latest patches (not sure about the rest, because I never flew on them). Not sure about the rest, although most of the terrains released in the last 6 months should work, since they are being constantly updated. I want an updated EAWEuro...

I went and check the WoV/WoE set (Feb2008), turns out that there is no completely grey 370 wing tank in the pack.

I'm in the F-4J, getting intercept by some Fishpots.

With reference to this thread over there: http://forum.combatace.com/index.php?showt...&hl=ye-152m Are you still interested in doing the MiG-21-on-roids? I think a lot of people would love to see that guy in-game, since we got InSky's J-8 (which would make a pretty good base).

Don't worry, no one is rushing on it.

Yeah, that too, but they are envisioned as escort fighters in the first place.

Their loadouts needs to be defined, I think. And which F-101 you're talking about? Because if you are talking about -A or -C they are AAM-less interceptors.

You need to check the avionics for the said aircraft.

Whichever flies with you, to be honest.

There is no need for a readme file in this case, as this is just a 3D model.

[Thread Hijack] Yup. This is what I did to create a Hi ANG-specific F-4C: 1. Copy the F-4C folder in your aircraft folder, and rename it into "F-4C_Hi_ANG". 2. Rename F-4C.ini into F-4C_Hi_ANG.ini, and have the following: [AircraftData] AircraftFullName=F-4C Phantom II (Hi ANG) <--- take note AircraftShortName=F-4 AircraftDataFile=F-4C_Hi_ANG_data.ini <--- take note CockpitDataFile=F-4C_cockpit.ini HangarScreen=F-4C_hangar.bmp LoadoutImage=F-4C_loadout.bmp LoadoutFile=F-4C_Hi_ANG_loadout.ini <--- take note AvionicsDLL=Avionics60.dll AvionicsDataFilename=F-4C_avionics.ini 3. Extract both the F-4C_data.ini and F-4C_loadout.ini using the extractor (from the ObjectData.cat in the Objects folder), and put them into the F-4C_Hi_ANG folder. Rename the files to F-4C_Hi_ANG_data.ini and F-4C_Hi_ANG_loadout.ini respectively. 4. In the F-4C_Hi_ANG_data.ini, this is what you should have at the start: [MissionData] NationName=USAF ServiceStartYear=1964 ServiceEndYear=1987 AircraftRole=FIGHTER AircraftCapability=DAY_AND_NIGHT Availability=COMMON Exported=TRUE ExportStartYear=1971 ExportAvailability=VERY_RARE PrimaryRoles=CAP,INTERCEPT <--- take note SecondaryRoles=SWEEP <--- take note NormalMissionRadius=579 MaxMissionRadius=989 Ceiling=16764.0 MinBaseSize=MEDIUM This would make sure that the aircraft appears only in CAP and intercept missions, and fighter sweep to a lesser degree. 5. F-4C_Hi_ANG_loadout.ini can be left alone, season to taste. 6. Copy the Hawaii skin folder into the F-4C_Hi_ANG folder, and delete the other skins in only THAT folder. This would make sure that the game uses the Hawaii skins from the get-go. 7. Check the Decals.ini in the Hawaii folder. Change each "F-4C" into "F-4C_Hi_ANG". Example: F-4C/Hawaii/d/HaeuNum ---> F-4C_Hi_ANG/Hawaii/d/HaeuNum <--- Do this for all lines. 8. If you did it right... Optional: Remove ALL the A2G munition callout in the data.ini. We don't need bombs, LGBs, rockets and so in a pure A2A bird, although you might need to keep the EP (ECM and CM) and FT (fuel, obviously) callout just in case. [/Thread Hijack end]

You can simply extract the original data.ini for this...

Try checking what the loadout.ini calls out for in that case, though the stock F-4C loadout file should work in that case as everything for A2A has been called out. As for the missions variables, only these should remain (like in the other thread): CAP, INTERCEPT and SWEEP (since this is an air defence bird CAP and INTERCEPT could be the primary missions, and SWEEP as the secondary missions), so that the plane would only appear for combat air patrols and intercepts, with fighter sweeps on a lesser degree. Somewhat related to the topic... Any good chance of an ACTUAL F-4E AUP (Greek) pit? Like the ones shown in: http://www.f-16.net/f-16_forum_viewtopic-t-5034.html

Primary missions defined in the data.ini would be CAP and INTERCEPT. Secondary missions would be SWEEP.

Just another day at the Range...

.....Great heavens.

...About 48 here (33 active variants). That includes what-if and fictional ones. Come to think of it, we need an F-4E with the fintip RHAW, TISEO, slimers, and generally all the bells and whistles in one.

I don't know, there is this charm about Liverpool FC that I don't really see in other EPL clubs. Let us say that it is kind of magical.

I mean, rumours is that Liverpool is going to sell Torres if they are going to finance anything for the January transfer window. Hope that is not happening, it would be painful...

Actually, these few weeks would prove to be critical. There were rumours that Liverpool have to offload Torres if things got really bad...

It is just the InSky's J-8II, actually. I took them since it looks like a somewhat logical evolution of the Ye-152A design. Notice that it is mostly a half-hearted attempt (missing the avionics hump etc).

Just post this up first, if I broke the "once a day" rule then feel free to delete it: A pair of Ye-152S Flipper-M interceptors of the PVO Strany. These aircraft filled a niche between the MiG-23 (which does not have either the carry capacity and range) and the MiG-25 (for which half of the time the speed is not required). Strangely, they resembled the Su-15 Flagon more than anything else built at that time.

Believe me, YOU'LL NEVER WALK ALONE.

And how you could forgot the MEESTER BEEG PANTS MAN!!!

Not really, at least because AESA is currently not modeled in the .dll of the avionics, plus we do not know whether we would ever see the capability in the games or not at all in the near future.