You are not logged in.

Dear visitor, welcome to Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.


Tuesday, December 10th 2013, 4:46pm

Possible display bug with architectural mode in 1.17?


I've been playing with the prerelease of 1.17, not for very high resolution panos but with an input file of only 8192 x 4096, simply to allow a sharper result when zoomed in.

I have the following line in my .xml file -

<view architectural="0.7" hlookat="0" vlookat="-6" fovtype="DFOV" fov="105" fovmin="60" fovmax="105" limitview="auto" />

Viewing the pano on my iPad Mini, if I zoom in and drag to display the zenith I get a misplaced tile appearing, aligned to the top left of the window, rather than at its correct position. Scroll back away from the zenith and the tile disappears.

If I remove the architectural mode everything displays correctly. Also, everything seems OK in Safari on my MacBook, with or without the architectural mode.





Posts: 38

Location: Trento - Italy

  • Send private message


Tuesday, December 10th 2013, 11:46pm

Replaing a very similar question a cuple of day ago Klaus wrote to me


I'm currently not able to reproduce the problem now with your pano,
I know about that problem and it was already fixed for the next 1.17


The reason is a very simple 'number to string' conversion
related to the css3d transforms. The css3d transforms require the

transformation values in a normal numeric format like '123.45679', but

Javascript sometimes write the numbers in a exponential-notation like

'1.23457e3' and this lets the css3d rendering fail. All other css3d

values will be already automatically corrected by krpano, but only the

ones for architectural projection were missed in the previous 1.17

Best regards


Wednesday, December 11th 2013, 12:30am

Grazie Matteo. I'm glad to hear that Klaus is already aware of the problem and has fixed it for the release version of 1.17.

Apart from this little glitch, multiresolution seems to work very well on iPads, so I'm really looking forward to its release.