1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
//
// Copyright (c) 2009-2010 Mikko Mononen memon@inside.org
//
// This software is provided 'as-is', without any express or implied
// warranty. In no event will the authors be held liable for any damages
// arising from the use of this software.
// Permission is granted to anyone to use this software for any purpose,
// including commercial applications, and to alter it and redistribute it
// freely, subject to the following restrictions:
// 1. The origin of this software must not be misrepresented; you must not
// claim that you wrote the original software. If you use this software
// in a product, an acknowledgment in the product documentation would be
// appreciated but is not required.
// 2. Altered source versions must be plainly marked as such, and must not be
// misrepresented as being the original software.
// 3. This notice may not be removed or altered from any source distribution.
//
// Ported to Rust and altered for DayZ (see the dayzmake navmesh spec); this is not the original software.
//
//! The server's walkability test (spec 5.2).
/// `1 / sqrt(d)` as the game computes it: the x86 `RSQRTSS` approximation (a relative error of about
/// `1.5 * 2^-12`) where SSE is in the build's baseline, which includes every `x86_64` target. On other
/// targets an exact `1.0 / d.sqrt()` is used, so slope classification there can differ from DayZ's.
/// `1 / sqrt(d)` as the game computes it; see the x86 variant. This target has no `RSQRTSS`, so the
/// result is exact and can differ from DayZ's in the low bits.
/// Whether the triangle `(v0, v1, v2)` as the server sends it is walkable: its normal
/// `cross(v2 - v0, v1 - v0)`, normalised with one Newton step after `RSQRTSS`, has a `y` above
/// `slope_threshold`. On targets without `RSQRTSS` the result can differ from DayZ's. The caller passes `(v0, v2, v1)` to the rasteriser.