Need to Know!

[Zaggy]

Hey guys.

I need to know how to interpolate data into a Terrain Mesh, to increase the terrain resolution, like the way 250m Iceland was done.

Anyone able to help?

[87th_striker]

Hi Tilemaker gone bad... With a program like Matlab or similar... you can increase the resolution by inserting new data into the matrix.

[Zaggy]

Matlab eh? Cool... got a URL or anything?

[Zaggy]

So how hard is this Matlab to use for this? Im reading some documentation and im kinda freaking at what might need to be done!!! You guys have any equations already formatted?

[87th_striker]

It's not that hard. You need to know how much data you want inserted , and how it should relate to the data around. A simple program or so.... or just a matrix manipulation maths program. Get a demo downloaded and get going.

[Zaggy]

Cool... I will play once the DL is done... If i strike too much hassle, i guess i will ask more dumb questions...

[Zaggy]

OK here's my issue ATM. I have the Terrain, I have matlab. The terrain data is in a binary format. Wont i need to get it into a Text array for matlab? Ive tried to export the terrain data as ASCII text from one GIS reader (3DEM), but the file size got to 144Mb before i cancelled it.

Is this the way you did it?? Convert the data to text, then MatLab it? or have i missed something?

[87th_striker]

I seem to remember that Matlab can read the binary file directly.

[Zaggy]

Yeah??? Cool... Will try that!! Thanx man!

[orion]

Zaggy,

this is really interesting topic and I wonder if you made any progress on increasing the terrain resolution?

did you try manually editing the L1 and L0 files, where the resolution doubles for each file.

orion

[Zaggy]

Im now actually messing with SRTM Data to create Pre-Interpolated meshes at 92.7m res (1/20th Nm)... Then the mesh will feature some software interolation to get us up near 1/40Nm res or maybe more... This isnt for F4 tho, unless BMS re-write the terrain engine to allow for greater detail terrain meshes as well as allowing textures to cover more than on cell within the terrain mesh matrix.
www.nightbomber.com

[Zaggy]

If they did, Id be more than happy to help sort out a replacement terrain mesh at higher res's... Like 100m...

[kinggeorge]

afaik Matlab uses the binary read only for its own m matrix storage binaries... but you can use the filescan function from c in matlab also - it's just a little trickier. Unless matlab can read those falcon binaries it's eeven better is to write a small proggie in C that converts the elevation data in a ASCII matrix file... Then import it in matlab and interpolate around There are different interpolation mechanism in matlab build in by the way... (linear, cubic and another one..)

[Com_gp]

Hi,

Just want to let you know that im working for Falcon capable of admiting more levels of terrain, not only 6, i mean, not only L0,L1,L2,L3,L4,L5 so this way we can have much better resolution, instead 250 meters... without having small tiles like Iceland.

Com_GP

[kinggeorge]

you mean better terrain texture resolution without better elevation points resolution?

If so that doesnt make sense at all imo

[Com_gp]

quote:Originally posted by kinggeorge:
you mean better terrain texture resolution without better elevation points resolution?

Mmmmmmh, no..., I mean more elevation points with same texture resolution, for example using L3 as 1km resolution tiles and getting at L0 125m, this would require 7 levels of terrain instead the actual 6.

Com_GP

[kinggeorge]

ah i understand

Whats the differece in keeping the number of LODS but increasing the near LOD resolutions except slightly smoother transitions between LODs?

[Zaggy]

But the problem with F4 is still the one tile per evelvation point deal... If we could increase the density of the elevation data and STILL apply the textures unaltered, at 1Km res, it wouldnt be that hard that improve the terrains.... we just create SRTM terrains, resolution at 100m, and replace the Mesh... in the most part, we'd be done!

[Zaggy]

We need BMS or G2i to address that...

In order of necessity, what would the major issues in Terrain be, if either BMS or G2i could address them?

Like would increasing the elevation mesh density, while retaining the 1Km texture size be at the top of the list or not? Or would larger theaters be more important?

[Com_gp]

quote:Originally posted by Zaggy:
But the problem with F4 is still the one tile per evelvation point deal... If we could increase the density of the elevation data and STILL apply the textures unaltered, at 1Km res, it wouldnt be that hard that improve the terrains.... we just create SRTM terrains, resolution at 100m, and replace the Mesh... in the most part, we'd be done!

Buff... Actually Im working on that, using L3 as LastNearTexturedLod but using L2 for it would make L0 to have texture resolution points of 125m... this would require 7 levels...

The best way to explain i think is like this...
imagine the actual terrain engine L0, L1, L2, L3, L4 and L5 and then you could add a L(-1), that L(-1) would be 125m, well, im trying to do that, but instead calling it L(-1) just callin it L0 and adding 1 to the rest of levels (L0 would become L1, L1 would become L2,...)

I hope you finally understand

Com_GP

[kinggeorge]

understood that 7 LODS would retain the structure compatibility versus 6 LODS with different distances...

About the textures Zaggy - if you lay a 1kmx1km over a mesh that is not planar then you need to stretch it and it hasn't the original resolution fidelity...

[Zaggy]

Com GP... Nope! No idea what u are talking about!!

Make some pictures! That'll help me!