Skip to content

Tile levels incorrectly numbered #482

@josefbry

Description

@josefbry

Hello,

I noticed a mismatch between the tile folder structure and the level numbering generated in data.js.

Problem
The exported panorama tiles use level numbering:
1/
2/
3/
4/

But the generated Marzipano configuration (data.js and index.js) references levels:
0/
1/
2/
3/

So Marzipano tries to load:
.../0/l/0/0.jpg

but the actual downloaded directory is:
.../1/l/0/0.jpg

Symptoms
The tour loads with a black screen (no tiles shown). Manual inspection confirms that tile level “0” does not exist, only 1–4.

Expected behaviour
Tile levels should match those defined in the exported Marzipano configuration — traditionally 0 is the lowest-resolution level.

Consequences
The tour cannot load any image tiles unless:
the user renames folders manually, or the user edits data.js and index.js manually to match the actual folder names

Questions
Is this numbering shift intentional (1–4 instead of 0–3)?
If yes, why does the generated Marzipano config still use 0–3?
If no, then it seems like a bug in tile level generation.

Environment
Windows 11
Latest version of the exporter

Thank you — this seems like a small but critical inconsistency that prevents the tour from loading.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions