mue

Yes, you are correct. The solid TOD objects of a tile share the same texture (atlas) defined by SolidObjectTexture (and respectively the alpha objects share the same texture defined by AlphaObjectTexture). Thats how the game engine works and there is nothing I can do about it. That also means objects that use different texture files can not be imported and used together in a tile. The objects must be first remapped to use the same texture atlas that also has to be created. I should update the readme.txt to clarify that restriction.

View File TODEditor After nearly 6 years since my proof of concept experiments with the TOD files I'm ready to release a first version of the TODEditor (could almost be a nominee for the Duke Nukem Forever Award ). Main Features: Easy editing of TOD files: cut/copy/paste, moving and rotating of objects Import of object models files: *.lod, *.obj or *.3ds Warning: Use at your own risk. The TODEditor is currently in an early beta stage and can contain serious bugs. So, please backup your terrain files before you work with the TODEditor. I have warned you! The program is free for whatever use (commercial or personal). Installation: Extract the content of the zip package to a convenient location. The TODEditor depends on the Microsoft Visual Studio 2019 C++ libraries. If not already installed on the computer (e.g. by other applications) they have to be installed by running vcredist_x64.exe (you can find it in the redist subfolder of this package). Start the program by double click the todeditor.exe. For further information see TODEditor_readme.txt. Mue Submitter mue Submitted 03/01/2022 Category Utilities / Editors  

In the TrackIR software you must disable the Z-Axis and maybe Trueview too.

AFAIK that's not correct. Control surface meshes don't have any influence on the FM. You can test this by e.g. linking the mesh node of the right wing to the left aileron. This gives a funny animation but the flight behaviour doesn't change. That's correct. Weapon station entries are one of two cases I know of where the 3D model influences the FM (the other case are the landing gear entries). The weapon mass is attached at the pivot point (not necessarily the mesh) of the node defined by ModelNodeName. If ModelNodeName is missing, then the position defined by AttachmentPosition is used. In either case only the lateral (left, right and maybe? up, down) coordinates are considered, the longitudinal coordinates (fore, aft) are ignored.

Hi all, I'm OK. But as GKABS correctly assumed, I was and still am very busy with real life work. And now even more so. In september we had a sudden change at work that eventually increased my workload again. So, SF2 modding is still on a back burner .

I'm curious what the root cause was and how you fixed it?

Wow, thank you all for the praise. It means a lot to me. Really! I still have plans to update the tools: TargetAreaEditor, LODViewer and LODExporter. And first and foremost I want to eventually release a first version of the TODEditor! I know I promised the TODEditor since by now more than 5 years(!). And three months ago I thought the first version will be "ready in two weeks"(TM). But than again RL stuff, vacation, etc. ... happened, and I haven't worked much on it since then. But right now I hope (again) the first release will be "ready in two weeks"(TM). TODEditor WIP screenshot:

I think you are looking at the wrong section. [LeftElevator] and [RightElevator] are the crucial sections: [LeftElevator] ... MaxControlSpeed=162.29 ControlMachTableNumData=4 ControlMachTableDeltaX=0.05 ControlMachTableStartX=0.86 ControlMachTableData=1.000,0.920,0.681,0.000 ...

Per default the games write the options.ini and version.ini to %Userprofile%\Saved Games\Thirdwire\<game exe name>\ (e.g. C:\Users\<username>\Saved Games\ThirdWire\StrikeFighters2 Vietnam\). By changing the Options/OptionsFile entry in the <game exe name>.ini file you can indeed change the location of the options.ini file: [Options] OptionsFile=F:\MyOptionsDir\MyOptions.ini But you have to make sure that the target folder (in the example above F:\MyOptionsDir) already exists. However, the version.ini (and I think some auto update stuff) will still be written under ...\Saved Games\... The %Userprofile%\Saved Games folder is actually one of the 'special folders' in Microsoft Windows. Windows allows you to change the location of the special folders and therefore also of the Saved Games folder: Right click on the folder -> Properties -> Location. After that all games in windows will write it's data to this new location. Unfortunately the SF2 games with the exception of SF2 North Atlantic are buggy in this regard. They will still write to the original location %Userprofile%\Saved Games .

https://combatace.com/forums/topic/93428-lodviewer/?do=findComment&comment=756172

I think you mean the directory (not direction) entry in the [Mods] section of the options.ini file(s), e.g.: [Mods] Directory=F:\ThirdWireMod\StrikeFighters2 Europe If you change it in every game options.ini to point to the same mod folder, then I think every game will use the same mod folder. But since I haven't tested it myself, I don't know if it causes any problems.

Is it possible to select the GPU from within the game: Options->Graphics->Display Device? I can't test it because I have only one single GPU.

@Wrench I think ponyboy meant the links to thirdwire.com (posted by crusader) are dead. @ponyboy314 The links crusader posted are indeed dead. But as Wrench wrote, you can also download the thirdwire tools here from combatace.com. But I also recommend the cat extractor from mues toolbox. After a small configuration step (i.e. setting the SF2 install directory) the cat extractor (from mues toolbox) searches all CAT files at once. In contrast with the thirdwire cat extractor you must open each cat file separately, meaning you have to know what cat file contains the file you are looking for.

I think Gepard is correct. Maybe the road you added is seen by the game as runway. Can you please check what TargetType the road is? Maybe something like MEDIUM_RUNWAY? I made some tests and it seems that if you add a second runway to a target area then the headings of both runways are added up and the other objects are rotated according to the sum of both headings.

In game at airfields the objects are oriented in reference to the runway orientation. E.g. if you rotate the airfield then the other objects are rotated too. The target area editor also supports this but with the following limitations: The runway object must be the first target in the target area. The offset of the runway must be 0,0. It doesn't matter if you first add the objects and then rotate the runway or the other way around.

You can try the dot label mod: http://combatace.com/topic/86215-showing-label-as-a-dot-mod/ This mod overlays all friendly/enemy objects within a 10 nm radius with a blue/red dot. The disadvantage of this mod is, you lose the target info box.

You must extract VIEWLIST.INI from FlightData.CAT (located somewhere in the game install directory tree, I think in the Flight folder). To extract the file you need a cat extractor program. You can use the cat extractor from the 3W toolkit or the one from Mues Toolbox. VIEWLIST.INI must be extracted into <mod folder>/Flight/ Neither SF2 games support multiplayer. The multiplayer entries you found are legacy from the SF1 games.

You can disable the view pitch and yaw limit in the VIEWLIST.INI with [ViewClass002] ViewClassName=CockpitViewClass ... LimitPitch=FALSE LimitYaw=FALSE

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?