FreeMesh X Global 1.0 - Release Announcement

[AviatorMoser 353]

Hello,

Thanks for these mesh.

BUT most of the files on Mediafire cannot be processed by 7z.

These files seams corrupted, can you reload these on Mediafire?

Thanks in advance.​

 

Please see our installation tutorial.

 

http://www.avsim.com/topic/469373-freemeshx-installation-tutorial/

 

All of the files are okay.

[Emile 28]

Hello,

Thanks SOLVED I installed Torrent.

Edited November 6, 2015 by Emile

[cnarvaez 0]

Hi guys, I just want to say THANK YOU!!!   I checked the Andean mesh and the difference is outstanding!!  Here's two pics from the Andes (before & after) (P3Dv3 default mesh vs. FreeMeshX)
 
Huascarán (Peru)

 
Nevado del Huila (Colombia)

 
Once again, thanks for this awesome project!!

[AviatorMoser 353]

Hi guys, I just want to say THANK YOU!!!   I checked the Andean mesh and the difference is outstanding!!  Here's two pics from the Andes (before & after) (P3Dv3 default mesh vs. FreeMeshX)

 

 

Yes, the Andes do certainly benefit greatly. I think they were LOD6 before FreeMeshX, which gave them absolutely no justice whatsoever.

[FlyingAxx 2]

Not far away from Bogotá, south of VOR GIR you can find a pole at N 04° 0.01', W 074° 47.42. I shouldn't forget saying, it's the same with FSG including NEXT mesh.

 

Furthermore, I experienced disturbing peaks (rather cones) in the same area that in most cases disappeared when being really close. Any idea how to get rid of such effects or to smoothen them?

[AviatorMoser 353]

Not far away from Bogotá, south of VOR GIR you can find a pole at N 04° 0.01', W 074° 47.42. I shouldn't forget saying, it's the same with FSG including NEXT mesh.

 

Furthermore, I experienced disturbing peaks (rather cones) in the same area that in most cases disappeared when being really close. Any idea how to get rid of such effects or to smoothen them?

 

Thanks Axel. With the billions of elevation data points come a few bad ones. I'll see what I can do to fix them for the upcoming patch (coming soon).

[Togi 0]

Just want to say thank you from France for this awesome job (and free) !

 

And wanna share some screen of the improvement miles North-East of SBUA (Brasil), between FSX default mesh and yours =>

 

Without : http://imgur.com/86h1ejb

With : http://imgur.com/AYDeQPz

 

Without : http://imgur.com/7SgziAG

With : http://imgur.com/OefL4me

 

Without : http://imgur.com/QicyxkJ

With : http://imgur.com/esgyKvi

 

Without (from 20000 feet): http://imgur.com/EJGxvTz

With : http://imgur.com/7anVB7g

 

No bugs so far, still have to download Asia and patchs with my bad connection, keep the good work guys !

[Sbacchini 15]

It's scary how bad MS data was for South America. Thanks for the pictures Togi, and thanks again AviatorMoser for this fantastic work. You, sir, are a legend.

 

Cheers!

[AviatorMoser 353]

Patch 1.05

 

Thanks for seeding! It truly helps! The more seeders, the quicker the downloads!

 

This patch is mainly an update for the Mediterranean and Middle East area with new 1 arc-second data from NASA. This replaces many tiles and makes the older patches obsolete. Some bug fixes are also present.

 

Patch Description

In August 2015, three months after the 1.0 release of FreeMeshX Global, NASA released the last of its new 1 arc-second SRTM datasets. The new data finally updated the Mediterranean and Middle East regions with the highest resolution SRTM data available. For the FreeMeshX Global 1.0 release, a combination of LOD9 and LOD10 data was used for this region, but this approach was a bit buggy, and had to be straightened out with subsequent patches. Today, no combination of different resolution data is needed as this region is now completely LOD10.

As a result, much of the older patched terrain tiles will be replaced with full LOD10 tiles, and so it was decided to make this patch an all-in-one solution to bring FreeMeshX Global 1.0 to version 1.05. All of the previously patched data and the new patched data will be contained with this patch, so patches 1.01 - 1.04 will no longer be needed.

 

Other fixes include:

•  Fixed artifacts in NW Borneo near Gaya Island
•  Eiffel tower hump removed
•  Smooth out small artifacts near NTMU
•  Many Columbia spikes filtered out -- replaced an entire tile

The total file size of the 1.05 patch is quite large: 9.7 GB. An incremental patch was considered for existing 1.04 users, but since much of the older patches will be overwritten, an incremental patch from 1.04 to 1.05 would still be large at 7.7 GB, so it was decided to just make a cumulative merged patch instead of possibly creating confusion with a second, incremental version.

 

Installation

The installation procedure is different from the previous patches. Because there is a lot of new data in this patch, the patched data is now organized by region instead of being within a single "FreeMeshX - Patches" directory. Only miscellaneous fixes are now included in this particular folder.

Here is your installation guide for patch 1.05:

1. Inside your existing, installed "FreeMeshX - Patches/scenery" folder, delete all existing files. If you are a new FreeMeshX user and upgrading from 1.0 to 1.05, then you do not need to worry about this step.
2. Drag and drop the scenery folder from each FreeMeshX region folder from the 1.05 patch into your corresponding installed region folder. Overwrite all files. Do the same for the FreeMeshX - Patches folder.
3. You're done. That was easy.

If you're a new user, make sure you add scenery entries to your scenery library. See http://xtrnets.com/evntech/freemeshx/fmx-installation/ for a pictorial guide on that process.

 

Hypothetical relative scenery library order:

1. FreeMeshX - Patches
2. FreeMeshX - Africa
3. FreeMeshX - Antarctica
4. FreeMeshX - Asia
5. FreeMeshX - Australia and Oceania
6. FreeMeshX - Europe
7. FreeMeshX - North America
8. FreeMeshX - South and Central America

Of course, your real load order will be different, but you must keep the FreeMeshX - Patches library entry above the FreeMeshX regions.

 

I've been frequently asked on where to add these in the scenery library. The answer is: It's up to you. I would keep them before any ORBX regions and after your stock scenery. That's about all the advice we can give you since everyone's library is so different.

 

Download (9.7 GB)

 

Both BitTorrent or MediaFire download is supported. If there is active seeding by numerous seeders, the BitTorrent option is often faster, and the file integrity checks are exceptional. However, MediaFire serves great download speeds, especially if a download manager is used, which we highly recommend in order to avoid corrupted downloads and for pause/resume functionality.

 

Torrent

http://www.mediafire.com/download/9j3wi16745y1377/FreeMeshX_-_1.05_Patch.torrent

 

MediaFire Direct Download

http://www.mediafire.com/download/spnyd8smt92argj/FreeMeshX_-_1.05_Patch.7z

 

MD5SUM
9470c232145bf50bac0a426acd42670b

 

License: You may use and share this work, as long as original credit is given to the authors: Daniel Moser and David Esnouf. No commercialization of this work or derivative works is allowed.
Full license here: http://creativecommo...d/4.0/legalcode

 

Thank you once again. Enjoy.

 

-- Nine-Two Productions

 

[JLuis 409]

Thanks! For patches.

 

:wub:

[AviatorMoser 353]

I added a seedbox to help speed up the 1.05 patch torrent. Torrent speeds should increase dramatically in about an hour or two.

[Bjoern 1,157]

Didn't have a problem with d/l speed and seeded to about a 1.10 ratio afterward. Hope it helped.

[ohny 3]

Thanks a lot for the patch.

After download I realized that North America is missing.

Lost or shall we use the current one?

[AviatorMoser 353]

Thanks a lot for the patch.

After download I realized that North America is missing.

Lost or shall we use the current one?

 

Missing from the patch? Well, that's intentional because we don't have any patches for that region yet, which is a good thing! The region is unchanged from the 1.0 release.

[ohny 3]

Thanks for clarification.

This means, North America and Antarctica is unchanged - right?