gerwin

Fair enough. :) I just added support for a ReferenceMap, which can be displayed just like the TileMap and the HeightMap. Details are in the manual.

My Classic TFD/HFD IcelandNA Is about as realistic as the Stock North Atlantic terrain, as it has the exact same targetareas: 2031 targets in 46 targetareas. The Stock North Atlantic targets are very generic, as the towns are just stock towns. It has a limited amount of tiles: greenish areas, brown rock/mud and snow. No roads or rivers. But great care was made to make the tiles blend in with eachother: no visible tile transitions or patterns. Places like the fjord airfield are pretty cool and real, but reykjavik is still nothing like it should be. I remember this terrain is shrunk compared to real size, like two thirds the size. The SF2NA naval campaign can be played with this terrain. Baltika's Iceland V2 Tried this briefly before, I would say more research went into this, regarding target areas and terrain type. 7519 targets in 166 targetareas. There are more different terrain tiles, but they are arguably contrasting a lot with eachother, as can be judged in the screenshots. Note that in reality the snow cover changes a lot throughout the year. I suggest you try both. The downloads are tiny in size anyways.

No, sorry. First thing on my TODO list for Strike Fighters is to finish the HEMTT truck model I started.

Thank you was enough already. :) There is this trick of listing the meshes for old style LODs like this. For newer LODs, made with a SF2 exporter, it is back to staring at the XVI 32 hex editor like wrench said....

OK it makes sense, I will see if such a thing can be added easily, when I next work on the program.

The attached document lists all the objects in the KC-10 LOD. I marked which ones appear to be the boom. Edit: 'Line03' and 'Line04' are the bulbs on the hull, where the boom starts. kc10.txt

Have you tried this?: http://combatace.com/topic/71249-sf2na-iceland-classic-tfdhfd-terrain/ In case you don't have the SF2NA stuff, use the files in the standalone folder (read the readme). If you really want the ocean plain, paint away the island in the middle ;)

TFDtool v0.94 is up @krfrge I raised the movement routes limits, you can find the current limits in the help file. @Eole2 Jpeg support has been added. Of course Jpeg compression has its advantages, when used under the right circumstances, like higher res tilesets. TFDtool works with images with the file extension "JPG", but extension "JPEG" does not work. So watch the file names. Windows hides extensions by default. Another new thing is the E key, which brings up a dialog with all the export options. @Centurion-1 Normally I would have added such a feature already. But the problem is that the DEM heightmap files used for Strike Fighters are usually in a rectangular format. And that projection does not really match any geographic reference maps. Unless someone converts projections with Geographic software (like Xplanet). But AFAIK I am the only one who did that once, for Wrench's North Sea map. Without exact projection conversion, a user remains approximating the exact locations of rivers and cities anyways. ...Feel free to correct me though.

Don't bother testing, I just noticed I indeed capped it at 64 somewhere. Will raise that limit in a few days.

Currently most, if not all things in TFDtool have a set limit. I see that the total movement points/coordinates is 4096, regardless of the amount of movement routes. Is the program failing to draw all your movement data? (PS. I answered the question from 14 February 2014 by combatace PM)

Yes; raw X, Y and Z coordinates. IEEE float format. With the far edge of the tile being 2000 meters. IIRC @10107 Glad you like it. Regarding quack74 his request, I mailed him an adjusted version of the program, with a target area limit of 1024. @101

I have never seen an updated hi-res version with the brown rock tiles.

With SF2NA in march 2012 a new LOD 3D model format was introduced (v8). DLCs after that time use this format. This is still the last LOD format up to this point in 2013. Any base install from 2011 or older cannot read this format.

Both yes and no. Angle is gone in the tod file, and there is no location for a single object. Instead there are coordinates of points/vertices which belong to triangles. The computer renders textured triangles. A square building has 5 square sides, 10 triangles. 8 different points. but possibly up to 3*10 stored points. Then the texture part stary just mentioned. And maybe some additional data I forgot about. Thanks for the list, it is still useful.

When I looked at the TOD files with a hex editor, I understood only half of it. Just (1) the amount of 3D objects and (2) the coordinates of their edges. Every TOD object being stored as an independant and individual bunch of polygons. This info would be enough to draw an overlay on the tiles to show where tod objects are located. But there are sections and bits of data in the tod file which I do not understand, so creating tods may be beyond my ability. One day I will try to draw the overlay I mentioned.

SF2 is a 32-bit program. And SF2 May 2012 is already large address aware. Based on the output of 'Dumpbin.exe /headers', which states: 'Application can handle large (>2GB) addresses. Trivia: The total 4GB address space of Windows XP 32-bit could have been much higher if microsoft and driver programmers would have put effort in. Instead Microsoft locked it to 4GB since Service Pack 2.

This is the technical table regarding addressing space in Windows. http://support.microsoft.com/default.aspx?scid=889654 General memory limits 32-bit OS 64-bit OS ------------------------------------------------------------------------------------- Total virtual address space 4 gigabytes (GB) 16 terabytes Virtual address space per 2 GB, 3 GB if the 2 GB, 4 GB if the application 32-bit process system is booted is compiled with the with the /3GB switch /LARGEADDRESSAWARE switch Virtual address space per Not applicable 8 terabytes 64-bit process

Old post, I know. This is the same issue I once had with an airfield. It was caused by having wrong 'tag' values for tiles below the airfield, 'tag' must be zero IIRC.

Is the SF2 game that works on the same patch level as the merged one? if so, try to copy over the game settings (options.ini)

Centurion-1: Looks much better now! I wish weathering was as simple as blurring panel lines, but I am afraid it is not. It appears like pointless shadows. Some things that worked nicely for the Silver F-5E was to make some panels differ in hue/saturation/brightness. (Though this trick is rather silver specific.) Then overlay a 'dust texture' layer. Add some smearing of a more rusty/oily color in the direction of movement (motion blur). Paint chipping may be nice too but should not be overdone. Etc.... When I find some nice weathering effect in an existing skin I often try to transfer it over by using 'color-range selection'. Then try out with which filter it blends the best on the new skin: Normal/Multiply/Color burn/Screen. The 3DS source? cool, so the shadow line, that comes from the cockpit when flying upside-down, can still be fixed.

IMHO Skin-modders should consider disabling that 'panel line blur' layer enterily, or use it very sparingly and locally. Try to mimic the pro's instead:

The Heightmap copy paste is fixed now. It was bad when I wrote it last week, I don't know why it even worked for me then. I also noticed the TFD_info2 detection had a typo, which triggered it everytime. This is also fixed. The TFDtool package is now updated to v0.93.

You are right, the heightmap copy function obviously got messed up with the last overhaul. It will be fixed soon.

IMHO the F-5 would look better if you did not overspray most panel lines with a dark color.

I don't mean misalignement really. more like the line starts shimmering when the camera moves. There is a bit in the LOD format, right before each texture name which means 'alpha blending yes/no' I guess. I changed that one too to get better results.