Cliff7600

Well it's my choice, and I can explain it. I like to have 16+ aircrafts on the number list of each skin when it's possible (I mean without making up the serial numbers). In game it avoids aircrafts without serial number and tactical letter. With the details of the evolution of the Spitfire MkXII there should have been 3 models : Fixed tail wheel of the MkV : 0 aircrafts for the 41 squadron / 6 for the 91 squadron Retractable tail wheel of the MkVIII : 16 aircrafts for the 41 squadron / 8 for the 91 squadron Griffon IV : 4 aircrafts for the 41 squadron / 2 for the 91 squadron So it means : - one skin for the early version with 6 aircrafts - two skins for the mid version with only one numbers list file with 16 aircrafts - 6 aircrafts for two skins for the late version. Otherwise I would have had to produce many more tgas. It's not a problem when I want to, it's just I chose not to do it. I chose to have two skins with 20 and 16 aircrafts, without asking for another 3d model just for a tail wheel. The making of this MkXII sneaked out between other projects. The A-team MkXII has the fixed tail wheel. All the other changes are ini edits. On the production list I have, 81 aircrafts are powered by the Griffon III and 19 by the Griffon IV. -> 80 aircrafts are powered by the Griffon III and 20 by the Griffon IV and some of them were retrofitted with Griffon III. I agree there was another way to model the MkXII but, given that aircrafts were retrofitted during their service, I chose this way even if it's not the best. Since the beginning of this project there have been many "licenses" taken and all the Spitfires and Seafires released have some. This MkXII is no exception and I'm happy with it.

It's based on the Mk VIII so it's the late version. Some serial numbers won't match but it was simpler than doing the early and late versions. Mainly it was a matter of drag, fuel tanks and retractable tail wheel (if I'm right). Maybe the engine too.

Testing testing No I don't take screenshots when I'm the one shot down... xD I forgot to check the tractor beam. Nothing wrong by now. I too have met Mirages

Because they have too much lift at touch-down speed. (And the game cannot handle a wrong approach / go-around.) --> turned out to be false during a test

View File Spitfire Mk12 --------------- Spitfire for CombatAce --------------- SF2 version 2021 TurboSquid : original 3D model Snapper21 : source file donated to CA, project development, textures editing and decals Wrench : project development origin and inis Starfighter2 : original Spitfire Mk9 cockpit Logan4 : additionnal 3D parts and model editing to import into TW sims, textures editing, decals and inis. Cliff7600 : textures editing, decals and inis, cockpit editing. Thirdwire : textures and inis. These are the models made for CombatAce from the original TurboSquid 3D source file. It is made to be downloaded for free at CombatAce site only, and not to be used in any other way. The models have been designed for a SF2 / ThirdWire use and nothing else. Not to be merged with other files sharing the same original 3D model. - Spitfire Mk12 Submitter Cliff7600 Submitted 08/10/2023 Category Spitfire  

I don't have it but wanted to post anyway

Testing (and editing) over the welcoming kingdom of Dhimar

The wingmen reach out of fuel, the propellers stop but the aircrafts don't slow down, and they held the formation until WP 9 to finally crash when doing the landing approach. If you're cheating, do it til the end damn !

Just my 2 cents : Component[019]=Remove <-- Add component [Remove] <-- Component name must match ModelNodename=Empty <-- this can be any word you want DestroyedNodeName=gunner <-- this is the name of the part you want to remove DetachWhenDestroyed=TRUE HasAeroCoefficients=FALSE MassFraction=0.0 <-- You must add this line If you don't add the "MassFraction=0.0" entry the remaining weight will be shared with the part you added. And if the fuselage part (most of the time) doesn't have a "MassFraction=" entry, there is weight to allocate.

I didn't understood why the pictures were so dark. I thought "C'mon it was 1948, they knew how to take a photograph back then" ( / what's wrong with them !?! xD) And while I was studying the fading of the green paint on black and white pictures, my brain did its daily effort and I realised : the Spitfires had been repaint in NATO camo colors, dark grey / dark green / PRU blue. I used these values : Dark grey / Basalt Grey : hexa 575D64 Dark green / Yellow Olive : hexa 453F2F PRU blue : hexa 5C7A82 If you have more reliable values for these colors please tell me ! (the tail is in lighter olive green on purpose)

Ki-65 skins have been updated.

RM 693 / 350 sq

Spitfire Mk.XIV masquerading as a P-47D of the 410 Fighter Squadron / 373 Fighter Group

I was working hard on a very historical skin and then I don't know, I lost it... a little update / the anti glare panel is needed for the real bird Something related but still not the bird I want to do (LOD is done since 18 months) And this is the bird I wanted to make at first : Still some details to do

No.11 squadron also had their Mk.XII

You guys Spitfire enthusiasts have an amazing train of thoughts

View File Spitfire Hydroplane Mk1 / Mk5 / Ki-65 --------------- Spitfire for CombatAce --------------- SF2 version 2021 TurboSquid : original 3D model Snapper21 : source file donated to CA, project development and textures editing Wrench : project development origin and weapons pack Starfighter2 : original Spitfire Mk9 cockpit Logan4 : additionnal 3D parts and model editing to import into TW sims, textures editing, decals and inis. Cliff7600 : textures editing, decals and inis, cockpit editing. Thirdwire : textures and inis. Bunyap and Killerbee : weapon packs The guns come from the "SF2_Gun_collection" by Flogger23 These are the models made for CombatAce from the original TurboSquid 3D source file. It is made to be downloaded for free at CombatAce site only, and not to be used in any other way. The models have been designed for a SF2 / ThirdWire use and nothing else. Not to be merged with other files sharing the same original 3D model. - Spitfire Mk1a Hydroplane - Spitfire Mk1a Hydroplane Long Range - Spitfire Mk5b Hydroplane - Spitfire Mk5b Hydroplane w Vokes filter - Ki-65 Hydroplane Only two aircrafts of this pack actually existed : R 6722 and W 3760 Submitter Cliff7600 Submitted 07/13/2023 Category What If Hangar  

Su-33 Flanker D in parani colours by GKABS and team.

It's doable but it requires first some additional 3D meshes. Currently the hierarchy is : Fueslage_2 / LeftCanard Fueslage_2 / RightCanard If you would had : Fueslage_2 / "LeftPivotCanard" / LeftCanard Fueslage_2 / "RightPivotCanard" / RightCanard you could use the "LeftPivotCanard" & "RightPivotCanard" (whatever the names) as control surfaces, and use them as leading edge flaps "DeploymentMethod=AUTOMATIC_ANGLE_OF_ATTACK". I think it would bring some issues when on ground, with the canards moving without reason when the plane is stopped. (or maybe not, depending on the settings)

When making a new gunsight, you know you're done when you're blaming again the handling of the aircraft instead of the lack of successful hits.

@Spinners Can you post a screenshot of this seaplane in the water please ? I'm curious and I'll never have the chance to check it by myself. ------------- Mandatory Screenshot -------------

There's a Spitfire Mk XIV project in progress It's probably the same 3D model source.

It's easy to know when a parani tries to enter the Dhimari airspace. The air force interceptors don't let him any chance to evade. The picture is taken from a little airfield I added near Al'Duhok. It's the same place as the post before, with the Hueys. I'm the chased MiG you can see on the left (so you can admire the accuracy of the shot with their nuclear thingy) and I won't make it because they kept shooting at me even at sea level.