arma3:terrain:satellite-image-resolution-size-explained
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
arma3:terrain:satellite-image-resolution-size-explained [2017-10-25 03:22] snakeman added note about opteryx. |
arma3:terrain:satellite-image-resolution-size-explained [2020-05-16 10:36] (current) snakeman updated for 2020 latest high tech info. |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Satellite Image Resolution Size Explained ====== | ====== Satellite Image Resolution Size Explained ====== | ||
| + | |||
| + | **2020-05-16 Update** | ||
| **Why is my terrain's satellite texture very low quality!?** frequently asked question - answered! | **Why is my terrain's satellite texture very low quality!?** frequently asked question - answered! | ||
| - | Anybody who has computer hardware to run ArmA 2 / ArmA 3 can edit about 20480 x 20480 resolution satellite images in photoshop or gimp. This resolution is enough to do decent enough 40km x 40km terrains. | + | Anybody who has computer hardware to run ArmA 2 / ArmA 3 can edit about 20480 x 20480 resolution satellite images in photoshop or gimp. This resolution is enough to do decent enough 40km x 40km terrains, but you are recommended to use higher resolution (read below). |
| - | Satellite texture resolution is not an really issue, unless you are creating a huge terrain, perhaps above 50km. | + | Satellite texture/mask resolution is not an really issue, unless you are creating a huge terrain, perhaps above 50km, then you need to split satellite into 2 x 2, 4 x 4 etc tiles (read below). |
| - | This page is about **satellite texture / mask image resolutions**, if you are looking for **terrain sizes** then please refer to [[arma3:terrain:grid-cell-size|Terrain Grid and Cell Sizes]]. | + | This page is about **satellite texture/mask image resolutions**, if you are looking for **terrain sizes** then please refer to [[arma3:terrain:grid-cell-size|Terrain Grid and Cell Sizes]]. |
| Line 20: | Line 22: | ||
| | 15 | 15360 | | | 15 | 15360 | | ||
| | 20 | 20480 | | | 20 | 20480 | | ||
| - | | 40+ | 40960 | | + | | 40 | 40960 | |
| + | | 81| 81920 | | ||
| - | Of course you can go higher than 40960 res but good luck running your photoshop / gimp with such resolutions :) | + | Once you go well over 20480 resolution image size you need to split it up to smaller tiles and [[arma3:terrain:import-satellite-in-smaller-tiles|import satellite texture / mask as tiles]]. |
| Line 30: | Line 33: | ||
| When you start to increase that ratio, you stretch that texture over to wider area, 2, 5, 10 or whatever the ratio would be and then you get lower and lower quality the further you stretch pixel above terrain meters. | When you start to increase that ratio, you stretch that texture over to wider area, 2, 5, 10 or whatever the ratio would be and then you get lower and lower quality the further you stretch pixel above terrain meters. | ||
| + | |||
| + | There is really no reason to use low quality meters per pixel scale, use one that is a good high quality scale. | ||
| ^ Meter / Pixel ^ Quality ^ | ^ Meter / Pixel ^ Quality ^ | ||
| Line 36: | Line 41: | ||
| | 2 | Good | | | 2 | Good | | ||
| | 3-5 | Okay | | | 3-5 | Okay | | ||
| - | | 5-20 | Low | | + | | 5-10 | Low | |
| - | | 20+ | Very low, dont use | | + | | 10+ | Very low, don't use | |
| - | It is up to you to decide what ratio to use, what quality do you want. One fact that does not depend on personal opinion about quality is large terrain size, for example 1 meter / pixel ratio with 40960 resolution image means you can do //only// 40km sized terrain. | + | It is up to you to decide what ratio to use, what quality do you want. |
| - | Now some might already run away scared when we talk about 40960 resolution images and many think even 20km is too large terrain. But that has nothing to do with the fact that the larger your terrain, the closer you are to photoshop editing limits like the mentioned 40960 resolution. | + | Now some might already run away scared when we talk about 40960 resolution images and many think even 20km is too large terrain. But that has nothing to do with the fact that the larger your terrain, the closer you are to photoshop / gimp editing limits like the mentioned 40960 resolution //for single images with limited RAM//. |
| Line 76: | Line 81: | ||
| | 60 | 2 | 30720 | | | 60 | 2 | 30720 | | ||
| - | Miro (the bis dev who made Take On Helicopters South Asia terrain) said that TOH South Asia satellite was 61,000 resolution and it worked fine. | ||
| - | When we (PMC + some guys in arma2 community) did experiment with 40960 satellite texture resolutions, it was borderline doable with photoshop (no idea about gimp, if someone has info please let us know), but even then saving took several minutes while photoshop swapped to the disk like a crazy. This was with 16gb ram on win 7 64bit. | + | ====== Huge Satellite Texture Sizes ====== |
| + | |||
| + | Miro (the bis dev who made Take On Helicopters South Asia terrain) said that TOH South Asia satellite was 61,000 x 61,000 resolution and it worked fine. | ||
| + | |||
| + | In 2018 the arma(1) terrain / object making legend Opteryx, have 64gb ram in his monster computer and he used photoshop to edit 102,400 x 102,400 resolution image. He attempted to edit 150,000 resolution image as well but without extensive SSD hardware support it was borderline unusable. | ||
| + | |||
| + | In 2010s when we (PMC + some guys in arma2 community) did experiment with 40960 satellite texture resolutions, it was borderline doable with photoshop (we didn't use gimp back then), but even then saving took several minutes while photoshop swapped to the disk like a crazy. This was with 16gb ram on win 7 64bit. | ||
| + | |||
| + | Now with terrain builder we can [[arma3:terrain:import-satellite-in-smaller-tiles|import satellite texture / mask as tiles]] which eases the load while compiling our WRP (back in arma2 visitor3 we had no such option). | ||
| + | |||
| + | PMC terrains use 1 or 2 meter per pixel scale pretty much on all terrains (if some leftovers are using larger those will be upgraded in the future). Our older 143km terrains use 2m/px but the newer terrains use strictly 1m/px for example PMC Suwalki Gap is 81km with 81,920 x 81,920 resolution satellite and the mega monster PMC Iran Jahrom is 163,840 x 163,840 res and the craziest terrain of all PMC Mongolia uses 204,800 x 204,800 resolution satellite (yes, it was not a typo, it really is 204k res). | ||
| - | Now with terrain builder we can [[arma3:terrain:import-satellite-in-smaller-tiles|import satellite texture / mask as tiles]] which eases the load while compiling our WRP (back in arma2 visitor3 we had no such option). So one could think that using larger resolution satellite images (than mentioned 40960) is now possible... | + | PMC terrains in general for 40km size use 2 x 2 tiles, above that its 4 x 4 tiles and some of these special mega monster experiments use 8 x 8 and even 16 x 16 tiles (I believe PMC Mongolia uses 16x16 tiles). |
| - | Also in late 2017 the arma(1) terrain / object making legend Opteryx, have 64gb ram in his monster computer and he used photoshop to load 71,680 x 71,680 resolution image there and he still had RAM to spare. | + | Terrain Builder's ability to load satellite as tiles is awesome, please use it to your advantage on larger terrains. No longer you are limited to what photoshop and gimp can load, just edit the satellite in smaller tiles. |
| - | So the bottom line is, your computers **RAM** dictates what size of single image satellite texture / mask you can do, this limit is removed if you split satellite into smaller image tiles. | + | So the bottom line is, your computers **RAM** dictates what size of single image satellite texture / mask you can do, this limit is removed if you split satellite into smaller image tiles. Use only 1 meter per pixel scale and you're fine. |
arma3/terrain/satellite-image-resolution-size-explained.txt · Last modified: 2020-05-16 10:36 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
