mue

The speed in the bottom left corner and the KIAS number in the debug screen show the same airspeed: indicated airspeed (IAS). Only the unit in the bottom left can be different (km/h or mph instead of knots). True airspeed (KTAS) at a given altitude translates to an indicated airspeed (KIAS) and vice versa. (In the game TK uses equivalent airspeed (EAS) for indicate airspeed) An online converter for airspeeds you can find here: http://www.hochwarth.com/misc/AviationCalculator.html Therefore IMHO it's not correct to average both types of velocities and compare it with real life data. Depending on what real life velocity is measured (indicated airspeed or true airspeed) the according numbers (KIAS or TIAS) should be compared. I think with ConstantSpeed=TRUE a constant speed propeller is simulated in the game. (AFAIK most WW-2 and post WW-2 prop aircraft have constant speed propellers.) The corresponding automatic variable pitch is simulated with the high prop efficiency over a broad range of the advance ratio. From TK: and HTH

Sorry for hijacking this thread. But as a layman I have a question: What are the advantages of photoshop over gimp?

After sifting through the archive of the thirdwire forum: Third Wire.7z I found the formula for thrust computation: Thrust = Power / Velocity * Efficiency Power is dependent on throttle setting and is multiplied with the coefficient from the altitude table Efficiency is taken from the prop efficiency table With the FM set to Normal the thrust (from debug output) matches this formula exactly. But with the FM set to Hard, the thrust in game is smaller. In the forum archive there is a thread "TK, ran into a constant speed prop thrust issue" that covers this issue: From TK: and If I understand this correctly then the InducedVelocity must be added to the Velocity in the thrust formula. But in the above formula the InducedVelocity is dependent on thrust (but for the thrust calculation I need the InducedVelocity). Maybe the thrust variable in the InducedVelocity formula is different to thrust calculated by the thrust formula? Does anybody have an idea and can shed some light on this?

The unit is Watt (W). MinManifoldPressure, MaxManifoldPressure and WEPManifoldPressure are not used for the flight model. Those values are used only for the display of the cockpit manifold pressure gauges.

Does anyone have a documentation (e.g. formulas) how the resulting thrust is computed from the FM ini values at given input values (throttle, altitude, velocity)?

No.

As most of you know spotting other aircraft in SF2 is quite difficult. I think most are using the red targeting box to engage enemy aircraft. But only the currently targeted aircraft is marked with the red box and not the other aircrafts. Another option would be to turn labels on (HUD Display option set to "Easy"). Unfortunately the label text is too verbose and is also shown at too long distances. Some people already had the idea to change the label text into a single dot but AFAIK nobody has accomplished it yet...until now... I proudly present the "dot label mod": dot_label_mod.zip With this mod labels are shown as a dot and only within a distance of 10 nm. This mod uses a modified text drawing shader that hides all characters and digits of the label text and only draws the "dot" character. Unfortunately there is a negative side effect: the text in the target info box is also "filtered" by this shader and therefore not correctly displayed. So I disabled the target info box. Furthermore to get rid of the way point label text (which shows up if the HUD Display option is set to "Easy") the shader also completely hides all text that is drawn with NormalColor. This means that also the text in the top info box and in the bottom left info box is hidden. But the afterburner message is still shown. To install this mod just put the contents of the zip file (huddata.ini and twfont.fx) into your Flight folder and set the HUD Display option to "Easy". The enemies are shown with red dots, and friendlies are shown with blue dots. But you can change the colors to your liking by changing the values of EnemyTargetColor and/or FriendlyTargetColor in the huddata.ini AND setting exactly the same values (without the alpha compononent) in the twfont.fx files: e.g: if you set in huddata.ini EnemyTargetColor=0.1,0.2,0.3,0.4 you must set in twfont.fx float3 EnemyTargetColor = float3(0.1,0.2,0.3);

The draw distance for labels is determined by the game engine and AFAIK can not be changed. What my mod does is, it blocks all characters but the 'dot'. The distance text for distances greater 10 nm is drawn in the format x nm (e.g. 23 nm). That text contains no 'dot', all text is blocked. If the distance is less than 10 nm, the format changes to x.x nm (e.g. 9.9 nm). That text contains a 'dot' and the dot is visible because it's not blocked.

My measurements in SF2: flying over a 3000m runway with 200 KTAS takes around 30 seconds, with 400 KTAS around 15 seconds. That means the velocity in game is 100%.

Do you mean the subjective perception of velocity or do you think the aircraft is really moving with 50% of the real life velocity?

Probably your merged installation is somehow faulty. Can you create a single mission with the A-4B?

I don't ignore facts. I only want to clarify once and for all the scaling in the thirdwire games. Myself I could only test SF2, FE2 and WOV stock objects (aircraft, ground objects and buildings). And they all (including buildings in FE2) are full size. Sorry, I forgot to mention here that the measurements were made for FE2 buildings, not SF2. So again, since I don't own FE1: Can please someone measure floor height of FE1 buildings. Thanks!

I also checked some terrain lods: buildings. The measured average floor height is around 2.5m. Seems it's real life scale.

Sorry for the interruption, but where is this 63% scale for First Eagle objects is coming from? I know that stock SF2 game (including First Eagles 2) objects are of 100% size. I also know that Wings Over Vietnam (the only SF1 game I have) stock objects are of 100% size. Therefore I suppose that First Eagles stock objects are of 100% size too. To be sure, can someone please measure some First Eagle objects with the LODViewer and compare it with real life size.

Maybe just to preselect the campaign in the "create campaign menu"?

Never noticed this before. After some tests, it seems it depends on the flight model setting (normal or hard). If set to normal, the user gets the same weight reduction as the AI. The question is, what defines the amount of weight reduction?

After running the renamed exe (StrikeFighters2 Formosa.exe) for the first time and selecting the create create campaign menu, then exited the game without changing anything, the campaign section in options.ini is as follows: [Campaign] CampaignName=561029 Operation Kadesh PlayerService=Israel PlayerUnit=No. 117 First Jet Squadron AircraftType=Meteor8 Difficulty=NORMAL Length=NORMAL AircraftSupply=NORMAL WeaponSupply=NORMAL LoadCampaign=FALSE CampaignSavename= As said already, those entries are just the saved settings from the campaign->create campaign menu. In my case it's the first stock campaign from my fully merged install. After restarting the game and selecting the create campaign menu, selecting the campaign "590721 Operation Formosa Freedom", choosing a service and aircraft the campaign section in options.ini now reflect the last selections, e.g: [Campaign] CampaignName=590721 Operation Formosa Freedom PlayerService=USN PlayerUnit=VA-106 Gladiators AircraftType=A-4B Difficulty=NORMAL Length=NORMAL AircraftSupply=NORMAL WeaponSupply=NORMAL LoadCampaign=FALSE CampaignSavename=formosa freedom a-1j.SAV You don't have to change this entries manually. All can be changed / choosen from within the game create campaign menu.

Ok, I installed and tested the "Operation Formosa Freedom" Campaign (the first example you mentioned above, that supposedly missed required options.ini edit instructions): And ...surprise... I could start the campaign without problems (and without editing anything in the options.ini manually). So maybe there are no instructions to edit the options.ini because it's simply not required for this campaign.

IMHO the entries under [Campaign] are just the saved settings from the campaign->create campaign menu in the game ui. So I doubt this entries have to be edited manually.

There is a document for sf1, but I think most also applies to sf2: https://combatace.com/forums/topic/92182-requested-strike-fighter-editing-info-document/

I think the aliasing is defined in ALIAS.LST contained in ObjectData001.CAT. The TW cat extractor does not extract this file, but my cat extractor does. e.g. ALIAS.LST contains the following lines, that maps insignia003 and insignia004 to insignia002: Insignia003.tga Insignia002.tga Insignia004.tga Insignia002.tga

It should be possible to change texture filenames inside a LOD file with a HEX editor, but I haven't done it myself yet. If you send me the lod file and tell me what texture file name should be changed, I can try it.

Finish my todo lists from 2016, 2017 and 2018

Since I mostly fly older jets I never noticed the following hud behavior: If I yaw the aircraft, the pitch ladder in huds from "modern" jets (e.g F-14, F-15, F-16) in game moves horizontally. Is this a bug or engine limitation? Edit: uups, after watching some youtube videos of real life huds, this behavior seems correct...

Is it possible to create a "caged" HUD in the game?