Hmmm, i see... i just went with a small test days ago... i've created just a small terrain has a test (around 1280 m2 i think - using area size and heightmap resolution of 128), with just a few objects on it, and using just 2 or 3 textures. I've got a package around 30MB i think... so i've extended that same terrain to about 3968 m2 (using area size and heightmap resolution of 128), and i'm using the same objects and textures as in the first example. After this the game package has now about 120MB... so i assumed that a large terrain will occupy too much space for the mobile platforms.
That's why i assumed 1 meter for me is 1/100 of Esenthel unit (1m), and all objects use this scale also, of course. With this, and with the same terrain i mentioned above, i get a terrain with 396,8km2.
But i'll make some more tests (and searches on the forum) regarding the terrain size and how the size of the package is related with it.
Thanks!
In a fast search on the forum i found this, also about a flight sim, and Esenthel suggested also to use own scale (1/100 he suggested as example also) :\
http://www.esenthel.com/community/showth...in+size%22
This may suggest that a big terrain will have some drawbacks... maybe it's disk space usage...