Opened 4 years ago

Last modified 5 days ago

#12074 new defect

TWINE: rendering of the holomap is broken

Reported by: mgerhardy Owned by: mgerhardy
Priority: normal Component: Engine: TwinE
Version: Keywords:
Cc: Game: Little Big Adventure

Description


Attachments (6)

holomap-broken.png (17.2 KB ) - added by mgerhardy 4 years ago.
holomap2.png (92.3 KB ) - added by mgerhardy 4 years ago.
holomap.png (50.8 KB ) - added by mgerhardy 4 years ago.
notice-the-black-gap-holomap.png (42.9 KB ) - added by mgerhardy 4 years ago.
current-state-holomap.png (103.1 KB ) - added by mgerhardy 4 years ago.
scummvm-lba-de-00060.png (54.5 KB ) - added by mgerhardy 3 years ago.

Download all attachments as: .zip

Change History (21)

comment:1 by mgerhardy, 4 years ago

Status: A lot of stuff is reversed now - a few file formats are also known now. There are still a lot of rendering errors.

Last edited 4 years ago by mgerhardy (previous) (diff)

comment:2 by mgerhardy, 4 years ago

Summary: TWINE: holomap feature is incomplete/missingTWINE: rendering of the holomap is broken

by mgerhardy, 4 years ago

Attachment: holomap-broken.png added

by mgerhardy, 4 years ago

Attachment: holomap2.png added

by mgerhardy, 4 years ago

Attachment: holomap.png added

comment:3 by mgerhardy, 4 years ago

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

comment:4 by mgerhardy, 4 years ago

Renderer::renderPolygons still contains errors.

comment:5 by mgerhardy, 4 years ago

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).

Version 1, edited 4 years ago by mgerhardy (previous) (next) (diff)

by mgerhardy, 4 years ago

by mgerhardy, 4 years ago

Attachment: current-state-holomap.png added

comment:6 by mgerhardy, 4 years ago

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.

comment:7 by mgerhardy, 4 years ago

The gap is fixed in 34ed1dc02f604be82c178809e2e6d2ff57f2caf7 and fa09c8083080c10c9554759a6a4ea1e2936d6737

so only the position markers are left (the flickering)

comment:8 by mgerhardy, 3 years ago

Priority: normalhigh

by mgerhardy, 3 years ago

Attachment: scummvm-lba-de-00060.png added

comment:9 by mgerhardy, 3 years ago

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

comment:10 by mgerhardy, 3 years ago

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

comment:11 by lotharsm, 2 years ago

Owner: set to mgerhardy
Resolution: pending
Status: newpending

comment:12 by lotharsm, 2 years ago

Priority: highnormal

comment:13 by mgerhardy, 5 days ago

Resolution: pending
Status: pendingnew

comment:14 by mgerhardy, 5 days ago

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.

comment:15 by mgerhardy, 5 days ago

the initial delay of the holomap is fixed with f655ae5daa3708b7ced24e30a26f9f8e672ec8aa

Note: See TracTickets for help on using tickets.