Jump to content

mue

+MODDER
  • Content count

    189
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by mue

  1. Why are there textureset definitions in two places: one in the <aircraft>.ini file and the other in the textureset.ini file (within the texture sub folder). It seems both contain the same information. And if the content differ, which one has priority?
  2. What I've learned so far about the decals system: Position=a,b defines the position of the center of the decal texture at the aircraft in meters. a,b are either the x,y-, y,z- or y,z- coordinates depending on DecalFacing. If DecalFacing is TOP or BOTTOM then its the x,y coordinates, if LEFT or RIGHT its y,z and if FRONT(?) or BACK(?) its x,z. In the lod viewer you can move the mouse pointer over the aircraft and the x,y,z coordinates are shown in the status bar at the bottom. Scale defines the size of the decal in meters. E.g. a Scale of 1.0 means that the decal has the size of 1x1m on the aircraft, a Scale of 0.5 means a size of 0.5x0.5m...
  3. I'm trying to understand the decals system. In which directories does the game look for decal texture files (referenced by decals.ini)?
  4. So, the game ONLY looks in Objects/Decals (and maybe subfolders here) and not in Objects/Aircraft/ or other folders?
  5. 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);
  6. The font texture is internally generated by the game accordingly to the given font type and size. An example you can see here: https://learnopengl.com/In-Practice/Text-Rendering If your defined texture area (uvMin, uvMax) cuts some characters then only fragments of those characters are drawn .
  7. None that I know of. I think I used some kind of binary search: 1.) split the texture in two halfs: rectangle1 with uvMin / uvMax = (0.0,0.0) / (0.5,1.0); rectangle2 with (0.5,0.0) / (1.0, 1.0) 2.) try both rectangles and check with which the dot (besides other characters) is drawn. 3.) split this rectangle further on (step 1.)): e.g. if the dot is in rectangle 2, then the next two (smaller) rectangle areas to check are (0.5,0.0) / (1.0,0.5) and (0.5,0.5) / (1.0,1.0)
  8. The relevant parameters are uvMin and uvMax in lines 93 and 94. These parameters define the rectangular area (which should contain the "dot") on the font texture. Only fragments (pixels) with texture coordinates within that rectangular area are drawn visibly.
  9. In the huddata.ini the following must be set: [SmallLabelFont] TextFontName=Courier TextSize=10 The color numbers for grey are x,x,x. For dark-grey x is small, e.g EnemyTargetColor=0.1, 0.1, 0.1
  10. I wrote a tool that someone may find useful: a LOD viewer. I tested it on Windows 7 and 8. Unfortunately it doesn't run on Windows XP. From the readme.txt: LODViewer Version 0.1 Author: mue Use at your own risk. The program is free for personal, non-commercial use. Usage: LOD files are loaded with File->Open... The program also tries to read the ini file with the same basename (eg. tank.lod -> tank.ini) for textureset information. The texture directory can then be selected via the texture directory combo box. If no ini file is found or it does not contain textureset information then the texture files are assumed in the lod file directory. The left upper window shows the node structure: node names and material ids. Nodes can be selected with left click and deselected with ctrl+left click. The lower left window shows the texture file names of the materials. The right graphic window displays the 3D view of the lod object. The view can be manipulated with the mouse: rotation: left click + move translation: right click + move zoom: mouse wheel reset view: middle click Nodes can be selected with ctrl+left click, and deselected with ctrl+left click on a blank area. Selected nodes are highlighted in red. Nodes whose texture couldn't be read are displayed in green. Known issues, missing features, bugs: -simplistic lighting (no specular, glossiness, reflection, bump mapping,...) -no transparency -no decals -problems with reading some tga files Screenshot: (Download link temporarily redacted)
  11. My (partial) understanding of the tfd file format. Maybe Gerwin can fill the gaps since he wrote a tfd/hfd editor. number variable type description of bytes 4 integer number of tiles in x (W-E) direction 4 integer number of tiles in y (S-N) direction 8 double tile size in meters two dimensional array of tiles in row (W-E) major order, beginning in the south-west of the map: for each tile 2 short texture id, references the texture tiles as follows: texture id = NNN - 1, with NNN the number from the [textureNNN] entries in terrain_data.ini file 2 short tile rotation: 0 = 0 degree, 1 = 90 degree, 2 = 180 degree, 3 = 270 degree (I forgot if clockwise or counterclockwise) 8 ? ?
  12. "Sachsen ist wie das Internet. Nur in echt."
  13. Mues Toolbox

    Version 0.2.1

    1,037 downloads

    In this package you find the current versions of my programs. Since all programs are using the same Qt and Microsoft Visual Studio libraries I thought it is convenient to put them all together. This package contains currently: LOD Viewer V0.5.2 Target Area Editor V0.2.2 (Updated) CAT Extractor V0.1.0 (NEW!) For usage instructions of the programs please read the readme files located in the Readme folder.
  14. Do335 has already done it. He (manually!) downloaded all threads with posts from TK from the thirdwire forums: https://combatace.com/forums/topic/85815-preserving-the-tw-official-forum/ His download link is dead now, but fortunately I found a copy of this package on my HD : Third Wire.7z
  15. Although the target area editor in its current state only has viewing (and no editing) capabilities I decided to release a first version. Maybe someone find it already useful. For usage instructions read the readme.txt. I tested it with stock terrains, Rends germany terrain and the range terrain. Feel free to report bugs, feature wishes etc. TargetAreaEditorV0.1.zip Screenshot: Rends germany terrain, (now ex-) airbase near my hometown.
  16. Regarding view/head position changes: With Track IR you can change your view/head position also in the lateral direction (up/down and left/right). Add/configure the following entries in the [CockpitSeat001] section in the <aircraft>_cockpit.ini to allow larger lateral head movements: MinMovementX=-0.1 MaxMovementX=0.1 MinMovementZ=-0.1 MaxMovementZ=0.1
  17. View File LOD Exporter for Blender I tried to implement the exporter only based on the information I found by investigating LOD files. I'm not a 3D Modeler myself. I only tested the exporter with rather simple object (hierarchies). The bottom line is that I have no idea if the exporter works for you. So please give feedback. 1.) Installation Open the Blender User Preferences - Add-ons Tab (File -> User Preferences... -> Add-Ons) Click "Install from File..." Browse to and select the exporter python script "io_export_sf2_lod.py" Click "Install from File..." (or double click on the script name) In the Add-Ons Tab under Supported Level select Testing and enable "Import-Export: Strike Fighters 2 LOD Exporter" The LOD exporter is now installed and enabled. Under File -> Export you should see the menu item "Strike Fighters 2 LOD (.lod)". It's greyed out until an exportable object is selected. 2.) Usage Select the object you want to export and click File -> Export -> Strike Fighters 2 LOD (.lod) The file browser opens. In the lower left area you see the LOD exporter options: -enable/disable writing the out file (text file with information about the exported object(s)). -enable/disable animation export -allow decals: This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." This dialog setting is used as default for all objects to be exported. However, it can be overwritten by each individual object via the custom object property "AllowDecals" = 0(false) or 1(true) The selected object and all child objects are exported. Two custom object properties are supported by the exporter: -AllowDecals = 0 or 1, This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." -UseFlatNormal = 0 or 1, if set to 1 then all vertex normals are pointing straight up (normal = (0,0,1)) in the objects local coordinate system. Please note! The objects must meet the following requirements: -No scaling in the Transform Properties allowed (that means: scale x = y = z = 1.0). If your object has scaling, it should be applied to the mesh (Ctrl-A) Scaling is only allowed for animations. -A material must be assigned to the object. Only the first material of an object is exported. The following material parameters are exported: -Diffuse Color (the lod file format also contains ambient color. Currently the exporter set ambient color = diffuse color) -Specular Color -Specular Intensity -Specular Hardness (I think in 3ds Max it's called glossiness) -if "Shading -> Emit" > 0.0 then self illumination is enabled -Transparency (if transparency is enabled, then the object doesn't cast and doesn't catch shadow. if transparency is disabled, then the object cast and catch shadow. The specific LOD format version the exporter writes, doesn't support arbitrary cast/catch shadow combinations. The other LOD formats I don't understand enough (yet). Sorry!) -Alpha -Mirror Reflectivity -Diffuse texture image name (as diffuse texture the exporter uses the texture where "Influence -> Diffuse -> Color" is enabled) -Normal map texture image name("Influence -> Geometry -> Normal" is enabled and the Normal value is also exported) -Specular map texture image name("Influence -> Specular -> Intensity" is enabled) -Normal and specular map can only be used together with a diffuse map. (If I exported a normal or specular map without diffuse map, then the LOD wasn't shown in the game or the game crashed. I don't know why...) Animation Export: This exporter supports the following object animation types: location, rotation and scaling. Frames 10, 20, 30, ..., 100 are exported as animation 1 Frames 110, 120, 130, ..., 200 are exported as animation 2, ... 3.)Credits: Thanks to logan4 and angelp who provided me with specific lod files that helped me to understand the lod file format better. 4.)Changelog: Version 0.1: -initial release Version 0.2: -bugfix: didn't work in blender version 0.79 Version 0.3: -animation support -added custom object properties: "AllowDecals" and "UseFlatNormal" Submitter mue Submitted 04/30/2018 Category Utilities / Editors  
  18. Version 0.3

    87 downloads

    I tried to implement the exporter only based on the information I found by investigating LOD files. I'm not a 3D Modeler myself. I only tested the exporter with rather simple object (hierarchies). The bottom line is that I have no idea if the exporter works for you. So please give feedback. 1.) Installation Open the Blender User Preferences - Add-ons Tab (File -> User Preferences... -> Add-Ons) Click "Install from File..." Browse to and select the exporter python script "io_export_sf2_lod.py" Click "Install from File..." (or double click on the script name) In the Add-Ons Tab under Supported Level select Testing and enable "Import-Export: Strike Fighters 2 LOD Exporter" The LOD exporter is now installed and enabled. Under File -> Export you should see the menu item "Strike Fighters 2 LOD (.lod)". It's greyed out until an exportable object is selected. 2.) Usage Select the object you want to export and click File -> Export -> Strike Fighters 2 LOD (.lod) The file browser opens. In the lower left area you see the LOD exporter options: -enable/disable writing the out file (text file with information about the exported object(s)). -enable/disable animation export -allow decals: This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." This dialog setting is used as default for all objects to be exported. However, it can be overwritten by each individual object via the custom object property "AllowDecals" = 0(false) or 1(true) The selected object and all child objects are exported. Two custom object properties are supported by the exporter: -AllowDecals = 0 or 1, This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." -UseFlatNormal = 0 or 1, if set to 1 then all vertex normals are pointing straight up (normal = (0,0,1)) in the objects local coordinate system. Please note! The objects must meet the following requirements: -No scaling in the Transform Properties allowed (that means: scale x = y = z = 1.0). If your object has scaling, it should be applied to the mesh (Ctrl-A) Scaling is only allowed for animations. -A material must be assigned to the object. Only the first material of an object is exported. The following material parameters are exported: -Diffuse Color (the lod file format also contains ambient color. Currently the exporter set ambient color = diffuse color) -Specular Color -Specular Intensity -Specular Hardness (I think in 3ds Max it's called glossiness) -if "Shading -> Emit" > 0.0 then self illumination is enabled -Transparency (if transparency is enabled, then the object doesn't cast and doesn't catch shadow. if transparency is disabled, then the object cast and catch shadow. The specific LOD format version the exporter writes, doesn't support arbitrary cast/catch shadow combinations. The other LOD formats I don't understand enough (yet). Sorry!) -Alpha -Mirror Reflectivity -Diffuse texture image name (as diffuse texture the exporter uses the texture where "Influence -> Diffuse -> Color" is enabled) -Normal map texture image name("Influence -> Geometry -> Normal" is enabled and the Normal value is also exported) -Specular map texture image name("Influence -> Specular -> Intensity" is enabled) -Normal and specular map can only be used together with a diffuse map. (If I exported a normal or specular map without diffuse map, then the LOD wasn't shown in the game or the game crashed. I don't know why...) Animation Export: This exporter supports the following object animation types: location, rotation and scaling. Frames 10, 20, 30, ..., 100 are exported as animation 1 Frames 110, 120, 130, ..., 200 are exported as animation 2, ... 3.)Credits: Thanks to logan4 and angelp who provided me with specific lod files that helped me to understand the lod file format better. 4.)Changelog: Version 0.1: -initial release Version 0.2: -bugfix: didn't work in blender version 0.79 Version 0.3: -animation support -added custom object properties: "AllowDecals" and "UseFlatNormal"
  19. Since Stary kindly remembered me in the "tree planting" thread of my promised TOD Editor, I want to apologize for the (very) long delay. Shortly after I made the proof of concept of custom shaped tod objects another (Real Life) project took over: planning and building our house. Therefore in the last one and a half year I didn't have that much time and energy for modding/programming activities. Now we finally live in our new house and I recently resumed my modding/programming activities. This is my roadmap for 2018: 1) LOD Exporter for blender: Currently I'm working on a LOD Exporter for blender. It's in an early stage. Mesh export seems to work but only uses color information yet, no textures, no bump maps, no animation, ... . 2) Updating LOD Viewer and Target Area Editor Besides implementing new features I plan to switch to the OpenSceneGraph library for 3D visualizing instead of pure OpenGL. It will reduce the programming effort in the future and also brings other benefits. 3) TOD Editor Maybe I will implement it as an extension of the Target Area Editor, I'm not sure yet. The use of the OpenSceneGraph library should give me the capability to import several 3D file formats that OpenSceneGraph supports (instead of writing the file importer myself) and let me convert them to TODs.
  20. What do you mean by "configure the models"? Do you mean defining/simulating aircraft systems, avionics,...? Then it's dependent on the game/simulation engine you are using, e.g: -In the SF/SF2 game engine the aircraft systems are not defined by a scripting language but by configuration (*.ini) files. -The Digital Combat Simulator uses LUA as scripting language. -The open source flight simulator Flightgear uses it's own scripting language NASAL. But if you mean a scripting language that supports the 3d modelling? Then it's dependent on the 3D model software you are using, e.g Blender uses Python.
  21. Do you mean using more than 999 target areas with SF2NA? I don't know if any of the SF2 games can handle that number of target areas.
  22. I really hope flightsimlabs gets sued. What they did was very unethical and illegal. I'm a software developer myself and I know piracy is a problem, but I would never ever install malware on my customers computers. And even if the malware was targeted only at pirates, thats not the point. It's illegal. Period! The companys CEO even doesn't see the problem. He appologized not because he has done something unethical and illegal but because some customers may have been offended. I would never trust this guy. It seems he was also involved in the "PMDG MD-11 drm destroys fsx installation" stuff.
  23. A question to the FM gurus: How do you develop and test your flight models? I'm especially interested in how to gather telemetrie data (e.g. velocity, height, acceleration, turn rate, ...) and how to plot graphs from those data (e.g. velocity over time, height over time, ...). I know about the debug display. But is there a way to output this data into a text file?
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..