arma2:terrain:l3dt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
arma2:terrain:l3dt [2012-09-12 00:01] snakeman added attribute / mask rgb color header. |
arma2:terrain:l3dt [2022-06-25 16:03] (current) snakeman info moved to a new homepage. |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== L3DT ====== | ====== L3DT ====== | ||
| - | Using L3DT to create terrain for ArmA 2. | + | [[tools:l3dt|L3DT]] |
| + | |||
| + | Using L3DT to create terrain for ArmA 2. This page was written mostly on L3DT v14.xx era. (I recall most of this text was written by Bushlurker). | ||
| You can export the final Texture Map directly and use as a Sat_lco... | You can export the final Texture Map directly and use as a Sat_lco... | ||
| Line 10: | Line 12: | ||
| One point to watch when exporting the AM layer is to switch it to color output - otherwise you'll be deeply disappointed... (options button in the save as dialog - change "ColourMapped (bool) to "true")... | One point to watch when exporting the AM layer is to switch it to color output - otherwise you'll be deeply disappointed... (options button in the save as dialog - change "ColourMapped (bool) to "true")... | ||
| - | |||
| - | That's how to export the relevant images... is that what you were wanting? | ||
| - | |||
| - | I wrote a PM a little while back where I woefully under summarized basic L3DT usage... I'll paste the relevant chunk of it here as an easy way out of having to type any more (bedtime )... | ||
| Once you have made a height-field in there you can just save that - export height-field as .png - you make your own .pbl - its just a text file - adapt the tutorial one | Once you have made a height-field in there you can just save that - export height-field as .png - you make your own .pbl - its just a text file - adapt the tutorial one | ||
| Line 20: | Line 18: | ||
| Then you get to "Attributes layer" - this is the bit that uses Climates - you can just use "DemoRockGrassSand" to start with... this will generate a layer with different colors for 3 different ground textures... Later on if you want more complex masks you'll need to read the L3DT instructions heavily - then adapt or create a "climate" of your own... | Then you get to "Attributes layer" - this is the bit that uses Climates - you can just use "DemoRockGrassSand" to start with... this will generate a layer with different colors for 3 different ground textures... Later on if you want more complex masks you'll need to read the L3DT instructions heavily - then adapt or create a "climate" of your own... | ||
| - | |||
| - | As a demo of L3DT 3 color output you could check out the [[http://forums.bistudio.com/showpost.php?p=1574684&postcount=1|Falkland Islands Scale Test]] & [[http://forums.bistudio.com/showpost.php?p=1574727&postcount=5|Source Files]] I gave away a while back - that's done exactly as described here - same "climate" - same procedure... | ||
| ...basically what it does is analyze your height map - decide where sand, rock, grass, etc needs to go - and it draws a map with colors where each of them go... sounds awful like a Mask_lco.... you can use it as one... | ...basically what it does is analyze your height map - decide where sand, rock, grass, etc needs to go - and it draws a map with colors where each of them go... sounds awful like a Mask_lco.... you can use it as one... | ||
| Line 58: | Line 54: | ||
| - | ====== Tips ====== | + | ====== L3DT With Visitor 3 ====== |
| - | **Satellite Mask & Texture** | + | Use a .png greyscale export from L3DT as your "first" import of the terrain into Visitor - along with a .pbl file - exactly like in the tutorial. At this stage things will import fast - you can use the .pbl file to microtune the sea level and generally get things the way you want them. |
| - | Save attributes map. Paint/paste your roads and airfields etc there. Import back to L3DT and choose proper color and attributes for the ne areas. Now you can export this into texture map too. | + | Later on, once you've been laying roads, etc - you might decide to use L3DT to tweak some areas - maybe for settlements, or flatten an area for an airstrip... However - at this stage, you may already have manually fine-tweaked heights in Visitor, or smoothed roads, etc - this makes the version of your heightmap currently in use in Visitor the most up-to-date one - so in order to preserve that work, you'll need to Export your heightmap from Visitor - tweak in L3DT, then Import back into Visitor - hopefully without disturbing anything! - this is especially important once you start placing objects at "absolute heights" - like bridge sections, etc... this is where XYZ format comes in handy. |
| - | **Resizing Heightfield** | + | Once your terrain is advanced a little - you'll find that that 2minute "terrain import via greyscale" can take 2 hours!! - it still works - just takes forever to reimport! However - for some reason XYZ format will still import ultra-fast. |
| - | Open your XYZ terrain in L3DT and select Operations -> Heightfield -> Resize heightfield. Then choose new size. If you wish to change the cell size, select Operations -> Heightfield -> Change horizontal scale. | + | Initial .png export from L3DT - note your minimum and maximum heights exactly. Import into Visitor with same max and min in associated .pbl file. |
| - | Calculating 4096 heightfield with 10m cell size attributes / texture layer will be very very slow. More than 1 hour of processing. | + | For any subsequent terrain editing once work has progressed a bit. |
| + | * Export terrain as image from Visitor (you'll get a popup with two sets of max/min figures - write down the TOP ones) - this will result in a .pbl and a .png... throw the .pbl away and... | ||
| + | * Import .png into L3DT (use the exact max/min you wrote down). | ||
| + | * Edit terrain to little hearts content... | ||
| + | * Export as XYZ... | ||
| + | * Re-Import into Visitor..... | ||
| - | ====== ImageMagick Mosaic Stitching ====== | + | Subsequent imports of XYZ seem to work OK - but I've found the initial import should be a .png and .pbl setup - at least until you're happy with the overall heights, sea level, etc. |
| - | How to create one satellite image out of L3DT saved mosaic tiles using ImageMagick. | ||
| - | Save the attributes and texture layers in L3DT using 5 x 5 mosaic's. This mosaic size is nice because lets say you make common 20480 x 20480 resolution satellite, it will mosaic into 4096 x 4096 tiles (5 x 5). | + | ====== Climate Colors ====== |
| - | BTW Creating 20480 resolution attributes and texture with L3DT takes about 2 - 4hours depending on your computer speed. | + | Redo your climate so the different surfaces in the AM map have the bright primary colors you want to use in your Layers.cfg/mask_lco. when exporting this as a .png, *look at "options" - change it to "color". |
| - | Use (in this example) for mask: Satellite_mask_mosaic and for texture: **Satellite_texture_mosaic** file names. | + | When creating/exporting the TX map (Sat tex layer). *maybe skip "use lightmap" - it makes odd shadows on the texture that can look weird in-game, and maybe skip "antialias" as well. |
| - | Write the MASK file names into "mosaic_mask.txt" file, which in our example looks like this: | ||
| - | <code> | ||
| - | Satellite_mask_mosaic_x0y4.png | ||
| - | Satellite_mask_mosaic_x1y4.png | ||
| - | Satellite_mask_mosaic_x2y4.png | ||
| - | Satellite_mask_mosaic_x3y4.png | ||
| - | Satellite_mask_mosaic_x4y4.png | ||
| - | Satellite_mask_mosaic_x0y3.png | ||
| - | Satellite_mask_mosaic_x1y3.png | ||
| - | Satellite_mask_mosaic_x2y3.png | ||
| - | Satellite_mask_mosaic_x3y3.png | ||
| - | Satellite_mask_mosaic_x4y3.png | ||
| - | Satellite_mask_mosaic_x0y2.png | ||
| - | Satellite_mask_mosaic_x1y2.png | ||
| - | Satellite_mask_mosaic_x2y2.png | ||
| - | Satellite_mask_mosaic_x3y2.png | ||
| - | Satellite_mask_mosaic_x4y2.png | ||
| - | Satellite_mask_mosaic_x0y1.png | ||
| - | Satellite_mask_mosaic_x1y1.png | ||
| - | Satellite_mask_mosaic_x2y1.png | ||
| - | Satellite_mask_mosaic_x3y1.png | ||
| - | Satellite_mask_mosaic_x4y1.png | ||
| - | Satellite_mask_mosaic_x0y0.png | ||
| - | Satellite_mask_mosaic_x1y0.png | ||
| - | Satellite_mask_mosaic_x2y0.png | ||
| - | Satellite_mask_mosaic_x3y0.png | ||
| - | Satellite_mask_mosaic_x4y0.png | ||
| - | </code> | ||
| - | Write the TEXTURE mosaic file names into "mosaic_texture.txt" file, which in our example looks like this: | + | ====== Tips ====== |
| - | <code> | + | |
| - | Satellite_texture_mosaic_x0y4.png | + | |
| - | Satellite_texture_mosaic_x1y4.png | + | |
| - | Satellite_texture_mosaic_x2y4.png | + | |
| - | Satellite_texture_mosaic_x3y4.png | + | |
| - | Satellite_texture_mosaic_x4y4.png | + | |
| - | Satellite_texture_mosaic_x0y3.png | + | |
| - | Satellite_texture_mosaic_x1y3.png | + | |
| - | Satellite_texture_mosaic_x2y3.png | + | |
| - | Satellite_texture_mosaic_x3y3.png | + | |
| - | Satellite_texture_mosaic_x4y3.png | + | |
| - | Satellite_texture_mosaic_x0y2.png | + | |
| - | Satellite_texture_mosaic_x1y2.png | + | |
| - | Satellite_texture_mosaic_x2y2.png | + | |
| - | Satellite_texture_mosaic_x3y2.png | + | |
| - | Satellite_texture_mosaic_x4y2.png | + | |
| - | Satellite_texture_mosaic_x0y1.png | + | |
| - | Satellite_texture_mosaic_x1y1.png | + | |
| - | Satellite_texture_mosaic_x2y1.png | + | |
| - | Satellite_texture_mosaic_x3y1.png | + | |
| - | Satellite_texture_mosaic_x4y1.png | + | |
| - | Satellite_texture_mosaic_x0y0.png | + | |
| - | Satellite_texture_mosaic_x1y0.png | + | |
| - | Satellite_texture_mosaic_x2y0.png | + | |
| - | Satellite_texture_mosaic_x3y0.png | + | |
| - | Satellite_texture_mosaic_x4y0.png | + | |
| - | </code> | + | |
| - | Notice how the coordinates go from x0, y4 - top left to x4, y0 - bottom right. If you would use different number of mosaics, this file list would have to be changed accordingly. | + | **Satellite Mask & Texture** |
| - | Then create DOS .bat file like this: | + | Save attributes map. Paint/paste your roads and airfields etc there. Import back to L3DT and choose proper color and attributes for the ne areas. Now you can export this into texture map too. |
| - | <code dos> | + | |
| - | montage -mode concatenate -size 20480x20480 @mosaic_mask.txt Satellite_mask_lco.png | + | |
| - | montage -mode concatenate -size 20480x20480 @mosaic_texture.txt Satellite_texture_lco.png | + | |
| - | pause | + | |
| - | </code> | + | |
| - | Now just execute the .bat file and you have the mask and texture PNG's saved nicely. | + | Resizing Heightfield moved to [[tools:l3dt:heightmap-resize|Heightmap Resize]]. |
| + | |||
| + | |||
| + | ====== ImageMagick Mosaic Stitching ====== | ||
| - | Tip; if your montage run fails or gets stuck just running endlessly, reboot your computer to do fresh start, then try again and most likely it will run OK. | + | Header moved to [[tools:l3dt:mosaic-stitching-imagemagick|Mosaic Stitching ImageMagick]]. |
| ====== L3DT Mosaic Coordinates ====== | ====== L3DT Mosaic Coordinates ====== | ||
| - | L3DT Mosaic Coordinates for the image stitching are following. | + | Header moved to [[tools:l3dt:mosaic-coordinates|Mosaic Coordinates]]. |
| - | + | ||
| - | *_x0y0.png is lower left corner\\ | + | |
| - | *_x0y1.png is one up left side\\ | + | |
| - | ...\\ | + | |
| - | *_x0y4.png is top left corner | + | |
| ====== Satellite Resolution ====== | ====== Satellite Resolution ====== | ||
| - | When you are trying to save large attributes (mask) or texture (texture, doh) it only allows you to increase and decrease the values by multiply... to counter this, type your own number in the spinbox. | + | Header moved to [[tools:l3dt:satellite-resolution|Satellite Resolution]]. |
| - | + | ||
| - | When generating large mask/texture it will take a long time in L3DT, you should test all settings first in the smallest (or smaller) resolution to save time. 20480 resolution texture generation takes hours. | + | |
| ====== Large PNG Save ====== | ====== Large PNG Save ====== | ||
| - | You cannot save for example 20480 resolution image out of L3DT, you have to save it in tiled mosaic first. | + | Header moved to [[tools:l3dt:large-image-export|Large Image Export]]. |
| - | + | ||
| - | You can choose to save tiled output - with each tile as a png, in any size of grid you want. | + | |
| - | + | ||
| - | See above how to stitch together the mosaic files. | + | |
| ====== CPU Usage ====== | ====== CPU Usage ====== | ||
| - | On default settings L3DT uses all the CPU power it can get. This makes your windows sluggish and almost impossible to use. You can tweak L3DT by going Utilities -> Throttle CPU and put that to about %50 and Settings -> Multi-Thread settings, tick Core count manual override and put it at least one lower than the amount of cores you have. Like 4 core system put in 3. | + | Header moved to [[tools:l3dt:cpu-usage|CPU Usage]]. |
| - | + | ||
| - | Now your L3DT attributes and textures processing does not cause your windows to get sluggish and other programs work fine. L3DT is much **slower on processing** this way, so lets say in our computer 20480 res textures computed in 2hrs with default/full settings while on the suggested settings here its 4hrs. If you look at the times and say no thanks, consider that with full settings your windows is pretty much unusable for that 2hrs amount... | + | |
| - | ====== Attribute / Mask RGB Colors ====== | ||
| - | How to change the Attribute map / Mask image colors that are used for the land types. | + | ====== Attributes Map / Mask RGB Colors ====== |
| - | Resources -> Climates -> Climate Manager | + | Header moved to [[tools:l3dt:attributes-map-rgb-colors|Attributes Map RGB Colors]]. |
| - | Select Climate Type (I recommend copying one first and changing that) then Edit, then choose land type, edit and there you'll find the RGB's under "Display col." box. | ||
arma2/terrain/l3dt.1347408114.txt.gz · Last modified: 2012-09-12 00:01 by snakeman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
