Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[montify]

Hello.
I love Outerra

But my question is: How you handle float precision in the "Terrain System".

You use double instead float?


And do you use Chunked-LOD for the Terrain?

please answer me

best regards from your neighbor (Austria)

[cameni]

No, doubles are slow on GPUs and take unnecessarily more memory. We are using the switching to local coordinate reference systems.
Initially the planet geometry is rendered with 0,0,0 in the planet's center. Once the precision is not enough (from a certain quad-tree level), all sub-tile geometry is referenced from the center of the tile where the switch happens.

Btw there's a good book that talks about the ways that can be used to deal with the precision problems (among other stuff): 3D Engine Design for Virtual Globes
Some info & code about it is also here: http://blog.virtualglobebook.com/2010/11/vertex-transform-precision.html

Yes we are using a system similar to the Chunked LOD, though we didn't know it was named so when we created it

[montify]

Thank your for reply.

And many thanks for the Links!

here is my try:



very basic and 0,0001% done

[cameni]

Everybody has to start somewhere
Good luck!

[montify]

Thank you!

Outerra is my motivation to work every day hard on it

[montify]

Here you see the float precision...NOT

The white dot's

[PytonPago]

Looks nice tho ... 

[Edding3000]

Seems a stitching problem, not FP precision.

[montify]

In this Screenshot stitching is not implemented, but i implemented now and seems like in the screenshot.


Here you se without Normals a closer look to the border of 2 Chunks ( same LOD level)


Think the inaccuracy are from the PerlinNoise Heightmap... hm