Inconsistent procedural terrain

[Kurt-Dekker]

@randomUsrname

However, the perlin noise is inconsistent, and it slightly changes when it is updated with new player position values. Any fixes for this?

Don’t use the player position as input if it is going to be different.

OR… use a reduced-accuracy version of the player position, such as one rounded off to a lower level of accuracy.

Perlin noise will give the same numeric output for a given input pair. Your job is to make that input pair consistent. If you truly care about accuracy, your computations should probably be in integer space, then downscaled all at once right before feeding into the Perlin function. Here’s why:

Floating (float) point imprecision:

Never test floating point (float) quantities for equality / inequality. Here’s why:

https://starmanta.gitbooks.io/unitytipsredux/content/floating-point.html

Debug.Log(2000.0f * 000.1f); is 200

Now that you have had your coffee, don’t forget about floating point imprecision: // @kurtdekker: don't forget about floating point imprecision using UnityEngine; public class FloatingPointImprecision : MonoBehaviour { void Start () { float a = 2000.0f; float b = 0.1f; float product = (a * b); float answer = 200; Debug.Log( "a = " + a); Debug.Log( "b = " + b); Debug.Log( "product of a*b = " + product); Debug.Log( "answer =…

Why Doesn't This Code Work?

This will explain it all. In an IEEE single-floating point number you can represent certain numbers perfectly and unambiguously. For instance, 0.5f is precisely represented as 0x3f000000 However, 0.1f CANNOT be precisely represented. One possible approximate representation is 0x3DCCCCCD The analogy is that you cannot show 1/3rd precisely as a decimal. 0.33 is correct to 2 decimal places 0.3333 is correct to 4 places etc. But you can never exactly represent 1/3rd as a decimal numeral. Yo…

“Think of [floating point] as JPEG of numbers.” - orionsyndrome on the Unity3D Forums