TWINE: rendering of the holomap is broken

[mgerhardy]

Status: A lot of stuff is reversed now - a few file formats are also known now. There are still a lot of rendering errors and the planet surface is not yet rendered.

[mgerhardy]

The planet rendering works now - but the models that are rendered on the surface of the planet are not yet working properly.

[mgerhardy]

Renderer::renderPolygons still contains errors.

[mgerhardy]

set_holomap_trajectory 15

this doesn't render the path points - only the vehicle and the planet (every other trajectory index is affected, too of course).

give_allitems
set_holomap_flags -1

open holomap with h or via inventory menu
cycle between the locations to see the rendering errors

the planet front and back side have some vertices not properly placed

[mgerhardy]

trajectory path points are rendered now.

the holomap models that produce rendering artifacts might only do so when looking straight onto them - maybe a projection math error that extends the polygon to inf or something like that.

[mgerhardy]

The gap is fixed in 34ed1dc02f604be82c178809e2e6d2ff57f2caf7 and fa09c8083080c10c9554759a6a4ea1e2936d6737

so only the position markers are left (the flickering)

[mgerhardy]

ComputePolyMinMax performs some clipping that we are lacking in our Renderer::computePolygons implementation.

[mgerhardy]

clipping is implemented now in db4eb789e70135c22f20107c9c83e7706e135d91 - but the issue is not yet fixed.

[mgerhardy]

the initial delay on the holomap (black screen) is most likely due to the fact that the screen is just not updated as long as the location text is displayed char-by-char - only once this is done.

[mgerhardy]

the initial delay of the holomap is fixed with f655ae5daa3708b7ced24e30a26f9f8e672ec8aa