Limits of images dimensions for crop animation, version 1.20.6

  • This is a project made first in swf in 2011.

    Then I update it for html5 with version krpano 1.18 and everithing was working, on desktop, tablet and mobile.
    To make the movement of the objects it use a “crop animation”, single column cycling process.

    With the first version,http:// https://www.studioargento.com/test1</a> the images that were processed were made with only one columm, with this dimensions:


    sphere (objects/sfera.png) = 90 x 10.800 px
    cube (objects/cubo.png) = 202 x 24.240 px
    equi (objects/quadro.jpg) = 170 x 12.000 px
    cross (objects/croce.png) = 90 x 14.400 px

    everything ok, desktop, tablet, mobile.


    Then I updated to version 1.20.6 see https://www.studioargento.com/test2
    same xml, it works for all images below 15.500 px length (I made several tests):
    on desktop all ok, except for cube that is > 15.000 px
    tablet and mobile are not working at all.
    And there are strange issues on dragging the pano, as there is an invisible hotspot...


    Then with version 1.20.6 see https://www.studioargento.com/test3 I updated the cycling process using a multi-column one (do crop animation, https://krpano.com/viewsource.htm…anihotspots.xml )
    so to reduce the lenght of the images that are now :

    sphere = 600 x 4500 px (4 columns)
    cube = 808 x 6060 px (4 columns)
    equi = 1020 x 8000 px (3 columns)
    cross = 720 x 7200 px (4 columns)

    desktop is ok for all, tablet and mobile not.
    (Same strange behavior as it have a hidden hotspot)

    So, what are the dimensions limits to import images with new Krpano version?
    (I notice that 1.19 version too had same problem…)

    Thanks, Toni

  • Hi,

    the limits for hotspot images is the maximum supported texture size of the device.

    On desktop typically 8192x8192 to 16384x16384,
    on mobiles typically 4096x4096, except for a few older and lower-end ones, there just 2048x2048.

    For version 1.20.7 and I have already implemented a kind of 'workaround' for that case - when larger than the maximum supported texture size, the image first will be automatically downscaled before uploading to the GPU as texture. Only the width or the height that exceeds the limit will be downscaled, that means no proportional scaling to keep as many pixels as possible.

    For further usage (displaying, crop-coordinates and so) that downscaling will not make any difference, that's fully internal inside krpano. The only disadvantages are that the downscaling needs some processing time and that the image will be less sharp of course.

    When such downscaling happens there will be a warning in the krpano log.

    And for custom control there will be also a 'device.maxtexturesize' variable for e.g. manually using/loading a lower-res version of the image when necessary.

    Best regards,
    Klaus

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!