- image.png (276.12 KiB) Viewed 7040 times
In their close surrounding, you can’t hit the ground and can’t crash into the sea.
EF2000, in contrast to F22, does not provide collision data for the sea – sea tiles have no collision triangles in their SSD at all. TFXplorer detects that and, for these tiles, provides a hard-coded quad to crash into.
It seems like this is not triggered here because the icebergs do provide some collision triangles (for the icebergs), so TFXplorer does not create the dummy for the sea.
We may have to create that dummy quad in every tile, regardless of the presence of other collision triangles, which I would like to avoid due to the performance implications. (Mind that collisions are currently terribly slow.)