I went to the FS Genesis store looking for mesh primarily for the US but might also be interested in all of North America.  Their pricing has me totally befuddled. Would someone let me know if the underlying mesh in the following products is somehow different?

 

Canada 19m resolution - $30

All of North America 19m resolution - $25

World - 19m resolution - $20

 

It doesn't make sense to me that the larger the area you buy the less you pay.

 

 

I think their labeling is messed up. The World package is really 76m even though the graphic says 19m (see http://www.fsgenesis.com/world-terrain-mesh-for-fsx), and then the description says the source data is actually 90m. So, it's interpolated to 76m? It's difficult to tell what you're actually getting.

 

I don't think a World 19m mesh product could be made today, source data at that resolution for the whole world doesn't exist AFAIK.

 

Somehow they made 19m mesh for Canada from 23m CDED source.  :blink:

I'm in another boat.  It seems "Justin" is no longer part of the company. I take it FSGenesis has been bought.

 

Alas they seem to have "lost" my order history.  Good thing I ordered the actual North American disks when V1.2 came out

but all the other stuff like Asia, Australia, Pacific Islands, South America, etc which I did through download I will not have

access to.  :(

 

CK

I have just used the website to reset my password and gain access to my account.

You then need to submit your previous order numbers to have them added to your account which I have just done.

Lets see how this pans out....

I'm just glad that I received all that was then available from my now defunct "Galaxy Membership" in the form of discs, as that membership is gone forever...

 

I really cannot complain however, since I did receive far more value per dollar spent than I would have spent purchasing 'piece-meal'! :Applause:

I had one of the memberships from before and wisely downloaded everything I could.  I cant make heads or tails of the new site, nothing makes sense.  My old account doesn't work, although I guess according to a previous comment I just need to contact them.  Even though the old site was pretty dated looking, it was at least easy to tell what everything was.  I think I'm going to just switch over to FSGlobal though, since I want to use FTX Vector and as far as I know, it doesn't work with FSGenesis.

I believe that FSGenesis will work with vector. However, because Vector was a joint projects between PILOTS and ORBX that FSGlobal is optimized. the newest version of FSGlobal has been optimized for Vector and FTX. 

I believe that FSGenesis will work with vector. However, because Vector was a joint projects between PILOTS and ORBX that FSGlobal is optimized. the newest version of FSGlobal has been optimized for Vector and FTX. 

 

I find that hard to believe with all the bugs reported.

I cant make heads or tails of the new site, nothing makes sense.

At least Justin had the good sense to keep the FS9 and FSX products separated and alphabetized, and not all jumbled together in seeming random order...

 

I mean, one would expect Indiana to at least be on the same page as say, Illinois and Idaho, but...

 

...apparently that would make too much sense!  :LMAO:

Well I received a reply to my support ticket at the new site.

I had sent them all of my order numbers and purchase dates.

They got back to me this morning and have added them to my new account there.

I have just been over and checked and everything is there in my download section.

You could go onto the Pilot's site and read all about their explanation of Mesh...

 

A new compiler analyses the data and sets the maximal possible Fractional Bits (max. 7) in relation to optimalen Base level. This ensures, we ALWAYS work with the maximal vertical resolution. Then the data is put together from the various sources, modified for the Base Level and handed over as a 32bit-value to the Compiler of the SDK. The worst vertical resolution in this product is just 1/8m. Only three grid squares in the Himalayas needs 14 Bits fo altitude, thus reducing vertical resolution to 0.25m. Most parts of the world can be displayed using 7 Fractional, equal a vertical resolution of 1/2^7m = 7,8mm (!). There even are mountains of 6000m altitude, which can be displayed using 5 Fractional Bits (3cm vertical resolution) because of their very high Base Level (Tibetan Plateau). AA

 

Clear as day, I think not, what a load of old tosh!!

This might make it a bit more clear (or not):

 

- We have 16 bits to play with, to represent a number range from -N.M to N.M, where N.M is elevation in meters

- The more bits we can use for M, the finer the resolution: 1/M

- As the total elevation above base gets bigger, we have to use more bits for N, so we have less bits to use for M (we only have 16 total).

 

For example, if we want to make mesh for Everest:

- The base altitude is 4200m

- The max altitude is 8848m

So we need enough bits to represent 8848 - 4200 = 4648m of elevation change, but since the numbers can be negative we need enough bits to represent 9296 different values (-4648 to 4648). To represent that many values we need 14 bits (with 13 bits we only get 8192 values, 14 bits gives us 16384, way more than we need but it's powers of 2 so that's as close as we can get).

 

That only leaves us with 2 bits to represent the fraction, which can represent 4 possible values, so M=4 and the resolution is 1/M = 1/4 = 0.25.

 

In areas where you have less elevation change, say only 200m, then you can represent that with just 9 bits (-200 to 200 is 400 values, and with 9 bits you get 512 values), so you have 7 bits left for the fraction M. 7 bits can represent 128 values, so you have 1/128 = .0078m = 7.8mm.

 

http://msdn.microsoft.com/en-us/library/cc707102.aspx#UsingScaledElevationValues

This might make it a bit more clear (or not):

 

- We have 16 bits to play with, to represent a number range from -N.M to N.M, where N.M is elevation in meters

- The more bits we can use for M, the finer the resolution: 1/M

- As the total elevation above base gets bigger, we have to use more bits for N, so we have less bits to use for M (we only have 16 total).

 

For example, if we want to make mesh for Everest:

- The base altitude is 4200m

- The max altitude is 8848m

So we need enough bits to represent 8848 - 4200 = 4648m of elevation change, but since the numbers can be negative we need enough bits to represent 9296 different values (-4648 to 4648). To represent that many values we need 14 bits (with 13 bits we only get 8192 values, 14 bits gives us 16384, way more than we need but it's powers of 2 so that's as close as we can get).

 

That only leaves us with 2 bits to represent the fraction, which can represent 4 possible values, so M=4 and the resolution is 1/M = 1/4 = 0.25.

 

In areas where you have less elevation change, say only 200m, then you can represent that with just 9 bits (-200 to 200 is 400 values, and with 9 bits you get 512 values), so you have 7 bits left for the fraction M. 7 bits can represent 128 values, so you have 1/128 = .0078m = 7.8mm.

 

http://msdn.microsoft.com/en-us/library/cc707102.aspx#UsingScaledElevationValues

 

Clear as mud Barry :lol: 

 

 

Clear as mud Barry

 

LOL, just remember that the deeper the pile of mud the lower the resolution.  :lol:

I just went to their new site. The United States section includes the state of....Cuba. :blink:  Did I miss some big news? I guess I've got to get out more often.

 

Ted

Edited February 24, 201412 yr by Ted Striker