Differences

This shows you the differences between two versions of the page.

--- arma3:exportnogrid [2021/08/11 12:32] – created initial page. snakeman
+++ arma3:exportnogrid [2024/08/03 11:59] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
 ====== ArmA 3 ExportNoGrid ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=68|ArmA 3 Forum]], [[:arma3|ArmA 3]], [[arma3:config|ArmA 3 Config]], [[arma3:missions|ArmA 3 Missions]], [[arma3:modeling|ArmA 3 3D Modeling]], [[arma3:scripting|ArmA 3 Scripting]], [[arma3:terrain|ArmA 3 Terrain]], [[arma3:texturing|ArmA 3 Texturing]], [[arma3:tools|ArmA 3 Tools]]
 **2021-08-10**
@@ Line 19: / Line 21: @@
 {{ https://pmc.editing.wiki/images/ArmA-3-ExportNoGrid-Tanoa.png }}
+====== Large Terrains ======
+Unfortunately exportnogrid is not very viable method for large terrains. ArmA 3 will export EMF just fine and rather quickly too, EmfToPng will painstakingly slowly convert it to PNG no problems there either... but imagine what use PNG of 40,960 x 40,960 resolution is for you as that is how large export you get from 40km terrain.
+meter is 1 pixel, 40km terrain is 40,960 meters which is 40,960 x 40,960 pixel resolution image.
+What if your terrain is even larger, 81km? 102km? or like some PMC and VTE terrains 143km, not to mention the special cases which are 204km or over...
+There is no way to handle images of that size.
+GIMP can load 40,960 resolution PNGs and convert them to 8192 just fine, so you aren't totally out of options, it just means manual work in GIMP. I don't believe GIMP is taking 81920 resolution images very well, I've heard photoshop will read even 102,400 resolution images if you have crazy amount of RAM, but... that is so insane image size that its just not suitable to work with those kind of sizes.
+With huge terrains you're better of going to mission editor and take one screenshot there and call it a day :)