OK, site is back up, and in the process of migrating to a more robust, dedicated server, a bit earlier than planned or expected, but should give us a nice performance boost.

 

Thanks

 

Justin

Toposim

OK, site is back up, and in the process of migrating to a more robust, dedicated server, a bit earlier than planned or expected, but should give us a nice performance boost.

 

Thanks

 

Justin

Toposim

Congrats J!

 

Good Luck!

 

I want everyone of you guys who can afford it or close to afford it...to support Toposim and get the premier mesh that I have happily lived with for over 10 years. Justin's mesh has created many hours of Eye-candy and smiles.

 

Chas

Not entirely true.  While the source data doesn't necessarily change, the formats and structures for the new platform will have changed and the source data has to then be recompiled to take advantage of the tweaks and tuning of the new engine. 

 

For example. the transition between FS2004 and FSX . . . While FSX could read FS2004-compiled terrain mesh files, in order to enable the new Multi-LOD enhancement, the source data had to be recompiled in order to take full advantage of the new capabilities.  Conversely, FS2004 would choke on FSX-compiled BGLs because it wouldn't know what to do with the new instructions.

 

 

Thanks for the informative reply. I understand now. I didn't realize the data files had to be changed to fit the newer sim's data reading format. I assumed they were just lat-longs with an altitude, (something like 58.955568, -48.573323, 1000) and the sim took care of the rest.

 

I have Toposim Canada and like it very much. Looking forward to more...

Yes with ease ;-)

 

 

I have to disagree. 

 

We may have other issues ...but VAS would be least of our problems with 64 bit

 

I don't get why people don't understand this simple math.

 

A 64-bit register can store 2^64 different values - a really large number (16 exbibytes), 32 bit can only store 2^32 values = 4GB.