mue

Back then, as I last played the game (around 2010?), the command bindings were hardcoded to key presses. You couldn't bind commands to your HOTAS from within the game. You had to use the programming software of your HOTAS to map HOTAS buttons to key presses.

EECH brings back memories. I haven't played it for years. BTW, with EECH I started my modding activities. Back in 2008 I implemented the MFD export feature in EECH. Having access to the source code definitely helped (TK, do you hear me? ) Regarding tutorials: have you checked EECH Central? Maybe the original game manuals are also still applicable?

Transparency of the material must be disabled. From the lod_exporter_readme.txt: And maybe you have to add something like [Shadow] CastShadow=TRUE ShadowCastDist=500 MaxVisibleDistance=500 to the object' .ini file.

I only know about two "domains", where the 3D model has an impact on the FM: Ground handling depends on position of the 3D model' gear nodes. Mass balance change by loadout depends on position of the weapon station nodes (e.g. pylon, ...) Are there any further "domains", where the 3D model can influence the FM?

Could it be that you already lost the file while moving the SF Israel mod folder, meaning the game is not to blame for removing the file?

Do you remember if it does happen on random or only after a game/DLC update/install?

I doubt that the game removes any files from the mod folder. I've never experienced such things. But what I think the game indeed does (and then only after a game update or a merged install of another SF2 game or DLC) is to revert stock aircraft and ground object ini files, i.e. Object/Aircraft/<aircraft>.ini and Object/GroundObject/<groundobject>.ini. I think no other files, e.g. *_data.ini files are touched. Can anyone confirm this?

There are no individual Effect.ini files in the CAT archives. All stock effects are defined in particlesystem.ini (contained in FlightData.CAT).

Yes the LODViewer has no problem with spec and bump (normal) maps, ... because the LODViewer completely ignores them

It seems every GIMP user stumbles upon this (myself included, of course ): https://combatace.com/forums/topic/93235-how-do-you-make-serial-number-decals/?do=findComment&comment=753952

Holding the shift key gives you finer control. From the readme: The position and heading of selected objects can be changed with the mouse: -translation (coarse): ctrl + left click + move -translation (fine): ctrl + shift + left click + move -rotation (coarse): ctrl + mouse wheel -rotation (fine): ctrl + shift + mouse wheel

The LODViewer can read the LODs directly from the CAT files. For this you have to set the SF2 install directory and enable CAT file access under Settings->CAT File Access. If you open an aircraft.ini file with the LODViewer and it didn't find the lod file in the same directory then it tries to load the lod file from the CAT files.

Technical explanation: TK uses for decal texturing the "clamp to edge" (or rather its DirectX equivalent) texture wrapping mode. For more info see: https://open.gl/textures

Of course for a switch it won't work. Thats why I wrote "3D objects [that] are not that much extruded", e.g. screws, nuts, bolts, grooves, ...

Actually the whole rendering of a 3D scene onto a (2D) monitor is an illusion. If the 3D objects are not that much extruded it shouldn't make a big difference if the surface normals (for lighting computation) come from a normal map or from a detailed mesh.

Thirdwire forum threads with post form TK were thankfully archived by the combatace user Do335. You can find the TW forum archive here: https://combatace.com/forums/topic/92272-third-wire-forums-no-longer-linked-on-website/?do=findComment&comment=745634 Regarding the question, if that aircraft systems are implemented, TK posted on 10 Dec 2009 the following: Well, I think the answer is No, please check the stock plane's data to see whats implemented. TK Maybe some of those systems were implemented after 2009. I don't know.

Yes, I can recommend the Flugplatzmuseum Cottbus (Sorry, it seems the webpage is in german only). Very nice and friendly people there. I too had the chance to sit in the cockpit of this very Mi-24D. If interested, I can post some cockpit photos.

Yes, a wiki would be a good idea. I know there is a lot of information in this forum and especially the Knowledge Base sub forum. But searching for specifics can sometimes be tedious. A wiki with more structured / linked / updated information would be an improvement. But I have no experience how much effort it is to setup a wiki. And I wonder how many modders are still around and willing to actually contribute to the wiki?

Have you tested the TOD/terrain with the TargetAreaEditor? Are the TOD objects showing up in the TargetAreaEditor? Just to be sure that the TOD file is valid. Alternatively you can send me the TOD file and I will check it.

How do you determined that limit number. Have you counted the objects manually that show up in the game? Do you know if the first 1000 objects of the TOD are shown and the later are discarded, or does the game pick 1000 objects that are shown randomly from the TOD file? I wonder, if it's a limitation of the TE or the game? Are the TOD objects showing up in the TargetAreaEditor?

I like that comment someone made on reddit:

The "xx chaff left" and "xx flares left" messages in AIRCRAFTTEXT.STR can be overwritten with 'space' characters. Then an empty line is displayed on the screen instead. You can use this already modified AIRCRAFTTEXT.STR file. Just copy that file into your <mod-folder>/Objects/ folder.

The problem here is, that the model was exported without setting the option AllowDecals=True. With the option AllowDecals=True, your mesh can be as smooth as you like without getting decal bleeding problems.

Thanks! I didn't know about the movie Zero Hour! before. After some googling, I found this: Zero Hour! is a remake of Flight into Danger (1956). There is also a german remake (1964): And another US remake (1971):

From the Thirdwire forum (archive): Post by ThirdWire » Sat Dec 20, 2008 1:56 am: OnGroundPitchAngle is the angle the object is first placed, but once the object is placed, its final resting place depends on where your gears are and what their shock values are. So check your wheels data.