Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

1

Dienstag, 10. Dezember 2013, 16:46

Possible display bug with architectural mode in 1.17?

Klaus

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.

Regards

Andrew

2

Dienstag, 10. Dezember 2013, 23:46

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

Zitat


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

release.

The reason is a very simple 'number to string' conversion
problem
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
release.

Best regards

3

Mittwoch, 11. Dezember 2013, 00:30

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.

Regards

Andrew