Cliff7600

Not at all. All the parts count : Fuselage / Left & Right Wings / Left & Right Outer wings / VerticalTail / Left & Right Stab - engines - control surfaces - weapon stations - fuel tanks - landing gear Even "HasAeroCoefficients=FALSE" (Nose or Tail) part has a influence on the flight model when they have "massfraction" and "MinMaxExtents" values. (When they don't have massfraction entry at all, the weight is divided between parts that don't have massfraction entries. So "massfraction=0.0" is "not having a mass fraction value", and the lack of the entry gives a weight anyway.) If you want the F-4 to fly like F-86 you just copy/paste the F-86 data.ini and keep the F-4 structural parts (good luck with that...). It will be a total mess, won't work in game like you wanted at the start, and you'll had lost a huge amount of time doing so. You're welcome ! There's some special stall depart /spin lines "CheckStall=TRUE" and what is coming next. But the effect is very artificial. It triggers a stall spin, and several parts can have it (wings / outerwings / stabs) You can make an aircraft stall and the recovery impossible to do. You need at least one part of the lift surface in order to have the aircraft landing correctly (L/R wings and/or L/R outer wings) but the best spins that allow realistic recovery are made from a good flight model that don't call for these entries. Most of the time the less I use these stall entries the better is the stalling - spinning - recovering behaviour (as long as the FM is really working... take-off - flight - landing) I really don't like when I land and while rolling on the ground, as I slow down, these entries trigger a stall depart and the aircraft crashes on the runway AFTER the landing (ThirdWire Spitfire9 in hard mode)

Everything in the data.ini file. The AI aircrafts have their own mode for the flight model behaviour. It's never "hard mode" but some features apply though, that you don't have when flying "normal" as a player. And the game engine has something to do with the AI flights. You can use some entries in the data.ini file [AIData] but you'll never control them 100% with that part. There's some cheating as well (20 000 ft on way point 9 and on the glide slop in few seconds..., no collision point between wingmen on the runway, etc...)

Just plugging that wire back in and I'm back...

In soviet colours

7 mistakes game ? lol

Dhimari Air Force, 11th squadron on patrol following Spinners

An old screenshot from testing something else. The chasing Hurricane skipped the repaint, and he wants his share...

When 8 machine guns work longer than 4 cannons.

En route to Northern France.

Hey Lt if needed, send me the whole plane, tell me what you want and I'll fix it.

Still no joy CAT file access is enable. I have pointed to the "Strike Fighter 2" folder and the "Objects" folder and none worked.

I checked, I have the lastest version 0.6.3 Game installed in a separate folder, as I run Win 10

I fully agree I thank Mue each teach I work on inis, skins, decals... Hail Mue !

Well, there's a bunch of issues with this one. If you managed to have the canard surface move the right direction for the pitch up/down inputs, are they moving the right way for the roll inputs as well ? The whole control surfaces section must be checked and edited. There's no flap on the J-10.

Hello The 3D model is weirdly centered In the F-84F_data.ini file : [Pilot] SystemType=PILOT_COCKPIT PilotModelName= SetCockpitPosition=TRUE Position=0.00,1.57,0.96 SeatModelName=seat_f-84f SeatPosition=0.00,1.25,0.85 MinExtentPosition=-0.25,3.52,-0.30 MaxExtentPosition= 0.25,4.83, 1.09 CanopyNodeName=canopy_frame CanopyAnimationID=10

Sorry for the off-topic but... as you can see a ThirdWire model with the LOD viewer, can you tell me the name of the mesh below from the TW P-51D ? Because I have every intention to shutting it down for good xD ...I mean, having it operating the right way. ---------------------------------------------------- Edit after Wilches' answer ------------------------------------------------------------------------------------ [CoolerAnimation] SystemType=HIGHLIFT_DEVICE CDdc=-0.01 DeploymentMethod=AUTOMATIC_MACH Setting[1].Angle=0.0 Setting[1].DeployValue=0.0 Setting[1].RetractValue=0.28 Setting[2].Angle=25.0 Setting[2].DeployValue=0.28 Setting[2].RetractValue=0.27 MaxDeflection=25.0 MinDeflection=0.0 ControlRate=0.2 ModelNodeName=radiator_flap

Hi Jeff, if you have no answer maybe you should ask to Flogger23 as he is the skinner of the project ? Don't know if the man would share his templates... No seriously : everyone is involved in real life business and other projects, and there's something going on about the Mirage in which I'm out of hand... though I made the serial numbers ^^ (or I think so... not sure) So my answer is : if you need serial numbers, ask me

As much as the single seater...

It's the pilot increasing the heating system while the exterior get colder. During the battle of Guadalcanal, B-17 crews had to live by +50 deg Celsius / 120 deg F on the ground and fly by -50 deg C / -60 deg F at altitude. Hard for men and machines. (If I remember right) And on the other hand it's a cockpit entry that should work for an engine. I use it on other planes to have the exterior temperature. -----------------------------

Yes and no, I did half the job. Have you ever saw an european guy trying to set temperature with an US device ? [CabinTemp] Type=INLET_TEMPERATURE_INDICATOR NodeName=Selector_dial_ base_01 MovementType=ROTATION_Z Set[01].Position=140.0 Set[01].Value=-56.0 Set[02].Position=-140.0 Set[02].Value=30.0 "Set[02] value" to 30 or more as you like (Celsius lol ) Me, climbing to 30000 ft to check the temperature setting... Also I use the mesh name "Selector_dial_ base_01" not "Selector_dial_base_01", just in case you have deleted the space just before "base" in the LOD file.

Hello and welcome ! See post below, what Wrench said. ---------------------------------------------------------------------------------------- The problem comes from the terrain used. GermanyCE is the stock terrain by default and the problem won't happen as long as you stay between 1948 and 1984 (or maybe earlier/later). To solve it you should extract the "GermanyCE.ini" file and add the entry : [AllowedDates] StartDate=1923 EndDate=2030 With the years you want to have. But before doing such I would recommand to download a terrain and see how it's done. When you understood how things work then go modify it, but in the meanwhile take your time and don't try anything not under control xD Here you will find some content to read : https://combatace.com/forums/forum/268-thirdwire-strike-fighters-2-series-knowledge-base/ It won't adress all your issues but it's the place where to start. ----------------------------------- "Plane Year Problem" is better than "PLANE YEAR PROBLEM"

I have a very little contribution to add to the cockpit.ini : Instrument[xxx]=CabinTemp [CabinTemp] Type=INLET_TEMPERATURE_INDICATOR NodeName=Selector_dial_ base_01 MovementType=ROTATION_Z Set[01].Position=140.0 Set[01].Value=-56.0 Set[02].Position=-140.0 Set[02].Value=0.0 It adds nothing, but it works Great model !!! ------------------------------- Edit -------------------------------------- Set[02].Value=30 or more

Hey ! Someone left a wreck under this net ---------------------------------------------- Few years earlier ------------------------------------------------------------------------------------------------------------- And in case you wonder... yes it floats. Though a bit heavy for the float of the Rufe. Double "What-if", never happened either in real life or in game (officially...)

Nordo, Armed and Unafraid Made it ! I knew it Next time I'll take the cameras